Repositora AI - Ind AS 118 / IFRS 18
Knowledge Base
Transition Reporting

Transition Comparatives: Designing As-Reported, Restated and Reclassified Scenarios

A structured approach to preserving prior-year as-reported information, recording transition adjustments and producing restated comparatives for IFRS 18 and proposed Ind AS 118.

Transition Comparatives: Designing As-Reported, Restated and Reclassified Scenarios knowledge base article illustration
15
series article
18
article sections
Ind AS 118 / IFRS 18
reporting focus
Short Summary

Executive perspective

Comparative information is one of the most underestimated parts of a presentation-standard transition. Finance teams often focus on the current-year statement layout and assume that the prior-year column can be rearranged later. In reality, the comparative needs a controlled bridge from what was previously reported to the new presentation. That bridge must preserve historical truth, identify reclassifications, support notes and reconcile every subtotal.

A transition fact model should distinguish prior year as previously reported, transition adjustment and prior year restated. The as-reported amount is immutable and linked to the approved prior report snapshot. Reclassifications or other transition changes are recorded separately. The restated amount is calculated, not overwritten. The transition report shows line item, previously reported amount, reclassification, restated amount and explanation.

This design supports IFRS 18 and proposed Ind AS 118, where operating, investing and financing categories can change the structure of profit or loss without changing total profit. It also supports enhanced disaggregation, specified expense schedules and MPM comparatives. Repositora should make these scenarios first-class facts rather than additional spreadsheet columns.

Preserve the as-reported baseline

The prior approved report is the authoritative record of what users saw. Its statement lines, note amounts, rule pack, template and rounding should be stored in an immutable snapshot. The transition project should never edit that snapshot.

Preservation matters because transition decisions evolve. A classification initially treated as operating may later be moved to investing after technical review. If the working comparative overwrites the original, finance loses the ability to explain the change and reproduce earlier analyses.

The baseline should include notes, not only face statements. A new disaggregation may require prior-year detail, and the team needs to know which data was originally disclosed and which was reconstructed. The source and confidence level of reconstructed information should be documented.

Define transition scenarios

The minimum scenarios are prior as reported, transition adjustment and prior restated. Current year should also have current statutory and new-basis views where dual reporting is used. Group reporting may add entity, consolidation and elimination layers.

Transition adjustments should be typed. Category reclassification moves income or expense between operating, investing and financing. Line-item disaggregation splits an existing total. Note reclassification changes disclosure rows. MPM comparative adjustment updates the reconciliation. Cash-flow transition changes the indirect-method starting point or classification configuration.

Typing helps review and reporting. A user can distinguish a pure presentation reclassification from a correction of error or change in accounting policy. The accounting implications differ, and the disclosure language should not blur them.

Each adjustment should identify affected concepts, amount, rationale, rule reference, source, preparer and reviewer. It should be possible to drill to the original prior-year accounts and schedules.

Mapping old lines to new concepts

The prior report may contain broad lines such as other income, finance costs or exceptional items. The transition team needs to map their components to new reporting concepts and categories. A line-level reclassification is insufficient if the line contains mixed items.

The process should begin with prior-year account-level data where available. Accounts are mapped to stable concepts, and mixed accounts are split using supporting schedules or controlled allocations. The mapped facts generate the new statement and notes.

Where account-level data is unavailable, the team may reconstruct detail from archived workbooks or ledger extracts. The source and limitations should be recorded. Material estimates or allocations require approval and may need specific disclosure consideration.

Mapping should be consistent with the current-year taxonomy. Creating a one-off comparative structure makes future roll-forward difficult. The same reporting concepts and category logic should apply across periods, with documented exceptions.

Profit-or-loss categories and subtotals

IFRS 18 requires operating, investing, financing, income taxes and discontinued operations categories and defined subtotals. The transition model assigns each prior-year concept to a category. Operating profit and profit before financing and income taxes are then recalculated.

The bridge should explain why subtotals changed. A disposal gain previously included above an existing operating subtotal may move to investing. Interest on a provision may move to financing. Total profit before tax may be unchanged, but operating profit changes materially.

Main-business-activity conclusions can affect comparatives. The group must determine whether the conclusion applies consistently to the prior period and whether entity and group conclusions differ. The evidence and approval should be retained.

Comparative category assignments should not be inferred solely from current-year mappings if business activities or account contents changed. The prior facts need their own review.

Notes and disaggregation

Transition often requires more detailed prior-year notes. If the new presentation disaggregates a material "other" line, comparative detail should be provided where required and practicable under the applicable transition provisions. The system should identify missing comparative dimensions.

Specified expense disclosures require prior-year nature-by-function data for applicable operating lines. Finance may need cost-centre reports, payroll data, depreciation registers and impairment schedules. This data collection should begin early because it may not be available after systems archive or change.

Revenue, segment, debt and ageing notes may also need reclassification to align with the new face presentation. Note adjustments should be stored separately and reconciled to the restated statement lines.

The role of the note is to explain the new structured summary. The comparative should not be forced into an old disclosure format if that obscures the transition.

MPM comparatives

An MPM note requires current and comparative amounts and a reconciliation to the most directly comparable specified subtotal. The group must reconstruct the prior-year measure using the same definition unless the measure or calculation changed.

The MPM register should record changes in name, formula or components and the reason. If management did not use the measure in the prior period, the disclosure approach needs technical assessment. Public communications should be inventoried by period.

Tax and NCI effects of each reconciling item need prior-year data. These amounts may come from tax calculations or approved allocations, and their sources should be retained. A spreadsheet plug is not sufficient evidence.

Cash-flow comparatives

The cash-flow transition should use a separate mapping. Profit-or-loss categories and cash-flow categories are related but not identical. The indirect method may begin with operating profit under IFRS 18, requiring a bridge from the prior starting point.

Interest and dividend classifications should follow the applicable amended cash-flow requirements and entity activity. The transition model should preserve the prior as-reported cash-flow statement and record reclassifications separately.

Closing cash must continue to reconcile to the balance sheet. Cash-flow changes should be tested independently from profit-or-loss transition because an apparently consistent category assumption can be wrong.

Review and evidence

Each material transition adjustment should have a technical conclusion, source data, calculation, preparer and reviewer. The reviewer should see the prior as-reported line, underlying accounts, proposed category, restated line and effect on subtotals and notes.

The transition should be run through the same validations as production reporting. Face-to-note reconciliation, statement of changes in equity, cash-flow closing cash, comparative completeness, MPM reconciliation and specified expense totals should all pass.

A transition pack should be versioned. Management may review several scenarios before finalising policy choices. Each version should record the rule pack and assumptions. Final approval freezes the adopted transition basis.

Application in Repositora

For one entity, Repositora can preserve current and prior-year facts and support a transition report. It provides mapping, adjustments, notes and validation.

At group level, Repositora adds entity scenarios, contributions, group overrides, consolidated transition adjustments and multi-level review. The report composer can generate current statutory, transition and final new-basis packs from the same data.

Roll-forward then carries the restated comparative into the new reporting period while preserving the original as-reported snapshot. This is essential for reproducibility.

Illustrative transition bridge

A company previously reported Rs 500 million of other income, including Rs 80 million deposit interest, Rs 120 million gain on investment disposal and Rs 300 million operating grants and service income. Under the transition analysis, the components are mapped separately.

The disposal gain and certain investment income move to the investing category, while operating grants remain operating. Operating profit decreases by the reclassified amount, and profit before financing and income taxes is recalculated. Total profit before tax remains unchanged.

The transition table shows the old line, reclassifications and new lines. The related other-income note is disaggregated, and comparative MPM reconciliation is updated. Every amount drills to prior-year accounts and approved allocations.

Transition Comparatives: Designing As-Reported, Restated and Reclassified Scenarios knowledge base article illustration
Transition Comparatives: Designing As-Reported, Restated and Reclassified Scenarios knowledge base article illustration

Implementation guidance and metrics

Start with a frozen prior-year dataset and signed report. Build the new taxonomy, map account-level data and identify missing dimensions. Prioritise material lines, mixed accounts, MPMs and specified expense data.

Run dry closes well before the effective period. Review differences with auditors and management. Resolve policy questions before document production and investor communication deadlines.

Useful metrics include unallocated prior-year value, transition adjustments by type, accounts supported only by estimates, unresolved category conclusions, missing comparative note fields, MPM items without tax or NCI effects and versions after approval. These metrics show the real state of readiness.

Closing perspective

Transition comparatives should be treated as a controlled reporting product, not a last-minute reformatting exercise. The as-reported baseline, adjustment layer and restated view must coexist. That structure preserves historical integrity and explains the effect of the new presentation.

For IFRS 18 and proposed Ind AS 118, the largest visible changes may be reclassifications rather than measurement. A rigorous comparative model ensures that new subtotals, notes and MPMs are supported by the same level of evidence as the current-year accounts.

Evidence architecture for implementation

A controlled process begins with an explicit inventory of the data objects that drive management-defined performance measure governance. For this subject, the core objects are public communication, MPM candidate, MPM definition, specified comparable subtotal, reconciliation item, tax-effect calculation, NCI-effect calculation, comparative amount, change explanation, and approval record. 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. Each MPM should link to the public communication in which it was used and the conclusion that it meets the definition. Each reconciling item should trace to approved financial facts, with separately supported tax and NCI effects. Each change in name, formula or composition should show the comparative consequence and approved explanation. For management-defined performance measure 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

A practical design workshop for management-defined performance measure 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 finance identifies MPMs only from the annual report and misses other public communications and investor-relations materials introduce or rename a measure after the financial-statement note is substantially complete. 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 register of publicly communicated measures to the standalone foundation and introduce group-wide public-communication inventory and MPM candidate screening 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.

Questions for finance leadership

Implementation quality often deteriorates through apparently convenient shortcuts. Resist assuming all alternative performance measures are MPMs or that none are. Avoid using labels rather than public-use evidence to determine the population. Do not rely on maintaining the reconciliation only in the report document. Challenge applying one tax rate without analysing the underlying item. Treat as a warning sign allowing communications teams to change a measure outside the reporting workflow. The recurring pattern is that data, judgment or approval is moved outside the controlled model to meet a deadline, and the workaround becomes the next period's starting point.

  1. Who is accountable when finance identifies MPMs only from the annual report and misses other public communications?
  2. Can the team demonstrate, for a complete population, that each mpm should link to the public communication in which it was used and the conclusion that it meets the definition?
  3. What tolerance and escalation should govern confirmed MPMs without approved formula owners?
  4. Which owner maintains the definition and period version of public communication?
  5. Which foundational capability must be stable before the group introduces group-wide public-communication inventory and MPM candidate screening?

Technical Source Note

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.

Suggested Website CTA

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

Contact

Take this reporting issue into a focused implementation conversation.

Start with this article topic, or move straight into entity packages, mapping, consolidation evidence, group notes, transition views, and final report governance.

Entity-package design, mappings, and group-close hand-offs
Consolidation evidence, note logic, and transition reporting scenarios
Maker-checker approval, report composition, and immutable output governance
Transition Comparatives: Designing As-Reported, Restated and Reclassified Scenarios | Repositora AI - Ind AS 118 / IFRS 18