India Transfer Pricing Compliance Calendar (2026): Every Deadline
Every India transfer-pricing deadline in one table: the return, Local File, Master File, CbCR, Form 3CEB, MAA and TPO windows — with the penalty exposure of missing each one.
Transfer pricing failures in India rarely start with a wrong method or a thin pool. They start with a date: a documentation that was finished after the return due date, a Form 3CEB filed late, a TPO response that missed its window. This page is the annual cycle in one place — what is due, when, who files it, and what a miss costs — followed by the event-driven obligations that fall outside the calendar and the way a firm should run the whole thing.
The annual cycle
| When | What | Basis | Who | If it is missed |
|---|---|---|---|---|
| Through the FY (by 31 March) | Contemporaneous documentation in place — Local File (incl. the current-year benchmarking), MAA workings for in-scope intercompany loans | s.92D / Rule 10D; s.92B | Each in-scope entity (revenue ≥ ₹30 cr) | The contemporaneity protection is lost; s.271AA (2% of the international transaction value) becomes available on notice |
| With the return of income (31 July regular; 31 October where an audit extension applies) | Form 3CEB — the accountant’s report on the international transactions, with Annexures A and B | s.92E | The chartered accountant, with the return | ₹1,00,000 (s.271BA); the report is also the annexure to the documentation, so its absence weakens the file itself |
| With the return (parent level, where in scope) | CbCR — per-jurisdiction revenue, profit, tax, employees, tangible assets; group consolidated revenue ≥ ₹1,000 cr | Rule 10DB | The ultimate parent, or the competent group member | Exchange gaps; the CbCR is the scrutiny map, so a missing or wrong one draws attention to the entity’s own file |
| With the return (group level, where in scope) | Master File maintained and available | Rule 10DA | The group / designated member | Availability failures surface at the same moment as the Local File fight |
| With the return | MAA filing for intercompany loans above the statutory threshold (mark-to-market documentation) | s.92B | The resident party | The loan’s transfer price stands without the required contemporaneous support |
| On service of a TPO notice under s.282BC | Produce the contemporaneous documentation — 30 days from the notice | s.282BC; s.271AA proviso | The entity | The s.271AA penalty (2% of transaction value) is no longer avoidable; the examination proceeds on the TPO’s materials |
| After the TPO’s proposal | Response and, where warranted, appeal to CIT(A) within the statutory window (30 days from the proposal) | The assessment provisions | The entity / advisors | An unchallenged proposal is a concluded adjustment; interest accrues from the original due date |
Two rows do the most damage in practice. The Local File row: the documentation must exist before the return due date — a perfectly correct file assembled in April after a notice is not contemporaneous, and the 30-day production window is the only protection left. And the 3CEB row: it is filed, not merely kept, and it carries its own penalty — the one practitioners remember as “the cheap one” (₹1,00,000) while it sits on the same filing day as everything else.
Event-driven obligations (outside the calendar)
These do not arrive on a date; they arrive on an event, and they are missed because no one put them in the calendar:
| Event | Obligation | Timing |
|---|---|---|
| New or modified intercompany loan above the MAA threshold | Mark-to-market documentation + MAA filing for the year | Before the return for the year the loan exists |
| New corporate guarantee to a related party | The genuine-benefit analysis and the fee, documented in the Local File; safe harbour election where eligible (fee ≥ 1% p.a. under Rule 10TD) | Contemporaneous with the year |
| Restructuring (merger, asset transfer, business line change) | The exit/location-savings analysis; the affected study re-scoped — the old tested party and pool no longer describe the entity | Before the return for the year of change |
| Royalty or licence terms renegotiated | New benchmarking for the changed transaction; the old study does not cover the new price | Contemporaneous with the new terms |
| Safe harbour election (Form 3CEFA) | The election filed before the return due date; the election particulars maintained for the election period | Per year of election |
The pattern: each event changes a fact the documentation is built on, so the obligation is not “file something” but rebuild the affected piece before the year closes. Firms that calendar their events alongside their dates miss far fewer of these than firms that calendar dates only.
Building the calendar in a firm
The calendar works as a control when it has four properties:
- One owner per row — a name, not a team. “TP team” owns nothing.
- Due date minus buffer — the working deadline is the statutory date less 15–30 days, because the benchmarking re-run, the 3CEB sign-off and the board-level review all compress into the same two weeks otherwise.
- Evidence attached, not linked — the calendar row carries the file reference (the study id, the 3CEB, the MAA document) so that “done” means “done and findable”, not “done and remembered”.
- The TPO row is live — the s.282BC 30-day window is the calendar’s highest-consequence row and it starts on service, not on a date. A firm that has not pre-staged the documentation package (Local File, 3CEB, matrix, agreements) before a season of notices is building it under a 30-day deadline, which is exactly when it should be being produced, not written.
The substantive content of each deliverable — what the Local File must contain, what the benchmarking annex must show — is in the documentation pillar guide and the Local File checklist. The calendar tells you when; those tell you what.
FAQ
What is the Local File due date, exactly? The documentation must exist before the due date of the return of income for that year — 31 July for regular filers, 31 October where the audit extension applies. It is maintained, not filed; the 3CEB is the filed companion.
Does the ₹30 cr Local File threshold apply to the entity or the group? The entity — its own revenue for the year. Group size governs the Master File and CbCR (₹1,000 cr consolidated); the two thresholds are independent, and an entity inside a large group can be out of Local File scope (and vice versa for a small group’s large entity).
Can a missed 3CEB be cured after the fact? It can be filed late, and the ₹1,00,000 penalty applies — but the cure does not restore the file’s contemporaneity for the year, and a 3CEB that post-dates a TPO notice reads as a reconstruction. The row that matters is the one where it was filed with the return.
How early should the benchmarking re-run start? The one that feeds the Local File: early enough that the full study (search, screens, adjustments, range) and the documentation drafting fit inside the pre-return window with the 15–30 day buffer. In practice that means the re-run starts in the first quarter after the fiscal year-end, not in the month of filing.
Run the screens as a study, not a spreadsheet
Quartyl applies the method, PLI and screening steps above as a pipeline — and keeps a documented reason for every exclusion.
Related docs
Transfer Pricing Documentation: Master File, Local File & CbCR (2026)
The three-tier documentation architecture: what lives in the Master File, Local File and CbCR, the India thresholds that trigger each, and how to keep the three documents consistent.
Read docRule 10D Documentation: The Complete Checklist
A Rule 10D documentation checklist for Indian transfer pricing — every item required, with practical tips for defending your Accept-Reject matrix before the TPO.
Read doc