Please ensure Javascript is enabled for purposes of website accessibility
Home FinTech Risk Your Diligence Cannot See: Settlement Structure as a Board-Level Question

Risk Your Diligence Cannot See: Settlement Structure as a Board-Level Question

fintech: settlement structure as a board-level question

Most executives can name their payment providers. Considerably fewer can say which settlement structures their cross-border flows actually pass through, or who else is using them. A forfeiture case in Thailand has turned that gap from an operational detail into a risk position.

Ask a leadership team about counterparty risk and you will get a competent answer. Who the customers are, how they were onboarded, what screening runs against them, which jurisdictions carry elevated exposure. That work is mature, well resourced, and, in most organizations, genuinely effective.

Ask the same team which rails a given corridor’s money actually moves on, and the answer tends to arrive more slowly. Payments infrastructure sits with treasury or operations. Risk sits with compliance. The structure of the settlement layer falls between them, owned in practice by whoever negotiated the provider contract, and reviewed on the schedule that contract renewal happens to impose.

That arrangement was defensible when settlement structure was a cost-and-speed question. It is becoming harder to defend now that enforcement practice has started to treat it as a liability question.

Key Takeaways

  • Executives know payment providers but often lack clarity on the settlement structure behind cross-border flows.
  • Pooled-account settlement structure is widely used for cross-border transactions, particularly in Southeast Asia, due to its efficiency.
  • Compliance obligations lie with the regulated operator, leaving firms unaware of other users in the pooled account, creating hidden risks.
  • The Yim Leak case illustrates how seemingly ordinary transactions can result in significant forfeiture due to lack of upstream visibility.
  • Leadership teams should map settlement structures to manage risk, ensuring they can demonstrate compliance and readiness if questioned.

What the Settlement Layer Actually Looks Like

Pooled-account settlement structure is the standard mechanism for cross-border currency exchange across much of Southeast Asia and many other regions. A regulated operator maintains a single clearing account through which many unrelated transfers settle each day. A business receiving funds is credited from that operator’s pool rather than from an identified upstream sender, and the operator handles the matching internally.

The model exists because it works. It clears faster and costs less than routing every transaction through correspondent banking, which is why an estimated 40 to 55 percent of cross-border funds entering Thailand from neighboring Southeast Asian countries move this way. Businesses using it are not taking a shortcut. They are using the infrastructure regional commerce developed around.

The compliance architecture was built to match. Under both regional and international anti-money-laundering frameworks, primary customer due diligence and transaction monitoring obligations sit with the regulated operator, for a reason that is purely structural: the operator can see into the pool and the recipient cannot. As analysis published on Washington City Paper has set out, allocation is deliberate design rather than an oversight in the rules.

The Turn That Changes the Calculation

Backward-tracing enforcement methodology cuts against that allocation. Where authorities trace funds back through a co-mingled clearing account and treat downstream recipients as connected to suspicious upstream deposits, a company’s exposure stops being a function of its own decisions and becomes a function of who else happened to use its operator’s pool.

For a board, this is a genuinely unfamiliar category. Ordinary risk is manageable because it is knowable, and the standard response to an unknown is to commission work that makes it known. That response is unavailable here. A firm can confirm its settlement partner is properly regulated, keep complete records of every transaction, and evidence the commercial purpose of each flow. It cannot audit the other users of that partner’s pooled account, because no mechanism exists for it to do so and none is going to be built. The information is not withheld. It is structurally unavailable to anyone but the operator.

The result is a risk that can be documented but not fully mitigated. That may be uncomfortable to present to a risk committee, but it needs to be presented accurately.

The Case That Made It Concrete

Thailand’s largest-ever forfeiture proceeding is where the question is currently live. The country’s Anti-Money Laundering Office has stated that a joint investigation with Thai police found links to alleged drug crimes, human trafficking, and transnational criminal organization. More than 20 billion baht, roughly USD 580 million, has been frozen in assets connected to Cambodian businessman Yim Leak and his wife. No criminal charges have been filed.

According to his legal team at Dentons Pisut and Partners, the contested transaction at the origin of the case was a currency exchange transfer worth approximately USD 165,000, processed through a regulated operator’s pooled clearing account, with no visibility into the upstream origins of the pooled funds. The frozen sum stands at roughly 3,500 times the value of that transaction. The legal team says the outcomes appear factually wrong as well as disproportionate, and points to a 2024 AMLO investigation that reviewed substantially the same assets connected to the same party, found no connection to criminal activity, and returned them.

For business leaders, the instructive detail in the Yim Leak case is not the headline number. It is that the transaction at the origin would look entirely unremarkable in any company’s records: a modest currency exchange, executed through a regulated intermediary, using the ordinary settlement route for that corridor. There is no decision in that sequence that a competent finance function would have flagged.

What This Changes in Practice

Two Thai criminal courts have already ruled that shared use of an authorized currency exchange and pooled accounts is insufficient to establish liability without evidence of intent or knowledge, and those decisions align with FATF Recommendation 3, which treats intent or knowledge as essential elements of a money laundering offense. Whether that reasoning carries into civil forfeiture proceedings is the open question, and it will be answered by courts rather than by anything a company does internally.

In the meantime, the useful work is narrower than most executives would like, and it is worth naming honestly rather than dressing up as a solution.

Leadership teams can require a corridor-by-corridor map of which settlement structures their flows actually use, and most will find this less visible than expected once they go looking. They can document the regulatory standing of every intermediary in the chain and keep it current rather than filed. They can retain settlement structure records granular enough to demonstrate the commercial basis of individual transactions rather than aggregate volume. Where one corridor depends heavily on a single pooled operator, they can treat that concentration as a risk position rather than purely a commercial arrangement.

For anyone conducting diligence on a payments business, whether as an investor or an acquirer, corridor and settlement structure exposure belongs alongside regulatory permissions and counterparty risk in the assessment. A target with concentrated dependence on pooled settlement in an aggressive enforcement jurisdiction carries a profile that a review of licenses will not surface. None of this eliminates the exposure, and any vendor claiming otherwise is selling something. What it does is put a company in a position to explain itself quickly and credibly if the question ever arrives, which in a category of risk that cannot be engineered away is the whole of what is available.

Subscribe

* indicates required