Skip to main content

Comparison · Liquidity rail versus ledger custody

Account Currency vs Settlement Currency

Settlement currency names the monetary rail where cash or liquidity actually clears—bank networks, treasury workstations, netting agreements—often at State 03 between obligation and ERP custody. Account currency names how balances persist inside charts once finance asserts accountable ledger identity at State 04. Identical ISO symbols still answer different forensic questions: Which currency moved versus which currency holds reconciled exposure?

Governing distinction

Settlement currency proves how liquidity executed.
Account currency proves how balances reconcile inside governed postings.

Currency identity comparison · AccountCcy.com

Side-by-side posture

Cash execution versus accounting custody

Treasury teams steward settlement paths—confirmations, nostro timing, corridor choices—while controllers steward ledger assignments feeding trial balance integrity.

When settlement reroutes through USD clearing while obligations remain denominated in MAD or EUR, FX realization narratives belong to traceable bridges—not rhetorical blending.

Confusing the two invites phantom reconciliations: banks agree while ERP custody scopes disagree about which balances remain open across closes.

Controlled vocabulary

Conceptual comparison inside enterprise finance

Deploy this contrast during bank mandate redesigns, treasury pooling launches, AP factory migrations, and forensic reconstructions after FX variance escalations.

  1. Settlement currency — liquidity closure

    Specifies denomination of realized cash movement, confirmations, and clearance—the monetary rail where exposure converts into settled liquidity.

    Reference: Settlement currency state

  2. Account currency — ERP retention posture

    Specifies how balances accumulate inside charts—reconciliation scopes, open-item treatments, and downstream revaluation eligibility.

    Reference: Account currency state

Failure anatomy

Where confusion appears—and what breaks

Teams assume matching ISO codes between bank feeds and GL accounts erase custody storytelling—yet confirmations often reveal deliberate corridors unlike invoice denomination.

Multi-bank workflows exacerbate drift when netting calendars diverge from ERP posting calendars.

Accounting consequence: realized FX recognition disconnects from identifiable banking artifacts—auditors challenge gain/loss narratives lacking confirmation lineage.

ERP consequence: clearing accounts balloon because settlement postings cannot marry custody scopes controllers expect.

Reporting consequence: liquidity dashboards narrate banking rails while management packs cite ledger balances—leadership debates phantom gaps.

Custody interrogation

Custody questions—each side

Treasury and accounting must intersect these answers before declaring exposures closed.

  1. Settlement currency question

    Which currency cleared banking rails—and does confirmation evidence tie back to obligation currency without undocumented netting?

    Reference: Settlement currency (defined)

  2. Account currency question

    Which ERP custody assignment still carries open monetary items after settlement—and does reconciliation prove continuity into ledger measurement?

    Reference: Account currency (defined)

Doctrine & mechanics

Framework continuity after this contrast

Chain-of-custody doctrine demands traceable hops between commercial obligation, liquidity execution, and ledger custody—never improvised spreadsheets bridging silence.

Reference continuity

Liquidity and ledger identities in one lineage

Readers linking treasury execution to ERP custody should traverse states sequentially—obligation, settlement, account assignment—before interpreting FX outcomes.

State sequencing

Settlement precedes accountable ledger custody in operational narratives.

Yet postings may retain foreign custody while banks cleared corridors differently—document bridges explicitly.

Evidence coupling

Bank confirmations anchor settlement truth.

Posting metadata anchors ledger custody—both belong in forensic bundles.

Risk concentration

Pooling and netting amplify silent divergence.

Govern forums where treasury reshapes rails without accounting revisiting custody scopes.

Practical control implication

Bridge treasury confirmations to ERP custody assignments

Maintain pairing matrices linking mandate currencies to chart assignments; escalate when netting calendars shift; rehearse month-end tie-outs between bank statements and open-item lists scoped by account currency.

Risk if vocabulary collapses

Liquidity truth divorced from ledger truth

Collapsed identities invite contested realized FX, inflated clearing balances, and assurance findings where leadership cannot prove monetary lineage from bank to balance sheet.

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.