Skip to content
Kuala Lumpur, MalaysiaMYT (+6) 03-7890 3946
EN Contact Partner portal Sign in
eBook · Planning

Choosing between single-entity and multi-entity ERP

How to decide whether your next system should run one set of books or several — and the questions that usually force the answer.

SectioneBooks & guides
DateEvergreen
Written bySenangUrus implementation team
Reading time18-page guide
WhatsApp
Start reading Request the PDF

The single-entity or multi-entity decision is usually made too late, in the middle of an implementation, when changing it costs the most. It is a business structure question that determines which edition of an ERP you should be buying.

At a glance

  • Entities, branches and dimensions listed and agreed
  • Inter-company transactions mapped
  • Currency requirements documented
  • Upgrade path and data continuity confirmed with the vendor
  • Consolidation reporting requirements specified
Chapter 01

What counts as an entity

An entity is a set of books: its own chart of accounts, customers, suppliers and documents, with its own statutory reporting. A branch, outlet or department is not automatically an entity — it is usually a dimension inside one set of books.

What this phase owes you

  • Legal entity: statutory accounts, tax filings, separate registration
  • Branch or outlet: same books, separate reporting dimension
  • Brand or business line: reporting split, not necessarily separate books
  • Franchise or joint venture: almost always its own entity
Chapter 02

Signals you need more than one account

Five signals reliably indicate multi-entity: separate statutory filings, inter-company transactions, different ownership or shareholders, different currencies, and reporting to a group or holding company.

What this phase owes you

  • Statutory accounts are filed separately for each company
  • Transactions move between the companies and must be recorded on both sides
  • Shareholders or directors differ between the companies
  • Revenue and costs are reported in more than one currency
  • A holding company or group requires consolidated reporting
Chapter 03

What multi-entity changes in daily work

Multi-entity adds inter-company transactions, consolidation with eliminations, and a permission model where each user's visibility is defined by entity. It also removes a whole class of manual month-end work.

What this phase owes you

  • Inter-company invoicing and matching
  • Consolidated profit and loss and balance sheet with elimination entries
  • Multi-currency transactions and revaluation
  • Entity-level and group-level permissions
Chapter 04

Deciding, and timing the upgrade

If you expect a second entity within twelve months, model it from the start. Editions that share one data model make this an upgrade rather than a re-implementation — history, configuration and user accounts carry forward.

What this phase owes you

  • Model the next twelve months, not only today's structure
  • Confirm the upgrade path between editions before you commit
  • Check whether history and configuration carry forward on upgrade
  • Choose the edition that fits the structure you are moving toward
Filed underPlanningBusiness case
SenangUrus implementation team · editorial

Written by the SenangUrus implementation team and reviewed by the consultants who run these deployments. Where a piece draws on a customer's numbers, the customer has agreed to be named.

Other guides

Keep going

The ERP implementation playbook for Malaysian SMEs

24-page guide

e-Invoice readiness checklist

16-page checklist

Print or PDF version available on request

Next step

Run this guide as a workshop with your team

We can facilitate the guide as a working session — scoping, data readiness or the entity decision — and leave you with the completed document.

Book a workshop All guides