Policy
Account currency assignment policy
Defines which account classes carry which custody currency and who approves exceptions.
CCY State Chain · State 04
Account Currency
Account Currency is State 04—the monetary state ERP assigns to an account, balance, receivable, payable, obligation line, ledger position, or account-level monetary record. Currency becomes attached here to a governed chart context: how postings accumulate, reconciliations scope, foreign balances qualify for restatement, and auditors replay custody—not merely as an obligation denomination from a transaction event or a cosmetic ISO display field.
Custody Gate
Where monetary identity enters governed chart context.
Upstream states narrate quotation, obligation, and settlement motion; State 04 freezes custody decisions inside charts—what currency balance lives inside this account, how controllers reconcile it, and how downstream ledger measurement, translation narratives, consolidation hubs, and assurance artifacts inherit identity. ERP currency configuration and currency master data silently dictate numeric behavior inherited by postings and valuation batches; account mapping and posting logic decide how subledger facts summarize into general ledger custody while system-of-record discipline declares where authoritative replay begins. State ownership must be explicit: weak discipline here is structural—reconciliation theater replaces lineage finance could defend, and audit trails lose contiguous reconstruction paths.
Custody Question
Which currency identity governs how this account records, revalues, reconciles, and defends its balances—and who owns that assignment when postings span subsystems?
Position in Chain
Account Currency inside the chain of custody.
State 04 sits between settlement-era narratives and ledger-era measurement. Readers anchor definition intent on the primary entry page, then traverse the CCY State Chain tiles, Currency State Control Framework layers, doctrine pillar, and glossary-defined neighboring identities—transaction through audit reconstruction—without collapsing distinct forensic questions into identical ISO symbols.
Quoted Currency
Market quotation before obligation attaches.
Transaction Currency
Denomination of the recorded financial event.
Settlement Currency
Cash or settlement rail actually moved.
Account Currency
Assigned custody currency for maintained balances.
Ledger Currency
Books maintained for the entity.
Reporting Currency
Presentation layer for management and filings.
Consolidation Currency
Group currency unifying reporting entities.
Audit Reality
Traceable, defendable monetary truth.
Evidence Map
Artifacts that make Account Currency defensible.
Each state must be provable through artifacts, not asserted through narrative. These evidence classes define what reviewers should be able to inspect before this state passes downstream.
Configuration
ERP chart and account master extract
Proves the live account currency setting that postings, reconciliations, and valuation engines inherit.
Change control
Approval and migration evidence
Documents why account currency changed and how historical balances were bridged.
Control Artifacts
Minimum governance artifacts for this state.
| Artifact | Owner | Purpose |
|---|---|---|
| Account currency policy matrix | Controller | Sets the governed custody rule for each material account class. |
| Chart-of-accounts currency extract | ERP architecture | Proves live configuration matches approved policy. |
| Account currency change log | Finance systems governance | Prevents undocumented custody drift. |
Neighboring identities
Account Currency relative to published CCY vocabulary
State 04 answers custody configuration inside charts; each neighboring identity answers a different forensic question. Published glossary entries anchor language—never interchangeable synonyms.
Transaction currency — obligation denomination
Defines measurable commercial duties before postings stabilize balances; account currency assigns ERP custody where balances reconcile—aligned ISO codes still carry distinct control obligations.
Reference: Transaction currency
Quoted currency — pre-obligation signal
Market-facing rates precede measurable obligations; custody debates intensify once quotations convert into transactional duties feeding postings.
Reference: Quoted currency
Settlement currency — cash rail denomination
Governs clearing banks that move liquidity; divergence from transactional denomination crystallizes FX outcomes controllers must classify as realized once postings absorb banking proofs tied back to State 04 assignments.
Reference: Settlement currency
Ledger currency — measurement posture downstream
Frames maintained trial-balance measurement after custody enters charts; confusion collapses policy debates when ledger lenses substitute for explicit account assignments prematurely.
Reference: Ledger currency
Functional currency — economic-environment lens
Determines entity-wide measurement priorities before translation refracts outward; distinct from account-level custody yet tightly coupled inside ERP stacks.
Reference: Functional currency
Reporting currency — visibility narration
Presentation refracts ledger custody through disclosure choices—cannot substitute missing account-level lineage upstream.
Reference: Reporting currency
FX revaluation — period-boundary restatement
Period-end revaluation consumes foreign monetary populations account configurations expose—unrealized FX accumulates on open items until settlement realizes outcomes; remeasurement discipline must stay explicit when functional contexts diverge; exchange-rate-source governance proves which curve locked the batch.
Reference: FX revaluation
Currency translation — methodology versus custody
Converts measured ledger outcomes into presentation currencies—distinct mechanical discipline from configuring where balances accumulate beforehand.
Reference: Currency translation
Audit trail discipline — reconstructability
Contiguous audit trails, repeatable monetary reconstruction, and corpus-grade control evidence expose State 04 fractures regardless of polished disclosures downstream.
Reference: Audit reality
Operational consequence
Why Account Currency as a monetary state matters
Account-level monetary control decides reconciliation scopes, subsystem postings, and controller accountability—without naming custody, automation rearranges symptoms.
Receivables and payables fracture when customer-facing denomination diverges from chart custody without documented bridges tying proofs together.
ERP account configuration encodes identity populations FX batches consume—misassignment cascades through valuation engines silently.
Posting logic and account mapping translate subsystem facts into general ledger lines—when mappings drift, FX narratives blame markets instead of structural routing faults.
Currency master data governs precision, rounding, and activation—the mundane foundation auditors reopen when bridges implode silently.
Multi-currency ledgers amplify mismatch when local custody diverges from group methodology absent explicit governance.
Revaluation eligibility depends on which balances qualify as foreign versus functional-measured—ambiguous assignments distort batch populations.
Reporting integrity—in AccountCcy’s evidence vocabulary—inherits whichever fractures controllers tolerated at assignment time; investor packs cannot retrofit lineage absent upstream clarity.
Audit reconstruction demands postings reconcile to documented custody decisions—not improvised spreadsheets reconciling numbers without narrative coherence.
Monetary truth preservation—in doctrine terms—is reconstructable custody; State 04 is where external motion earns accountable internal identity.
Failure anatomy
Where Account Currency state fractures
Transaction obligation currency substitutes silently for ERP custody assignment—sub-ledgers balance while forensic narratives diverge.
Account currency degrades into ‘display label’ thinking—configuration drift proceeds without control owners recognizing custody transfers.
Ledger currency policy overrides account-level context rhetorically—committees debate measurement while postings obey conflicting assignments.
Functional currency vocabulary collapses into account currency debates—entity lenses confused with chart custody.
Revaluation executes without explicit account-state ownership—rates apply generically without documented populations.
Reporting currency narratives obscure originating account-level monetary paths—disclosures polish outcomes lacking reconstructable hops.
Audit teams cannot replay account-level currency state sequences—independence shifts toward qualitative storytelling instead of artifact replay.
Governance interrogation
Account Currency state control questions
Controllers, ERP architects, treasury partners, and assurance leads resolve these jointly—delegated ambiguity invites recurring close theater.
What currency does this account carry—and does evidence match configuration intent?
Is account currency inherited mechanically from transactional obligation or assigned deliberately via chart policy—and where is that decision documented?
Which system owns the account-level currency state—ERP core, subsystem, consolidation hub—and who signs custody transfers?
Is exposure revalued at boundary, settled via banking rails, translated into presentation currency, or merely narrated differently externally?
Which currency remains authoritative for operational control at State 04 versus downstream measurement versus disclosure?
Can reviewers reconstruct the account-level monetary path using postings, policies, rate tables, and subsystem extracts alone?
Site continuity
Bridge into AccountCcy architecture
Primary definitional intent begins at the entry pillar; canonical sequencing spans the CCY State Chain; layered custody vocabulary lives in the Currency State Control Framework; doctrine explains why monetary truth demands lineage; glossary clusters stabilize lexical discipline—including currency state and account currency control governance.
Risk if weak
Custody drift across postings
Teams silently alternate transactional framing and chart framing during migrations or retrofit projects—balances reconcile theatrically while auditors cannot anchor custody lineage State 04 should have frozen.
Control logic
Govern assignment as sovereign control
Co-own policy with controllers, treasury, and ERP architects; tie assignments to chart logic; prove reconciliations bridge obligation, settlement, account custody, and ledger measurement without heroic spreadsheets.
Transition Logic
What this state receives and what it passes forward.
Receives From
Quoted, transactional, and settlement narratives once monetary movement demands accountable chart custody.
Passes To
Ledger measurement disciplines, revaluation populations, translation methodology, consolidation absorption, and audit reconstruction artifacts downstream.