The One Question Nobody in Your Mumbai Boardroom Is Asking About Jakarta
Indonesia’s GloBE registration deadline is 30 September 2026. Here’s what Indian MNE groups with Indonesian operations must do — now.
Last month, over kopi tubruk with the finance director of an Indian group’s Jakarta subsidiary, I asked one question: “Who in your group owns the Indonesian GloBE registration?”
Silence. Then: “Isn’t Pillar Two handled by group tax in Mumbai?”
That answer — and I have heard versions of it across three boardrooms since — is exactly how Indian MNE groups will sleepwalk past 30 September 2026.
The short version
Indonesia has fully operationalised the OECD Pillar Two Global Minimum Tax. PMK-136/2024 delivered the substantive rules; PER-6/PJ/2026 (effective 4 May 2026) delivered the administrative machinery — registration, returns, payment mechanics, audits, disputes.
If your group’s consolidated revenue crosses EUR 750 million in at least 2 of the last 4 years, every Indonesian subsidiary and PE in your structure is now a “Wajib Pajak GloBE” — a GloBE Taxpayer — with its own local obligations. Not Mumbai’s obligations. Jakarta’s.
And the Directorate General of Taxes (DGT) has publicly confirmed the first hard date: for groups whose first GloBE year is 2025, registration closes 30 September 2026. Nine months after the 2025 GloBE year-end. No ambiguity.
The compliance calendar you need on one page
ObligationDeadline (2025 GloBE year)Legal basisGloBE Taxpayer registration (DJP Portal)30 September 2026PER-6/PJ/2026; DGT public guidanceTop-up tax payment (IIR, DMTT, UTPR)31 December 2026PER-6/PJ/2026SPT Tahunan PPh GloBE/DMTT/UTPR30 April 2027 (+2-month first-year extension available)PER-6/PJ/2026GloBE Information Return (GIR), XML per OECD template30 June 2027 (18 months, first year)PER-6/PJ/2026; OECD GIR guidanceNotifikasi (UPE, filing entity, Indonesian CEs)Same as GIRPER-6/PJ/2026
Five deadlines. The first one is fourteen months away from the year-end it relates to — and it is the one that determines how the DGT sees your group for everything that follows.
Why “group tax will handle it” fails in Indonesia
Here is the structural misunderstanding I keep encountering.
India’s Pillar Two journey so far has been about group-level recognition — the AS-22 amendments, disclosure of Pillar Two tax exposure in consolidated accounts. That conditions Indian tax teams to think of GloBE as a consolidation topic.
Indonesia flipped that. PER-6/PJ/2026 imposes obligations directly on the Indonesian constituent entity:
An electronic “penambahan status” application through the DJP Portal — capturing NPWP, UPE details (TIN, jurisdiction, accounting period), group name, first in-scope year, and a designated administrative contact.
A three-part annual return regime: SPT PPh GloBE (if an Indonesian entity is the UPE — rare for Indian groups), SPT PPh UTPR (where UTPR top-up is allocated to Indonesia), and SPT PPh DMTT — which every Indonesian GloBE taxpayer files.
GIR and Notifikasi obligations, with designation rules where the UPE sits in India and GIR-exchange arrangements between India and Indonesia are not yet in place.
Your Jakarta entity cannot outsource its legal status to Mumbai. It can only outsource the work.
What happens if you miss 30 September 2026
Do not assume the DGT waits for you to raise your hand.
Ex officio assignment. If a qualifying Indonesian entity does not apply, the Tax Office assigns GloBE Taxpayer status administratively — using CbCR data, exchange-of-information, and local filings. For a EUR 750m+ group, “staying below the radar” is not a strategy; it is a fiction. The DGT already has your CbCR.
The obligations survive. Ex officio status does not waive a single downstream requirement — the SPTs, the GIR, the Notifikasi, the top-up tax all remain due.
Sanctions stack. PER-6/PJ/2026 defers to the KUP (general tax procedure law) penalty framework: interest on late top-up tax payment, fines on late returns. Miss registration and the failure typically cascades — late SPT, late GIR, underpaid top-up tax, each with its own exposure.
You become an audit candidate. The regulation explicitly authorises GloBE-focused supervision and audits — for registered and unregistered in-scope groups. Indian MNEs with historically low ETRs in specific jurisdictions or layered transfer-pricing structures should assume they are on the shortlist.
Coretax remembers. Late payments feed risk-scoring in Indonesia’s Coretax system. For listed and PE-backed groups, non-compliance with a global transparency standard in a key ASEAN market is a board-level conversation, not a tax-team footnote.
The part nobody budgets for: data
Registration is a form. The GIR is a systems project.
Jurisdictional ETRs, adjusted covered taxes, GloBE income, SBIE, excess profit, top-up allocation — in XML, per OECD template, reconciled to three Indonesian returns. Standard ERP configurations do not hold this data at the required granularity. Every month spent debating ownership between group tax and the Indonesian entity is a month removed from the build.
And a caution on safe harbours: CbCR safe harbour, QDMTT safe harbour, simplified calculations — none of them exempt you from filing the GIR, the returns, or the Notifikasi. A missed deadline can undermine the very safe harbour position you were relying on.
The 90-day playbook
If you run group tax for an Indian MNE with Indonesian operations, here is the sequence:
1. Scope (this month). Confirm the EUR 750m test across the 4-year lookback. List every Indonesian subsidiary and PE that qualifies as a constituent entity. Confirm the first GloBE year — for most, 2025.
2. Assign ownership (this month). Name the person accountable for the DJP Portal registration of each Indonesian entity. Registration is entity-level; accountability must be too.
3. Register early (by mid-August 2026). The statutory date is 30 September. Your internal date should not be. Portal submissions generate an electronic receipt and an automatic status letter — build slack for rejections and data corrections.
4. Decide the GIR architecture (Q3 2026). Who files the GIR vis-à-vis Indonesia? Direct Indonesian filing, or reliance on exchange from another jurisdiction? This turns on competent-authority agreements — and India’s position is still evolving. Get a documented view.
5. Lock the calendar (now). Internal cut-offs: registration August 2026, payment-readiness November 2026, draft SPT and GIR Q1 2027. Treat the statutory dates as backstops, never targets.
Already past a deadline, or expecting to be? Register late anyway — voluntary late registration reads very differently to the DGT than an ex officio assignment. Pay and file proactively with documented explanations. Indonesia’s procedure law provides objection, appeal, and sanction-reduction channels, and prepared taxpayers consistently fare better in them.
The corridor view
I have spent two decades watching Indian groups treat Indonesian compliance as a translation exercise — take the group policy, render it in Bahasa, file it. Pillar Two is where that model breaks. Indonesia has built a genuinely local administrative regime around a global standard, and it expects local answers: an NPWP on the registration form, a named contact the KPP can call, a DMTT return from every constituent entity.
The groups that will clear September 2026 without drama are the ones treating this as an India–Indonesia joint workstream today — group tax, local finance, IT, and advisors who read both PER-6/PJ/2026 in the original and the Indian group’s consolidation reality.
Fourteen months sounds like a long time. In a registration-plus-data-plus-systems project spanning two jurisdictions, it is not.
Ask the Jakarta question in your next tax committee meeting: who owns our Indonesian GloBE registration?
If the room goes quiet, you have your answer — and your deadline.
Lift as you Rise.