Repositora AI - Ind AS 118 / IFRS 18
Knowledge Base
IFRS 18 Alignment

Ind AS 118 and IFRS 18: How Closely Are They Aligned?

Understand the relationship between Ind AS 118 and IFRS 18, what alignment means and why Indian companies should still monitor local differences.

Ind AS Basics
article group
10
article sections
Ind AS 118 and IFRS 18 alignment
focus topic
Ind AS 118 / IFRS 18
reporting focus
Article map

Move through the article with a clear review map.

Use the contents as a quick scan before going into the full article. The sections preserve the article structure and link directly to each discussion area.

  1. 01Why this topic matters
  2. 02Key concepts to understand
  3. 03Practical implications for finance teams
  4. 04Practical steps to prepare
  5. 05Common mistakes to avoid
  6. 06How Indas118 can support preparation
  7. 07Related Ind AS 118 guidance
  8. 08FAQs
  9. 09Additional implementation notes
  10. 10Final thoughts
Article

Ind AS 118 and IFRS 18: How Closely Are They Aligned? is written for multinational groups, Indian subsidiaries, accounting professionals and IFRS reporting teams. Ind AS 118 is expected to change how financial performance is presented and explained in Indian financial statements, particularly through a more structured statement of profit and loss and clearer disclosure of selected management measures. The issue is not limited to a new format. It affects how teams move from ledger data to statutory reporting, board discussion and external communication.

This article explains Ind AS 118 and IFRS 18 alignment with a practical implementation lens. The objective is to explain convergence while warning against careless copy-paste from IFRS group reporting. Readers should see the topic as part of a wider reporting communication framework: income and expenses need clearer categories, subtotals need more consistent meaning, and important information should be placed where users can understand it without unnecessary searching.

Timing is another reason to prepare early for Ind AS 118 and IFRS 18 alignment. The ICAI exposure draft proposed application for annual reporting periods beginning on or after 1 April 2027, while final MCA notification and related regulatory changes should still be checked before publication or implementation. Companies that start now can run dry exercises focused on this topic, test comparative information, discuss judgments with auditors and train users before the first mandatory reporting cycle creates deadline pressure.

Why this topic matters

The practical importance of Ind AS 118 and IFRS 18 alignment comes from the fact that Ind AS 118 is a presentation and disclosure standard, not merely a renumbering of older guidance. It is aligned with the IFRS 18 approach and is designed to make performance reporting more comparable and more understandable. For preparers, this means that existing balances may need to be organized, labelled and explained differently even when the underlying accounting measurement remains unchanged.

Three points frame the discussion: Ind AS 118 has been formulated on the basis of IFRS 18 as part of India's convergence approach. The central themes are aligned: structured P&L categories, defined subtotals, MPM disclosures and disaggregation. Indian legal notification, Schedule III and regulatory formats may create local implementation considerations. Taken together, these points show why the change cannot be handled by inserting a few extra headings into the annual report. The company needs a reliable route from accounts to categories, from categories to subtotals, and from subtotals to the explanations users see in the notes and public materials.

The remaining points are equally important: Subsidiaries of IFRS-reporting groups may need to bridge group reporting and Indian statutory reporting. Terminology and presentation in Indian financial statements should follow the final notified Ind AS wording. Alignment helps comparability but does not eliminate the need for local judgment and documentation. These matters affect the quality of the performance story. A clear presentation helps users understand what belongs to operations, what relates to investing or financing effects, and how management's own measures compare with the specified subtotals in the financial statements.

Key concepts to understand

For many entities, ind AS 118 has been formulated on the basis of IFRS 18 as part of India's convergence approach. This has both a technical side and a process side. The technical side is the classification or disclosure conclusion; the process side is how that conclusion will be reproduced during monthly, quarterly and annual reporting without relying on memory.

During implementation, the central themes are aligned: structured P&L categories, defined subtotals, MPM disclosures and disaggregation. The point matters because Ind AS 118 gives users a more structured way to read performance. If the company keeps old labels or informal logic, the new presentation may look compliant but still fail to communicate clearly.

From a governance perspective, indian legal notification, Schedule III and regulatory formats may create local implementation considerations. The safest response is to document the facts, identify the affected reports and record the judgment made. That record will help reviewers understand the conclusion and will also help the team apply the same approach in the comparative period.

Practical implications for finance teams

For reporting teams, subsidiaries of IFRS-reporting groups may need to bridge group reporting and Indian statutory reporting. This should be considered early because it can affect templates, consolidation schedules, board explanations and audit questions. Early analysis is usually cheaper than correcting a presentation issue at the end of the close cycle.

In a dry run, terminology and presentation in Indian financial statements should follow the final notified Ind AS wording. A useful control is to assign an owner for the decision and a reviewer for the evidence. That simple discipline reduces the risk of inconsistent treatment across entities, periods or public documents.

From an audit-readiness viewpoint, alignment helps comparability but does not eliminate the need for local judgment and documentation. The finance team should also ask whether the current system can generate the needed information directly. If it cannot, the workaround should be controlled, reconciled and eventually replaced with a repeatable reporting solution.

Practical steps to prepare

A workable plan for Ind AS 118 and IFRS 18 alignment should be specific enough to allocate owners and deadlines. The actions below can be used as a website checklist, a finance project plan or a workflow inside the Indas118 app:

  • Compare group IFRS 18 instructions with Indian Ind AS 118 requirements.
  • Identify terminology differences and local regulatory presentation needs.
  • Prepare a bridge file for group package versus statutory financial statements.
  • Review whether group MPMs appear in Indian public communications.
  • Monitor final MCA, Schedule III and SEBI-related changes.

The value of these actions is that they produce evidence for Ind AS 118 and IFRS 18 alignment, not only discussion. A team that completes them can explain what changed, why it changed, who reviewed it and how the same approach will be applied again when comparative information and future reporting periods are prepared.

Common mistakes to avoid

Ind AS 118 implementation can look straightforward when the team views only the final printed financial statements. For Ind AS 118 and IFRS 18 alignment, the real risk appears when the company tries to produce the new presentation repeatedly, under close deadlines, with comparative information and audit review. The following mistakes deserve particular attention:

  • Assuming IFRS 18 implementation files can be used unchanged for Indian statutory reporting.
  • Ignoring local formats and legal requirements.
  • Not reconciling group subtotals with local financial statement presentation.

Avoiding these issues in Ind AS 118 and IFRS 18 alignment requires more than technical knowledge. The team should make decisions visible by recording the issue, the conclusion, the evidence, the owner and the reviewer. When this happens before the first mandatory reporting period, implementation becomes a controlled process rather than a last-minute interpretation exercise.

How Indas118 can support preparation

For Ind AS 118 and IFRS 18 alignment, the Indas118 app can be positioned as the practical layer between technical reading and implementation evidence. Indas118 can maintain an IFRS 18 to Ind AS 118 bridge, local gap list and group reporting action tracker. The app should not be described as a substitute for management judgment, professional advice or auditor review. Its strongest role is to make tasks, assumptions, documents and follow-ups easier to manage.

This product connection also works well for repositora.com from an SEO perspective. The article can educate the reader first, then guide the reader toward a structured workflow for Ind AS 118 and IFRS 18 alignment. That sequence builds trust: the reader receives useful technical guidance before seeing how Indas118 may help organize the work.

Use these related articles to connect this topic with the surrounding implementation work:

FAQs

QIs Ind AS 118 based on IFRS 18?

Yes. It has been formulated on the basis of IFRS 18, subject to Indian notification and local requirements.

QCan Indian subsidiaries use group IFRS files?

They can use them as a starting point, but local requirements should be checked.

QWhat should multinational groups monitor?

They should monitor local notification, Schedule III, SEBI formats and subsidiary reporting calendars.

Additional implementation notes

For Ind AS 118 and IFRS 18 alignment, a useful readiness test is to ask whether a new team member could reproduce the conclusion using only the workpaper. If the answer is no, the documentation is not yet strong enough. The workpaper should show the source data, the classification or disclosure logic, the reviewer comments and the final approval. This makes the transition less dependent on individual memory and more resilient during audit or staff changes.

Final thoughts

Ind AS 118 should be treated as a reporting communication project. For Ind AS 118 and IFRS 18 alignment, the central lesson is to start with the purpose of the requirement and then connect it to data, templates, controls and communication. A company that can explain this connection will be better prepared for audit questions and user expectations.

The standard may not change the underlying measurement of many income and expense items, but it can change how users understand those items. That is why early preparation around Ind AS 118 and IFRS 18 alignment matters. Mapping accounts, reviewing performance measures, testing disclosures and training users before the deadline can reduce implementation risk and improve the quality of the final financial statements.

A useful next step is to convert this article into a live readiness task list. On repositora.com, Indas118 can be presented as the workspace that helps teams track Ind AS 118 and IFRS 18 alignment, maintain evidence and monitor unresolved actions until the first reporting cycle is complete.

Contact

Take this reporting issue into a focused implementation conversation.

Start with this article topic, or move straight into statement presentation, disclosures, controls, reporting workflows, and transition readiness.

Applicability, presentation, and disclosure implications for the topic
Owner, reviewer, and evidence expectations before live reporting
Comparative-period readiness across finance, audit, and stakeholder communication
Ind AS 118 and IFRS 18: How Closely Are They Aligned? | Repositora AI - Ind AS 118 / IFRS 18