Ind AS vs IFRS in Oracle Financials: What Changes for Indian Enterprises

Ind AS vs IFRS in Oracle Financials: What Changes for Indian Enterprises

  • By Rajkumar Awasthi, Vice President — Oracle Delivery
  • Published Jul 27, 2026
  • Share This:

In short: Ind AS is India's version of IFRS, and for most standards — including lease accounting — the two are near-identical in substance. But "near-identical" is not "identical," and the gaps that do exist (carve-outs, transition provisions, and a small number of India-specific modifications) matter directly to how Oracle Financials should be configured for an enterprise that reports under both, such as an Indian subsidiary of a multinational, or an Indian company with foreign listings or foreign parent reporting obligations.

Why Ind AS and IFRS are close but not the same

Ind AS was developed by India's Ministry of Corporate Affairs as a converged — not fully identical — adaptation of IFRS, administered through the Institute of Chartered Accountants of India (ICAI). "Converged" is the operative word: most Ind AS standards mirror their IFRS counterpart number-for-number in structure (Ind AS 116 mirrors IFRS 16, Ind AS 115 mirrors IFRS 15, and so on), but each carries a small number of carve-outs or carve-ins reflecting Indian regulatory, tax or market context. The practical effect is that an accounting team fluent in IFRS cannot assume Ind AS behaves identically in every respect — the standards have to be checked individually for the specific carve-out, not assumed to be a straight copy.

Where the gaps actually show up in practice

The differences that most often affect system configuration rather than just disclosure wording tend to cluster around: transition and first-time-adoption provisions (Ind AS 101 has India-specific transitional exemptions not present in IFRS 1), certain financial-instrument classification and measurement nuances, and specific carve-outs in standards covering revenue recognition and business combinations. For lease accounting specifically, Ind AS 116 and IFRS 16 are substantively aligned — the ROU asset and lease liability mechanics are the same — so a system built correctly for one is very close to correct for the other, but the reporting entity still needs to confirm which standard governs which set of books before assuming a single calculation serves both.

What this means for a dual-reporting enterprise

An Indian subsidiary of a multinational parent, or an Indian company with a foreign listing, frequently has to produce statutory financial statements under Ind AS for Indian regulatory purposes and consolidated financial statements under IFRS (or US GAAP) for the parent or foreign listing. The naive approach — maintaining two entirely separate sets of books — is expensive and creates reconciliation risk every reporting period. The better approach, where the underlying standards are substantively aligned (as with lease accounting), is a single source ledger with reporting-currency and disclosure-format differences handled at the reporting layer, rather than duplicating the underlying transactional calculation.

How Oracle Financials supports this

Oracle Fusion Cloud's multi-ledger and reporting-currency architecture is built for exactly this scenario — a primary ledger for statutory Ind AS reporting, with secondary ledgers or reporting currencies configured to produce the parallel IFRS or US GAAP view from the same underlying transactions, rather than re-entering data twice. For lease accounting specifically, because Ind AS 116 and IFRS 16 are substantively the same standard, a single lease-accounting calculation can typically feed both reporting views, with the configuration work concentrated on the handful of standards where a genuine divergence exists rather than lease accounting itself.

Where to get specific, not general, advice

The specific carve-outs between Ind AS and IFRS change as both standards are updated, and which ones are material to a given business depends on its actual transactions — this is genuinely a case where the right answer comes from a qualified chartered accountant reviewing the specific entity's position, not a general article. What ROSTAN configures is the system architecture that lets Oracle Financials produce both reporting views efficiently once the accounting treatment is determined; the accounting determination itself sits with the enterprise's auditors and finance leadership.

Related service

Oracle Fusion Cloud & EBS

We implement Oracle Fusion Cloud and support Oracle E-Business Suite. If someone is telling you EBS is end-of-life, read this first — Oracle has committed Premier Support through at least 2037.

See our Oracle ERP services

Frequently Asked Questions

Not identical — Ind AS is a converged adaptation of IFRS developed for India, and most standards mirror their IFRS counterpart closely (Ind AS 116 mirrors IFRS 16), but each carries a small number of India-specific carve-outs or carve-ins. An accounting team fluent in IFRS should confirm the specific carve-out for each standard rather than assume a direct copy.

Substantively yes — the right-of-use asset and lease liability mechanics are the same. A lease-accounting system configured correctly for one is very close to correct for the other, though the reporting entity should confirm which standard governs which set of books.

Not necessarily. Where the underlying standards are substantively aligned, a single source ledger with reporting-currency and disclosure-format differences handled at the reporting layer is generally more efficient and lower-risk than maintaining two fully separate books and reconciling them each period.

Through its multi-ledger and reporting-currency architecture — a primary ledger for statutory Ind AS reporting, with secondary ledgers or reporting currencies configured to produce the parallel IFRS or US GAAP view from the same underlying transactions, rather than re-entering data twice.

From a qualified chartered accountant reviewing your specific transactions and reporting obligations — the applicable carve-outs change as standards are updated and depend on the entity's actual activities. ROSTAN configures the Oracle Financials architecture to support whatever accounting treatment your auditors determine, rather than making that determination itself.
Rajkumar Awasthi — Vice President — Oracle Delivery, ROSTAN Technologies
Written & reviewed by
Vice President — Oracle Delivery, ROSTAN Technologies
Rajkumar Awasthi leads Oracle delivery at ROSTAN Technologies, overseeing Oracle ERP implementation, Oracle E-Business Suite support and EBS-to-Fusion Cloud migration engagements for enterprise customers across India and the GCC. More from Rajkumar →

Have questions about Oracle, AWS or Cloud?

Talk to our certified experts — free consultation, no commitment.


You May Also Know About
Back to Top
ROSTAN Support
Online · Typically replies instantly
WhatsApp Chat directly, fastest response Call Us +91-9810958952 Email Us info@rostantechnologies.com Send a Message Fill the contact form
Chat with us