State position
Each term belongs to a different control layer.
The distinction is strongest when mapped to the CCY State Chain rather than reduced to screen labels.
Comparison - State 02 versus State 04
Account Currency vs Transaction Currency
Professionals searching for account currency vs transaction currency are usually trying to separate invoice or contract denomination from the ERP custody setting that governs balances. Transaction currency identifies the monetary denomination of the obligation at State 02; account currency identifies how that balance is held, reconciled, and controlled inside ERP custody at State 04. The distinction matters because reconciliation scope, FX populations, and audit replay can break even when both fields display the same ISO code.
Governing distinction
Transaction currency is obligation denomination. Account currency is balance custody.
AccountCcy.com comparison reference
Search intent answer
Obligation identity versus account custody
Transaction currency belongs to the event that creates a receivable, payable, order, invoice, or contract measurement. It asks which currency the obligation was born in before finance absorbs it into controlled books.
Account currency belongs to the ERP and ledger custody layer. It asks which currency assignment governs balance maintenance, reconciliation, revaluation eligibility, and downstream reporting lineage.
Search intent is high because the two concepts often appear together in ERP screens. AccountCcy treats them as adjacent currency states, not synonyms.
Structured comparison
Side-by-side distinction
Use this section as the quick comparison layer: what each term means, where it sits in the currency-state chain, and which evidence proves it.
Transaction currency
State 02. The denomination of the recorded obligation or commercial event before it is absorbed into account custody.
Reference: State 02
Account currency
State 04. The custody assignment that controls how balances live inside accounts, reconciliations, and revaluation populations.
Reference: State 04
ERP, close, reconciliation, reporting
Operational consequences of the distinction
ERP consequence: document currency and account currency can be stored in different fields, owned by different configuration logic, and tested by different evidence.
Close consequence: open-item populations may be scoped by account custody even when invoice denomination drives the commercial explanation.
Reconciliation consequence: matching totals is not enough if reviewers cannot trace which currency identity governed the balance.
Reporting consequence: FX commentary can drift when transaction wording is used to explain account-level measurement.
Risk boundary
Where confusion creates risk
Confusion creates risk when invoice currency is treated as proof of ledger custody, when account assignments change during migrations, or when foreign monetary item populations are selected by narrative rather than configuration evidence.
The practical failure pattern is simple: the business can explain what was billed, but finance cannot prove how that billed amount became a controlled balance.
Custody questions
Questions each concept must answer
These questions are reference prompts for evidence discipline. They are not audit, accounting, tax, legal, treasury, or ERP implementation advice.
Transaction currency custody question: which source artifact proves the obligation denomination before posting?
Account currency custody question: which ERP setting proves the currency in which the balance is maintained and reconciled?
Bridge question: can a reviewer follow the event from document currency to account currency without an informal spreadsheet?
Related references
Glossary, state, and methodology links
The related references keep the comparison inside AccountCcy.com terminology and make the trust boundary explicit. The methodology link explains claim limits and source discipline.
FAQ
Practical comparison questions
Is transaction currency the same as account currency? No. They can share a code, but transaction currency names the obligation while account currency names ERP custody.
Which one controls reconciliation? Account currency normally governs balance custody and reconciliation scope; transaction currency explains the originating obligation.
Why does the distinction matter for FX? FX populations depend on controlled custody and measurement, not only on invoice wording.
Reference continuity
Keep comparison intent inside the custody chain
The purpose of this page is to strengthen professional search intent while preserving AccountCcy.com claim discipline and state architecture.
Evidence
Different evidence proves different currency identities.
Configuration, payment, ledger, translation, and consolidation artifacts should not be substituted for each other.
Trust boundary
The page is a reference framework, not advice.
The methodology page defines claim limits, source boundaries, and publication discipline.
Practical control implication
Separate document denomination from account custody evidence
Maintain a visible bridge from source documents to account-currency assignments, especially during migrations, chart changes, and period-end FX population selection.
Risk if vocabulary collapses
Obligation wording mistaken for custody proof
The page strengthens comparison search intent by showing why contract or invoice denomination cannot replace ERP custody evidence.
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.