Tax Compliance in Indonesia: The System Now Finds Discrepancies Before You Do

Since January 2025, Indonesia’s Core Tax Administration System or Coretax monitors every transaction, invoice, and payment in real time against a centralized ledger. Errors are no longer discovered at annual filing. They surface the moment the system detects an anomaly. XPND manages corporate tax compliance as a continuous program so your company’s position in the Coretax risk framework remains clean and defensible.

Where the Risk Is Sitting Right Now

Tax compliance problems in the Coretax era do not announce themselves. They accumulate quietly in the gap between what your records show and what the government’s system has already detected.

Your company completed the migration from the old SIDJP system to Coretax but nobody verified whether historical transactions were reconciled correctly in the Taxpayer Account Management ledger. Discrepancies that exist between the two systems now appear as anomalies in the Coretax risk engine, even when the underlying transactions are entirely legitimate.

You received an SP2DK, the Letter of Request for Explanation of Data or Information (Surat Permintaan Penjelasan atas Data dan/atau Keterangan), from the Directorate General of Taxes (Direktorat Jenderal Pajak or DJP). Under Minister of Finance Regulation (Peraturan Menteri Keuangan or PMK) No. 111 of 2025, SP2DK is now a formal supervisory instrument, not merely an administrative query. Your company has a defined response window and the outcome determines whether the matter closes or escalates to a formal tax audit.

Your monthly tax filings are being submitted on time but the pre-populated data generated by Coretax from third parties, vendors, and customs records has not been verified against your own records. If that data contains errors and you accept it as filed, the legal responsibility for those errors transfers entirely to your company.

Your Tax Identification Number (Nomor Pokok Wajib Pajak or NPWP) data and the National Identification Numbers (Nomor Induk Kependudukan or NIK) linked to your company structure have not been audited since the 16-digit NPWP format came into effect. Name mismatches, unlinked NIK records, or outdated Business Activity Location Identification Numbers (Nomor Identitas Tempat Kegiatan Usaha or NITKU) are causing invoice rejections and higher withholding tax rates without a clear system notification as to why.

Your finance team is managing monthly tax obligations across PPh 21, PPh 23, PPh 25, PPh 4 paragraph 2, and VAT simultaneously, all with payment deadlines concentrated on the fifteenth of each month under PMK No. 81 of 2024. The compression creates liquidity pressure and any late payment triggers penalty exposure that accumulates faster than most teams anticipate.

None of these are catastrophic individually. Together, they represent the kind of compliance profile that places a company in a higher risk classification in the Coretax system, which directly affects the frequency and intensity of supervisory attention your company receives.

Tell us what your current Coretax position looks like and where your concerns are. We will assess it honestly.

What Coretax Changed and Why It Matters for Your Company

The Core Tax Administration System, governed by Minister of Finance Regulation or PMK No. 81 of 2024, is not simply a new filing platform. It fundamentally changed how the Indonesian government monitors tax compliance.

Under the previous system, the Directorate General of Taxes reviewed tax positions primarily at the point of annual filing. Under Coretax, every company has a Taxpayer Account Management ledger that records all payments, credits, outstanding balances, and inter-branch transactions in real time. The government can see your complete tax position at any point, not just when you file.

Director General of Taxes Regulation (Peraturan Direktur Jenderal Pajak or PER) No. 11 of 2025 introduced further changes to periodic tax return procedures under Coretax, consolidating the reporting mechanism for Income Tax Article 21, Article 22, Article 23, Article 4 paragraph 2, and Article 15 into a Unified Periodic Tax Return. The annual corporate tax return is now submitted exclusively through the Coretax application for the 2025 fiscal year onward.

PMK No. 111 of 2025 formalized the SP2DK as an official supervisory instrument within Indonesia’s self-assessment tax system. Previously, SP2DK was regulated only through internal DJP guidelines under Circular SE-05/PJ/2022 and was not binding on taxpayers as an external legal instrument. Under PMK No. 111 of 2025, SP2DK now carries a formal legal basis, a defined taxpayer response framework, and explicit escalation pathways to tax audits or preliminary evidence examination if the response is unsatisfactory.

The combined effect of these regulations is a tax compliance environment where the government has more information, acts on it faster, and has clearer legal authority to escalate.

Not certain how your current compliance posture appears in the Coretax system? XPND can run that assessment.

The SP2DK: What It Is and Why Early Response Matters

The SP2DK is the point at which a tax compliance issue becomes visible. Under PMK No. 111 of 2025, it is issued when the Directorate General of Taxes identifies a discrepancy between data in its system and what has been reported by the taxpayer. This includes discrepancies surfaced through cross-referencing with banking data, customs records, third-party transaction data, and other government information systems.

Receiving an SP2DK does not mean a company has committed a tax violation. It means the DJP has identified a data point that does not match and is requesting an explanation. The response window and the quality of that response determine what happens next.

A company that responds with complete, accurate documentation that explains the discrepancy will typically see the matter closed at the supervisory stage. A company that responds inadequately, responds late, or is unable to produce documentation that reconciles its position will face escalation to a formal tax audit. At the audit stage, the range of penalties and the cost of resolution are significantly higher than at the SP2DK stage.

XPND treats SP2DK prevention as a core element of ongoing tax compliance rather than a reactive service. The internal risk simulation XPND runs before each filing cycle is designed to identify exactly the kind of discrepancies the DJP’s risk engine flags, so they are corrected before an SP2DK is issued rather than explained after one is received.

Pre-Populated Data: The Risk That Most Companies Underestimate

One of the features of Coretax that appears to reduce compliance burden is the pre-populated tax return. Coretax generates draft returns using data from vendors, counterparties, customs records, and third parties. This reduces manual data entry. It does not reduce the taxpayer’s legal responsibility for the accuracy of what is filed.

If a vendor has reported an invoice amount that differs from your own records and you accept the pre-populated figure without verification, you have filed a tax return containing a third party’s error. If that error is detected by the DJP’s system, the discrepancy will appear in your company’s compliance profile, not the vendor’s.

For companies with high transaction volumes, verifying every pre-populated record against internal accounts before filing is operationally intensive. This is one of the specific functions XPND takes over as part of ongoing compliance management, systematically checking inbound pre-populated data against the company’s own transaction records and flagging discrepancies for resolution before submission.

Master Data Accuracy Under the 16-Digit NPWP System

Since July 2024, Indonesian tax administration operates on a 16-digit NPWP format. For individual taxpayers, the NPWP is now aligned with the National Identification Number or NIK. For corporate taxpayers, the NPWP uses a 16-digit format with branch-level tracking through the NITKU.

This change means that data accuracy at the master data level has become a prerequisite for basic tax operations. A company whose vendor records, employee tax data, or counterparty information contains name mismatches, unlinked NIK records, or outdated NITKU data will encounter invoice failures, withholding tax mismatches, and service rejections in the Coretax system.

These failures do not always generate clear error messages that identify the root cause. They often appear as processing delays or unresolved transactions that accumulate in the Taxpayer Account Management ledger until someone with system fluency investigates the underlying data issue.

XPND conducts a master data audit at the beginning of every engagement, validating all NPWP, NIK, and NITKU records against the Coretax system and resolving discrepancies before they create operational disruptions.

Master data issues are one of the most common sources of Coretax friction. Let XPND audit yours.

What XPND Manages in the Monthly Tax Compliance Cycle

XPND operates as the external compliance function for the full monthly tax obligation cycle, covering each of the following:

Corporate income tax installments or PPh 25. Monthly prepayments against the annual corporate income tax liability, calculated to reflect current-year earnings and avoid underpayment penalties at year-end.

Employee income tax withholding or PPh 21. Calculation, withholding, and reporting of income tax on employee salaries, benefits, and professional fees. Under PER No. 11 of 2025, PPh 21 is now reported through the ITA 21/26 Return within the Coretax system.

Value Added Tax or PPN filing. Monthly VAT returns including input tax credits, output tax, and any adjustments required where pre-populated counterparty data does not match internal records.

Withholding tax obligations or PPh 23 and PPh 4 paragraph 2. Withholding on services, royalties, rent, and other designated income categories, reported through the Unified Periodic Tax Return under PER No. 11 of 2025.

Annual corporate income tax return. Preparation and submission of the annual SPT through the Coretax application, including financial statement reconciliation, deduction verification, and alignment with the monthly installments paid throughout the year.

All filings are prepared with documentation that is audit-ready from the moment of submission, not assembled retrospectively if an SP2DK arrives.

Why Tax Compliance

For a company operating in Indonesia under the Coretax framework, tax compliance is not a function that can run in the background without structured attention. The government’s system is generating a compliance score for your company based on data consistency, filing timeliness, and response history. That score affects how closely your company is monitored and what happens when a discrepancy appears.

The companies that manage this well are not necessarily those with the largest finance teams. They are the ones whose tax data is accurate, whose filings are verified before submission, and whose SP2DK exposure is managed proactively rather than reactively.

XPND is built specifically for this environment, with the system fluency and the procedural discipline to keep your company’s Coretax profile in the range that minimizes supervisory attention and maximizes operational continuity.