Most companies that come to an ERP have run for years on spreadsheets: one workbook for stock, one for purchase orders, one for invoices, and an accountant who rebuilds the profit and loss at the end of every month from all of them. That works until it doesn't. Somebody sorts one column without the others, two people edit copies of the same file, and the stock sheet says 400 units while the shelf holds 260. Nobody can say which number is right, because nothing ties them together.
An ERP (enterprise resource planning system) fixes this by keeping every part of the business in one database, recording each event once, and deriving everything else from that record.
One record of each event
In a spreadsheet, a single event is typed several times. When goods arrive from a supplier, the warehouse adds them to the stock sheet, purchasing marks the PO as received, and the accountant later enters the purchase in the ledger. Three people, three entries, three chances to disagree.
In an ERP, the warehouse posts one goods receipt against the purchase order. From that single event the system:
- adds the quantity to the stock ledger, in the right warehouse and bin;
- marks the PO lines as received, so purchasing sees what is still open;
- posts the accounting entry (inventory up, a liability for goods received but not yet invoiced);
- makes the receipt available for matching when the supplier's invoice arrives.
Nobody re-keys anything, so the stock report, the open PO list and the balance sheet cannot drift apart. They are views of the same records.
Documents instead of cells
A spreadsheet stores values in cells, and any cell can be changed by anyone at any time. An ERP stores documents: a sales order, a delivery order, an invoice, a payment. Each document has a type, a number, a date, an owner and a status, and each status allows only certain next steps.
That sounds bureaucratic, but it is what makes the numbers trustworthy:
- An issued invoice cannot have its amount quietly changed. If it was wrong, you issue a credit note, and both documents stay on the record.
- Stock is never "overwritten" to a new number. It is the sum of every movement in and out, so you can always explain how you got to today's figure.
- A posted journal is never edited. It is reversed, and the reversal is visible.
Accountants call this an audit trail. Auditors, tax officers and banks expect it, and it is the main reason companies above a certain size cannot stay on spreadsheets.
The modules, and how they connect
ERP vendors split the system into modules. The names vary (SAP says MM, SD, PP, FI, CO), but every serious ERP covers the same ground:
| Area | What it covers | SAP module | Voltrus area |
|---|---|---|---|
| Purchasing | Suppliers, quotations, purchase orders, receipts, supplier invoices | MM | Purchasing |
| Sales | Customers, prices, quotations, sales orders, deliveries, invoices | SD | Sales |
| Inventory | Items, warehouses, stock movements, counts, valuation | MM / WM | Inventory |
| Production | Bills of materials, routings, work orders, MRP | PP | Production |
| Finance | General ledger, receivables, payables, bank, tax, assets | FI | Accounting |
| Controlling | Cost centres, projects, budgets, product costing | CO | Accounting, Production |
| Maintenance | Assets, preventive maintenance, checklists | PM | Assets |
The modules matter less than the links between them. The two flows you will meet everywhere are:
- Procure to pay (P2P): need → purchase order → goods receipt → supplier invoice → payment. See The procure-to-pay cycle.
- Order to cash (O2C): quotation → sales order → delivery → customer invoice → receipt of payment. See The order-to-cash cycle.
In a manufacturing company a third flow sits between them: plan to produce, where demand from sales orders drives MRP, which proposes purchases and work orders. See MRP.
Every step in these flows that moves goods or money also posts to the general ledger, automatically. That is why, in a well-run ERP, the month-end close takes days instead of weeks: the accounting is already done as the business happens. How operations post to the general ledger walks through every one of those entries.
What changes for the people
Moving to an ERP is less a software change than a change in habits. The ones that matter most:
- Master data comes first. An order can only refer to a customer and items that exist. Setting up items, customers and suppliers properly, once, is the foundation. See Master data and transactions.
- Work happens in the document, at the time it happens. The receipt is posted when the truck is unloaded, not typed in on Friday from paper notes. Late entry is the most common reason ERP numbers look wrong.
- Corrections are new documents, not edits. A wrong delivery is fixed with a return, a wrong invoice with a credit note. It feels slower at first; it is what makes the history reliable.
- Approval is part of the flow. Instead of a signature on paper, the approver approves the document in the system, and the approval is recorded with a name and a time.
- Reports are read, not built. Stock, open orders, receivables and the profit and loss are always current. Nobody spends the first week of the month assembling them.
Where Voltrus differs
Voltrus is a full ERP in the sense above: one database, documents with statuses, a stock ledger that is append-only, and a general ledger that every operational document posts to. Two things are less common:
- Governed changes. Any change can be sent for approval as a proposal: a person or an AI agent describes the change, an operations user approves or rejects it, and only then is it applied. Agents can never write directly. See How Voltrus works.
- Next steps on every record. Each document shows the actions its status allows, such as Create invoice on a shipped sales order or Create bill on a received PO, so users follow the flow without memorising it.
Checklist
- Name an owner for each area (purchasing, sales, inventory, finance) who decides how their documents are used.
- List the spreadsheets you run today and which module will replace each one.
- Agree that from go-live, a document in the system is the only record that counts.
- Read Master data and transactions next, before importing anything.