TargetArchitecture_Match.xlsx

How the model read it

Current gold observes the qualified column `Account.AccountKey` as Int64, matching the requested column kind and data type.

How the model read it

Current gold observes the qualified column `Account.AccountName` as String, matching the requested column kind and data type.

How the model read it

Current gold observes the qualified column `Account.AccountType` as String. The object is directly covered, although the authoritative wording limits the definition to revenue/expense while representative rows also show Asset, Liability and Equity values.

Should the AccountType business definition and permitted domain explicitly include Asset, Liability and Equity as shown by the representative chart of accounts?

How the model read it

Current gold observes the qualified column `Calendar.Date` as DateTime, matching the requested column kind and data type.

How the model read it

Current gold observes the qualified column `Calendar.FiscalMonth` as Int64. The July-start prototype supports intended semantics. Current gold reports that the column summarises by Sum, which is a configuration review item rather than an absent-object gap.

Should `Calendar.FiscalMonth` be changed from Summarise by Sum to Summarise by None?

Confirm that the current model uses July as fiscal month 1, as illustrated by the workbook formulas.

How the model read it

Current gold observes `Ledger.DateKey` as Int64 and an active many-to-one relationship to `Calendar.DateKey`, consistent with the requested posting-date foreign key.

How the model read it

Current gold observes `Ledger.AccountKey` as Int64 and an active many-to-one relationship to `Account.AccountKey`, consistent with the requested account foreign key.

How the model read it

Current gold observes the qualified column `Ledger.SignedAmount` as Decimal. The prototype provides reporting-sign context, but value-level currency and sign conformance were not established by the bounded evidence.

Confirm that the current column is consistently expressed in the required reporting currency and reporting-sign convention.

How the model read it

Current gold observes the qualified column `Ledger.IsAdjustment` as Boolean, matching the requested column kind and data type.

Confirm the operational rule used to classify late or manual postings as adjustments; the object and type are observed but value-level business logic is not.

How the model read it

Current gold observes the qualified measure `Metrics.Actual Net` with currency formatting, satisfying the declared measure object. Exact DAX was not returned, so equivalence to the stated revenue-plus-signed-expenses logic remains a validation question.

Does the production DAX implement Actual Revenue plus signed expense balances with the intended account classification and filter context?

How the model read it

Current gold observes the qualified measure `Metrics.Actual Revenue` with currency formatting. The workbook prototype illustrates revenue selection, but exact production DAX and business semantics were not available in current gold.

What production account-classification rule should Actual Revenue use, and does the current DAX implement it?

How the model read it

Current gold observes the qualified measure `Metrics.Budget Net` with currency formatting. The workbook does not declare authoritative budget fact objects or a detailed budget calculation, and current gold did not expose the exact measure DAX.

What is the production budget source and grain, and does the current Budget Net DAX implement the intended budget revenue-plus-expenses logic?

How the model read it

Current gold observes the qualified measure `Metrics.Net Variance` with currency formatting. The declared logic is Actual Net minus Budget Net, but exact DAX was not returned for equivalence checking.

Confirm that current DAX is `Actual Net - Budget Net` and that favourable-positive sign behaviour is preserved across report contexts.

How the model read it

Current gold observes the qualified column `Calendar.DateKey` as Int64, matching the requested column kind and data type.

Confirm that current DateKey values follow the requested YYYYMMDD encoding; current gold establishes the object and type but not value-level conformance.