Multi-entity expense management: 2026 Malaysia guide

Key takeaways:

• If your expense platform requires separate logins per entity, you have account-switching, not true multi-entity expense management

• Malaysian group structures vary: a domestic multi-Sdn Bhd group and an ASEAN-expanding business face different problems, but the same platform limitations.

• Airwallex Global Entity Management gives Malaysian finance teams one login to view balances, approve spend, and run reports across every entity in the group.

Multi-entity expense management becomes essential once your business operates across more than one legal entity, and in Malaysia, that threshold arrives sooner than most finance teams expect.

It might be a holding company overseeing three operating Sdn Bhds across Peninsular Malaysia. It might be a retail group where each brand runs as its own entity. Or it might be a Malaysian business that has expanded into Singapore or Indonesia and now manages entities in multiple countries.

In each case, the problem is the same: expense platforms built for a single entity start working against you. This guide covers why that happens, what to look for in a multi-entity expense platform, and the questions to ask before you choose one.

Why Malaysian businesses end up with multiple entities

Not every multi-entity business starts with a plan to go global. In Malaysia, multiple legal entities often emerge gradually, driven by practical decisions that made sense at the time.

Here are some common structures:

• Holdco and operating Sdn Bhds: a holding company owns one or more operating subsidiaries, each incorporated separately for liability ring-fencing or group tax planning

• Domestic multi-entity groups: separate Sdn Bhds for different business units, brands, or geographies within Malaysia, each with its own SSM registration and LHDN Tax Identification Number (TIN)

• F&B, retail, and franchise operators: each outlet or brand runs as its own Sdn Bhd, a common structure in Malaysia where liability isolation matters

• ASEAN-expanding businesses: a Malaysian group adding entities in Singapore, Indonesia, Thailand, or Vietnam as it enters new markets

Each structure is legitimate and common. Each one also creates a distinct expense management problem the moment your finance team tries to get a consolidated view.

Why single-entity platforms break down when you expand

Most expense management platforms are built around one legal entity, with one currency, one chart of accounts, and one approval chain.

That works fine when your business operates out of a single office. The moment you add a second entity, the architecture starts working against you.

Every new entity multiplies your admin

When you add an entity on a single-entity platform, you're not extending your existing setup; you're rebuilding it from scratch.

You need a new account, a new card programme, a new approval policy configured independently, and a new vendor list, even if you're paying the same suppliers you pay everywhere else.

In Malaysia, a new Sdn Bhd also means a new LHDN TIN and its own MyInvois implementation obligation. Finance teams managing three or four entities end up running three or four parallel finance operations, each with its own login and its own reporting cadence.

The cost shows up at month-end. Someone has to export data from each portal, convert currencies manually for any ASEAN entities, and consolidate figures into the group’s reporting currency.

Approval workflows don't cross entity lines

On a single-entity platform, approval policies are set per account. A policy carefully configured for one Sdn Bhd has no bearing on what happens in another. If a group CFO needs visibility across both, they typically need separate logins.

There's also no way to catch a policy breach in one entity while reviewing spend in another, and this is the gap that finance teams flag most often when multi-entity setups outgrow their tooling.¹

The intercompany problem

Single-entity platforms typically don't manage intercompany transactions natively.

When a Holdco charges management fees to its subsidiaries, or one Sdn Bhd pays a shared supplier on behalf of another, those intercompany transactions become a manual spreadsheet problem.

They grow in volume with every entity you add, and none of them are visible at the group level.

When do you need multi-entity expense management?

Many businesses don't need multi-entity expense management from day one. But once you operate across multiple legal entities, managing expenses separately becomes increasingly time-consuming.

You may benefit from a multi-entity platform if:

• You've incorporated a second Sdn Bhd, whether for a new business unit, a second geography, or a new brand

• Your finance team exports reports from multiple systems every month to produce a consolidated group view

• Each Sdn Bhd has its own MyInvois compliance trail to manage, adding overhead for a single finance team

• You're tracking Sales and Service Tax (SST) across multiple entities with different revenue thresholds and vendor mixes

• The same suppliers — SaaS tools, logistics providers, professional services firms — are being managed and paid separately by each entity

• Executives or directors need consolidated MYR visibility across the group for board reporting

• Approval policies need to be applied consistently across entities, but today each entity runs its own process

• You're planning further expansion into ASEAN and want a finance setup that scales without rebuilding from scratch each time

If several of these apply, you've likely outgrown a single-entity platform.

What multi-entity expense management looks like

Not all multi-entity expense tools are built the same. Before evaluating platforms, it helps to understand which capabilities actually matter, and what problem each one solves.

1. Entity-level card issuance

Each entity needs its own cards, tied to its own currency and cost centre.

An employee in your Johor Sdn Bhd shouldn't be spending on a card denominated in the KL entity's budget, and your group finance team shouldn't have to reconcile transactions sitting in the wrong entity's ledger.

Entity-level card issuance means cards are issued per entity, with spending limits and policies that reflect that entity's budget. For groups with ASEAN entities, this extends to currency: an employee in your Indonesian entity spending in IDR needs a card that reflects that, not one denominated in MYR.

2. Consolidated group reporting

This is where most platforms fall short. Consolidated group reporting means your group can see aggregated balances, transactions, and spend across every entity in one view, without logging into each account separately or exporting data to a spreadsheet.

For Malaysian directors, this is the difference between a finance team that spends two days extracting and reconciling figures before every board meeting, and one that pulls a group-level MYR report in minutes.

3. Cross-entity approval workflows

A genuine multi-entity setup lets you manage approval policies centrally across all entities.

For example, you can set a rule that any expense above RM5,000 requires CFO sign-off and apply it consistently whether the expense originates in Kuala Lumpur, Penang, or Singapore.

4. Shared vendor directory

If your group pays the same software vendor or logistics supplier across multiple entities, you shouldn't have to enter that vendor's details separately in each account.

A shared vendor directory means payment information is entered once and available across the group, reducing admin and the risk of duplicate or incorrect vendor records.

Together, these four capabilities are useful to look for when evaluating multi-entity expense platforms.

Airwallex Spend gives you all four. Learn more about Airwallex Spend or sign up for free.

MyInvois and SST compliance across multiple entities

Most conversation about multi-entity expense management focuses on consolidation and approvals.

For Malaysian businesses, there's a compliance dimension that sits on top of all of that: each Sdn Bhd in your group is a separate taxpayer, with its own LHDN Tax Identification Number and its own MyInvois obligations. Here’s what to keep in mind:

Each entity carries its own e-invoicing obligations

Malaysia's mandatory e-invoicing rollout under the MyInvois system is assessed per entity, not per group. A subsidiary of a Holdco that has already implemented e-invoicing cannot claim the RM1 million revenue exemption; it is required to comply regardless of its own revenue figure.²

This matters for expense management. When employees in one Sdn Bhd incur costs from vendors who are required to issue MyInvois e-invoices, a paper receipt alone may not be sufficient documentation for LHDN purposes.

Your business should ensure MyInvois-validated documents are captured and retained for at least seven years. Your expense platform should support those record-keeping requirements where appropriate.

SST adds a per-entity layer

The 2025 SST scope expansion brought more business services under coverage.³ For multi-entity groups, SST amounts need to be tracked and reported separately for each Sdn Bhd: they do not roll up automatically just because entities share a finance team.

Your expense platform should capture SST fields per transaction so each entity's finance records are clean for filing.

Together, MyInvois and SST compliance give Malaysian businesses a concrete reason to evaluate expense platforms on documentation capability, not just consolidation features.

Multi-entity expense management vs. multi-entity accounting

The two terms are sometimes used interchangeably, but they solve different problems. Here's a quick overview:

Multi-entity expense management helps finance teams control and monitor day-to-day spending across multiple legal entities. It focuses on expenses before they reach the general ledger, giving teams visibility into employee spending, corporate cards, bill payments, and approval workflows.

Multi-entity accounting focuses on financial reporting. It consolidates financial data from multiple entities to produce accurate financial statements, manage intercompany transactions, and meet statutory obligations, including MPERS or MFRS reporting standards and LHDN filing requirements for each Sdn Bhd in the group.

For growing Malaysian businesses, the two systems complement each other.

Account linking vs. true multi-entity management

Many platforms market "multi-entity support", but the term covers a wide range of capabilities. Before taking a vendor's word for it, it's worth understanding the distinction between account linking and true multi-entity management.

Account linking

Account linking means separate entity accounts are connected under one login, so a user can switch between them. You can see one Sdn Bhd's spend, then switch to another's. But you're still looking at each entity in isolation.

There's no aggregated group view, no single approval engine, and no shared vendor directory. Reporting still happens per entity — you just don't need a separate password for each one.

For a finance team producing board-level reports, account linking doesn't remove the manual work. It just puts it in one browser tab instead of several.

True multi-entity management

True multi-entity management means the platform operates at the group level, not just the entity level.

You can see consolidated balances and transactions across all entities in one view. Approval policies can be managed centrally where appropriate, while still supporting entity-specific rules where needed. Vendor records are shared. And when you need to run a report, the data is already aggregated.

The practical test: can your group CFO see consolidated MYR balances across your Holdco and its operating Sdn Bhds without exporting to Excel? If not, the platform is closer to account linking than true multi-entity management.

Why this matters for board reporting

Board reporting requires group-level numbers. If your platform can't aggregate across entities natively, someone on your team is doing that aggregation manually every reporting cycle. That's where errors enter, and where finance teams lose hours they can't recover.

Questions to ask before choosing a multi-entity expense platform

The term "multi-entity support" appears on a lot of vendor websites. These questions help you cut through the marketing and test whether a platform genuinely manages across entities.

Can you see consolidated group spend in one view?

Ask the vendor to show you a group-level dashboard with aggregated balances and transactions across all entities. If the answer involves exporting data or switching between accounts, you're looking at account linking, not true multi-entity management.

Does one approval policy apply across all entities?

Find out whether approval rules are configured per entity or at the group level. A true multi-entity platform lets you set a policy once — say, any bill above RM10,000 requires CFO approval — and apply it across every entity automatically.

Is there a shared vendor directory?

If your group pays the same suppliers across multiple entities, ask whether vendor details carry across. Re-entering the same logistics provider or professional services firm in each entity account is a sign the platform wasn't built with group operations in mind.

How much setup does a new entity require?

Ask specifically what happens when you incorporate a new Sdn Bhd. If the answer is a full onboarding process, where you’ll need to create a new account, new card programme, and new approval configuration, that’s not ideal.

What does group-level reporting look like?

Request a demo of the reporting output your board would actually receive. Can it show spend by entity, by currency, and in a consolidated MYR view without any manual steps?

Why Malaysian businesses choose Airwallex for multi-entity expense management

Airwallex offers true multi-entity management, giving finance teams consolidated visibility across entities, a group-level approval engine, and infrastructure to scale into new markets without rebuilding your finance operations from scratch.

Here’s what you get with Airwallex:

• One login, consolidated view. See balances, transactions, and reports across every entity in your group (whether that's three domestic Sdn Bhds or a regional group spanning Malaysia, Singapore, and Indonesia) without logging into separate accounts or exporting to a spreadsheet.

• One approval engine. Set group-wide spend policies once and apply them across every entity automatically. Update a rule and it cascades everywhere.

• One vendor directory. Bill Pay means supplier details entered once are available across the group. No duplicate vendor records, no re-entry when paying the same logistics provider or SaaS vendor from a different entity.

• Cards that reflect your structure. Issue Corporate Cards per entity, with entity-level controls and group-level visibility sitting above them. Employees get reimbursed via local Malaysian rails so approved claims land in their accounts quickly.

• ASEAN-ready. As your group adds entities in Singapore, Indonesia, or Thailand, Airwallex scales with you. No rebuilding your finance operations from scratch for each new market.

Frequently asked questions (FAQs)

What is multi-entity expense management?

Multi-entity expense management is the process of tracking, controlling, and reporting on spending across multiple legal entities (such as a group of Sdn Bhds or a Malaysian holding company with regional subsidiaries) from a single platform. It goes beyond standard expense management by giving finance teams group-level visibility, rather than requiring them to manage each entity's finances in isolation.

Does my business need multi-entity expense management if all my entities are in Malaysia?

Yes, if you operate more than one Sdn Bhd. Each entity has its own LHDN Tax Identification Number and its own MyInvois obligations. Where applicable, SST registration and reporting are also assessed at the entity level. Managing them on separate platforms means separate card programmes, separate approval workflows, and manual consolidation at month-end, regardless of whether any of your entities are overseas.

What is the difference between account linking and true multi-entity management?

Account linking means separate entity accounts are connected under one login, so you can switch between them, but you're still viewing each entity in isolation with no aggregated group view. True multi-entity management means the platform operates at the group level: consolidated balances, group-wide approval policies, and shared vendor records across all entities.

How does MyInvois affect expense management across multiple Sdn Bhds?

Each Sdn Bhd is a separate taxpayer with its own MyInvois compliance obligation. A subsidiary of a holding company cannot claim the RM1 million revenue exemption, even if its own revenue falls below that threshold.² For expense management, this means platforms need to capture and store MyInvois-validated documents and retain them for at least seven years.²

How is multi-entity expense management different from multi-entity accounting?

Multi-entity expense management controls and monitors day-to-day spending before it reaches the general ledger. Multi-entity accounting focuses on financial reporting — producing consolidated financial statements, managing intercompany transactions, and meeting statutory obligations such as MPERS or MFRS reporting and LHDN filing for each entity. The two complement each other rather than overlap.

Can I manage expenses for entities in different ASEAN countries from one dashboard?

Yes, but only on platforms built for true multi-entity management. Airwallex Global Entity Management lets Malaysian-headquartered businesses view consolidated balances, transactions, and reports across all entities from one organisation-level login, regardless of where each entity is based.

What is a shared vendor directory and why does it matter for Malaysian group companies?

A shared vendor directory stores supplier payment details once at the group level and makes them available across all entities. Without one, finance teams re-enter the same vendor in each entity account, creating duplicate records and increasing the risk of payment errors. It's a practical test of whether a platform was built with group operations in mind.

Sources

1. community.concur.com/t5/Concur-Expense-Forum/One-user-works-in-different-legal-entity/m-p/16264

2. hasil.gov.my/media/0xqitc2t/lhdnm-e-invoice-general-faqs.pdf

3. /en-my/blog/what-is-expense-management