Enterprise resource planning (ERP) is a type of business software that runs a company's core processes, such as accounting, purchasing, inventory, sales, manufacturing and payroll, on a single shared database. Because each department works from the same records, an order entered by sales can update stock, trigger a purchase, create an invoice and post to the accounts without being re-keyed.
For finance teams, the ERP is usually the system of record: it holds the general ledger, the payables and receivables subledgers and the data behind the financial statements. It works alongside specialist tools such as a treasury management system, a bank's online platform or a payroll provider. Well-known ERP products include SAP S/4HANA, Oracle's ERP applications, Microsoft Dynamics 365 and NetSuite; these are examples, not an exhaustive list.
ERP in plain terms
Imagine a restaurant where the waiter's order pad, the kitchen's stock list, the supplier order book and the cash register all update one shared notebook. When a dish is ordered, the notebook shows fewer ingredients left, flags when to reorder, records the sale and adds it to the day's takings, with no one copying numbers from one book to another.
Without that shared notebook, each part of the restaurant keeps its own records, and someone spends the evening reconciling them. An ERP system is the shared notebook for a whole company, which is why it saves time and reduces errors, and why replacing one is such a large undertaking.
History
ERP grew out of manufacturing software. Material requirements planning (MRP) systems in the 1960s and 1970s calculated what parts a factory needed and when. In the 1980s, manufacturing resource planning (MRP II) added capacity planning, scheduling and links to finance. The research firm Gartner is generally credited with coining the term "enterprise resource planning" in 1990 to describe systems that extended this integration to the whole business, not only the factory.
During the 1990s companies adopted large client-server ERP suites, partly to replace older systems ahead of the year 2000 date change. From the 2000s, web and later cloud-based ERP made the software available to smaller firms on a subscription basis. Vendors are moving customers to newer products; SAP, for example, has said mainstream maintenance of its older ECC 6.0 system runs to the end of 2027, with optional extended maintenance to 2030.
Finance modules and money flows
The finance side of an ERP typically includes:
- General ledger. The chart of accounts and every posted journal entry, built on double-entry accounting.
- Payables. Supplier records, invoice matching and payment runs for accounts payable.
- Receivables. Customer records, invoicing, cash application and ageing for accounts receivable.
- Fixed assets, tax and consolidation. Depreciation schedules, tax codes, intercompany entries and group reporting.
The ERP also connects to banks. Payment runs produce files in formats such as Nacha ACH files in the United States or ISO 20022 pain.001 credit transfer messages, which are sent to banks through bank connectivity channels such as SWIFT, secure file transfer or a bank API. Bank statements come back in MT940, BAI2 or camt.053 formats and feed automatic bank reconciliation. The same data supports treasury tasks such as cash positioning and cash forecasting, and the financial close runs largely inside the system.
Implementation, controls and risks
ERP projects are known for being expensive, long and risky because they change how many departments work at once. Typical challenges include cleaning and migrating data from old systems, deciding whether to change business processes to fit the software or customise the software, and training staff. The US Government Accountability Office, for example, has reported on Department of Defense ERP programmes that ran late and over budget, leaving older systems in use for longer than planned.
Because the ERP holds supplier bank details and releases payments, it is central to internal control. Companies use role-based access control to separate who can create suppliers, approve invoices and release payments, keep audit trails of changes, and monitor for unusual activity as part of fraud prevention. Changes to supplier bank details are a common route for payment diversion fraud, so many firms add workflow approvals and external checks. Cloud ERP also raises third-party risk and data security questions that are handled through vendor due diligence and contracts.
ERP in fintech and payments
Payments and fintech firms increasingly build products that plug into ERP systems: embedded payment buttons inside invoices, automated payables services, receivables tools that match incoming payments, and banks' "ERP-integrated" treasury services delivered through an application programming interface. For the business user, the goal is that money movements start and finish in the ERP, with the ledger updated automatically, rather than being typed into a bank portal and reconciled by hand afterwards.