A consolidation journal can remove the correct amount from the balance sheet or statement of profit and loss and still leave the notes wrong. This happens because face statements present totals, while notes present dimensions. An intercompany receivable elimination may remove Rs 100 million from trade receivables, but the ageing note still contains that amount across several buckets. An intra-group sale may be eliminated from revenue, while the revenue disaggregation note continues to show it by product or geography.
Note-level eliminations address this dimensional gap. They adjust structured disclosure facts by entity, counterparty, ageing bucket, segment, maturity, asset class or other note dimension. They are linked to the relevant statement journal where possible and require an approved explanation where the amounts differ. The final note then reconciles to the consolidated face line and accurately reflects the group as a single economic entity.
The need becomes more significant under IFRS 18 and proposed Ind AS 118. Specified expense tables, MPM reconciliations and disaggregated "other" items use dimensions that are not always present in statement journals. A controlled note-adjustment layer is therefore a core part of statutory group reporting, not an optional workaround.
Statement journals are designed around accounts and reporting concepts. A receivable elimination may debit payables and credit receivables, identifying the two entities and the amount. The ageing note, however, needs to know how much of the receivable sits in each ageing bucket. Unless that dimension is carried into the journal or provided through a separate adjustment, the note cannot be corrected automatically.
The same issue appears in revenue. A sales elimination may identify revenue and cost of sales but not product, customer type, geography or segment. A segment note may require elimination between reportable segments, while external revenue remains. The group needs a method to allocate the elimination to the relevant disclosure rows.
PPE and intangible notes can also differ from face statements. Acquisition accounting or uniform-policy adjustments may affect opening balance, additions, disposals, depreciation or impairment. Posting only a closing-balance journal leaves the movement table internally inconsistent.
The conclusion is that a face amount and a note schedule are related but not identical data structures. The reporting model must preserve that relationship explicitly.
Intra-group balance eliminations remove receivables, payables, loans and accrued amounts from ageing, maturity and counterparty tables. The adjustment should use entity and counterparty dimensions and normally agree to the statement elimination.
Intra-group income and expense eliminations remove sales, purchases, interest, fees, royalties and other transactions from revenue, expense and segment notes. The allocation may require product, function or geography. The group should use source schedules or a documented allocation rather than an arbitrary plug.
Related-party eliminations distinguish transactions within the consolidated group from relationships that remain reportable. A subsidiary transaction with the parent may be eliminated in the consolidated accounts, while transactions with associates, key management or other related parties remain. Stable party identifiers are essential.
Movement-note adjustments affect PPE, intangibles, goodwill, provisions, equity and other roll-forwards. They may record acquisition accounting, disposal, impairment or group policy effects in the correct movement category.
Maturity and liquidity adjustments reclassify amounts between buckets or remove intra-group financing. Because these notes support risk analysis, the adjustment basis should be particularly clear.
A note adjustment should identify the reporting pack, note, field, dimensions, current or comparative period, amount, reason and source. It should specify whether it links to a consolidation journal, another schedule or a group-only conclusion. The preparer and reviewer are recorded, and only posted adjustments affect the final note.
Statuses can mirror journals: draft, submitted, approved, posted and reversed. A note adjustment should not be edited after posting; a change creates a new version or reversal. The final report snapshot retains the exact posted set.
The system should validate that adjustment dimensions exist in the note template and that the resulting totals remain coherent. A negative amount in an ageing bucket may indicate an incorrect allocation. Opening, movement and closing schedules should recalculate after adjustment.
Material note adjustments should require maker-checker approval. High-risk adjustments, such as goodwill, NCI or MPM tax effects, may require technical accounting review.
The strongest control is a direct link between the note adjustment and the relevant statement journal. The link allows the system to compare amounts and identify expected note impacts. A journal can have multiple linked note adjustments where it affects several disclosures.
The amounts do not always have to agree. A statement journal may include a component outside the note's scope, or the note may be presented at a different rounding level. When the linked totals differ, the preparer should provide a reason and the reviewer should approve it.
Unlinked note adjustments should appear on an exception dashboard. Some will be legitimate group-only changes, such as refining a disclosure category without changing the statement. Others may indicate that a note is being forced to agree after an incomplete consolidation journal.
The relationship should work in both directions. From the journal, the reviewer sees affected notes. From the note, the reviewer sees linked journals and explanations. This reduces the risk that an accounting change is reflected in one part of the report but not another.
Allocation should follow the best available source data. If entity schedules identify ageing buckets and counterparties, the elimination can be applied directly. If a revenue journal lacks product detail, the group may use transaction schedules or entity submissions. Only when detailed data is unavailable should a documented allocation basis be used.
The allocation should reconcile at full precision. For example, a Rs 100 million receivable elimination allocated across four ageing buckets must sum to Rs 100 million. Rounding is applied during presentation, and any displayed rounding adjustment should be controlled.
Allocation bases should be stable and reviewed. A proportional allocation based on gross balances may be reasonable in one context and misleading in another. The system can preserve the basis, input amounts and approval for repeatability.
AI may suggest an allocation based on patterns, but the result must remain a suggestion. Note eliminations affect statutory disclosures and require human validation.
Current-year and comparative note adjustments should be stored separately. A prior-year reclassification for IFRS 18 or proposed Ind AS 118 transition belongs to a restated comparative scenario, not to the prior as-reported snapshot.
The transition bridge should identify the previously reported note amount, reclassification, restated amount and explanation. If a note is newly required or restructured, the system should preserve the original comparative data and document how it was transformed.
Comparative consistency checks can identify current-year detail without corresponding prior-year information, changed bucket definitions and eliminations applied only to one period. These exceptions require review rather than automatic correction.
Specified expenses by nature may be collected by operating function. A group journal reclassifying expenses between functions should update the nature-by-function table. A statement-only reclassification would otherwise leave the note inconsistent.
MPM reconciliations may include group-only adjustments, tax effects and NCI effects. These are disclosure facts with their own dimensions and sources. They should be controlled like note adjustments, although they may not correspond to accounting journals.
Aggregation and disaggregation review may lead to a new note category without changing the face line. The adjustment is a reclassification within the note and should preserve the total. The reason should link to the materiality assessment and reviewer conclusion.
Profit-or-loss category changes can affect revenue or expense notes and defined subtotals. The group should ensure that note labels and classifications reflect the approved category assignments.
For a single company, Repositora supports note-only adjustments where detailed schedules need correction or allocation. The adjustment remains traceable and subject to review.
At group level, Repositora adds note eliminations, links to consolidation journals, entity and counterparty dimensions and cross-note validation. The same adjustment architecture supports pre-consolidated mode and the basic consolidation workbench.
The report composer should use final posted note facts. Manual editing in Word or PDF after generation should not become an alternative adjustment process. If a note changes, the structured fact and report version should change together.
A group has Rs 200 million of intra-group trade receivables. The statement elimination journal removes the full amount. Entity ageing schedules show Rs 140 million current, Rs 40 million 31-60 days and Rs 20 million 61-90 days.
The note adjustment removes those amounts from the respective buckets. It links to the Rs 200 million journal and reconciles exactly. The related-party note uses party identifiers to remove transactions within the consolidated group while retaining transactions with an associate.
The final balance sheet and ageing note agree. Drill-down shows entity submissions, the statement journal, note adjustment, allocation by bucket and reviewer approval. Without the note layer, the face amount would be correct but the disclosure materially overstated.
Reviewers should ask whether every material statement journal has been assessed for note impact, whether note adjustments use the best available dimensions, whether linked amounts reconcile, and whether unlinked adjustments are justified. They should also assess whether current and comparative treatments are consistent and whether the final note retains material information.
A note adjustment should not be approved merely because it makes the table agree. The reviewer needs to understand the source, classification and allocation. The goal is faithful disclosure, not arithmetic closure.
Useful analytics include note adjustments by type and value, unlinked adjustments, differences from linked journals, repeated manual allocations, late adjustments after note approval and report versions caused by note changes. High volumes may indicate that entity schedules or journal dimensions need improvement.
Inventory common statement eliminations and identify their note impacts. Define which dimensions should be collected in entity packages and which can be supplied at group. Build standard allocation and evidence requirements for high-volume areas such as receivables, revenue and debt.
Pilot the process on signed historical accounts. Recreate the face eliminations and test whether the note schedules can be reproduced without manual document edits. Differences reveal missing dimensions and uncontrolled assumptions.
Train preparers and reviewers to think in both statement and note terms. A consolidation journal is not complete until all affected disclosures have been assessed. This mindset change is as important as the software feature.
Statement eliminations create the consolidated totals; note-level eliminations create the consolidated explanation. Both are necessary. A group that controls only the face statements may still publish ageing, segment, revenue or related-party disclosures that contain intra-group amounts.
A structured note-adjustment layer makes the relationship visible and testable. It supports current statutory reporting and the more demanding disclosure architecture of IFRS 18 and proposed Ind AS 118. The result is a group report in which the statements and notes tell the same, reconciled story.
A controlled process begins with an explicit inventory of the data objects that drive main-business-activity assessment and category governance. For this subject, the core objects are main-business-activity assessment, assessment evidence, reporting concept, category assignment, entity exception, group override, classification rationale, mixed-account allocation, rule-pack version, and review approval. Each should have a business definition, source, owner, effective period, version, status and relationship to the reporting output. That metadata is what allows the team to distinguish a valid change in policy or business activity from an unexplained movement in a spreadsheet.
Evidence should be captured as part of the workflow rather than attached after the reviewer asks for it. The activity conclusion should show the evidence evaluated and the reporting level to which it applies. Each material category assignment should link to the concept population, rule, rationale and reviewer. Each period-on-period classification change should explain whether it arose from facts, business activity, interpretation or rule-pack change. For main-business-activity assessment and category governance, the reviewer should be able to move from the reported result back through the decision, rule or mapping to the complete source population without changing systems or requesting an offline reconstruction.
A practical design workshop for main-business-activity assessment and category governance should use one completed reporting period and one difficult entity or disclosure population. Bring together group reporting, entity finance, accounting policy, tax, treasury, investor relations, internal audit, external-audit liaison and technology as relevant. Reconstruct the path from source file or manual schedule to the final statement, note and approval. Mark every copied value, mixed account, offline adjustment, unversioned judgment, repeated reviewer query and late document edit. The purpose is to identify where the statutory fact or conclusion leaves the controlled model.
Test the proposed design against main business activity is selected from a dropdown without evidence or accounting-policy review and a business-model change affects category assignments but the prior-year conclusion is rolled forward without review. For each break, agree the accountable owner, preventive or detective control, source evidence, materiality or tolerance, reviewer, escalation route, affected reports and acceptance test. Assign standalone questionnaire and accounting-policy conclusion to the standalone foundation and introduce entity and group assessments with inherited defaults and controlled overrides only after the underlying concepts and evidence are stable. The output should be a prioritised backlog with rule, data, workflow and report-design decisions-not a generic list of desired features.
Official materials checked on 25 June 2026: IFRS Foundation - IFRS 18; issued IFRS 18 text; IFRIC Update - March 2026; ICAI Accounting Standards Board.
This article is educational and does not replace applicable standards, final MCA notifications, professional advice or entity-specific judgment. Product capabilities should be verified against the approved release scope before publication.
Explore how Repositora can connect entity submissions, group reporting, statutory notes, source lineage and Ind AS 118 transition readiness across standalone, group and transition reporting. Visit repositora.com
