Chain discipline
States 02 and 04 bracket external duties entering ERP custody.
Skipping vocabulary between them invites silent substitution where dashboards show balanced FX lines yet forensic replay fails.
Comparison · State 02 versus State 04
Account Currency vs Transaction Currency
Transaction currency names the denomination of the measurable obligation—the commercial or contractual monetary identity attached when finance recognizes an event. Account currency names how ERP custody assigns balances inside charts so postings, reconciliations, revaluation populations, and forensic replay stay coherent. Same ISO code on screen does not imply same institutional job; conflating the two reroutes FX debates to the wrong owners and seeds structural reconciliation drift.
Governing distinction
Obligation currency answers “in what currency was this duty born?”
Account currency answers “in what currency does this balance live inside governed ledger custody?”
Currency identity comparison · AccountCcy.com
Side-by-side posture
Two identities on one economic thread
Transaction currency sits at State 02 in the CCY State Chain: pricing and obligation crystallize before postings freeze custody choices. Account currency sits at State 04: configurable ledger identity reconciles external movement into accountable balances.
ERP postings carry both signals—document currency versus account assignment—but controllers must prove which lens governs reconciliation scope, open FX populations, and disclosure bridges back to commercial evidence.
When teams substitute obligation narration for custody configuration, sub-ledgers appear balanced while auditors cannot replay how monetary truth migrated across systems.
Controlled vocabulary
Conceptual comparison inside enterprise finance
Use this contrast during quote-to-cash design, AP/AR policy forums, intercompany billing reviews, and multi-currency ERP migrations—anywhere obligation wording meets chart configuration.
Transaction currency — obligation identity
Anchors measurable duties in the currency of invoices, contracts, bank instructions, or instrument denomination before ERP postings absorb them into custody populations.
Reference: Transaction currency state
Account currency — ERP custody identity
Assigns how balances accumulate, reconcile, feed period-end revaluation batches, and inherit translation methodology downstream.
Reference: Account currency state
Failure anatomy
Where confusion appears—and what breaks
Confusion clusters where obligation currency equals custody ISO codes visually—teams assume matching symbols erase the need for documentary bridges.
Payables and receivables modules fracture when commercial denomination spans multiple corridors yet charts collapse into a single custody assignment without governed mappings.
Accounting consequence: incorrect posting populations enter foreign-monetary-item treatments, misrouting unrealized versus realized FX narratives.
ERP consequence: reconciliation scopes widen inexplicably—controllers chase variance inside the wrong subsystem.
Reporting consequence: management commentary cites transactional wording while disclosure packs rely on ledger custody—external readers inherit incompatible mental models.
Custody interrogation
Custody questions—each side
Finance, treasury, and systems owners should answer these independently, then reconcile answers before accepting period-end totals.
Transaction currency question
In which currency did counterparties measure legal performance of receivable or payable, and which artifact locks that denomination before postings reshape it?
Reference: Transaction currency (defined)
Account currency question
Which ERP custody assignment reconciles this balance across books, entities, and migrations—and who authorized deviations when obligation currency diverged?
Reference: Account currency (defined)
Doctrine & mechanics
Framework continuity after this contrast
Stabilize vocabulary before layering FX mechanics—revaluation assumes identifiable custody populations; translation assumes ledger measurement already earned truth upstream.
Reference continuity
Comparison anchors inside the custody stack
Move from obligation clarity into custody governance, then outward across ledger measurement and reporting—preserving reconstructable lineage at every hop.
Lexical spine
Published glossary entries lock adjacent meanings.
Transaction currency and account currency definitions cite enterprise contexts—not interchangeable synonyms.
Executive posture
CFO narratives inherit whichever fractures controllers tolerated upstream.
Translation polish cannot substitute missing bridges between obligation currency and custody currency.
Practical control implication
Separate forums own obligation wording versus chart custody
Document joint approvals when invoice currency intentionally diverges from account assignments; archive evidence tying postings to commercial confirmations; rehearse reconciliation scopes before migrations rename currencies.
Risk if vocabulary collapses
Structural FX and reconciliation distortion
Collapsed identities route variance analytics to treasury rhetoric instead of configurable ledger truth—audit teams rebuild spreadsheets because ERP metadata no longer narrates custody hops.
Evidence Discipline
Original framework. Real institutional behavior.
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.