An ERP system is business software in which a company's main departments work from the same data: finance, purchasing, inventory, production, sales and human resources (HR). ERP stands for enterprise resource planning. When a customer orders 500 crates, the salesperson can see whether there is enough in stock, production schedules the shortfall, purchasing buys in the raw material and accounts send the invoice, all in the same database. For maintenance, though, an ERP often falls short: it knows what an installation cost, but usually not which bearing went into a pump last month. That is why many companies run a system for assets and maintenance alongside it: a CMMS or an EAM system.
What does ERP stand for?
ERP stands for enterprise resource planning: planning the resources of a business, such as money, people, materials and machines. In practice, ERP system, ERP software and ERP package all mean the same thing. At its heart is one shared database: a customer, item or cost centre is entered once, and every department then uses the same version.
ERP grew out of MRP (material requirements planning): software from the 1960s and 1970s that worked out which materials a factory needed and when. MRP II (manufacturing resource planning) followed in the 1980s and brought in capacity and finance, and in the early 1990s the name ERP caught on, as the approach spread to the whole business. That is why an ERP still thinks in orders, items and money.
Which modules does an ERP system have?
An ERP system is made up of modules: parts for a department or task, sharing the same database. The names vary by package, but you will nearly always find these six.
| Module | What it covers | Example |
|---|---|---|
| Finance | general ledger, cost centres, fixed assets, depreciation and payments | monthly figures per department |
| Purchasing | suppliers, purchase orders, goods receipt and invoice checks | an order for 2,000 kilos of plastic granules |
| Inventory | items, warehouses, stock levels and stock value | how many crates are in the warehouse |
| Production | bills of materials, production orders, material planning and capacity | the weekly schedule for the injection moulding machines |
| Sales | customers, quotations, sales orders, deliveries and sales invoices | the order for 500 crates |
| HR | employees, contracts, leave and sometimes payroll | an employee's leave balance |
The general ledger is the central set of accounts. A cost centre is a department or area where costs are collected, such as "Cooling water". Fixed assets are possessions that last for years, such as a machine, which the accounts depreciate over a number of years. The item master is the list of all items with their number, description, unit and price. A bill of materials lists the parts a product is made from.
Many packages also offer modules for projects, service or quality, and some for maintenance too.
Who uses an ERP system?
An ERP pays off once goods and money pass through several departments and separate lists can no longer keep up with each other. Think of a manufacturer, a wholesaler or a logistics company, but also of waste processors and energy companies, which often have an ERP for finance and purchasing. According to the EU's statistical office, Eurostat, 41 per cent of small enterprises in the EU (10 to 49 persons employed) used ERP software in 2025, against 89 per cent of large enterprises (250 or more).
Why does maintenance often fit poorly in an ERP?
An ERP is built around orders, items and money, maintenance around the plant itself: what is there, what happens to it and what can go wrong. The standard for linking business software with the plant, ISA-95 (IEC 62264 internationally), draws the same line. The ERP sits at level 4, with planning and logistics for the business as a whole. Maintenance operations management sits at level 3, alongside the management of production, quality and inventory operations on site.
With only a few installations, an ERP's maintenance module may be enough. With many installations, or plant whose failure is costly or dangerous, maintenance needs something different on six counts.
Asset management
An ERP often knows an installation only as a fixed asset: one line with purchase value, depreciation and book value. A technician wants to know, for each pump, what it is made of, which drawing goes with it and what has been done to it before. For that you need an asset tree, from installation down to component, with positions (the fixed places) and assets (the items installed there today). How to build one is covered in setting up an asset register.
Notifications and work orders
An ERP is made mainly for office work, with lots of fields and screens. A technician stands by the machine with a phone and wants to report a fault with a photo, book out a part and close the work order (the instruction for that job) right there. If that is cumbersome, it ends up on paper or not at all, and the history is wrong. How a work order runs is explained in work order management.
Maintenance planning
Preventive maintenance is work done in advance to reduce the likelihood of failure. You schedule it by the calendar (every quarter) or by use (every 4,000 running hours), fitting it around the technicians' hours and the plant's shutdowns. Planning in an ERP is designed mainly for production orders and materials, less for recurring tasks driven by meter readings and the capacity of a maintenance crew.
Spare parts per asset
Stock planning in an ERP usually works from expected demand or past consumption. Many spare parts are hardly ever used, yet you still want them on the shelf, because a breakdown without that part can mean days of downtime. You make that call per asset: which parts fit it, how bad is a failure and how long is the lead time? Read more in which spare parts to keep in stock.
Failures and history
Maintenance records failures: what went wrong, why, and how long the plant was down. An ERP usually has no set place for this, so you cannot see which installation keeps breaking down.
Cost per asset
In the ERP, maintenance costs usually land on a cost centre such as "Cooling water", which covers many installations. To know what one pump has cost in five years, you record costs per asset, through the work order. That is the figure you need when choosing between repair and replacement.
ERP vs CMMS vs EAM: what is the difference?
A CMMS (computerised maintenance management system) is software for notifications, work orders, preventive maintenance, assets and spare parts; see what a CMMS is. An EAM (enterprise asset management) system does all of that and also follows each asset through its whole life cycle, from acquisition to disposal; see what EAM is. Set next to an ERP, it looks like this:
| Aspect | ERP | CMMS | EAM |
|---|---|---|---|
| Core question | How do orders, stock and money move through the business? | What work is due when, and has it been done? | What do we know about each asset, and what does it cost over the years? |
| Built around | orders, items and money | the work order | the asset |
| An installation is | a fixed asset with a book value | an object with work orders and maintenance tasks | an asset with history, condition, cost and life-cycle stage |
| Who uses it | finance, purchasing, sales, production planning, HR | technicians, planners, work preparers | also stores, maintenance purchasing and asset managers |
In short: the ERP runs the business, the CMMS runs the maintenance work and the EAM system manages the assets themselves. They complement each other, and many companies run them side by side. How CMMS and EAM differ from each other is covered in CMMS vs EAM.
How do ERP and EAM work together?
Two systems side by side work well with one rule: every piece of data has one owner. That system is the source; the other receives a copy or reads along, but changes nothing. Below, the maintenance system is simply called EAM; the same applies to a CMMS.
Which system owns which data?
A common split:
| Data | Owner | Why there |
|---|---|---|
| Cost centres | ERP | Finance sets the cost structure |
| Item master | ERP | Purchasing and accounts use the same numbers and prices |
| Purchase orders | ERP | Ordering, budgets and payment run through finance |
| Invoices | ERP | The invoice is checked and paid |
| Assets and positions | EAM | Maintenance knows every pump, motor and location |
| Work orders | EAM | The work is reported and closed on the shop floor |
| Maintenance plans | EAM | Intervals, meters and tasks belong to the asset |
| Maintenance history | EAM | The basis for improving and replacing |
Two things vary from company to company. If the maintenance stores are in the ERP, the EAM system books consumption back there; if they are in the EAM system, only the costs go back. How such a store works is shown under warehouse and spare parts. And some companies order parts and services for maintenance from the EAM system and pass the order on to the ERP. Each variant works, as long as it is clear which system is the source.
What data goes back and forth?
Six flows run between the two systems, three each way.
From ERP to EAM:
- Cost centres, so that every work order is booked to a valid cost centre.
- Item master: number, description, unit and price, so that maintenance and purchasing talk about the same item.
- Purchase order and receipt: order number, delivery date and the message that the part has arrived, so the planner knows when the work can start.
From EAM to ERP:
- Purchase requisition: which part or service a work order needs, how many and against which cost centre.
- Hours and costs per closed work order: hours worked and materials used, booked to the cost centre.
- Commissioning and disposal of assets, so that finance can start or stop depreciation at the right moment.
Example: a pump needs a new bearing
This is how it works at a factory that makes plastic crates. Cooling water pump P-201 is making a humming noise at the bearings. All amounts exclude VAT.
- Notification. An operator reports the noise in the EAM system by phone, on position P-201.
- Work order. The planner turns it into a work order. P-201 belongs to cost centre 4210 Cooling water, which comes from the ERP.
- Spare part. P-201's parts list shows the right bearing: item 100457 from the item master. There are none left in stock.
- Purchase requisition. The planner requests two bearings, one for the repair and one as a spare. The requisition goes to the ERP with the work order number and cost centre.
- Purchase order. Purchasing orders two bearings in the ERP at €42 each. The order number and delivery date, Thursday, appear on the work order.
- Receipt. On Thursday the stores book the delivery against the purchase order in the ERP; the work order shows the material is in. The pump is still running, so the job goes into Friday's planned shutdown.
- Execution. A technician replaces the bearing in three hours, books one bearing to the work order, records the cause (wear) and closes the work order.
- Invoice. The supplier's invoice for €84 arrives in the ERP. Accounts check that order, receipt and invoice agree, known as a three-way match, and approve it for payment.
- Costs. The EAM system sends the hours and costs to the ERP: three hours at €65 is €195, plus one bearing at €42, making €237 on cost centre 4210 Cooling water. The second bearing sits in the stores and counts as stock, not yet as a cost.
Finance now sees €237 on the cost centre, with nothing re-keyed. Maintenance sees in P-201's history what went wrong, what was done, which part went in and what it cost. If this is already the second bearing change in a year, you look at the cause, such as alignment or lubrication. For that you need the history in the EAM system; the ERP only sees an amount on a cost centre.
What to look for when choosing
Whether maintenance fits in the ERP or gets a system of its own depends on your plant and your shop floor. These questions help when you weigh up ERP and maintenance:
- How many installations do you have, and how critical are they? A few machines with an annual service often fit in an ERP's maintenance module. Hundreds of positions, costly downtime and failures you want to analyse call for a CMMS or EAM system.
- Will the shop floor actually use it? Have a technician report a fault and close a work order on their phone. If they cannot do it without help, you will not get reliable history.
- Who owns which data? Fill in the table above for your own company, including stock and purchasing, and record which cost centre belongs to which part of the asset tree.
- Is the item master in good order? Duplicate items and vague descriptions such as "bearing, misc." make parts hard to find. Clean that up first.
- Start small and test with a real example. Begin with the flows that cause the most re-keying today, such as cost centres into the EAM system and hours and costs back. In a demo, follow one breakdown from notification to invoice, like the pump above. More criteria are in choosing maintenance software.
Frequently asked questions
Is an ERP system the same as accounting software?
No. Accounting is one part of an ERP. An ERP links the accounts to purchasing, inventory, production and sales, so that an order, a delivery and an invoice all use the same data.
What is the difference between ERP and a CMMS?
An ERP supports the whole business, from finance to sales. A CMMS is made for maintenance: notifications, work orders, preventive maintenance, assets and spare parts. The ERP sees an installation mainly as a possession with a book value; the CMMS knows what has been done to it and what still needs doing.
Can you run maintenance in your ERP?
Yes, some ERP packages have a maintenance module. That works best with few installations. With many assets, critical plant or a maintenance team that works mostly on the shop floor, a separate CMMS or EAM system alongside the ERP is often the better fit.
What is an item master?
The item master is the central list of all items with their fixed details: item number, description, unit, price and often the supplier. It usually lives in the ERP. The maintenance system uses the same item numbers and links the items to assets and work orders.
