Financial reporting and consolidation
Financial report, consolidation perimeter, transformation rules and elimination of intragroup transactions. Common definitions of the report and the run are reused.
Bundle → Layer → Finding → Questions Filled
3 bundles · 4 layers · 5 findings · 10 questions
Perimeter Which entities are consolidated, and on what basis.
Consolidation scope
The perimeter version and its basis.
Scope version
Entities included, with the basis for inclusion.
- Which entities does the perimeter version include, and on what basis?
- Does the management perimeter differ from the accounting perimeter?
Perimeter change
Entities entering or leaving the group.
- Which entities entered or left the perimeter in the period?
- Was inclusion based on control rather than on shared owners alone?
Consolidation How group figures are produced.
Consolidation run
A run pinned to methodology, perimeter and data.
Run record
Methodology, perimeter version and knowledge date.
- Which methodology and perimeter version did the run use?
- Can the report be reproduced as of a past knowledge date?
Eliminations
Intragroup transactions removed with paired justification.
Elimination entry
Paired evidence from both sides of an intragroup transaction.
- Which intragroup transaction is eliminated, and what evidence does each side give?
- Do the two sides agree, and how is any mismatch handled?
Statements Published statements and their restatements.
Financial statements
Editions of statements and restatements.
Statement edition
A published edition kept after restatement.
- Which edition of the statement was published, and when?
- Is a restated edition shown alongside the original?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseFIN
- Industry
- Cross-industry
- Tags
- EM-FIN-04W3subjectFinancialStatementConsolidationScopeConsolidationRunEliminationEntry
What it is Filled
Financial report, consolidation perimeter, transformation rules and elimination of intragroup transactions. Common definitions of the report and the run are reused.
Why it exists Filled
Financial report, consolidation perimeter, transformation rules and elimination of intragroup transactions. Common definitions of the report and the run are reused.
Distinguishing features Filled
- A consolidation pins the methodology and the perimeter version it used.
- Each elimination is backed by matching evidence from both sides of the intragroup transaction.
- Inclusion in a group rests on control or other defined criteria, not on shared owners alone.
- A restated edition is added to the record and does not erase the original publication.
What robots and AI may and may not do Filled
Must not
- Include a company in a group report only because it shares owners with group members.
- Eliminate an intragroup transaction without evidence from both sides.
- Overwrite a published statement with a restated one.
- Publish statements before the responsible officers approve them.
Only with a human decision
- Approving and publishing financial statements.
- Changing the consolidation perimeter or methodology.
May
- Run consolidations and record methodology, perimeter and knowledge date.
- Match intragroup transactions and report unmatched balances.
- Explain differences between management and statutory perimeters.
Moral aspects Filled
- Investors, lenders and employees rely on group statements for decisions that affect them.
- Misstated consolidations can hide losses or liabilities and cause financial harm.
Who is affected
- Investors and lenders
- Auditors and regulators
- Group companies and their staff
Owners Filled
Steward
The chief financial officer or finance lead who answers for books, budgets and reporting.
Master systems
- ERP
- Accounting system
- Banking system
- Billing system
- FinOps platform
Links to other meta-models Filled
references
- WM-ECO-018 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by reporting entity, period, perimeter version and edition; group entities by LEI where one exists.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A consolidated statement names a perimeter, a methodology, eliminations and an edition.
- Often confused with a single entity's statements or with management reports.
Capabilities and actions required Filled
- Past consolidations can be reproduced as of their knowledge date.
- Intragroup mismatches can be detected before publication.
Hazards and failure modes required Filled
- Wrong perimeters that include or exclude entities incorrectly.
- Unsupported eliminations that hide intragroup balances.
- Lost original editions after restatement.
Standards and interfaces required Filled
- XBRL from XBRL International for financial statements.
- IFRS Accounting Taxonomy from the IFRS Foundation.
- GLEIF Legal Entity Identifier (ISO 17442) for group entities.
Context of use required Filled
- Used for group financial reporting, management reporting and audit.
- Listed groups in many jurisdictions report under IFRS and must file tagged statements.
Sources Filled
- FIBO: instruments, parties, transactions
- UBL/FOCUS: documents and costs; choose by contour
- XBRL and ERP/accounting-policy practice: books, periods, recognition and disclosure
- IFRS Foundation: Issued Standards - Checked live (HTTP 200) on 2026-10-07.
- XBRL Specifications - Checked live (HTTP 200) on 2026-10-07.
- EDM Council Financial Industry Business Ontology (FIBO) - Checked live (HTTP 200) on 2026-10-07.
Open questions
- When do the management and accounting perimeters differ?
- How to reproduce a report as of a past knowledge date?
- How to justify the elimination of a transaction?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-fin-04/brief.json, ver-cy/world-models/card-supplements/em-fin-04.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.