One payment, many GST questions: Why payment businesses need a transaction map

Why this matters now

Singapore's payments and digital asset sector has grown quickly and product innovation shows no sign of slowing. New fee models, embedded finance partnerships, cross-border corridors and loyalty structures are being launched at pace. The Inland Revenue Authority of Singapore (IRAS)'s updated e-Tax Guide on Digital Payment Tokens that was published in January 2026, is a timely reminder that the authorities are looking closely at how these arrangements are actually structured, not simply how they are labelled or marketed.

We are seeing a familiar pattern play out across the sector. Product and commercial teams move first, launching new features and pricing structures to stay competitive. Tax and finance are often brought in later, once the product is already live, rather than at the design stage. For a period, this gap is manageable. The risk is what happens when it is not.

Issues we are seeing

The further a commercial model runs ahead of its tax and finance documentation, the more expensive the eventual correction tends to be. A treatment that could have been resolved with a straightforward review at launch can, two or three years and several million transactions later, become a significantly larger exercise, involving historic exposure, systems rework and difficult conversations with the board.

A few patterns come up repeatedly.

The “one product, one treatment” assumption. Many businesses apply a single GST treatment to a payment product because that is how it is sold commercially. In practice, a single payment journey can include a processing fee, an interchange fee, a foreign exchange margin and a platform fee, each potentially payable to or by a different party, and each capable of a different outcome. Businesses are often surprised at how much of their fee structure sits outside the treatment they originally assumed.

Unclear contractual roles. Whether a business is acting as principal or agent in a transaction chain has a real bearing on the GST outcome, but this is not always clearly reflected in commercial contracts, particularly where products have evolved organically or been built on third-party infrastructure. This is rarely spotted until a fundraising due diligence process or a tax audit asks the question directly.

Evidence that does not match the story. We regularly find that the GST position a business intends to apply is not well supported by its own systems data. Settlement records, tax invoices and general ledger coding do not always tell a consistent story about who is contracting with whom, and at what point in the chain. When this surfaces during an IRAS review, the cost is rarely limited to the tax itself; management time, adviser fees and reputational exposure with the regulator all add up.

Cross-border ambiguity. Where a payment involves an overseas platform, an overseas customer, or processing outside Singapore, questions around the customer's belonging status and place of supply are common, and the answer is not always obvious from the product design alone.

None of this reflects poor management. It reflects a sector where the commercial model is simply moving faster than the systems and documentation supporting it. The issue is not that the gap exists; it is what happens if the gap is left to widen unchecked. The longer a business waits, the larger the transaction population affected, and the harder the eventual fix becomes.

Practical considerations

One issue we frequently encounter is that businesses have not mapped their transaction flows in enough detail to answer basic questions with confidence: who is the customer, who is the supplier, what is actually being supplied and where does the value sits within the fee structure. A practical transaction map, built collaboratively with product, finance and tax, is often a useful starting point, well before any technical conclusions are drawn.

It is also worth revisiting whether tax coding in finance systems still reflects the current product, rather than an earlier version of it. As products evolve, embedded tax logic can quietly fall out of step with how the business actually operates, often without anyone noticing until year-end or an external review.

Taking a proactive approach

Businesses that map their transaction flows early tend to find GST questions considerably easier to answer and are better supported when tested. Those that leave it too long often find the review comes with a bigger price tag attached and at a less convenient moment.

We regularly help clients work through exactly this kind of exercise, translating complex payment journeys into practical questions for tax, finance, product and risk teams to work through together. Where the gaps we find sit closer to process ownership, documentation standards or control design than pure tax treatment, we draw on colleagues in our Business Risk Services team, who work alongside our tax specialists to review how payment processes actually operate in practice, not just how they are meant to work on paper.

If your payment products have evolved over time, it may be worth testing whether your transaction flows, systems data and GST treatment still tell a consistent story. Where they do not, addressing the gaps early is typically easier than explaining them later.