When expansion breaks your finance stack – everything worked, until the second entity opened
A Singapore scaleup opens a second entity in Malaysia or Indonesia. Nothing dramatic happens at first.
For a while, the existing setup holds. Then, quietly, it doesn’t. Cash positions become estimates. Payments slow down. FX costs accumulate without anyone noticing. Approvals move to WhatsApp because it’s faster than the actual workflow. The finance team spends the week reconstructing last week’s numbers instead of acting on today’s.
By the time someone names the problem, the damage has already been running for months.
The expansion thesis isn’t wrong. The mistake isn’t opening the second entity; it’s assuming the finance infrastructure that worked in one market will stretch to cover two or three. It won’t. A second entity isn’t twice the complexity. It’s a different category of problem entirely.
What looks like a growth strategy problem, or a local market problem, is usually a finance infrastructure problem. And by the time it’s visible, the company is already absorbing the cost.
It looks like four different problems. It’s one.
Founders typically read the symptoms as separate, market-specific issues. Fix each one locally, the thinking goes, and the whole thing settles down. It doesn’t. Every symptom traces back to a single root cause: single-market infrastructure running a multi-entity business.
- Cash visibility collapses. Separate banking relationships in each market mean no consolidated view. What passes for a cash position is a spreadsheet built on last week’s exports – always stale, never fully trusted.
- Payments become operational drag. Cross-border transfers mean navigating different rails, FX rates, and approval chains with no unified workflow. The audit trail that survives a compliance review is thin at best.
- FX exposure accumulates silently. Without consolidated visibility across payables and receivables, founders absorb currency costs they can’t measure and haven’t priced in.
- Compliance obligations multiply. Every new market adds its own regulatory layer. Finance teams on single-market tools are exposed to audit trail gaps they haven’t noticed yet.
The instinct is to add a tool: a new payment provider here, a local account there. This makes it worse. Every addition deepens the fragmentation. The problem isn’t the number of tools. It’s that tools don’t compose into a system.
The tools available were built for someone else
This gap isn’t accidental. It’s the product of a market that was never built for the middle.
A decade of fintech innovation followed consumer scale: payments for individuals, digital lending, BNPL. The capital went where the volume was. The founder or finance lead running a growing business across three Southeast Asian markets was never the target segment. Nobody built for them.
At one end: enterprise Treasury Management Systems – powerful, but months to implement, expensive to run, and built for organisations with dedicated treasury teams. At the other: basic payment tools and business accounts that hit their ceiling the moment multi-entity complexity arrives.
The middle layer – enterprise-grade visibility and control, without enterprise-grade overhead – didn’t exist. As we’ve explored in Treasury Management Simplified: A CFO’s Guide to Cash, Liquidity, and FX, most finance teams are still running on manual processes and siloed portals that obscure risk rather than reduce it.
And the gap is widening. Initiatives like Project Nexus will make cross-border transfers as fast as a local PayNow. The rails are getting faster. The infrastructure sitting on top hasn’t kept pace.
Not another app. A single layer where treasury and payments are the same problem.
The fix isn’t additive. What regional scaleups need is a category of infrastructure that is built for them. TMS-lite sits between the complexity of enterprise treasury systems and the limitations of basic payment tools; combining cash visibility, forecasting, and payments into a single operating system.
In practice, that means three things working as one:
- Real-time cash visibility across all entities and currencies. The operational baseline from which every decision is made. Before a payment run, before a board meeting: the full picture is visible without opening a single bank portal.
- Cross-border payments with a full audit trail. Payments are not just execution. They are where control, compliance, and liquidity decisions happen. Who approved it, at what rate, against what cash position – that decision needs to live in the same system as the visibility. One workflow, one audit trail.
- Cash flow forecasting built on live data. A forecast rebuilt manually from static exports once a month isn’t a forecast – it’s a guess with formatting. The right infrastructure generates rolling projections as a byproduct of live transaction data.
- The financial intelligence layer that acts before you ask. A modern treasury system shows not only data, but also structures and interprets it. The right infrastructure surfaces decisions before you go looking for them.
This shift – from reactive reporting to real-time decision-making – is what separates finance teams that enable growth from those that slow it down. CFOs who adopt modern treasury infrastructure anticipate challenges, respond faster, and build confidence with boards and investors.
Three questions worth asking before signing anything
Most platforms claim to solve this. Three questions cut through the positioning:
- Can I see my full cash position right now, across all entities and currencies, without manual input or a daily refresh delay?
- Can I send a cross-border payment and have it approved without switching tools? One workflow, one audit trail?
- If MAS or an auditor asked who approved a specific transaction and when, could I answer in five minutes?
If the answer to any of these is no, or “it depends”, the platform is almost certainly a single-market tool being stretched beyond what it was designed for.
Building infrastructure that matches the ambition
Expansion doesn’t break companies. Invisible infrastructure gaps do. Singapore scaleups have always punched above their weight. The ones that continue to do so aren’t just moving fast; they’re building the financial infrastructure to support the speed.
Speed without financial clarity isn’t growth; It’s risk. Retrofitting after something breaks is far more expensive – in time, in capital, in trust – than building correctly at the point of expansion. The second entity is the right moment. Not the fifth.
Akhil Nigam is Chief Product Officer & Co-Founder at Finmo.
Akhil has over 20 years of experience in payments, corporate banking and technology. Prior to founding Finmo, Akhil held leadership roles at Citicorp Investment Bank, Mastercard and Fiserv(FirstData). Akhil had built out and scaled large scale platforms on acquiring, issuing and treasury management systems.
TNGlobal INSIDER publishes contributions relevant to entrepreneurship and innovation. You may submit your own original or published contributions subject to editorial discretion.
Featured image: Kampus Production