Senior-authored Markdown
# Conclusion The selected target is **10 of 13 fields structurally covered** by recorded consultant-confirmed exact mappings. Each covered field maps to a current column with the same qualified name and matching declared and observed data type. The required action is `reuse_as_is`. No partial or transformed mapping is recorded. The remaining three cases are confirmed gaps. ## Exact mappings | Target | Current | Type | Decision | |---|---|---|---| | `Account.AccountKey` | `Account.AccountKey` | Int64 | Exact; reuse as is | | `Account.AccountName` | `Account.AccountName` | String | Exact; reuse as is | | `Account.AccountType` | `Account.AccountType` | String | Exact; reuse as is | | `Calendar.DateKey` | `Calendar.DateKey` | Int64 | Exact; reuse as is | | `Calendar.Date` | `Calendar.Date` | DateTime | Exact; reuse as is | | `Calendar.FiscalMonth` | `Calendar.FiscalMonth` | Int64 | Exact; reuse as is | | `Ledger.DateKey` | `Ledger.DateKey` | Int64 | Exact; reuse as is | | `Ledger.AccountKey` | `Ledger.AccountKey` | Int64 | Exact; reuse as is | | `Ledger.SignedAmount` | `Ledger.SignedAmount` | Decimal | Exact; reuse as is | | `Ledger.IsAdjustment` | `Ledger.IsAdjustment` | Boolean | Exact; reuse as is | ## Mapping classes | Mapping class | Count | Finding | |---|---:|---| | Exact | 10 | Consultant-confirmed | | Partial or transformed | 0 | No recorded case | | No candidate / gap | 3 | Consultant-confirmed | ## Confirmed gaps | Target | Bounded comparison result | Required action | |---|---|---| | `Account.AccountGroup` | No current candidate selected | Acquire or source | | `Ledger.CostCentre` | No current candidate selected | Acquire or source | | `Ledger.CurrencyCode` | No current candidate selected | Acquire or source | ## What exact mapping proves The decisions establish field-level structural reuse. They do not by themselves prove: - key uniqueness or referential integrity; - acceptable null rates and value domains; - equivalent business semantics over production data; - correct fiscal calendar behaviour; - that `Ledger.SignedAmount` has the intended reporting-currency semantics; - implementation in a separate target model. `Ledger.JournalSource` and `Ledger.ApprovalStatus` are outside this mapping result because they are not target rows and have no mapping cases.