Country
Indonesia
Article type
Regulatory update
Last checked
2026-08-30
Coretax changed where many Indonesian tax processes are carried out, but the enterprise obligation is larger than learning a new screen. Under the current framework, a taxable entrepreneur (PKP) must issue a Faktur Pajak at the correct tax point, state the actual transaction information, use an authorised electronic path and keep the result aligned with VAT reporting.
Current rules · Indonesia
Principal compliance requirements
Create the invoice at the correct moment
The tax invoice timing follows the taxable event rules, including relevant supply, advance payment or instalment situations. The ERP needs a defined event that starts invoice preparation rather than relying on a later manual batch.
Use the real transaction facts
Seller, buyer, goods or services, taxable base, VAT and transaction code must reflect the actual supply. Formal completeness is not a formatting exercise; it depends on authoritative master and transaction data.
Create the Faktur Pajak electronically
Coretax DJP is the central framework, while DJP also recognises integrated PJAP host-to-host services and e-Faktur Client Desktop for eligible scenarios. Channel choice does not change the underlying tax responsibility.
Carry the document into VAT reporting
Invoice acceptance, replacement, cancellation, input-credit visibility and VAT return preparation must preserve the same invoice identity. A successful creation in one channel is not enough if the periodic return cannot be reconciled.
Section references: DJP Regulation PER-11/PJ/2025 · DJP Coretax information center · DJP announcement on e-Faktur Client Desktop
The decisions behind a compliant tax invoice
Confirm the PKP and transaction
Identify the registered taxable entrepreneur, branch or centralised VAT entity, place of supply, counterparty and transaction date before selecting an invoice route.
Determine timing and tax base
Link invoice timing to delivery, payment, advance or milestone facts and calculate the taxable base, VAT and any luxury-goods sales tax from the approved commercial document.
Select the correct transaction code
Transaction codes affect the legal meaning and can affect channel availability. Codes 06 and 07 are among the Desktop exceptions identified by DJP.
Preserve replacement and cancellation lineage
A replacement, return or cancellation should reference the original tax invoice and remain connected to the VAT return and financial correction.
Section references: DJP Regulation PER-11/PJ/2025 · DJP Coretax information center · DJP announcement on e-Faktur Client Desktop
The operating baseline since 2025
| 1 Jan 2025 | Coretax implementation | Coretax became the operating core for tax administration processes, including tax invoices and VAT return workflows. |
|---|---|---|
| 12 Feb 2025 | Desktop channel broadened | DJP allowed all PKP to use e-Faktur Client Desktop subject to the exclusions in PENG-13/PJ.09/2025. |
| 22 May 2025 | PER-11/PJ/2025 issued | The regulation established technical reporting provisions for income tax, VAT, luxury-goods VAT and stamp duty in the Coretax framework. |
| Current operation | Three channels, one responsibility | Enterprises must keep channel eligibility, tax-invoice facts, corrections and VAT reporting under a single control model. |
Section references: DJP Regulation PER-11/PJ/2025 · DJP Coretax information center · DJP announcement on e-Faktur Client Desktop
Enterprise implementation considerations
- Tax point and billing date do not always mean the same thing. Advance payments, instalments and operational cut-offs need an approved rule in the source process.
- Transaction codes and buyer information are tax facts, not values for middleware to guess. Missing data should be returned to the accountable business owner before creation.
- Corrections must respect the original channel and document relationship. A replacement should not become an unrelated new invoice merely because another application performed the action.
- Desktop-generated invoices may appear in Coretax after a synchronization delay. Reconciliation needs to distinguish expected timing from a genuinely missing document.
Implementation controls for SAP/ERP landscapes
Tax-invoice readiness gate
Block transmission until PKP identity, buyer data, tax period, transaction code, tax base, VAT and original-document reference pass deterministic checks.
Channel eligibility rule
Route by official eligibility and scenario, not by temporary system availability. Record why Coretax, PJAP or Desktop was selected.
Number and identity control
Govern NSFP acquisition and use, Coretax 17-digit representation and original invoice identity without creating parallel numbering logic.
Correction lifecycle
Connect replacement, return and cancellation to the original invoice, source accounting entry and VAT-period treatment.
Period reconciliation
Reconcile SAP/ERP billing, issued tax invoices, Coretax visibility, error queues and VAT return totals before filing.
Recommended controls
- Build a scenario catalogue linking supply and payment events to tax-invoice timing and transaction codes.
- Assign one authoritative ERP source for each seller, buyer, tax, amount and original-document fact.
- Record the chosen channel on the invoice and use it when routing replacements or investigating missing visibility.
- Reconcile ERP billing, Faktur Pajak status and periodic VAT return data before close, including portal and desktop activity.
Frequently asked questions
Can every PKP choose any channel?
No. DJP identifies specific exceptions and process responsibilities. Eligibility and transaction scenario must be checked before routing.
Does using Desktop remove Coretax responsibilities?
No. DJP states that returns, cancellations and VAT-period reporting remain in Coretax, and Desktop data becomes visible there on a defined synchronization path.
Can the ERP generate an independent tax-invoice number?
The ERP should preserve the official numbering and identity rules. A local technical key may support integration but must not replace the legal invoice identity.
What is the minimum close control?
Match source billing, issued tax invoices, replacements or cancellations, Coretax records and VAT return totals, with unresolved differences assigned before filing.
Conclusion
Coretax is a tax-administration transformation, not merely a new endpoint. The safest design treats Faktur Pajak as a governed business document whose timing, data, channel, later events and VAT reporting remain connected from creation to period close.
Official sources
- DJP Regulation PER-11/PJ/2025
- DJP Coretax information center
- DJP announcement on e-Faktur Client Desktop
Last checked: 2026-08-30