Skip to content
FDE BI Evidence Workbenchobserved → compared → decided → scoped
Engagement board Current gold promoted Model codex Packet xlsx-evidence-v2 Identifiers and receipts

TargetArchitecture_Partial.xlsx

8 sheets · compared 2026-07-30T13:19:23.086Z

Exact model input Extraction review Receipts
  1. Source input Original workbook bytes · 8 sheets Source input detail
  2. XLSX.evidence 12 categories accounted for XLSX.evidence detail
  3. Current gold promoted build Current gold detail
  4. Model walk codex Model walk detail
  5. Your decisions 0 of 13 answered Your decisions detail
  6. Scope / SOW Blocked until every finding is answered Scope / SOW detail

The model says

14 findings

10 direct 1 context 3 not found

You say

0 of 13 answered

The gap is the outstanding work. Context-only findings are excluded — they describe the estate rather than propose it.

Ledger Sample

15 × 6 · 0 formulas · 3 findings cite this sheet

Visual aid Exact model input Clear filter

Needs your call 3

Each becomes a final, immutable disposition.

Review all 3
Ledger.SignedAmount column Direct match · Target Fields!A10:J10 · Ledger Sample!A2:C3 Decide

How the model read it

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.

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?

Evidence

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

Cited current gold

fde-finance.current-model
Ledger.CostCentre column Not found in this gold boundary · Target Fields!A12:J12 · Ledger Sample!E3:E15 +1 Decide

How the model read it

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.

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?

Evidence

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

Cited current gold

fde-finance.current-model
Ledger.CurrencyCode column Not found in this gold boundary · Target Fields!A13:J13 · Ledger Sample!F3:F15 +1 Decide

How the model read it

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.

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?

Evidence

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

Cited current gold

fde-finance.current-model

This project defines the next engagement. It does not assert that the target has been implemented.