Country
Indonesia
Article type
Platform explainer
Last checked
2026-08-30
DJP identifies three main ways to create a Faktur Pajak: Coretax DJP, a PJAP service integrated with Coretax through host-to-host, and e-Faktur Client Desktop. The useful question is not which channel is universally best. It is which channel is permitted and operationally appropriate for a specific entity and transaction—and how all three feed one control and reconciliation model.
Platform explainer · Indonesia
Authorized issuance channels
A finance team may use the Coretax portal for selected manual scenarios, a PJAP connection for high-volume ERP billing and the desktop application for eligible operational cases. These are not three independent invoice universes. They ultimately support the same taxpayer identity, VAT responsibility and periodic reporting process.
The desktop route was broadened from 12 February 2025, but the DJP announcement lists exclusions, including transaction codes 06 and 07, certain branch-centralisation cases and PKP registered after 1 January 2025. Eligibility therefore has to be explicit; volume alone cannot select the channel.
Once a channel creates the tax invoice, its origin remains important. Replacement behaviour, invoice-number handling, synchronization into Coretax and investigation of missing documents can depend on that original path.
Section references: DJP announcement on e-Faktur Client Desktop · DJP e-Faktur Client Desktop FAQ · DJP Coretax information center
Channel selection criteria
Confirm entity eligibility
Check PKP registration, registration date, VAT centralisation and any restrictions published for the channel.
Classify the transaction
Determine the real transaction code, supply type, buyer facts, tax point and whether the scenario is excluded from a channel.
Match the operating need
Portal supports direct human operation, PJAP supports integrated host-to-host processing, and Desktop supports eligible local operation. Consider volume, control and support—not only connectivity.
Record the chosen route
Store the channel together with invoice identity, number, source document and response so later events follow the correct path.
Reconcile in one place
Bring Coretax, PJAP and Desktop results into one finance view for replacements, missing visibility and VAT return preparation.
Section references: DJP announcement on e-Faktur Client Desktop · DJP e-Faktur Client Desktop FAQ · DJP Coretax information center
Channel characteristics
Coretax DJP
Direct use of the central taxpayer platform.
Useful for supported portal processes and authoritative visibility, but manual work and role design must be controlled.
Integrated PJAP
Host-to-host service connected with Coretax DJP.
Suited to ERP automation and volume where the provider, interface contract, acknowledgement and support responsibilities are clear.
e-Faktur Client Desktop
Local desktop application available to PKP subject to published exclusions.
Requires local operational ownership, correct invoice-number handling and monitoring of synchronization into Coretax.
Enterprise control layer
Not a fourth tax channel, but the common view across all routes.
Owns deterministic routing, source traceability, exception worklists and reconciliation without redefining tax facts.
A channel-aware operating architecture
Coretax, PJAP and e-Faktur Client Desktop are not interchangeable transport buttons. The operating model must preserve one invoice identity while assigning the correct responsibilities to each channel.
Eligibility and routing
Evaluate PKP status, registration date, branch centralisation and transaction code before choosing the authorised channel.
Coretax direct operations
Use Coretax for the processes assigned to it, including returns, cancellations and VAT-period reporting identified in DJP's Desktop announcement.
PJAP host-to-host
Where an approved PJAP route is used, govern interface credentials, message acknowledgement, business status, error ownership and reconciliation separately.
Desktop continuity
For eligible scenarios, manage NSFP through e-Nofa, keep the original invoice identity and recognize that data visibility in Coretax may follow the stated H+2 synchronization path.
Unified control layer
Expose one workbench for source invoice, selected channel, official number, status, replacement chain, Coretax visibility and period-close reconciliation.
Common control deficiencies
Default every failure to another channel
A technical failure does not prove that another route is legally eligible. Uncontrolled fallback can split the document history.
Let the provider invent missing tax facts
A PJAP may transport and validate data, but buyer status, transaction code, taxable base and original-document relation must come from an approved business source.
Treat synchronization delay as loss
Desktop data is expected to become available in Coretax no later than two days after issuance under the DJP FAQ. Monitoring needs an ageing rule before declaring a missing invoice.
Frequently asked questions
Which PKP cannot use Desktop under PENG-13/PJ.09/2025?
The announcement lists transactions with codes 06 or 07, certain branch-centralisation situations and PKP registered after 1 January 2025 among the exceptions.
Where are Desktop replacements created?
DJP states that a replacement for an invoice originally created in Desktop is made through Desktop, preserving the original processing lineage.
How quickly does Desktop data appear in Coretax?
The announcement states that Desktop transaction data is available in Coretax periodically, no later than H+2.
Where are returns, cancellations and VAT-period returns handled?
DJP assigns those processes to Coretax even when the original tax invoice was created through Desktop.
Should an outage automatically switch channels?
No. A channel change can alter eligibility, numbering, status ownership and correction flow. It requires a governed business decision, not an automatic transport fallback.
Recommended architecture principle
Choose the channel explicitly, preserve it as part of the invoice history, and reconcile all routes through one business identity. This gives local teams flexibility without turning Coretax, PJAP and Desktop into disconnected records that finance must repair at period end.
Official sources
- DJP announcement on e-Faktur Client Desktop
- DJP e-Faktur Client Desktop FAQ
- DJP Coretax information center
Last checked: 2026-08-30