Coretax and Indonesian Tax Compliance in an ERP
What Coretax DJP is, the change in tax identity it brings, and the practical consequences for master data and transactions in an ERP such as NetSuite.
Coretax is the core tax administration system of the Indonesian Directorate General of Taxes, effective from 1 January 2025. It consolidates services that used to be spread across several applications — registration, tax invoices, withholding slips, return filing and payment — into a single taxpayer account.
For anyone building or maintaining an ERP, what matters is not the portal's appearance but its consequence for data: tax identity changes shape, and data that has been merely good enough until now stops being enough.
The identity changes with the most impact
| Identifier | Shape | Used for |
|---|---|---|
| 16-digit NPWP | Entities: 0 plus the old 15-digit NPWP | The primary identity of a corporate taxpayer |
| NIK as NPWP | 16 digits, belonging to an individual | The identity of an individual taxpayer |
| NITKU | 22 digits: the 16-digit NPWP plus a place-of-business code | Distinguishing head office from each branch |
NITKU is the one most often overlooked. A company with several branches or warehouses can no longer store a single NPWP in its master data — each place of business has its own identifier, and tax documents must reference the correct one.
Tax documents attached to transactions
| Document | Related transaction | Contains |
|---|---|---|
| Output Tax Invoice | Sales invoice | VAT collected from the customer |
| Input Tax Invoice | Purchase vendor bill | VAT paid to the supplier, creditable |
| Withholding Tax Slip | Payment for services and rent | Tax withheld, for example under Article 23 or Article 4(2) |
| Periodic Tax Return | Monthly recapitulation | A summary of collections and withholdings for one tax period |
Consequences for the ERP
- Customer and supplier master data must hold the 16-digit NPWP and the NITKU, not just the old NPWP. That is a data cleansing job, not a configuration job.
- Every item and service needs the correct tax code, because that is what VAT is calculated and reported from.
- Tax invoice numbers need to be stored on the transaction so reconciliation to the return can be done without manual matching.
- Names and addresses must match the official documents exactly; small mismatches get invoices rejected.
- Cancelled and returned transactions need a clear invoice cancellation path, not simply deletion in the ERP.
The monthly reconciliation that has to happen
- 01Extract every VAT-bearing invoice from the ERP for the current tax period.
- 02Compare against the list of output tax invoices recorded in the tax system.
- 03Trace each difference individually: invoices without a tax invoice, tax invoices without an invoice, or differing amounts.
- 04Do the same for input tax invoices against Vendor Bills.
- 05Confirm the total VAT in the return equals the Tax Payable balance on the Balance Sheet.