Skip to main content

Comparison · Custody assignment versus maintained books

Account Currency vs Ledger Currency

Account currency configures how individual accounts, balances, or postings retain monetary identity inside ERP charts—the custody assignments controllers reconcile at State 04. Ledger currency names the currency in which the entity’s primary books maintain measurement and trial-balance integrity—typically aligned with functional currency at State 05. Misreading configuration-level custody as synonymous with entity-wide ledger measurement misroutes close routines, revaluation batches, and forensic explanations.

Governing distinction

Account currency decides where balances reconcile inside charts.
Ledger currency decides which measurement lens hosts the entity trial balance.

Currency identity comparison · AccountCcy.com

Side-by-side posture

Micro custody versus macro measurement shell

ERP architectures might assign foreign account currencies while ledger currency remains functional—foreign monetary items demand explicit remeasurement discipline feeding trial balance proofs.

Posting logic and account mapping translate subsystem detail into GL populations; ambiguous custody language obscures which engine owns residual FX.

Controllers defending period-end integrity must narrate both layers—custody assignments feeding populations versus ledger lens tying disclosures back to measured outcomes.

Controlled vocabulary

Conceptual comparison inside enterprise finance

Use this distinction during chart redesigns, shared service migrations, multi-ledger consolidations, and audits comparing subsidiary configurations to group methodology.

  1. Account currency — chart-level custody

    Determines reconciliation currency per account population, impacts foreign balance identification, and informs which lines enter period-end revaluation scope.

    Reference: Account currency state

  2. Ledger currency — entity measurement lens

    Hosts systemic balances after postings, allocations, and subsystem rolls resolve—where trial balance closure proves internal monetary coherence.

    Reference: Ledger currency state

Failure anatomy

Where confusion appears—and what breaks

Teams speak about “local currency” interchangeably for account assignments and ledger measurement—yet forensic obligations differ.

Weak mapping between subledger engines and GL obscures which custody population produced suspicious FX lines.

Accounting consequence: foreign-monetary-item classification errors distort unrealized versus realized pathways.

ERP consequence: duplicate or missing revaluation batches when populations disagree between account currency tags and ledger-close calendars.

Reporting consequence: CFO commentary cites ledger headlines without acknowledging foreign account populations still custodied differently upstream.

Custody interrogation

Custody questions—each side

Close forums should rehearse both questions before signing trial balance certifications.

  1. Account currency question

    Which chart assignments prove this balance reconciles inside named custody—and which migrations changed assignments without retrospective evidence?

    Reference: Account currency (defined)

  2. Ledger currency question

    Which ledger lens proves trial balance integrity before translation layers narrate outward visibility—and does functional alignment hold under stress scenarios?

    Reference: Ledger currency (defined)

Doctrine & mechanics

Framework continuity after this contrast

ERP ledger control vocabulary—posting logic, account mapping, subledger rolls—exists precisely because custody hops must remain deterministic between accounts and GL measurement.

Reference continuity

Configuration depth beneath ledger headlines

Foreign account currencies inside functional ledger shells explain many sophisticated FX diagnostics—name them before debating translation policy downstream.

Measurement stack

Custody assignments feed ledger measurement—they do not substitute it.

Close integrity demands both narratives reconciled to postings.

ERP reality

Engines expose account currency fields deliberately.

Bypassing them invites invisible fractures surfaced only at audit depth.

Audit replay

Independent reviewers trace populations before totals.

Collapsed vocabulary forces heroic spreadsheets replacing metadata discipline.

Practical control implication

Publish population maps tying accounts to ledger measurement

Document how foreign account populations roll into functional ledger closes; align revaluation runbooks to explicit custody tags; guard chart migrations with replay tests comparing trial balances pre- and post-change.

Risk if vocabulary collapses

Broken trial balance narratives and FX misclassification

Collapsed identities mislabel foreign monetary items, orphan subsystem batches, and expose leadership when auditors demand population-level proofs behind consolidated FX commentary.

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.