Enterprise Resource Planning (ERP)

You've just been told the company is replacing its accounting software with an ERP, you have 90 days to help select it, and the last three people who tried to explain what an ERP actually is gave you three different answers. That's not unusual: the term covers a wide range of platforms with very different implementation profiles. Enterprise resource planning (ERP) is an integrated software system that runs core business processes across multiple functions (finance, procurement, inventory, manufacturing, HR, sales, and service) in a single platform with a shared data model. The defining characteristic is integration. Instead of separate systems for accounting, procurement, and HR that sync data through point-to-point integrations, an ERP consolidates these functions so that a purchase order in procurement automatically creates accounting entries in the general ledger, reduces inventory in the warehouse module, and generates payment terms in AP. In theory, this removes the reconciliation work between systems and gives management a single source of truth for financial and operational data. In practice, how well an ERP achieves this depends on which modules are implemented, how they're configured, and whether the business processes feeding the system are disciplined enough to keep the data clean.

What an ERP actually consolidates

The financial modules in an ERP (general ledger, accounts payable, accounts receivable, fixed assets, and financial reporting) are usually the most mature and the most tightly integrated. They form the accounting backbone of the system and are what most finance teams work in every day. Operational modules such as inventory management, order management, procurement, and project accounting vary more in quality and in how tightly they connect. Some ERPs have strong inventory modules built for manufacturers and weaker project accounting for service businesses. Others are built for services businesses and are weak on inventory. The gap between what the ERP covers and what it covers well is where point solutions pile up: a company on NetSuite might still use Salesforce for CRM, Expensify for expense management, and Rippling for HR, and each of those creates an integration someone has to maintain. The 'all-in-one' pitch usually means 'all the major modules are available', not 'all the modules are good'. Evaluating an ERP means being clear about which modules the business will actually use versus which would be nice to have if they were good enough, then testing the specific modules that matter instead of being impressed by the size of the module catalog.

Where it gets complicated

Financial ERPs focus on what the finance function needs for accounting and reporting: GL, AP, AR, fixed assets, consolidation, and financial reporting. Operational ERPs focus on the processes that run the business: supply chain, manufacturing, warehouse management, and order fulfillment. Some platforms are built for one or the other (Sage Intacct is a financial-first ERP; SAP and Oracle lean heavily operational). Mid-market platforms like NetSuite and Microsoft Dynamics 365 sit in the middle, covering both with varying depth. The 'all-purchased' vs 'all-configured' distinction is often underestimated during selection. A typical case: the organization licenses the full ERP suite, including project accounting, fixed assets, and multi-currency. At go-live, only the core financials are configured because the implementation timeline ran out. Six months later, the project accounting module is still set up the way it was demoed, with sample data and generic settings, and the team is tracking actuals in a spreadsheet next to the ERP. Modules that are purchased but not configured create shelfware costs (licensing with no benefit) and leave the processes they were meant to support running on workarounds.

How to evaluate ERP breadth vs depth

ERP demos are built to show breadth. The vendor walks through finance, then operations, then HR, to show that the platform covers everything. Depth, meaning how well the system handles your specific use cases, edge cases, and volumes, rarely shows up in a standard demo. The only reliable source for depth is reference customers with similar complexity: same industry, similar revenue, entity count, and transaction volume. When you are shortlisting ERP software, reference calls should cover: How long did the implementation take relative to the initial scoping estimate? What modules were live at go-live, and what was descoped and why? What are the two or three things the system does less well than the sales team implied? How has the vendor handled support issues and enhancement requests? What would you do differently if you were starting the selection over? Those answers come from running the system for 18+ months in a real operation, which no demo can give you.

Questions to ask

• Which modules are we committing to configure fully in Phase 1, and is there a written agreement with the implementation partner about what 'configured' means for each module?
• What is the vendor's implementation methodology, and can we speak with three reference customers who completed implementation within the last 18 months with a similar scope to ours?
• How does the system handle the complexity most relevant to our business (multi-entity consolidation, project accounting, revenue recognition, or multi-currency), and can we test those scenarios in a sandbox before signing?
• What does the vendor's support model look like after go-live? Is there a dedicated customer success resource, what is the SLA for critical issues, and how long does a typical support ticket take to resolve?
• What is the total cost of ownership over three years, including implementation, annual licensing, customization, and ongoing administration, rather than the annual subscription cost alone?

Common mistakes

Selecting based on the demo instead of reference calls with companies of similar complexity is the most expensive ERP mistake. Demos are produced by people whose job is to make the software look capable. Reference customers have been through the implementation and lived with the system. The quality of information is not comparable. A team that doesn't hold at least three substantive reference calls before choosing an ERP is deciding without the most relevant evidence available. The second mistake is underestimating implementation scope. ERP implementations consistently take longer and cost more than the first estimate: scope expands once detailed requirements are written down, data migration turns out harder than expected, and user acceptance testing exposes configuration gaps. Teams that build no contingency into the timeline and budget almost always end up with a timeline extension and cost overrun, which creates pressure to descope Phase 1 functionality that then becomes Phase 2 or Phase Never.

Comparing ERP platforms

Most of an ERP decision is settled by data model and entity structure, not by the feature list a demo walks through. Once Enterprise Resource Planning (ERP) is settled as a requirement, read the ERP Software category guide for how the market splits, then weigh the NetSuite profile against the Sage Intacct profile on that requirement rather than on the feature list. Our OneStream pricing breakdown records what the vendor publishes and what is quote-based. The OneStream against Planful comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the ERP ROI calculator so the business case is written down before a vendor writes it for you.

Enterprise Resource Planning (ERP) questions

Related terms

Chart of Accounts Mapping, Cloud ERP vs On-Premise ERP, and ERP Customization vs Configuration come up in the same workflow as Enterprise Resource Planning (ERP), and the rest of the ERP platforms cluster is indexed in the finance operations glossary.