TP Compliance that starts with the calendar, not the week before filing

Most groups do not miss a Local File because they forgot the OECD exists. They miss it because the Indian accountant's October window collides with a UAE disclosure threshold, a European Master File date, and a CbCR notification that uses a different year-end convention. TP compliance is the discipline of knowing which obligation applies, which entity it attaches to, and which document must already be finished when that date arrives.

The calendar in TP DOC GEN AI is evergreen data shipped with the product. It works with zero AI and zero network. Deadlines resolve from your fiscal year-end: 31 March, 31 December, and 30 June recompute the board. Coverage runs 2020–2035 so historical and forward years stay in one view.

The mix we actually track: 145 CbCR filings, 116 TP disclosure forms, 109 Master File obligations, 107 Local Files, 89 CIT returns, and 69 CbCR notifications, among others. Every row carries the statutory section, form name, timing rule, penalty language, and a source URL. That is the difference between a pretty calendar and a file you can show an engagement partner.

If two entities share a calendar but not a year-end, they do not share a due date. The product recomputes from the FYE you attach to the entity. That sounds obvious until a HoldCo on 31 December and an Indian manufacturer on 31 March are staffed from one colour-coded row in a spreadsheet.

India still runs on the Form 3CEB accountant's report alongside Local File documentation. The platform includes a Form 3CEB wizard (clauses 10–26) with per-clause Excel import and export to PDF, XLSX, and the official ITD e-filing JSON. FY conventions, rupee rendering, and an Income-tax Act / CBDT knowledge bank sit next to the Prowess pipeline so the compliance calendar and the study are not two different products.

The UAE Corporate Tax regime added a second hard clock. The disclosure form captures the statutory AED 40 million related-party threshold and the AED 500,000 connected-persons threshold, with arm's length versus booked value. Local Files cite Ministerial Decision No. 97 of 2023. Connected-persons profiling is an annexure, not an afterthought. Arabic deliverables are a first-class Local File translation, with true RTL and digit-integrity checks so figures cannot silently change in translation.

If your footprint is Europe plus India plus a GCC HoldCo, the calendar is the only honest way to staff the season. Filter by country and requirement, then export ICS into the team's Outlook. Do not wait for an email reminder that the product does not send.

A static calendar goes stale. A live-only calendar cannot be reproduced. We keep both. The baseline JSON lives with the product. A regulatory updates feed refreshes every six hours from tier-1 and tier-2 TP sources (OECD, ITR, MNE Tax, Bloomberg Tax, Taxsutra, UN DESA Tax, and others). Merged at read time, so a deadline you printed last month still has a paper trail.

TP compliance also means the document you file is the document you can explain. Documentation, benchmarking, Instant PLI, and the calendar share master data. When a disclosure form says a transaction existed, the Local File should already describe it. When the Local File cites a range, the benchmarking annexure should still contain those comparables.

Read the methodology page for how OECD Local File logic is encoded, or the compliance article for a practitioner walk through India and UAE dates. To see the calendar on your year-end, request a walkthrough.

We will not call ICS export "automatic alerts." We will not claim Hindi translation. We will not pretend a dashboard sparkline is a filing. TP compliance, in this product, is: know the obligation, resolve the date from FYE, produce the document the obligation names, and keep an audit trail of how figures were computed.

That is slower to market than a slogan and much faster in October. If your firm still tracks deadlines in a shared spreadsheet with colour-coded rows, you already know the failure mode. Move the clock into the same system that writes the file.

CbCR is a different artefact from the Local File, with a different owner in many groups. The calendar still has to show both, plus the notification, or the tax team discovers the notification date from a penalty notice. Master File due dates often sit on the parent while Local Files sit on the tested parties. Staff them as a portfolio, not as "the TP study."

A multi-FYE group should keep one board per year-end convention, then a roll-up. Export ICS into the shared mailbox. Put the Local File generation on the same week the calendar row turns red, not the week after. That is TP compliance as operations, which is the only version that survives a partner review.