Indonesia
B2B, B2C, Outbound, Tax Reporting
2026-08-28
Invoice creation is only the start of the Indonesian tax invoice lifecycle; corrections and reporting need the same document lineage.
How to use this guide
A useful project outcome is not a document that merely repeats the rule. It is a traceable decision model that connects the rule to legal entities, transaction scenarios, source data, system behaviour, operating ownership and evidence.
Country-specific decisions
01
Respect channel-specific correction rules
DJP states that a replacement for an invoice created in e-Faktur Client Desktop remains in that desktop application. The operating model must therefore retain the original channel as part of the invoice identity.
02
Plan for visibility timing
Desktop invoice data is made available periodically in Coretax DJP no later than two days after issuance. Reconciliation controls should distinguish expected synchronization delay from a genuine missing document.
03
Connect invoice and return controls
Returns, cancellations, replacements and VAT return preparation must reference the same original invoice facts so that tax reporting does not diverge from customer and accounting records.
Operate by scenario, not by a single status field
Daily control needs an explicit action and owner for every material scenario.
| Decision area | What must be decided | Evidence to retain |
|---|---|---|
| Accepted | Confirm that the authority/platform result, customer delivery and ERP status agree. | Matched document chain and reconciliation timestamp. |
| Rejected | Classify master-data, tax, format or routing cause and send it to the correct resolver. | Reason, owner, correction action and resubmission result. |
| Unknown / timeout | Query status before retrying; never assume failure merely because a response was not received. | Status enquiry, correlation ID and idempotent retry decision. |
| Corrected / cancelled | Keep the original document immutable and link every subsequent event or document. | Relationship chain and final legal/business state. |
| Period-end open item | Explain every source invoice without a terminal electronic-invoice outcome. | Signed reconciliation and ageing of unresolved exceptions. |
Responsibility cannot sit with IT alone
The same exception often crosses tax interpretation, accounting, customer communication and technical processing. Assign the business decision before go-live.
| Primary owner | Required outcome |
|---|---|
| Tax | Own scope, tax treatment, statutory timing and interpretation of authority changes. |
| Finance operations | Own invoice completeness, exception ageing, correction execution and reconciliation. |
| Business / customer service | Own missing commercial facts, customer communication and delivery disputes. |
| IT / integration | Own technical availability, deterministic routing, observability and safe replay. |
| Local adviser or compliance owner | Resolve ambiguous cases and document the approved interpretation. |
Control rhythm from daily work to period close
Operational quality comes from cadence and ownership, not from a dashboard alone.
- Continuous
Capture responses, prevent uncontrolled duplicates and route actionable exceptions. - Daily
Reconcile posted source documents to submissions, outcomes and customer deliveries. - Weekly
Review recurring rejection causes, master-data defects and manual interventions. - Period close
Resolve or formally explain every non-terminal item before tax and financial close. - After change
Regression-test critical scenarios whenever authority rules, mappings or ERP logic change.
Minimum operating controls
- One business identity remains stable across source, transmission, response and adjustment.
- A retry cannot create an uncontrolled duplicate.
- Users see the next business action, not only a technical error message.
- Manual portal activity is captured in the same reconciliation view as automated traffic.
- Audit retrieval reconstructs the complete history without relying on an individual's mailbox or spreadsheet.
Official sources
- DJP Coretax information center
- DJP announcement PENG-13/PJ.09/2025 on e-Faktur Client Desktop
- DJP FAQ for e-Faktur Client Desktop