Enterprise resource planning (ERP) is business software that runs a company’s core operational and financial processes on a single shared database. Finance, purchasing, inventory, order management and, depending on the product, manufacturing, projects, HR and payroll all work from the same records, so an order placed in one department updates stock, billing and the general ledger without anyone re-entering it. ERP is sold by vendors such as Oracle NetSuite, Microsoft Dynamics 365, SAP and many industry-specific providers, increasingly as cloud subscriptions.
At a glance
- ERP connects back-office processes, such as order-to-cash, procure-to-pay and record-to-report, on one database.
- It is modular; you license the functions you need, and the depth of each module varies by product.
- Much new mid-market ERP is bought as cloud software, commonly billed per user, by module or both.
- Implementation, data migration and process change often take more effort and budget than the software itself.
- Integration with CRM, e-commerce, payroll, banking and warehouse systems is part of nearly every project.
What problem it solves
Growing companies often run on a patchwork: entry-level accounting software, spreadsheets for inventory and forecasting, a separate order system and manual exports between them. Each handoff is a chance for errors, month-end close takes longer as volume grows, and nobody fully trusts the numbers because each system tells a slightly different story. Adding a new entity, warehouse or currency makes it worse.
ERP replaces those handoffs with shared data and defined workflows. A purchase order, a receipt and a supplier invoice match against each other automatically; a sales order reserves stock, triggers fulfillment and creates an invoice; and finance closes from the same data operations use. It also creates the controls and audit trails that lenders, auditors and investors expect.
How it works
Modules on a shared database. Financials sit at the center. Around them are modules for purchasing, inventory and warehousing, order management, manufacturing, project accounting, fixed assets and, in some products, HR and payroll. Because modules share customer, supplier, item and account records, a transaction in one flows through to the others.
Deployment. Cloud ERP is hosted and updated by the vendor, which typically pushes upgrades on its own schedule. On-premises or privately hosted ERP runs on infrastructure you or a hosting provider manage, giving you more control over timing and customization but more work. Licensing is commonly per named user, by role or module, or a combination.
Configuration and customization. ERP is configured to match your chart of accounts, approval rules and processes. Where it doesn’t fit, companies add custom fields, scripts, workflows or add-on products. Heavy customization makes upgrades harder, so many projects aim to adopt standard processes where possible.
Integration and reporting. ERP connects to CRM, e-commerce, payroll, banks, tax engines, shipping carriers and warehouse systems through APIs or integration platforms. Built-in reports cover routine needs, while many companies feed ERP data into analytics and business intelligence tools for deeper analysis. Our ERP solutions page covers selection in more detail.
When it matters for buyers
- When the business outgrows entry-level accounting software. Multiple entities, currencies, inventory locations or complex revenue rules are common triggers.
- When preparing for investment, audit or an IPO. Investors and auditors expect controls, audit trails and a faster close.
- After a merger or acquisition. Combining companies on different systems forces a decision about consolidating onto one ERP.
- When an old system is out of support. Legacy on-premises ERP that is heavily customized or no longer maintained is a business risk.
- When integration is the bottleneck. If staff spend days moving data between systems, ERP or better integration may be the fix.
Questions to ask vendors
- Which modules are included in the quote, and which functions will need add-ons or third-party products?
- How is pricing structured (users, roles, modules, transactions), and how much can it rise at renewal?
- Who will implement the system, how many similar projects have they delivered, and can we speak to those customers?
- What is included in the implementation scope, especially data migration, integrations and training?
- How are upgrades handled, and how will our configurations and customizations be affected?
- What reporting is built in, and how do we get our data out for analytics?
- What are the availability SLA and support hours, and where is our data hosted?
- What happens to our data and access if we leave?
How it differs from CRM
Customer relationship management (CRM) software runs the front office: marketing, leads, opportunities, quotes and customer service. ERP runs the back office: fulfilling orders, managing inventory and purchasing, billing and accounting. The two meet at the order, which is why integration between them matters. Some vendors sell suites covering both, and some ERP products include basic CRM, but many companies run a dedicated CRM and connect it to their ERP.
Problems this helps with
- Month-end close that depends on spreadsheets and manual re-keying
- Inventory, orders and finance numbers that never match
- Outgrowing small-business accounting software
- An old, heavily customized system nobody wants to touch
