Loading Zantara...
Zantara AI
AI Research Assistant
Zantara AI
AI Research Assistant
Bali Zero handles visas, company setup, tax and property compliance in Indonesia. Ask us directly on WhatsApp.
Chat with Bali Zero on WhatsAppA tax payment, a commercial transaction and a VAT invoice tell different parts of the same story. For a Bali business, including a PT PMA, reviewing those records together can expose a discrepancy that an individual receipt does not explain.
DDTC reported on 19 October 2026 on weaknesses identified by Indonesia's Audit Board, BPK. The findings can also be checked directly in the official IHPS I/2026 report, printed page 32, in the central-government audit section.
BPK describes weaknesses in the Directorate General of Taxes Information System, SIDJP. These include inadequate timely detection of late payments, underpayments and payments assigned to the wrong tax period. The report identifies potential administrative-sanction revenue that had not been followed up through tax collection letters.
It also says SIDJP had not fully verified and validated VAT invoices against transactions, payments and reporting in periodic VAT returns. BPK identified indications of invoices not reported by taxpayers.
BPK recommended that the finance minister evaluate the system's detection capability and follow up the evaluation, including issues previously recommended for attention.
The section concerns the audit of 2025 financial statements. These are audit findings about systems and follow-up. They are not an assessment of an individual Bali company. Nor does this passage establish the current performance of every Coretax function.
The following is a practical preparation checklist, not a new reporting obligation announced by BPK.
Start with a defined tax period. Put the transaction record, relevant invoice, payment evidence and submitted return in the same review file. Record the taxpayer identity and reference numbers rather than relying only on a bank transaction description.
Check whether the payment was associated with the intended tax type and period. A payment receipt should be traceable to the obligation being reviewed; its existence alone does not resolve a mismatch elsewhere.
For VAT records, compare the invoice details with the underlying transaction and the return in which it was reported. Note cancellations, replacements or corrections so that the reviewer can follow the sequence without counting the same transaction twice.
A discrepancy is a reason to investigate, not an automatic instruction to make another payment or submit an amended return.
Ask the responsible tax adviser to establish whether the issue concerns the transaction data, an invoice, a payment allocation, reporting or the way a record is displayed. Keep supporting evidence and the explanation for any action taken.
Where a correction is appropriate, preserve the original record and the acknowledgement of the correction. This makes the file easier to review later and reduces the risk of treating an already resolved item as a fresh difference.
The cited passage does not announce a mass inspection campaign against PT PMAs or automatic penalties for every discrepancy. Any company's tax position must be assessed from its own facts and the applicable procedures.
For owners and finance teams, the useful response is a clear reconciliation trail: which period was reviewed, what differed, what evidence explains it and whether a responsible person has resolved the issue.
Primary source: BPK, IHPS I/2026, printed page 32. News context: DDTC, 19 October 2026. The preparation checklist is editorial guidance drawn from the record-matching issues described in those findings.