ERP modules — what each does, and the five you cannot skip

Every ERP presentation opens with a slide of twenty boxes, and everyone in the room takes the same thing from it: the system does all of that. The impression is accurate. The decision built on it is not, because the audience reads a capability list and the vendor is showing a price list. Fifteen of those twenty boxes are separately licensed in most products.

Three things are worth separating before you sign anything: what each module actually does, which of them no system works without, and the sequence they should be switched on in.

Five that are not optional

A product missing any one of these is not an ERP. It is a program, and it will need a second program beside it within the year.

Module	What it does	Why it cannot be dropped
Finance and the general ledger	Receives postings from every other module and produces the statements	It is the book. Nothing else is a system of record.
Purchasing	Requisition through to supplier invoice	Creates the liability and brings cost in
Sales	Quote through to customer collection	Creates the revenue and takes cost out
Inventory	Every movement in and out, at value	One number that appears in both the balance sheet and the P&L
Master data	Items, partners, chart of accounts	Everything above points at it; it points at nothing

The last row is the one that gets waved through. Master data is not a module anyone sells, so it never appears on the quote and never gets a project owner. It is the ground the other four stand on. A company that builds an item master without a naming convention and a unit-of-measure discipline pays for it in every report for the next decade, and the repair is a migration project rather than a setting.

Ten that are a decision

This is where a project with one budget becomes a project with double it. The third column matters more than the second: it is the observable sign, not the aspiration.

Module	You need it if	The sign that says so
Manufacturing	You convert materials into a product	You have a bill of materials and a routing
Projects	You sell time rather than goods	You want margin per project, not per month
HR and payroll	Payroll is large and rule-heavy	Allowances, end-of-service, local social insurance
Fixed assets	You own depreciating assets	A depreciation schedule runs outside the system today
Quality	You inspect on receipt or before shipment	You issue or receive binding inspection certificates
Maintenance	Equipment downtime stops production	You already run preventive maintenance on a calendar
Point of sale	You sell across retail branches	A till that has to work with the internet down
E-commerce	You sell from a website	One stock pool serving both the shop and the site
E-invoicing	Your jurisdiction mandates it	Read the contract, not the demo
Revenue recognition	You sell subscriptions or long contracts	Your invoicing schedule is not your revenue

The last two are the ones discovered late. Neither gets asked about during evaluation, and both get demanded in month three — e-invoicing by a regulator with a deadline, revenue recognition by an auditor who will not sign off on invoiced-equals-earned.

The question that saves more than any discount

Every module you saw in the demo must have a named line in your price schedule.

Anything without a line is not part of what you are buying, however convincing it looked on screen. This is not usually deception. A demonstration environment is fully enabled by its nature, because it exists to show the product’s ceiling. Your contract describes your floor.

So ask it in the form that cannot be answered vaguely: which module, by name, covers this requirement, and is that module in my quotation? The acceptable answer is a numbered line item. A screen is not an answer.

The order they go live in

The sequence is a dependency chain, not a preference. Each stage assumes the one before it, and inverting any two means doing the work twice.

1. Master data. Chart of accounts, items, partners, units of measure, tax codes. Not one transaction yet.

2. Purchasing. It brings goods in and produces the first real balance to work against.

3. Inventory and costing. The costing method cannot be chosen sensibly until you have watched what it does to actual numbers.

4. Sales. Cost of goods sold cannot be computed before stage three is settled.

5. Finance and the close. The close aggregates the effect of everything above it.

6. Optional modules. Each in its own wave, one at a time.

The most damaging deviation from this order is switching on manufacturing before costing and inventory are stable. A production order consumes materials and produces a finished item at a cost. If the costing underneath is unreliable, you are building a number on top of a number you do not trust, and the error compounds through work in progress into the balance sheet.

The mistake that doubles the budget for nothing

Going live with everything in one wave.

On paper it is efficient: one project, one training programme, one launch date. In practice, any defect in any module stops the entire launch, so the critical path runs through the least important thing you bought. And the client team is asked to learn ten modules in a fortnight, which produces competence in none.

The alternative that works: wave one is the five essentials, go live, then wave two after two clean monthly closes. A company that has closed two months with confidence has the capacity to absorb a new module. A company that has not closed one does not, and adding manufacturing to that company adds a second unsolved problem to the first.

What to do today

• Write out the five essentials and confirm each appears by name in your quotation.
• Walk the ten optional rows and mark the ones where the sign in the third column is true, not the ones you would like to have.
• Ask for every marked item to be written into the price schedule with its own number.
• Draw two waves rather than one, with a date against each.

Where to go from here

Each of the five essential modules has its own article: the procurement cycle, order to cash, inventory and costing, and the ledger and the close. Read them in that order; the full sequence is on the learn ERP page.

Which modules each product ships itself and which it leaves to a third party is set out system by system in the systems comparison.