Case Study: Handling a DJP Tax Audit for a Foreign Manufacturing Company

A note before this starts. What follows is an illustrative scenario, built from a pattern consistent with how a formal DJP audit actually proceeds under current regulation, not an account of one specific, identifiable client. The document requests, the preliminary findings, and the resolution are realistic and reflect how this process genuinely works, but the details have been composited rather than pulled from a single named engagement.

The SP2DK had already come and gone. The finance director’s team had responded within the window, submitted the requested reconciliation, and assumed, reasonably, that the matter was closed. Six weeks later, a different letter arrived. This one was not a request for explanation. It was a Surat Pemberitahuan Pemeriksaan, formal notification that DJP was opening a focused audit into the company’s transfer pricing position for the two most recent fiscal years. The company had never been through a formal tax audit before, and the assumption that a well-handled SP2DK would prevent one turned out to be exactly that, an assumption.

Why a Manufacturing PT PMA Draws This Kind of Scrutiny Specifically

Manufacturing entities carry a distinct audit profile compared to service-based PT PMA structures, largely because of what sits on their balance sheet and moves through their supply chain. This company imported components from its parent manufacturer overseas, priced under an intercompany arrangement, while also carrying inventory valuation methods that had not been revisited since the entity’s original incorporation. Both of those facts, related party transaction pricing and inventory accounting, sit squarely inside the risk categories Coretax’s data matching system is specifically built to flag. The broader mechanics of how transfer pricing documentation gets evaluated during a DJP audit, including the formal and material standard examiners apply, are covered in full in a separate look at Indonesia’s transfer pricing documentation requirements for 2026, and this case followed that standard closely once the audit was underway.

What Changed Once the SP2 Arrived

Under Minister of Finance Regulation No. 15 of 2025, DJP now formally classifies every audit into one of three types, each carrying a different scope and a different maximum assessment period. A comprehensive audit examines every item across a full tax return and can run up to five months. A focused audit narrows to one or several specific items, capped at three months. A specific audit is narrower still, targeting particular data points or obligations under a simplified process. This company’s audit was classified as focused, aimed specifically at the transfer pricing arrangement with its overseas parent, which meant a three month clock started the day the SP2 was received, not an open-ended examination of the entire return.

That classification mattered immediately for how the response was resourced. A comprehensive audit calls for marshaling documentation across the full breadth of the company’s tax position. A focused audit rewards depth on a narrow question instead, and treating this one as if it required a comprehensive response would have spread the team’s attention across material the auditors were never going to examine.

Explore Our Services Tax Compliance in Indonesia

The Procedural Right Most Companies Do Not Know They Have

The most consequential part of this audit was not the document request list. It was a formal step introduced under the same PMK 15 of 2025 framework, the Pembahasan Temuan Sementara, a mandatory discussion of preliminary findings between the auditor and the taxpayer before those findings harden into a final assessment. This is a genuinely new procedural right. Under the older audit framework, a company often learned the auditor’s conclusions only when the formal assessment letter arrived, with limited room to correct a misreading of the underlying facts before the number became official.

In this scenario, the preliminary findings identified the intercompany component pricing as inconsistent with an arm’s length standard, based on a comparable set the auditor had selected. The Pembahasan Temuan Sementara session gave the company’s tax team a formal opportunity to walk through why that comparable set did not reflect the actual functional and risk profile of the transaction, supported by the transfer pricing documentation prepared in advance for exactly this contingency. This is not a courtesy meeting. It is a defined procedural stage, and companies that treat it as optional or send an underprepared representative are giving up one of the only opportunities to correct an auditor’s preliminary read before it becomes a formal, harder to reverse position.

The Closing Conference and What Actually Got Resolved

Following the preliminary findings discussion, the audit moved into its closing conference and reporting phase, where the auditor’s final position gets formally presented and discussed before the assessment letter, the Surat Ketetapan Pajak, is issued. Because the comparable set issue had already been addressed during the Pembahasan Temuan Sementara stage, the closing conference in this case did not reopen that argument from scratch. It confirmed a revised position that reflected the company’s documentation rather than the auditor’s original comparable set, a materially different outcome than if the correction had first surfaced at the closing conference itself, with far less room to actually change the auditor’s analysis at that late stage.

The company still owed an adjustment, since the audit did identify a genuine, if smaller, pricing gap the original documentation had not fully addressed. What the process avoided was an assessment built entirely around a comparable set the company had never had a formal opportunity to contest before it became final.

Why the Documentation That Existed Before the Audit Mattered More Than Anything Produced During It

Looking back across the audit, the single factor that determined the outcome was not anything assembled after the SP2 arrived. It was the transfer pricing documentation and bookkeeping records the company had already been maintaining as a matter of ongoing compliance, not audit preparation. Indonesia requires companies to retain financial and accounting records for ten years specifically because tax audits, disputes, and regulatory queries can surface years after the underlying transactions occurred, a retention obligation covered in more depth in a dedicated guide to bookkeeping requirements for PT entities in Indonesia. A company that treats documentation quality as something to address once an SP2DK arrives is already working from a weaker position than one that has been audit-ready continuously, since there is no realistic way to reconstruct two years of properly contemporaneous transfer pricing analysis inside a three month audit window.

It is also worth separating this kind of DJP tax audit from Indonesia’s statutory financial audit requirement, a distinct obligation triggered once a PT PMA crosses the IDR 50 billion asset or turnover threshold, explained fully in a separate guide to audit requirements for foreign companies in Indonesia. The two processes are not the same thing, but a company with clean, audited financial statements walks into a DJP tax audit from a considerably stronger position than one without them, since the auditor’s baseline confidence in the numbers starts higher.

XPND’s tax compliance team works with manufacturing PT PMA clients through exactly this kind of formal audit process, preparing for the Pembahasan Temuan Sementara stage as a genuine opportunity rather than a formality, and making sure the documentation an auditor eventually asks for already exists rather than needing to be built under a three month deadline. An SP2DK handled well does not guarantee a formal audit never follows. What determines how that audit actually goes is almost entirely decided before the SP2 ever arrives.