Foreign-owned companies operating in India tend to discover e-invoicing in one of two ways. Either their finance team reads about it in advance and prepares, or a customer rejects an invoice because it carries no valid reference number and cannot be claimed. The second route is considerably more expensive.

E-invoicing is not a new tax. It is a change in how an invoice becomes valid: certain documents must be reported to a government portal at the moment of issue and returned with an official reference before they count as invoices at all. For a foreign parent used to issuing documents from its own global system, that is a meaningful shift in sequence.

What E-Invoicing Actually Changes

Under the traditional model, a company raised an invoice, sent it to the customer and reported it later in a periodic return. Under e-invoicing, the reporting happens first. The invoice data goes to the portal, the portal validates it and returns a unique reference number and a signed version of the document, and only that returned version is the legally valid invoice.

Three consequences follow, and they are the ones that catch foreign-owned subsidiaries out:

  • Your ERP is now part of a compliance chain. Invoice numbering, item descriptions and tax classifications have to satisfy the portal’s validation rules, not just your internal conventions
  • Timing stops being flexible. An invoice raised and sent without being reported is not a valid invoice, which affects both your position and your customer’s ability to claim credit
  • Your customer has a direct interest in your compliance. Indian business customers routinely check the reference before processing payment

Why the Global Template Usually Fails

Most groups run a single invoice template worldwide. India’s requirements are specific enough that the global template rarely passes validation unchanged. Field-level mismatches, classification codes that do not exist in the Indian schema, and numbering series that break uniqueness rules are all common. The work is not conceptually hard, but it has to be done before the first invoice goes out, not after a rejection.

Does It Apply to Your Indian Entity?

Applicability turns on the notified turnover threshold, measured across the entity rather than per branch or per business line. That threshold has been lowered several times since e-invoicing was introduced, bringing progressively smaller companies into scope. Do not rely on the figure that applied when your subsidiary was incorporated — the limit in force today is what matters, and it should be confirmed against the current notification rather than from memory or an old advisory note.

Two points matter more than the number itself:

1. Crossing the Threshold Is Not a Future Problem

Once an entity crosses the notified limit, the obligation attaches from the applicable date and does not reverse if turnover later falls. A subsidiary that had one strong year remains in scope afterwards. Groups planning a large one-off transaction in India should check the effect on applicability before the transaction, not in the following financial year.

2. Group Turnover and Entity Turnover Are Different Questions

Foreign parents often assume consolidated global revenue decides the matter. The test applies to the Indian entity’s own turnover as computed under Indian rules, which is usually a far smaller number than the group figure, and is calculated on a specified basis rather than simply taken from the management accounts. Getting this computation right is the whole question of whether you are in scope.

Not Every Document Is Covered

E-invoicing applies to specified categories of supply. Business-to-business supplies and exports are generally within scope, while certain transactions and certain classes of registered person are excluded or treated differently. Credit notes and debit notes linked to covered invoices carry their own reporting requirements.

The practical risk here is not over-compliance but inconsistency: a company that reports some covered documents and not others creates reconciliation differences that surface later, usually during an audit or a customer dispute, when the underlying records are harder to reconstruct.

A Realistic Preparation Sequence

  • Establish applicability first, computing the Indian entity’s turnover on the prescribed basis against the limit currently in force
  • Audit your invoice data before touching the portal. Most failures are data quality problems — classifications, descriptions, numbering — not integration problems
  • Decide how invoices will be reported: directly from the ERP, through an intermediary, or manually in low volumes. Volume and transaction complexity decide this, not cost alone
  • Test with real documents, including credit notes and an export invoice, before going live
  • Reconcile monthly from the start. Reported documents, your books and your periodic returns should agree every month; a year of unreconciled differences is a genuine project to unwind

For foreign-owned companies this sits alongside the rest of the monthly cycle rather than apart from it, which is why we handle it within monthly compliance rather than as a standalone exercise. Treating it as an IT project owned by the parent’s systems team, with no India compliance input, is the most reliable way to end up with invoices your customers will not accept.

Check Your Position Before the Next Invoice

AeTx works with foreign parents and their Indian subsidiaries on exactly this: establishing whether e-invoicing applies, getting the invoice data fit to pass validation, and keeping the monthly reconciliation clean afterwards. If you are unsure whether your Indian entity is in scope, or an invoice has already been rejected, message us on WhatsApp at wa.me/919810555783 and we will give you a straight answer on where you stand.