A finance controller reconciling a July invoice for a cloud subscription noticed something odd. VAT had been deducted, but not by the vendor. The deduction showed up on the payment statement instead, issued by the bank that processed the transaction. Nothing about the underlying subscription had changed. What had changed was the government’s second attempt at catching VAT on foreign digital transactions that the first attempt never fully reached.
That second attempt now has a name, a legal basis, and, as of a few weeks ago, an operating regulation. It runs alongside the older system rather than replacing it, and understanding why two systems now cover the same tax object is exactly the kind of detail that gets lost between the regulation being announced and a finance team actually reconciling against it.
Two Regimes, One Underlying Tax Object
Both schemes tax the same thing: the use, in Indonesia, of intangible goods or services delivered from abroad through electronic means, software subscriptions, cloud infrastructure, digital advertising, streaming content, and similar arrangements. Neither one changes what counts as taxable. What changes is who is legally responsible for collecting the VAT before it reaches the state treasury.
The older system, Perdagangan Melalui Sistem Elektronik (PMSE), has been running in some form since 2020 and currently operates under Minister of Finance Regulation No. 81 of 2024 together with Director General of Taxes Regulation No. PER-12/PJ/2025. Under PMSE, the foreign vendor or platform itself collects the VAT, once the Directorate General of Taxes has formally appointed it as a collector. The registration thresholds, the 11 percent effective rate mechanics, and which vendors have already been appointed are covered in detail in a separate explainer on how VAT works for foreign companies transacting into Indonesia.
The newer system, Sistem Pemungutan Pajak atas Transaksi Digital Luar Negeri (SPP-TDLN), sits on a different legal foundation. Presidential Regulation No. 68 of 2025 established the framework, and Minister of Finance Regulation No. 49 of 2026, signed on 14 July 2026 and promulgated on 20 July 2026, sets out the operating mechanics. Both rest on the same underlying statutory authority, Article 32A of the General Tax Provisions Law (Undang-Undang Ketentuan Umum dan Tata Cara Perpajakan), which lets the Minister of Finance appoint third parties to withhold, collect, remit, and report tax on the government’s behalf.
Who Actually Collects the Tax Is the Real Difference
PMSE: The Vendor Is the Collector
Under PMSE, the party closest to the sale, the vendor or the platform facilitating the sale, does the collecting. This works well for large, well-known vendors that clear the appointment thresholds. It does not reach every foreign digital vendor a company might pay, because appointment under PMSE depends on the vendor crossing a transaction value or user count threshold in the first place.
SPP-TDLN: The Payment Channel Is the Collector
SPP-TDLN closes that gap by moving the collection point away from the vendor entirely and placing it on the payment side of the transaction instead. Under PMK 49/2026, the entity responsible for collecting is termed Pihak Lain, defined as the Penerbit, which is the bank or non-bank payment service facilitating the transaction. The Minister of Finance formally appoints each Penerbit as Pihak Lain, a power delegated in practice to the Director General of Taxes.
Sitting above the Penerbit is the Penyelenggara SPP-TDLN, the entity operating the underlying system itself. That role has been assigned, under Perpres 68/2025, to PT Jalin Pembayaran Nusantara, a fintech subsidiary of a state-owned financial technology and payment systems group. When a payment is made, the Penerbit sends transaction data to Jalin for confirmation, and the VAT obligation only becomes formally due at the moment Jalin confirms the transaction is subject to VAT, a confirmation PMK 49/2026 requires to be issued within one working day.
Because SPP-TDLN operates on the payment rail rather than the vendor relationship, it catches exactly the transactions PMSE structurally cannot, purchases from smaller or newer foreign vendors who have never crossed the PMSE appointment threshold, paid through a card or payment provider that has itself been designated as Pihak Lain.
Explore Our Services Tax Compliance in Indonesia
How the Timing and the Formula Differ
Beyond who collects, the two schemes diverge on when the tax becomes due and how the amount is calculated.
| Aspect | PMSE | SPP-TDLN |
| Tax point | When the consumer makes payment | When the Penyelenggara SPP-TDLN confirms the transaction is taxable |
| Calculation | Roughly 11 percent effective rate applied to the amount paid | 11/111 extracted from a payment value treated as VAT-inclusive |
| Remittance deadline | End of the month following the tax period | Within 7 days of the confirmation being issued |
The formula difference is easy to skip over and matters more than it looks. PMSE treats the amount paid as the base and applies VAT on top of it. SPP-TDLN, under Pasal 7 of PMK 49/2026, works in the opposite direction. It assumes VAT is already embedded in the price the payer sees, and extracts it out using the 11/111 fraction. Neither approach overcharges the payer relative to the other by design. They simply start from different assumptions about whether the displayed price already includes tax, and a finance team reconciling VAT across both schemes needs to know which assumption applied to which transaction rather than applying one formula uniformly across all foreign digital spend.
Telling Which Track a Given Vendor Payment Falls Under
For a company paying multiple foreign digital vendors, working out which scheme applied to a specific transaction comes down to a few practical signals.
- A vendor invoice that already itemizes VAT, from a name widely known as an appointed PMSE collector, has almost certainly been handled under PMSE, with the vendor as the collector.
- A smaller or newer vendor, paid through a specific card or payment provider, is more likely to have had VAT collected at the payment level under SPP-TDLN, with the vendor itself playing no collection role at all.
- Either collection proof is valid for input tax credit purposes. Documents issued under PMK 49/2026 Pasal 10, whether structured as a formal document or a bill statement, are treated as equivalent to a tax invoice, provided the payer’s registered email or phone number is on file with the Directorate General of Taxes and standard input tax crediting conditions are met.
That crediting mechanism matters operationally, and it connects directly to how a company’s monthly VAT return gets built. Where the proof of collection lands, and how it reconciles against a company’s own Coretax records, is exactly the process covered in a separate look at issuing and reconciling tax invoices under Coretax, which applies whether the underlying collection document came from a PMSE vendor or an SPP-TDLN Penerbit.
A Gap Worth Watching: Overlap Between the Two Schemes
Because PMSE and SPP-TDLN run on structurally different tracks, vendor identity for one and payment channel for the other, there is a real possibility that a single transaction gets touched by both mechanisms at once, particularly for vendors that sit in an ambiguous middle ground.
PMSE already has a defined resolution path for this. Where VAT has been collected by an appointed vendor but a consumer separately self-assessed and remitted VAT on the same transaction, the excess can be reclaimed, credited, or deducted from gross income under existing PMSE provisions.
PMK 49/2026 does not yet spell out an equivalent cross-scheme resolution specifically for a transaction that gets caught by both PMSE and SPP-TDLN simultaneously. What the regulation does provide, under Pasal 16, is a mechanism for reclaiming VAT that was collected through SPP-TDLN when it should not have been collected at all, whether because the underlying transaction was cancelled or because it was exempt. That is a narrower remedy than a dedicated PMSE-versus-SPP-TDLN overlap rule, and companies transacting at volume with a wide mix of foreign vendors are the ones most likely to encounter the gap before a formal resolution path for it exists.
What This Actually Changes for a Company’s VAT Position
For most companies, the practical answer is reassuringly narrow. Total VAT liability on foreign digital purchases does not increase because SPP-TDLN exists. What increases is the number of places collection proof can now come from, and the discipline required to match each proof document against the correct scheme before it gets entered into a VAT return.
XPND’s tax compliance team reviews exactly this kind of mixed evidence trail for clients with recurring foreign vendor spend, checking whether a given collection document reflects PMSE or SPP-TDLN, confirming it meets the conditions to be credited as input tax, and flagging the transactions still sitting in the overlap gap described above before they turn into a mismatch at filing time. Two collection systems now cover the same tax object from two different directions, and the only real risk is treating a document from one system as if it followed the other’s rules.