# The Modular ERP Buyer's Guide

> How to evaluate a modular ERP for a business of 20 to a few hundred people: how it's built, rollout, cost, security, and the questions that predict fit.

By Circumz Team · Published 12 May 2026 · 14 min read
Source: https://circumz.com/resources/modular-erp-buyers-guide

This is the long version of [what to look for in an ERP](https://circumz.com/blog/what-to-look-for-in-erp-for-growing-businesses). Use it with a vendor in the room: each section ends with questions you can ask and what a good answer sounds like.

## Who this is for

Businesses that have outgrown spreadsheets and separate tools but do not need a multi-year enterprise programme. Typically 20 to a few hundred employees, with sales, purchasing, stock, payroll and invoicing as daily work, where reconciling between systems has become a measurable cost.

If you are weighing the largest enterprise suites with a dedicated implementation team, the system and security sections still apply. The rollout and cost sections will look different.

## Part 1. How the system is built

### 1.1 Shared data, or shared login

Modular can mean pricing or how the system is built ([the difference](https://circumz.com/blog/how-modular-erp-systems-work)). Test it directly.

- Create a customer in CRM. Does it appear, without action, in quotations, invoices and any industry module?
- Enable a module you have not used. Does it need an import or a mapping of your customers and items?

A good answer: modules read the same records, and enabling one is a setting.

### 1.2 Dependencies stated

Modules depend on each other. Accounting needs Finance. Payroll-based billing needs HR. A vendor should have a clear list and block a bad combination at setup.

### 1.3 Saved together

Ask whether a document and the entries it produces are saved together. If a bill can save but its ledger entry fail, you will spend months finding the difference.

## Part 2. Rollout

### 2.1 Time to first real month

For a business of this size, a first real month-end inside a quarter is a reasonable target. Ask what a typical customer did in the first 90 days, not what the brochure says.

### 2.2 Order of adoption

A sensible order for most businesses:

1. Customers, items, suppliers and opening stock.
2. Sales and procurement, so documents start flowing.
3. Finance and invoicing in parallel with the old process for one cycle.
4. Accounting, with a go-live date and an opening journal ([guide](https://circumz.com/resources/accounting-go-live-guide)).
5. Industry modules and payroll, once the core numbers are trusted.

### 2.3 Getting your data in

Ask which records can be imported, in what format, and who corrects errors. Opening balances and stock are the difficult ones.

## Part 3. Money, tax and language

If you operate in more than one currency or country, check each of these.

| Capability | What to check |
|---|---|
| Base currency | Chosen per company, and what locks it once you have documents |
| Foreign-currency documents | Rate frozen on the document, inherited by what it creates |
| Settlement | Exchange difference recorded when a payment clears an invoice |
| Revaluation | Whether open foreign balances are revalued, and when |
| Tax codes | Per line, with category and rate, not one rate per company |
| E-invoicing | What is produced for your country, and whether unfiled documents say so |
| Language | Which languages, whether layout reverses for right-to-left, how much is translated |

See the [currency and tax setup guide](https://circumz.com/resources/currency-and-tax-setup-guide).

## Part 4. Controls and security

- **Permissions** per module with separate rights to view, create, edit, delete and approve.
- **Approvals** where money leaves: purchase requests, large discounts, payroll, returns at a till.
- **Audit trail** on documents: who created, received, issued or paid, and when.
- **Immutability** of issued invoices and posted journals. Corrections should be new documents.
- **Separate company data**, so no company can ever see another's records, even by mistake.
- **Sensitive data**: who can see salaries, how bank details are stored.

Ask to see the role list and what each role can do, not just that roles exist.

## Part 5. Fit for your industry

Industry modules are where vendors are weakest, and where the limits matter most. For each one you need, ask:

- What is the workflow from the first document to the last?
- What does the module not do? Ask for specifics.
- Which of those missing things would you have to run outside the system?

A vendor with a specific list of limits has looked at them. Examples of the kind of answer you want: "receipts are sales receipts, not tax invoices", "bank statements are matched from a CSV file only, with no bank feed", "an award goes to one supplier for the whole request".

## Part 6. Cost

Per-seat pricing is easy to compare and often wrong for how you work. Ask:

- What is included at each price, and what is a separate charge?
- How does price change when you add a module, a company or a user?
- Is anything priced that you cannot use today?
- What does it cost to leave: export format, retention of your data?

## Part 7. Scorecard

| Area | Question | Good sign | Your notes |
|---|---|---|---|
| Build | New module needs mapping? | No, it reads existing records | |
| Build | Document and entry saved together? | Yes, always | |
| Rollout | First real month-end | Within a quarter | |
| Money | Foreign-currency documents | Rate frozen, difference recorded | |
| Tax | Per-line tax codes | Yes | |
| Controls | Approvals and audit trail | Per module, visible on records | |
| Industry | Listed limits | Specific, named | |
| Cost | What is priced | Only what you use | |
