Indian companies preparing for new presentation requirements face a timing problem. IFRS 18 has been issued and is effective for annual periods beginning on or after 1 January 2027. ICAI issued an exposure draft of Ind AS 118 with a proposed Indian effective date, but the proposed standard should not be treated as notified until the Ministry of Corporate Affairs completes the process. Finance teams therefore need to prepare for change without replacing the current statutory basis prematurely.
Dual-basis reporting solves this by separating financial facts from presentation rules. The same approved trial balances, schedules and adjustments can generate current notified Ind AS and Schedule III statements, a proposed Ind AS 118 transition view and an IFRS 18 view. Each output displays the rule pack used. Differences are explained through category assignments, reclassifications, transition adjustments and disclosure requirements rather than through duplicated spreadsheets.
This architecture reduces implementation risk. It allows finance to test data, classifications, subtotals, MPMs and comparative impacts early while continuing to produce the legally applicable report. When final Indian requirements are notified, the rule pack can be updated and compared with the transition pack. The underlying fact model remains stable.
A financial fact represents an amount with entity, period, scenario, currency, reporting concept, source and adjustment layer. It should not be defined by where it appears in a particular report. A trade receivable fact remains a trade receivable even if the note number or face ordering changes.
Rules determine classification, aggregation, calculations and applicability. Current Ind AS and Schedule III rules produce the existing statutory presentation. IFRS 18 rules classify income and expenses into operating, investing, financing, income taxes and discontinued operations and calculate defined subtotals. A proposed Ind AS 118 pack applies the exposure-draft logic and Indian context for transition analysis.
Templates determine layout, labels, note order and document style. They draw from concepts and rules. Keeping templates separate prevents regulatory logic from becoming embedded in cell references or manually edited documents.
The report snapshot combines the data version, rule-pack version, calculation engine and template. That combination makes each output reproducible and clearly identifies its basis.
Current statutory mode applies notified Ind AS, Schedule III Division II and applicable Companies Act disclosures. It remains the authoritative Indian reporting basis until new requirements are notified and effective. The mode controls statement formats, comparative columns, note cross-references, rounding and disclosure checklist.
Preparing for Ind AS 118 should not change current statutory classifications unless another notified requirement supports the change. Transition work belongs in a separate scenario or report view. This protects the integrity of signed financial statements and avoids confusing proposed requirements with current law.
The system should allow current mode to coexist with group IFRS reporting. An Indian subsidiary may submit facts once and produce local statutory and group IFRS views, subject to any measurement adjustments required by the group basis. Presentation differences remain distinguishable from recognition or measurement differences.
IFRS 18 mode applies the issued international standard. Income and expense concepts receive category assignments and the statement presents operating profit and profit before financing and income taxes, subject to the standard's requirements and specified business activities.
The mode also activates MPM disclosures, aggregation and disaggregation review, specified expenses by nature for function-based operating lines, and amended cash-flow presentation. It may reorder lines and notes while retaining the same total profit and underlying measurements unless other IFRS differences exist.
The group should document main-business-activity conclusions at entity and consolidated levels. Classification exceptions and group overrides are stored with rationale and approval. This is essential because the same account label can have different classification depending on the entity's activities.
The transition mode is clearly labelled as proposed or readiness reporting. It applies the ICAI exposure-draft architecture and any controlled internal interpretations. It should not be represented as a notified statutory pack.
The mode supports category assignments, defined subtotals, MPM register, specified expense schedules, aggregation review and comparative reclassification. It can produce an impact report showing current presentation, reclassification and proposed presentation.
When the final Indian standard is notified, the transition pack is not overwritten. A new notified pack is created and compared with it. Differences are assigned to owners and tested. This preserves prior readiness work and makes changes visible.
At minimum, the fact model should support current year, prior year as reported, prior year restated, transition adjustment, entity adjustment, consolidation adjustment, elimination and final consolidated. Reporting-basis dimensions identify current Ind AS, proposed Ind AS 118 and IFRS 18 views.
A presentation reclassification should not alter the prior as-reported fact. It creates a transition adjustment or changes the classification rule in the restated scenario. The bridge shows the effect on each line and subtotal.
Measurement differences, if any, should remain separate from presentation differences. For an Indian entity reporting to an IFRS parent, group accounting adjustments may change amounts. Those adjustments should be identified as basis adjustments, while IFRS 18 presentation then applies to the adjusted facts.
Scenario discipline prevents a common problem: using a single "prior year" column that is silently overwritten as transition decisions evolve. Historical truth and restated presentation both need to be retained.
Each income and expense concept stores category, relevant rule, main-business-activity effect, entity exception, group override, rationale, preparer, reviewer and rule-pack version. Unclassified concepts and mixed accounts are flagged.
Subtotals are calculated from category assignments, not hard-coded report rows. Operating profit comprises the operating category. Profit before financing and income taxes reflects operating and investing categories, subject to the standard's provisions. Profit before tax and total profit remain reconciled.
A category change can materially alter operating profit while leaving total profit unchanged. The transition report should explain this clearly. Reviewers should be able to drill from the subtotal to concepts, entities, accounts and transition adjustments.
An MPM register can exist independently of the output basis, but disclosure requirements are activated in IFRS 18 and proposed Ind AS 118 modes. The register captures measures used in public communications, formulas, components, comparable specified subtotals, reconciliations, tax and NCI effects and changes.
Current statutory mode may still track alternative performance measures for governance, even if the specific MPM note is not required. This gives finance an early inventory and supports consistency between investor communications and financial statements.
The same structured reconciliation can be rendered differently by rule pack. This avoids maintaining a separate spreadsheet for the transition note.
Dual-basis reporting needs side-by-side comparison. Users should see current statement line, proposed category, IFRS 18 line, amount and explanation. The report composer can generate separate packs or a transition report.
Note numbers and cross-references may differ between bases. Because references are generated dynamically from note objects, moving or suppressing a note in one view does not break the other. Manual document editing would make dual-basis maintenance difficult.
Narrative policies should also be versioned by basis. A current Ind AS policy may be carried forward, while a transition note explains presentation changes. Controlled variables keep amounts aligned across views.
Each report must display the reporting basis and rule-pack version. Draft transition outputs should have an appropriate watermark or cover note to prevent accidental use as statutory accounts. Access and approval rights may differ by mode.
Material classification changes, main-business-activity conclusions, MPM definitions and applicability overrides require maker-checker approval. The system should block finalisation if material concepts remain unclassified or critical transition validations are unresolved.
A regulatory content owner monitors official developments. The organisation should establish a cut-off date for each reporting cycle and a process for late changes. Publication language should be reviewed so that proposed Indian requirements are not described as mandatory before notification.
For a single entity, Repositora can support current statutory mode and a basic transition view. Stable reporting concepts, mapping, adjustments, notes and validations provide the necessary foundation.
Across entities and consolidated packs, Repositora expands dual-basis reporting. Entity-level assignments are aggregated, group overrides are controlled, comparative scenarios are maintained and report snapshots identify the basis. The same data supports standalone, pre-consolidated and basic workbench modes.
The architecture turns regulatory uncertainty into manageable versioning. Finance can prepare and test without waiting for the last possible moment, while the product remains honest about what is current and what is proposed.
An Indian parent prepares current Ind AS standalone and consolidated accounts and reports IFRS information to a foreign investor. The group uploads one set of accepted entity facts and consolidation adjustments.
Current statutory mode generates Schedule III Division II statements. IFRS 18 mode classifies income and expenses and calculates operating profit. The proposed Ind AS 118 mode uses the exposure-draft rule pack and produces a transition bridge. A material disposal gain moves from "other income" in the current presentation to the investing category in the transition views.
The group MPM register reconciles adjusted operating profit to operating profit. The final statutory pack is approved under current Ind AS, while transition packs remain draft and clearly labelled. When the Indian standard is notified, the new pack is compared with the exposure-draft version.
Begin with a stable reporting concept taxonomy and preserve current statutory production. Build the transition view as a parallel layer. Classify material income and expense concepts, document main-business-activity conclusions and inventory public performance measures.
Run historical data through both bases and compare results. Focus on classification, note data and document changes rather than only the face statement. Involve auditors and investor relations early because MPMs and public communications cross organisational boundaries.
Useful metrics include unclassified value, mixed-category accounts, group overrides, transition adjustments, unresolved MPMs, rule-pack changes and differences between proposed and final content. These measures show readiness without confusing it with statutory compliance.
Dual-basis reporting allows finance to move early and safely. It preserves the current statutory report, creates a controlled readiness environment and avoids duplicating data in disconnected spreadsheets. The rule pack-not the source balance-determines how the same facts are presented.
For Repositora, this capability is a major differentiator. It connects regulatory content, structured facts, workflow and document production. When the reporting basis changes, the organisation can explain the impact, update the rules and reproduce every version.
A controlled process begins with an explicit inventory of the data objects that drive defined subtotals and calculation dependencies. For this subject, the core objects are financial fact, reporting concept, category assignment, calculation node, dependency edge, scenario, rule-pack version, rounding policy, validation result, and report line. 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 subtotal should expose its formula, contributing concepts, adjustment layers and scenario. Each change in a subtotal should be explainable through changed facts, classifications or rule versions. Each rendered amount should reconcile to the full-precision stored calculation and documented rounding policy. For defined subtotals and calculation dependencies, 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 defined subtotals and calculation dependencies 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 defined subtotals are calculated through fixed spreadsheet row ranges and a manual subtotal overwrite bypasses category assignments and downstream validations. 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 concept-based statement calculations for a standalone entity to the standalone foundation and introduce group calculation graph across entity, aggregation, elimination and consolidation layers 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
