TP compliance deadlines: India, the UAE, and the rest of the calendar

TP compliance is usually described as "having a Local File." That is necessary and not sufficient. Compliance is a portfolio of clocks: Local File, Master File, CbCR, disclosure forms, accountant's reports, and corporate-tax returns, each attached to an entity, each resolved from a fiscal year-end that may not be 31 March.

TP DOC GEN AI's compliance calendar tracks 767 obligations across 135 jurisdictions. This article is how we use that calendar in India and the UAE, where the busy season is least forgiving.

Resolve every date from FYE

A deadline written as "due 30 November" is incomplete. Due 30 November after which year-end? Groups with a 31 December HoldCo, a 31 March Indian manufacturer, and a UAE entity on a licensed FYE will compute three different boards. The calendar in this product recomputes from the year-end you actually use, for years 2020 through 2035, so historical restatements and forward planning live in one view.

The baseline is evergreen JSON shipped with the product. It works with zero AI and zero network. That matters when a partner asks "what did the statute say last year?" A live-only calendar cannot answer. A static-only calendar goes stale. We merge a six-hour news refresh from OECD, ITR, MNE Tax, Bloomberg Tax, Taxsutra, UN DESA Tax, and other tier-1/2 sources at read time.

India: Form 3CEB is part of the same compliance event

Indian TP compliance is not only the documentation study. The accountant's report on Form 3CEB is the public statement of the same international transactions. Mismatch between 3CEB and the Local File is an audit invitation. The platform's 3CEB wizard (clauses 10–26) imports per clause from Excel and exports PDF, XLSX, and the official ITD e-filing JSON. Keep claims about JSON coverage general; the point is that the form and the study share a house.

Prowess-backed benchmarking, rupee rendering, and an Income-tax Act / CBDT knowledge bank sit next to that wizard so the October crunch is not five tools taped together. Subscribe the ICS export into Outlook. The product does not send automatic reminders. Saying that it does would be a lie, and a dangerous one if someone skipped the calendar because they trusted a notification that never arrived.

UAE: thresholds, Arabic, and Ministerial Decision 97

UAE Corporate Tax turned TP compliance from "nice to have for HQ" into a filing problem. The disclosure form captures AED 40 million (related parties) and AED 500,000 (connected persons), with arm's length versus booked value. Local Files cite Ministerial Decision No. 97 of 2023. Connected persons are profiled in their own annexure.

Arabic is not a screenshot overlay. Local File translation is true RTL, with deterministic number localisation and a digit-integrity check. Statutory legal boilerplate stays in English until it has been professionally reviewed. Unreviewed machine-translated legal text is how you create a second, worse Local File.

Staff the season from the obligation list

The mix we track includes 145 CbCR filings, 116 TP disclosure forms, 109 Master File obligations, 107 Local Files, 89 CIT returns, and 69 CbCR notifications. Filter by country and form. Assign owners. Export CSV for the PMO. Then generate the document the obligation names in the same product, so the calendar row and the file cannot silently diverge.

See the documentation page for what that file contains, and how client data is handled when multiple entities share a workspace. To see the calendar on your year-ends, request a walkthrough.

Do not staff CbCR from the Local File team by accident

CbCR, Local File, and Master File often have different owners. The calendar has to show all three plus notifications, or someone discovers a date from a penalty. Keep one board per FYE convention. Export ICS. Generate the named document in the same week the row comes due.