Risk if weak
Ledger-policy divergence
Operational shortcuts maintain books in currencies contradicting documented functional determinations—bridges explode under scrutiny.
CCY State Chain · State 05
State 05 translates disciplined State 04 postings into books governed entities defend during close. Functional currency determinations (under IFRS/US GAAP contexts AccountCcy cites illustratively—not advice) typically align with ledger currency, yet carve-outs, acquisitions, and hybrid stacks frequently strain that alignment unless explicitly governed.
Measurement Books
General ledger custody absorbs subledger summaries when account mapping and posting logic remain deterministic; currency master data quietly constrains rounding and precision engines consume during valuation. Period-end revaluation and unrealized FX attach here on open monetary populations account configurations expose—exchange-rate-source governance proves which curve governed each batch.
Custody Question
Which currency anchors journals and trial balances—and does forensic replay tie each line to subsystem payloads plus functional-measurement policy?
Position in Chain
Ledger currency receives governed postings from State 04 and supplies measured packages reporting translation consumes at State 06. Confusing ledger discipline with presentation narration invites boards to misread operational exposure versus visibility overlays.
Market quotation before obligation attaches.
Denomination of the recorded financial event.
Cash or settlement rail actually moved.
Assigned custody currency for maintained balances.
Books maintained for the entity.
Presentation layer for management and filings.
Group currency unifying reporting entities.
Traceable, defendable monetary truth.
Monetary state thesis
State 05 answers how systematic postings accumulate before outward reporting reshapes narratives.
Receives account-assigned balances, settlement-absorbed cash flows, and subsystem summaries routed through posting logic.
Controls valuation batches, allocation engines, and tax integrations that mutate balances while preserving—or betraying—custody lineage.
Passes measured ledger packages toward reporting translation, management commentary, and consolidation ingestion.
Measurement lens
AccountCcy does not publish a standalone `/states/functional-currency/` URL—the functional lens is an accounting-measurement discipline tightly coupled to ledger books. State 05 is where functional policy meets postings auditors reperformance-test.
Entities determine functional currency under applicable standards; misalignment between documented determinations and live ledger configuration produces recurring bridge shocks finance narrates as opaque FX noise.
Remeasurement and FX revaluation consume populations classified against functional context—exchange-rate-source artifacts must tie batches to policy.
Functional currency vocabulary
Defines the economic-environment measurement baseline entities apply before translation refracts disclosure.
Reference: Functional currency
Remeasurement discipline
Separates monetary-item restatement mechanics from presentation translation—essential vocabulary at ledger close.
Reference: Remeasurement
FX revaluation batches
Ledger engines restate foreign monetary balances using governed rates—population scope depends on account assignments upstream.
Reference: FX revaluation
Period-end revaluation control
Closing-rate discipline binds unrealized FX suspense until settlement realizes economics.
Reference: Period-end revaluation
Exchange rate source governance
Artifacts prove which curve locked each valuation—not trader anecdotes.
Reference: Exchange rate source
Unrealized FX posture
Separates open-balance measurement drift from liquidity-realized outcomes settled at State 03.
Reference: Unrealized FX
Audit trail continuity
Ledger postings must replay to confirmations, configurations, and subsystem extracts—functional debates included.
Reference: Audit trail
Institutional consequence
Posting logic and account mapping decide whether automation preserves custody—silent mapping drift surfaces as FX investigations unrelated to markets.
Currency master data determines precision behavior millions of lines inherit—minor inconsistencies explode into material bridges.
Reporting integrity downstream cannot retrofit broken ledger lineage—investor packs amplify fractures conceived here.
Monetary reconstruction succeeds only when general ledger balances drill to identifiable subledger payloads and banking proofs.
Failure anatomy
Shadow spreadsheets reconcile GL totals while bypassing posting engines—forensic replay fails despite balanced trial balances.
Merged ledgers from acquisitions maintain legacy currencies contradicting current functional memos.
Hybrid tax or statistical ledgers diverge without documented bridges—audit committees hear qualitative excuses.
Valuation batches apply stale mappings—open populations misclassified between realized and unrealized buckets.
Functional currency debates occur in committee while postings obey contradictory ERP configuration.
Governance interrogation
Controllers, ERP architects, tax partners, and auditors resolve jointly—ledger shortcuts age into material weaknesses.
Does documented functional currency determination match live ERP ledger configuration exports?
Which posting logic version produced this close—and where is change control evidence?
Can each GL balance drill to subsystem transactions without improvised spreadsheets?
Which exchange-rate-source tables locked valuation batches—and who approved overrides?
How does account mapping route operational detail into GL accounts shown on trial balance?
Where do unrealized FX populations reconcile between GL, subledgers, and banking proofs?
Reference continuity
Ledger discipline binds framework layers to forensic replay—reference ERP and mechanics vocabulary deliberately.
Risk if weak
Operational shortcuts maintain books in currencies contradicting documented functional determinations—bridges explode under scrutiny.
Control logic
Require configuration snapshots, valuation run logs, and mapping matrices archived each period—tie functional memos to ERP extracts explicitly.
Transition Logic
Receives From
Account currency postings and subsystem summaries entering systematic journals.
Passes To
Reporting translations, management narratives, CFO packs, and consolidation ingestion pipelines.