# Workbook-to-current-gold assessment

## Executive conclusion

This workbook appears to specify a **new customer and booked-sales-order analytics subject area** for FY2026–FY2027. It requires customer identity, segmentation and relationship ownership; sales-order identity, gross value and acquisition channel; and two commercial measures: Customer Lifetime Value and Gross Order Intake.

The workbook explicitly designates `Target Fields` as its authoritative register (`Read Me`!B8). That register contains eight rows and marks every row required (`Target Fields`!F2:F9). None of the eight declared objects was found in the available current-gold model.

The current-gold landscape instead describes a small finance ledger model with `Account`, `Calendar`, `Ledger` and `Metrics` as its business-facing tables. Its observed measures are `Actual Net`, `Actual Revenue`, `Budget Net` and `Net Variance`; its observed amount is `Ledger.SignedAmount`. There are no observed Customer, SalesOrder or SalesMetrics objects [fde-finance.current-model]. The separate journal-controls page concerns two finance-ledger attributes and does not supply customer/order coverage [fde-finance.journal-controls].

**Authoritative coverage:** **0/8 mapped**; **8/8 not found** in the available discovered landscape.

## Interpreted business and data requirements

The authoritative register implies two principal business entities and a calculation layer:

- **Customer**, at customer-level grain, with enterprise identity, commercial segment and accountable relationship owner (`Target Fields`!A2:I4; corroborated by `Customer Sample`!A1:C3).
- **SalesOrder**, at representative booked-order grain, with order identity, gross value before discounts and sales channel (`Target Fields`!A5:I7; corroborated by `Sales Orders`!A1:D3).
- **SalesMetrics**, containing Customer Lifetime Value and Gross Order Intake (`Target Fields`!A8:I9; corroborated by `Sales KPI Prototype`!A3:C5 and formulas B4:B5).

The sample order sheet also contains `CustomerIdentifier` on each order (`Sales Orders`!B3:B15), implying a customer-to-order linkage. However, that order-side field is not declared as its own row in the authoritative register, so it is treated as design context rather than a ninth authoritative requirement.

The hidden reference sheet supplies candidate controlled domains for CustomerSegment and SalesChannel (`Reference Data`!A2:C7). These are design semantics, not proof of implemented validation or a production reference-data solution.

## Authoritative mapping results

| ID | Required object | Workbook evidence | Result | Current-gold assessment |
|---|---|---|---|---|
| TF-01 | `Customer.CustomerIdentifier` | `Target Fields`!A2:J2 | Not found | No Customer table or customer identifier was observed [fde-finance.current-model]. |
| TF-02 | `Customer.CustomerSegment` | `Target Fields`!A3:J3 | Not found | No Customer table or commercial-segment attribute was observed [fde-finance.current-model]. |
| TF-03 | `Customer.RelationshipOwner` | `Target Fields`!A4:J4 | Not found | No Customer table or relationship-owner attribute was observed [fde-finance.current-model]. |
| TF-04 | `SalesOrder.OrderIdentifier` | `Target Fields`!A5:J5 | Not found | No SalesOrder table or order identifier was observed [fde-finance.current-model]. |
| TF-05 | `SalesOrder.OrderGrossValue` | `Target Fields`!A6:J6 | Not found | `Ledger.SignedAmount` is a finance-ledger amount, not evidence of gross order value before discounts; no SalesOrder amount was observed [fde-finance.current-model]. |
| TF-06 | `SalesOrder.SalesChannel` | `Target Fields`!A7:J7 | Not found | No SalesOrder table or acquisition-channel attribute was observed [fde-finance.current-model]. |
| TF-07 | `SalesMetrics.Customer Lifetime Value` | `Target Fields`!A8:J8 | Not found | The current `Metrics` table contains only four named finance measures. A generic measure table does not establish this commercial measure [fde-finance.current-model]. |
| TF-08 | `SalesMetrics.Gross Order Intake` | `Target Fields`!A9:J9 | Not found | No measure with this name or booked-order semantics was observed. `Actual Revenue` and other finance measures cannot be treated as equivalents because their exact DAX and business semantics are unknown [fde-finance.current-model]. |

## Calculation interpretation

- **Gross Order Intake** is declared as the sum of `OrderGrossValue` (`Target Fields`!H9), and the prototype stores `=SUM('Sales Orders'!C4:C15)` (`Sales KPI Prototype`!B4). This is evidence of intended stored logic, not proof of successful recalculation, current cached results or production-ready semantics.
- **Customer Lifetime Value** is described as average gross order value multiplied by expected order frequency (`Target Fields`!H8). The prototype stores `=B4/COUNTA('Customer Sample'!A4:A11)*3.2` (`Sales KPI Prototype`!B5). The multiplier 3.2 is explicitly illustrative for discovery (`Sales KPI Prototype`!C5), so the production frequency basis, time horizon, cohorts and treatment of discounts, cancellations and returns remain undefined.

## Contextual design observations

1. **Customer-order relationship:** The order sample places `CustomerIdentifier` on orders (`Sales Orders`!B3:B15), but the authoritative register does not request `SalesOrder.CustomerIdentifier` or explicitly declare a relationship. A production semantic model will require a documented customer/order key and cardinality.
2. **Controlled values:** The workbook proposes CustomerSegment values Enterprise, Mid-market and Small business, and SalesChannel values Direct, Partner and Online (`Reference Data`!A2:C7). No workbook data-validation rule was found, so these are reference examples rather than enforced constraints.
3. **Planned sources:** Customer fields point to a CRM customer master, order fields to an order-management platform, and measures to a sales analytics calculation layer (`Target Fields`!I2:I9). The workbook contains no connections, queries or external links, so source accessibility and integration status are not evidenced.
4. **Current-model mismatch:** The available gold model is finance-ledger oriented, while this workbook requests customer/order analytics [fde-finance.current-model]. This may represent a genuine greenfield gap, a different subject-area model, or selection of a current model that was not intended to satisfy this request.

## Consultant guidance

The supplied consultant-guidance object contained no workbook-level or sheet-level comments. Consequently, no steering note changed the interpretation; the workbook's own explicit authority statement determined the denominator.

## Recommended decisions and next steps

1. Confirm whether the audited finance model is actually the intended destination for this customer/order subject area, or whether another semantic model/workspace should be discovered.
2. Add or explicitly reject `SalesOrder.CustomerIdentifier` in the authoritative register and document the customer-to-order relationship, key uniqueness and handling of unmatched customers.
3. Define production semantics for Gross Order Intake: booked-status event, booking date, cancellations, returns, discounts, tax, currency conversion and late changes.
4. Define production semantics for Customer Lifetime Value: forecast horizon, order-frequency method, customer cohort, margin versus gross value, churn assumptions and refresh cadence.
5. Confirm source contracts and ownership for the CRM customer master, order-management platform and calculation layer.
6. Re-run discovery against the intended sales/customer model or source estate before concluding that the objects are enterprise-wide gaps.