Risk if weak
Silent obligation drift
Operational shortcuts rename denominations during ingestion—balances reconcile cosmetically while statutory obligations remain denominated elsewhere.
CCY State Chain · State 02
Transaction Currency
State 02 locks obligation denomination—the measurable duty invoices and confirmations encode—upstream of settlement rails and account-level ERP custody. Misreading it collapses monetary reconstruction because auditors cannot tie postings back to the currency commercial participants believed governed performance.
Obligation Identity
Source-event denomination before chart custody.
Commercial teams select transaction currency in contracting and operational systems; finance inherits that signal when obligations hit ERP boundaries. Source systems must preserve obligation currency lineage so downstream assignments cannot silently substitute synonyms. Naming which application remains system of record for obligation extracts separates disciplined reconstruction from spreadsheet folklore.
Custody Question
In which currency does this counterparty legally measure receivable or payable performance—and which governed artifact proves it before postings absorb the exposure?
Position in Chain
Transaction Currency inside the chain of custody.
Transaction currency receives quotation narratives yet precedes liquidity execution and chart assignments. It passes denominated obligations toward settlement flows and, ultimately, toward State 04 custody—never interchangeable with cash rails or ledger lenses despite aligned ISO codes.
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.
Monetary state thesis
Transaction currency as obligation-bearing enterprise state
State 02 answers which currency measures legal and economic performance of an obligation—not merely which ISO badge appears on dashboards.
From quotation pressure: commercial desks inherit quoted-currency discipline before obligation crystallizes—rates locked upstream constrain downstream narratives.
Controls here: finance validates obligation extracts, interface mappings, and contractual annexes so ERP ingestion cannot drift denomination silently.
Passes forward: denominated duties feed settlement execution, account assignments, ledger measurement, and custody reconstruction—each hop must reference this baseline.
Institutional consequence
Why transaction currency discipline anchors monetary truth
ERP configuration at State 04 inherits obligation currency whether teams acknowledge it—ambiguous obligation signals distort reconciliation scopes and FX commentary.
Currency exposure narratives attach to identifiable obligation populations; collapsing transaction currency with account custody erases visibility into where risk truly lives.
Audit trails and monetary reconstruction demand linkage from postings back to obligation extracts—weak State 02 lineage invites qualitative variance storytelling.
Source-system integrity matters: procurement, billing, and treasury feeds must preserve denomination metadata controllers can replay under scrutiny.
Failure anatomy
Where transaction currency fractures
Side letters or annexes alter denomination assumptions ERP templates never captured—ghost currencies lurk beneath balanced dashboards.
Middleware converts currencies opportunistically without documenting policy—obligation currency arriving at ERP differs from counterpart expectations.
Teams treat display currencies inside portals as authoritative—while contractual denomination remains elsewhere—breaking forensic coherence.
Intercompany engines batch translations before obligation identity stabilizes—downstream custody inherits unexplained drift.
Settlement previews confuse treasury operators into believing obligation currency changed—when only corridor mechanics shifted.
Governance interrogation
Transaction currency control questions
Commercial, accounting, systems, and treasury owners resolve jointly—delegated ambiguity metastasizes before audit committees intervene.
Which contract clause or statutory instrument fixes obligation denomination—and where is that artifact archived?
Which source system remains authoritative for obligation extracts fed into ERP—and does metadata survive integrations?
Does interface logic alter denomination between operational capture and finance ingestion?
How do teams prove obligation currency when counterparties dispute performance measurement currency?
Where does transaction currency appear on audit trail extracts tying postings back to commercial truth?
How does currency exposure reporting identify populations still governed by State 02 versus States 04–06?
Reference continuity
Connect State 02 to AccountCcy architecture
Use published glossary language alongside CCY sequencing and framework layers—never improvised synonyms.
Control logic
Contract-to-system lineage
Institutionalize obligation currency metadata on every interface specification; pair legal review with ERP architects before automation scales ambiguous payloads.
Transition Logic
What this state receives and what it passes forward.
Receives From
Quoted commercial narratives once counterparties commit to measurable obligations.
Passes To
Settlement execution, ERP custody assignments, ledger postings, and forensic replay obligations downstream.