System Error Risks Input Tax Forfeiture: How PT SPV Saved IDR 4.4 Billion in Import VAT Due to Technical Reporting Constraints

Tax disputes are often not merely about legal interpretation, but a clash between administrative rigidity and technical realities on the ground. The case experienced by PT SPV against the Directorate General of Taxes (DGT) serves as a classic example of how the limitations of the tax authority's IT system can drag a Taxpayer into a dispute worth billions of Rupiah. With a dispute value reaching IDR 4.6 billion, this case highlights the crucial issue of crediting Input Tax (PM) from customs documents (BC 2.5) that were reported in the "wrong room" within the VAT Return.

The Core Issue

The core issue began when the DGT made a positive correction on SPV's VAT Tax Credit. The tax auditor found that SPV reported Import VAT in a lump sum in the "VAT prepaid within the same Tax Period" column (Form 1111 II.B), whereas normatively, it should have been detailed transaction by transaction in Form 1111 B1. For the DGT, this was a fatal procedural violation. Furthermore, the DGT argued that SPV did not submit the BC 2.5 document evidence during the audit, so pursuant to Article 26A paragraph (4) of the KUP Law, such evidence was deemed non-existent.

Technical Facts and Taxpayer Arguments

However, behind this reporting "error," there was a compelling technical fact. PT SPV argued that reporting in Form 1111 B1 was impossible because the e-Faktur/Web-Faktur application system failed to retrieve exchange data from the Customs and Excise (DJBC). Without synchronized data, the system rejected the BC 2.5 input. Upon consultation advice from the Account Representative (AR), SPV finally "parked" the reporting in the prepaid VAT post to ensure it was recorded as paid. SPV emphasized substance: the tax had been paid to the state treasury, evidenced by valid DJBC Billing and Tax Payment Slips (SSP).

Considerations of the Tax Court Judges

The Panel of Judges of the Tax Court, in their consideration, took a position prioritizing substantial justice (substance over form). The Judges confirmed that the data exchange system constraint between the DGT and DJBC indeed occurred and was implicitly acknowledged by the Respondent. Therefore, a reporting post error due to a system force majeure should not eliminate the Taxpayer's right to credit taxes that have factually been paid. The Judges asserted that BC 2.5 documents for which the Import Taxes (PDRI) have been paid hold a status equivalent to Tax Invoices pursuant to Article 13 paragraph (6) of the VAT Law and are valid for crediting.

Implications of the Ruling

This ruling provides a breath of fresh air as well as a warning for Taxpayers. The main implication is that the court tends to side with material truth (money flow/payment proof) over administrative defects caused by authority system failures. However, SPV's victory was not absolute; a correction of IDR 205 million was maintained by the Judges because SPV failed to present physical document evidence for that value.

Conclusion

In conclusion, the PT SPV case teaches that in the era of tax digitalization, a system "glitch" can be fatal. The most important lesson for Taxpayers is: manual documentation (hardcopy/digital archive) of customs documents like BC 2.5 and payment proofs are the backup "lifeline." When the system fails, physical evidence speaks in court. Never rely entirely on data stored in the authority's system without having independent backups.

A Comprehensive Analysis and the Tax Court Decision on This Dispute Are Available Here.