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 06 versus State 07
Professionals searching for reporting currency vs consolidation currency are usually separating entity-level presentation from group-level assembly. Reporting currency presents measured results at State 06; consolidation currency assembles multiple entity packages, eliminations, ownership effects, and group reporting at State 07. The distinction matters because a subsidiary reporting pack is not the same as a consolidated currency layer.
Governing distinction
AccountCcy.com comparison reference
Search intent answer
Reporting currency belongs to the entity or reporting package that presents measured results to a defined audience.
Consolidation currency belongs to the group process that combines entities, applies eliminations, handles ownership changes, and produces consolidated statements.
The two states are adjacent, but consolidation adds governance that does not exist inside a single reporting pack.
Structured comparison
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.
ERP, close, reconciliation, reporting
ERP consequence: consolidation systems may reshape, eliminate, or reclassify submitted reporting packages.
Close consequence: entity close and group close require separate evidence and timing controls.
Reconciliation consequence: consolidation bridges must tie entity reporting submissions to group adjustments.
Reporting consequence: group FX and elimination narratives weaken when entity reporting currency is treated as the final consolidated lens.
Risk boundary
Confusion creates risk when entity reporting packs are summed as if they were already consolidated truth.
The failure pattern is a group statement that cannot explain eliminations, ownership effects, or consolidation adjustments by source entity.
Custody questions
These questions are reference prompts for evidence discipline. They are not audit, accounting, tax, legal, treasury, or ERP implementation advice.
Reporting currency custody question: which entity package proves how measured results were presented?
Consolidation currency custody question: which group bridge proves eliminations, ownership effects, and consolidation adjustments?
Bridge question: can each consolidated line be traced back to entity packages and approved consolidation journals?
Related references
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
Is consolidation currency just group reporting currency? It is the group assembly lens, which includes elimination and ownership mechanics beyond entity presentation.
Can reporting currency and consolidation currency be the same code? Yes, but the governance layer is different.
Where does risk appear? In eliminations, intercompany balances, ownership changes, and group-level FX explanations.
Reference continuity
The purpose of this page is to strengthen professional search intent while preserving AccountCcy.com claim discipline and state architecture.
State position
The distinction is strongest when mapped to the CCY State Chain rather than reduced to screen labels.
Evidence
Configuration, payment, ledger, translation, and consolidation artifacts should not be substituted for each other.
Trust boundary
The methodology page defines claim limits, source boundaries, and publication discipline.
Practical control implication
Maintain bridges from entity reporting submissions to consolidation adjustments, eliminations, ownership entries, and group reporting lines.
Risk if vocabulary collapses
The risk is a consolidated narrative that cannot be reconstructed from entity submissions and group adjustment evidence.
Evidence Discipline
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.