Indonesia E-Faktur and VAT Invoice Control Guide

A tax invoice is controlled only when PKP status, transaction facts, buyer identity, timing, tax treatment, approval, accounting, and VAT return data agree.

Indonesia e-Faktur and VAT invoice work should start with transaction facts, not with typing data into a tax system. Confirm the seller, buyer, supply, contract, delivery or payment milestone, currency, amount, tax status, location, exemptions or facilities, credit note or return, and supporting commercial invoice. Then determine whether the seller is confirmed as a taxable entrepreneur, which current issuance channel applies, and who may approve and post the tax invoice.

Confirm the company's PKP status and the transaction scope before building the invoice lifecycle. Use the VAT registration and PKP status requirements to verify the starting position, then connect each issued invoice to customer documents, the sales ledger, output VAT, corrections, payment evidence, and the periodic VAT return. Stop issuance and obtain advice when the status, timing, taxable base, counterparty data, or transaction treatment is unresolved.

Key takeaways

• Confirm live PKP and system authority before representing that a tax invoice can be issued.
• Use a transaction evidence sheet for timing, taxable base, buyer identity, and VAT treatment.
• Separate draft, issued, approved, delivered, corrected, posted, reported, and reconciled states.
• Reconcile invoice data to the VAT return and ledger before the filing is released.

In this article

• Confirm PKP and e-Faktur readiness
• Build the VAT invoice evidence sheet
• Control issuance, corrections, and customer delivery
• Reconcile e-Faktur to the VAT return and ledger
• Official references and review basis
• The release gate for an Indonesia VAT invoice

Confirm PKP and e-Faktur readiness

Create a go-live record for the legal entity that will issue the tax invoice. Record the entity name, NPWP and branch or place-of-business identifiers where relevant, PKP approval evidence, effective date, registered address, Coretax or permitted invoice channel, authorized users, digital authorization or certificate status, invoice series or system configuration where applicable, recovery contacts, and tested access. Do not charge or describe VAT merely because an application was submitted or a provider says activation is complete.

DGT's Coretax guide index includes official manuals for PKP applications, digital authorization, tax invoices, periodic VAT returns, and taxpayer data changes. DGT also confirmed that from 12 February 2025 qualifying PKP could use e-Faktur Client Desktop for covered invoice types, subject to the stated exclusions. The official announcement should be checked against current rules and the company's approved channel before setup.

Run a controlled test without inventing a real supply. Verify user roles, maker-checker approval, master data, output format, cancellation or correction route, export, backup, and VAT-return posting workflow. Keep company-controlled credentials and prohibit shared personal accounts. If status, location, buyer identity, or transaction classification is uncertain, pause invoice issuance and obtain Indonesian tax advice rather than forcing the transaction into a convenient code.

Build the VAT invoice evidence sheet

For every non-routine invoice, prepare a compact evidence sheet before issuance. It should identify the contract, purchase order, delivery or service evidence, advance or milestone, commercial invoice, seller and buyer identities, supply description, transaction date, invoice date, taxable base, VAT treatment, currency and conversion source where relevant, facility or exemption evidence, responsible preparer, reviewer, and supporting files. The objective is to let another reviewer reconstruct why the invoice was issued in that form and at that time.

DGT's current Coretax guidance on advance and settlement invoices states that tax invoices must reflect true transaction information and explains the electronic invoice workflow. Review the official advance and settlement guide for the current process, while confirming the actual legal timing and taxable base for the transaction. A tutorial is operational guidance, not a substitute for the governing regulation or professional advice.

Validate buyer data independently, especially NPWP or other required identity, legal name, address, branch, transaction reference, and facility evidence. Match the tax invoice to the commercial invoice without assuming they serve identical legal purposes. Create exception codes for missing buyer data, disputed delivery, deposit, partial fulfillment, bundled supplies, foreign currency, returns, and related parties. Resolve the tax analysis before the final approval state.

Control issuance, corrections, and customer delivery

Use a state model rather than a shared spreadsheet marked done. A document may be prepared, reviewed, approved in the tax system, delivered to the buyer, accepted commercially, corrected, canceled, replaced, posted to the ledger, included in a return, or reconciled. Record each state separately. The invoice owner should prevent duplicate issuance and should be able to identify the current valid document and its relationship to every prior version.

DGT's Coretax manual library includes topics such as invoice creation, approval, buyer identity, input tax, synchronization between invoice lists and returns, and advance invoices. Use the current relevant module, because transitional methods and application behavior can change. Preserve official error messages and support responses rather than re-keying repeatedly until a document happens to pass.

Design a controlled correction route. Confirm whether the factual error affects the commercial invoice, tax invoice, accounting entry, customer record, or filed return. Obtain approval, link the old and new documents, notify the customer through a recorded channel, prevent double credit or double revenue, and decide whether a return correction is required. Do not delete source evidence or create a fresh invoice that hides the original sequence.

Reconcile e-Faktur to the VAT return and ledger

Before filing, reconcile issued output tax invoices to the sales ledger, general ledger, commercial invoice register, cancellations and corrections, customer advances, returns, foreign-currency entries, and any non-invoice taxable events. Separately reconcile input tax invoices to supplier documents, eligibility review, accounts payable, payment evidence where relevant, and claimed or deferred credits. Every difference needs an owner, reason, value, period, treatment, and closure evidence.

DGT's official Coretax periodic VAT return manual explains posting invoice data to the VAT return. Posting is not the same as confirming completeness or tax correctness. Compare the system-prepared data with the company's books and approved transaction population, then preserve the return, receipt, payment evidence, reconciliation, and outstanding items.

Close the period with a signed control pack: invoice population, exceptions, issued and corrected documents, customer delivery, input tax review, ledger bridge, return draft, payment approval, official receipt, and post-filing balance. Connect it to the post-registration tax setup map so VAT invoice operations do not begin before the surrounding tax, bank, and bookkeeping controls are ready.

Official references and review basis

The following primary sources were checked on August 1, 2026. They establish the regulatory or service boundary used in this article; bank, tax office, OSS, AHU, and immigration decisions can still depend on the current record and the facts of a particular application.

• DGT — Coretax manual library — Current official index for invoice, VAT return, registration, authorization, and related Coretax procedures.
• DGT — e-Faktur Client Desktop announcement — Official February 2025 announcement on covered desktop issuance and stated exclusions.
• DGT — Advance and settlement invoice guide — Official operational guidance on truthful invoice data and advance or settlement workflow.
• DGT — Periodic VAT return manual — Primary Coretax manual for preparing and posting data to the periodic VAT return.

The release gate for an Indonesia VAT invoice

Release an e-Faktur only when the issuing entity and PKP status are confirmed, the transaction and timing are evidenced, seller and buyer data are verified, the taxable base and treatment are reviewed, the correct current channel and authority are used, and the approved document can be linked to the commercial invoice and ledger. Record limitations rather than presenting system acceptance as a tax ruling.

At period end, prove completeness through a bridge from the transaction population to issued, canceled, corrected, and unissued items, then to the VAT return, payment, official receipt, and ledger. If PKP, supply, timing, cross-border, facility, or correction treatment is uncertain, obtain Indonesian tax advice. For wider entity readiness, use the Indonesia company registration framework .

Related insights

• VAT registration and PKP status
• Indonesia company tax setup
• Local payment collection controls
• PT PMA bookkeeping requirements