State 01
Quoted Currency
Market-facing currency signal preceding measurable obligations—rate-source governance precedes custody debates downstream.
Framework · State-Sequence Pillar
Inside enterprise finance, currency is not a cosmetic ISO badge beside USD, EUR, MAD, or any code—it is a state carried through systems, postings, accounts, ledgers, settlement rails, functional measurement discipline, reporting lenses, translation mechanics, revaluation logic, and reconstructable audit trails auditors replay state-by-state. Source systems originate monetary signals; governed posting logic moves them across subledger detail into general ledger measurement; currency master data and ERP currency configuration constrain how each hop behaves numerically; systems of record designate where authoritative postings live when subsidiaries disagree. The CCY State Chain names those transitions so teams stop collapsing incompatible meanings behind identical symbols; weak state ownership or fragmented monetary reconstruction anywhere fractures lineage downstream.
State Chain Doctrine
The CCY State Chain · AccountCcy.com
From Thesis Through Controls Into Mechanics
Monetary truth on AccountCcy.com begins as anchored discourse—the custody pillar describes why figures demand lineage rather than optimism.
The Currency State Control Framework converts doctrine into operational custody zones spanning ERP cores, source-system lineage, subledger and general ledger accountability, posting logic, close mechanics, translation narratives, and audit posture—not substituting standards or vendor logic, but exposing transitions finance must own.
This page sequences glossary-published checkpoints finance routinely scrambles—especially settlement versus account custody, ledger versus functional identity, revaluation versus translation, and reporting narration versus ledger proofs.
The eight numbered custody tiles below preserve canonical navigation toward quotation through consolidation into audit reality; the glossary-linked passage beneath complements them by spotlighting reconstruction-critical checkpoints ERP architects and controllers reconcile weekly.
Glossary-anchored sequence
Canonical state numbering from quotation through consolidation appears across `/states/` reference tiles and the grid beneath; AccountCcy also publishes defined terminology where treasury and controllers collide.
Ordered below as custody checkpoints—not reranking authoritative accounting sequence—you trace meanings ERP postings confuse unless custody vocabulary disciplines interfaces among treasury, accounting, consolidation, and disclosure owners.
1 · Transaction currency
Names obligation denomination and measurable commercial duties encoded before postings stabilize ledger custody; dominates invoicing, contract clauses, AR/AP recognition debates. Mistaken for ERP account assignment or reporting narration early—obligation currency survives unchanged while custody hops distort reconciliation silently beneath dashboards.
Reference: Transaction currency
2 · Account currency
Assigns ERP chart custody—balances reconcile inside subsystem postings bounded by configuration—not interchangeable with obligation denomination alone nor synonymous with ledger measurement conventions downstream.
Reference: What Is Account Currency?
3 · Settlement currency
Governs cash rails clearing counterparties—rates diverge from transactional obligation when corridors net differently; treasury proves settlement artifacts while controllers tie postings back to obligation currency where FX differences crystallize into realized outcomes.
Reference: Settlement currency
4 · Ledger currency
Materializes entity trial-balance measurement where close discipline accumulates FX differences before translation refracts narratives outward; confusion with functional currency governance invites misaligned policy debates across controllers.
Reference: Ledger currency
5 · Functional currency
Determines economic-environment measurement lens anchoring primary amounts before translation reshapes disclosure—distinct from ledger configuration artifacts yet tightly coupled inside SAP-class stacks and equivalents.
Reference: Functional currency
6 · Reporting currency
Frames outward management, investor, or regulatory lenses—presentation choices can diverge sharply from ledger custody without naming where translation policy intervened; currency exposure narratives amplify when visibility layers detach from measurement lineage.
Reference: Reporting currency
7 · Currency translation
Executes methodology converting measured results into presentation currencies—translation adjustments memorialize equity-side governance distinct from rate-driven restatements at period boundaries when teams mislabel translation runs as ‘just FX.’
Reference: Currency translation
8 · FX revaluation
Restates monetary balances still denominated foreign at period ends—period-end revaluation governs unrealized FX on open monetary items until settlement or derecognition shifts economics toward realized classification.
Reference: FX revaluation
9 · Audit reconstruction
Terminal posture requiring replayable monetary paths governed by contiguous audit trails—rates, postings, reconciliations, subsystem extracts—so monetary reconstruction proceeds without heroic spreadsheets storytelling audit committees tolerate briefly.
Reference: Audit reality
Institutional consequence
Multi-currency accounting breaks silently when obligation currency, ERP custody, ledger measurement, functional determination, revaluation batch logic, translation methodology, and outward reporting narration collapse behind identical ISO symbols.
ERP and accounting platform architects encode postings, valuation engines, tax integrations, and consolidation pipelines—each hop preserves numeric fidelity yet may discard custody narrative unless configuration mirrors disciplined vocabulary and named state ownership.
Ledger interpretation depends on knowing whether balances reflect transactional obligations, settlement-clearing differences, account assignments, or close-restated valuations.
FX revaluation discipline requires naming rate sources and boundary ownership before consolidation narratives absorb unexplained drift.
Currency translation discipline demands separating measured ledger outcomes from presentation conversions CFO packs summarize.
CFO reporting inherits whichever custody fractures controllers tolerated upstream—investor narratives amplify ambiguity unless sequencing clarity preceded disclosure drafting.
Audit reconstruction fails when evidence bundles omit subsystem hops reviewers cannot replay independently.
Preventing monetary ambiguity is therefore preventative governance—not quarterly reconciliation heroics—because ambiguity metastasizes before dashboards admit variance, even when monetary reconstruction exercises remain theoretically possible yet prohibitively expensive.
Architecture vocabulary matters as much as accounting vocabulary: naming systems of record, verifying currency master data inheritance inside valuation batches, and tracing ERP currency configuration snapshots prevents states from drifting inside automation rather than through deliberate policy.
Failure anatomy
Treat transactional obligation currency as ERP account assignment—or reverse them—and reconciliation scopes detach before cash settles.
Treat ledger measurement currency as interchangeable with functional currency governance—or vice versa—and policy debates mis-target controls while postings obey opposing conventions.
Confuse revaluation mechanics, remeasurement populations, and translation methodology—classic vocabulary drift—and teams debate variance narratives disconnected from actual pipeline transforms.
Allow reporting currency narration to obscure earlier custody hops—management packs polish outcomes while auditors hunt lineage upstream.
Leave audit teams unable to reconstruct originating obligation currencies through settlements into postings—assurance escalates into qualitative storytelling instead of artifact replay.
Preserve numeric balances while shedding subsystem state context—values survive while forensic narrative collapses—the silent precursor to material weakness conversations.
Governance interrogation
Operators spanning treasury, controllers, systems owners, consolidation hubs, and assurance leads answer these jointly—not sequentially delegated questions evaporating across inbox boundaries.
What was the originating transaction currency—and where is its obligation documented against counterparties?
Which chart-of-account assignment carried monetary custody when postings absorbed the exposure?
Which subsystem or integration transformed currency state—ERP batch, treasury workstation, consolidation hub, translation engine?
Was value movement driven by settlement clearing, period-end revaluation, translation methodology, or mere reporting presentation—and where is each distinguished?
Which currency is authoritative at this boundary for measurement versus disclosure versus audit replay?
Can independent reviewers reconstruct the custody sequence using artifacts alone—rates, policies, postings, reconciliations—without improvisational narrative?
Continuity map
Quoted currency precedes obligations commercially—anchor quotation discipline before transactional duties crystallize; consolidation currency still absorbs group reshaping prior to terminal audit posture across canonical `/states/` navigation.
Currency state vocabulary explains why ISO equality masks institutional inequality; account currency control names governance over custody assignments at State 04.
Eight Custody States
Follow numbered `/states/` tiles for end-to-end custody traversal across quotation, obligation, settlement, account custody, ledger measurement, reporting, consolidation, and audit posture.
State 01
Market-facing currency signal preceding measurable obligations—rate-source governance precedes custody debates downstream.
State 02
Obligation denomination attaching measurable duties commercial counterparties recognize—distinct from ERP custody until postings freeze balances.
State 03
Cash-movement denomination reconciling banking realities versus invoiced obligations—FX realization surfaces when divergence persists.
State 04 · Control Point
ERP custody assignment governing reconciliation scope—weak governance propagates ledger, reporting, consolidation, and audit fractures.
State 05
Entity measurement posture accumulating balances controllers defend before translation reshapes outward narratives.
State 06
Presentation lens refracting ledger truth through disclosure choices CFO narratives amplify internally or externally.
State 07
Group aggregation absorbing elimination logic, ownership adjustments, and multi-entity translation interplay.
State 08
Terminal reconstructable custody—rates, postings, reconciliations, scrutiny artifacts aligned without improvised storytelling.
State 04
Sequential checkpoints underscore why State 04 assignments deserve explicit account currency control—settlements, ledger measurement, functional lenses, translation, revaluation, and consolidation inherit whichever fractures originate here.
Sequence Risk
Identical ISO codes lubricate informal synonym swapping—obligation, custody assignment, clearing denomination, measurement lens, presentation narration—until reconstruction demands lineage finance cannot rapidly replay.
Evidence Discipline
AccountCcy.com develops original framework language while distinguishing it from established accounting terminology, ERP behavior, reporting practice, financial messaging conventions, and professional standards.
Vendor names, accounting standards, and system categories may be referenced only as context. Such references do not imply affiliation, endorsement, official interpretation, or professional advice.
Reference and educational framework only. Not accounting, audit, tax, legal, investment, or ERP implementation advice.