Review · TargetArchitecture

Finding 1 of 13

Direct match 99%

Account.AccountKey column

The authoritative register requires an Int64 Account.AccountKey stable identifier. Current gold observes the exact table, column name and data type.

Workbook evidence

Target Fields!A2:J2

Cited current gold

fde-finance.current-model

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 2 of 13

Direct match 99%

Account.AccountName column

The authoritative register requires a String Account.AccountName. Current gold observes the exact table, column name and data type.

Workbook evidence

Target Fields!A3:J3

Cited current gold

fde-finance.current-model

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 3 of 13

Direct match 98%

Account.AccountType column

Current gold observes the exact String Account.AccountType column. Structural coverage is direct, although the register definition mentions revenue/expense while the fictional examples also include asset, liability and equity values.

Workbook evidence

Target Fields!A4:J4 Chart of Accounts!C3:C13

Cited current gold

fde-finance.current-model

Should AccountType cover the full balance-sheet and P&L domain (Asset, Liability, Equity, Revenue, Expense), rather than only the register's stated revenue-or-expense classification?

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 4 of 13

Direct match 97%

Calendar.DateKey column

The authoritative register requires an Int64 Calendar.DateKey in YYYYMMDD form. Current gold observes the exact table, column name and data type; actual value encoding was not available for verification.

Workbook evidence

Target Fields!A5:J5

Cited current gold

fde-finance.current-model

Should the YYYYMMDD encoding and uniqueness of Calendar.DateKey be tested against source/model data during implementation validation?

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 5 of 13

Direct match 99%

Calendar.Date column

The authoritative register requires a DateTime Calendar.Date. Current gold observes the exact table, column name and data type.

Workbook evidence

Target Fields!A6:J6

Cited current gold

fde-finance.current-model

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 6 of 13

Direct match 95%

Calendar.FiscalMonth column

Current gold observes the exact Int64 Calendar.FiscalMonth column. Workbook context indicates a July fiscal-year start and supplies a formula for month numbering. Gold does not establish that the current model uses that exact derivation and notes that the column is summarised by Sum.

Workbook evidence

Target Fields!A7:J7 Fiscal Calendar!A2:C3 Fiscal Calendar!C4:C34

Cited current gold

fde-finance.current-model

Does the current Calendar.FiscalMonth use the required July-start numbering shown by the workbook formula?

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

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 7 of 13

Direct match 99%

Ledger.DateKey column and calendar linkage

The authoritative register requires an Int64 Ledger.DateKey posting-date foreign key. Current gold observes the exact column and an active many-to-one Ledger.DateKey to Calendar.DateKey relationship.

Workbook evidence

Target Fields!A8:J8

Cited current gold

fde-finance.current-model

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 8 of 13

Direct match 99%

Ledger.AccountKey column and account linkage

The authoritative register requires an Int64 Ledger.AccountKey account foreign key. Current gold observes the exact column and an active many-to-one Ledger.AccountKey to Account.AccountKey relationship.

Workbook evidence

Target Fields!A9:J9

Cited current gold

fde-finance.current-model

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 9 of 13

Direct match 97%

Ledger.SignedAmount column

The authoritative register requires a Decimal Ledger.SignedAmount in reporting-sign convention. Current gold observes the exact Decimal column. The audit confirms structure and formatting, but not source currency conversion logic or detailed sign semantics.

Workbook evidence

Target Fields!A10:J10 Ledger Sample!A2:C3

Cited current gold

fde-finance.current-model

Is SignedAmount already converted into a single reporting currency, and what conversion-rate/date rules are intended when CurrencyCode is added?

Is the workbook's positive-revenue/negative-expense sign convention the required production convention?

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 10 of 13

Direct match 99%

Ledger.IsAdjustment column

The authoritative register requires a Boolean Ledger.IsAdjustment. Current gold observes the exact table, column name and data type.

Workbook evidence

Target Fields!A11:J11

Cited current gold

fde-finance.current-model

What business rule distinguishes late or manual adjustments, and is the current field populated consistently with that rule?

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 11 of 13

Not found in this gold boundary 99%

Ledger.CostCentre column

The authoritative register requires Ledger.CostCentre for operating-area accountability, and working sheets illustrate cost-centre codes. The audited Ledger inventory contains only DateKey, AccountKey, SignedAmount and IsAdjustment; no CostCentre object is present in available current gold.

Workbook evidence

Target Fields!A12:J12 Ledger Sample!E3:E15 Reference Data!A1:A4

Cited current gold

fde-finance.current-model

Is CostCentre available in the finance posting source at the same posting grain as Ledger?

Is a separate Cost Centre dimension required, or is a code column on Ledger sufficient?

Who owns the authoritative cost-centre hierarchy and effective-dating rules?

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 12 of 13

Not found in this gold boundary 99%

Ledger.CurrencyCode column

The authoritative register requires an ISO transaction CurrencyCode for transaction-currency analysis, and working sheets illustrate AUD/NZD codes. No CurrencyCode object is present in the audited Ledger inventory in available current gold.

Workbook evidence

Target Fields!A13:J13 Ledger Sample!F3:F15 Reference Data!C1:C4

Cited current gold

fde-finance.current-model

Is transaction currency available on every posting in the finance source?

Are transaction amount, reporting amount and exchange-rate fields also needed to make transaction-currency analysis meaningful?

Should CurrencyCode link to a governed currency dimension?

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

Finding 13 of 13

Not found in this gold boundary 99%

Account.AccountGroup column

The authoritative register requires an Account.AccountGroup management roll-up. The audited Account inventory contains AccountKey, AccountName and AccountType only; no AccountGroup object is present in available current gold.

Workbook evidence

Target Fields!A14:J14 Chart of Accounts!D3:D13 Reference Data!B1:B4

Cited current gold

fde-finance.current-model

What is the authoritative source and owner for AccountGroup mappings?

Can an account belong to more than one management group, and are mappings effective-dated?

The reference examples differ in grouping vocabulary from some chart-of-accounts examples; what controlled hierarchy is intended?

Your answer Confirmed match Current estate already satisfies this. Confirmed partial Partly satisfied — the remainder becomes phase-two work. Confirmed gap Not satisfied — becomes phase-two work. Excluded from scope Stays visible for traceability, but is not proposed work. Needs more evidence Blocks scope until resolved. Enters the research queue.

Why (optional)

TargetArchitecture_Partial.xlsx

Account.AccountKey column

Account.AccountName column

Account.AccountType column

Calendar.DateKey column

Calendar.Date column

Calendar.FiscalMonth column

Ledger.DateKey column and calendar linkage

Ledger.AccountKey column and account linkage

Ledger.SignedAmount column

Ledger.IsAdjustment column

Ledger.CostCentre column

Ledger.CurrencyCode column

Account.AccountGroup column

Your overall position