Configuration
Currency behavior lives in settings.
Account currency must be proved through extracts and approvals, not inferred from reports.
ERP Reference Architecture
Account Currency in ERP Systems
Account currency in ERP systems is the governed account-level custody setting that shapes postings, reconciliation scope, FX revaluation populations, ledger measurement, reporting translation, and audit reconstruction. It is not a cosmetic display label and not a substitute for professional configuration judgment.
ERP custody thesis
ERP account currency is where monetary identity becomes executable accounting behavior.
Configuration is evidence, not background.
AccountCcy.com ERP Reference Layer
Reference posture
Treat ERP currency behavior as custody architecture.
ERP systems do not merely store currency labels. They operationalize account-level monetary custody through chart settings, subledger behavior, posting rules, revaluation eligibility, reporting extracts, and control logs.
This page avoids vendor-specific instructions. It defines the evidence and governance questions an enterprise finance team should ask before relying on account currency configuration as a source of monetary truth.
The correct posture is not to assume the ERP is right. The correct posture is to prove that live configuration matches policy, ownership, reconciliation design, and downstream assurance needs.
Architecture
The ERP layers that turn account currency into control behavior
Chart configuration assigns the account-level currency state.
Subledger integration decides whether transaction and settlement currencies survive ingestion.
Posting logic routes obligations, settlements, revaluation entries, and adjustments into governed accounts.
Currency master data constrains precision, activation, rounding, and allowed denominations.
Close controls freeze configuration snapshots so later audit work can replay the period as it actually operated.
State 04 custody
Account currency defines the maintained balance context that downstream ledger and reporting layers inherit.
Reference: Account Currency state
ERP configuration control
Configuration must be owned, reviewed, and evidenced before close outputs are trusted.
Reference: ERP currency configuration control
Diagnostic output
The Currency State Diagnostic turns configuration questions into a local maturity signal.
Reference: Currency State Diagnostic
Evidence map
Minimum evidence for ERP account currency defensibility
A defensible ERP posture should retain: account master extracts, configuration approval logs, policy matrices, mapping tables, revaluation run logs, exception reports, and period-specific snapshots.
The evidence must show not only what the configuration is, but why it exists, who approved it, which populations it affects, and how it changed across periods.
Governance interrogation
ERP account currency control questions
Does the account master extract match the approved account currency policy matrix?
Can configuration changes be tied to approval evidence and migration testing?
Do subledger interfaces preserve transaction and settlement currency metadata?
Are revaluation populations derived from configuration rather than manual recollection?
Does the close archive include the configuration snapshot used for that period?
Can auditors reconstruct account currency behavior without asking systems teams to recreate history?
Reference graph
ERP configuration is the operational surface of account currency control.
This page bridges AccountCcy doctrine into practical ERP evidence without becoming vendor-specific implementation advice.
Integration
Interfaces can erase custody metadata.
Subledger and middleware behavior must preserve currency-state lineage.
Close
Period snapshots protect audit replay.
The close archive should show the configuration that governed the period.
Control logic
Freeze account currency configuration as evidence.
Every material close should preserve account master extracts, mapping versions, revaluation parameters, and owner sign-offs.
Risk if weak
ERP confidence without replayable evidence.
Teams may trust the system while losing the ability to prove which currency rules actually governed postings and balances.
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.