ERP Buyer's Guide
Choosing an ERP platform is one of the most critical technology decisions an organisation makes. Once implemented, an ERP becomes the operational core connecting finance, supply chain, manufacturing, and often HR, and replacing it years later is a multi-year undertaking that most businesses go to considerable lengths to avoid. That makes the initial selection worth getting right the first time. This guide sets out a definitive, practical process for choosing ERP software: what it actually does, who the leading suppliers are, the terminology you will hear from vendors, how to run a structured selection, and the mistakes that most often derail an ERP project.
This guide focuses on process and knowledge rather than ranking individual vendors in depth. For an independent view of the leading ERP platforms across enterprise, mid-market, and specialist tiers, see our ERP Software Options 2026 post, which this guide references throughout. Viewpoint Analysis is a Technology Matchmaker: we help IT and finance leaders find and select the right technology fast. This is our viewpoint on how to run that process well.
What This Guide Covers
• ERP Software - the basics: what it is, what it does, why companies buy it, and how it has developed
• ERP Key Suppliers: a short, independent view of who the leading vendors are
• ERP Terminology: the key words worth knowing before you speak to vendors
• How to Run an ERP Selection Process: a step-by-step approach from requirements to contract
• What to Include in an ERP RFP: the criteria a good RFP should cover, explained
• Common pitfalls that most often derail a selection
ERP Software - the Basics
ERP, or Enterprise Resource Planning, software is an integrated suite of business applications that runs core operational processes from a single platform, in place of separate systems for finance, procurement, supply chain, manufacturing, and HR that rarely share data cleanly with one another. At its centre sits a shared database, so that a transaction entered once, such as a purchase order or a stock movement, flows through to every part of the business that needs to see it, rather than being re-keyed into several systems.
What the software does has grown considerably beyond core finance and inventory tracking. A modern ERP typically covers general ledger and financial consolidation, procurement and purchase order management, inventory and warehouse operations, production planning and manufacturing execution, and project or job costing, with many platforms also offering HR, payroll, and customer relationship modules within the same suite. Reporting sits across all of these functions, giving leadership a single, current view of the business rather than a set of disconnected departmental reports that need to be manually reconciled.
Organisations buy ERP software for reasons that have stayed remarkably consistent for decades, even as the technology has changed. The first is efficiency: removing duplicate data entry and manual reconciliation between systems that were never designed to work together. The second is visibility: giving leadership accurate, current information about the state of the business rather than reports that are days or weeks out of date. The third is control and compliance: a single system of record makes it far easier to enforce approval workflows, maintain an audit trail, and demonstrate compliance with financial and regulatory requirements as the business grows.
The market has changed substantially in how ERP is delivered, even where the underlying business case has not. On-premise deployments, requiring significant internal infrastructure and large upfront licence fees, dominated the market through the 1990s and 2000s. Cloud and SaaS delivery has since become the default for most new implementations, bringing faster deployment timelines, lower infrastructure overhead, and subscription-based pricing in place of large capital outlay. The most recent shift is the introduction of artificial intelligence into core ERP functions, automating routine tasks such as invoice matching and anomaly detection, and supporting demand forecasting and predictive analytics that were previously the domain of separate specialist tools.
ERP vendors, in the main, try not to sell to all the market. What is good for one segment or industry, might not be as good for another. Also, ERP for large businesses is very different to that built for small to medium-sized companies. You can read more about our Viewpoint on the various ERP software options here:
There are lots more resources at our Finance and ERP hub.
ERP Key Suppliers
The ERP market spans a small number of very large enterprise vendors, a competitive mid-market tier, and a number of specialist platforms built for particular sectors or operating models. Our Software Options report on this sector covers the following vendors in detail:
• SAP S/4HANA - the world's largest ERP platform by revenue and deployment count, built on SAP's in-memory HANA database and the benchmark choice for large, complex, multi-entity organisations.
• Oracle Fusion Cloud ERP - one of the most functionally complete cloud ERP platforms on the market, particularly strong in finance and procurement for large, finance-led organisations.
• Microsoft Dynamics 365 Finance and Supply Chain Management - Microsoft's enterprise ERP offering, differentiated by tight integration with Teams, Azure, Power BI, and Copilot for organisations already standardised on Microsoft.
• Infor CloudSuite - an enterprise ERP built around industry-specific editions with deep out-of-the-box functionality for sectors including manufacturing, healthcare, and distribution.
• NetSuite - the most widely deployed cloud ERP for mid-market organisations, owned by Oracle, covering financials, inventory, order management, and e-commerce in one platform.
• Sage Intacct - a cloud-native financial management and ERP platform with particular strength in multi-entity consolidation and project accounting, well regarded in professional services and non-profits.
• Epicor - a mid-market ERP with particular strength in manufacturing, distribution, and retail, built around strong shop floor and production scheduling functionality.
• IFS - a Swedish ERP vendor with strong credentials in asset-intensive industries such as defence, aerospace, energy, and field service management, built on a composable Cloud architecture.
• Acumatica - a cloud ERP built on a consumption-based pricing model rather than per-user licensing, well suited to distribution, construction, and manufacturing businesses with variable user populations.
• Odoo - an open-source ERP that has grown quickly in the SME and lower mid-market, covering CRM, sales, inventory, manufacturing, and accounting through a modular, app-based model at a competitive price point.
This list gives a starting orientation only, and is trimmed from a wider vendor set to the suppliers most relevant to a typical ERP buyer. For a fuller independent view of each vendor, including which type of buyer each one suits best, read the full ERP Software Options 2026 report.
ℹ️ We do our best to ensure that our Software Options and Guides are useful and help buyers find the right software for their needs. If you want a specific list of ERP vendors that can fit your exact requirements, take a look at our ERP Longlist Builder. Just answer a few questions to enable us to really understand your business, industry, size etc, and the Longlist Builder will give you a hand-picked selection of vendors that can help you.
ERP Terminology
ERP vendors and implementation partners use a specific vocabulary, and it is worth knowing the key terms before you start talking to them. These words are useful both for understanding what a vendor means when they use them, and for asking sharper questions of your own during a selection process.
• Single source of truth: the principle that each piece of business data exists in one place within the system, rather than being duplicated and potentially inconsistent across several systems.
• Multi-entity consolidation: combining financial results from several legal entities or subsidiaries into a single group-level report, usually a core requirement for organisations with more than one company.
• Multi-currency and multi-jurisdiction support: transacting, reporting, and complying with tax and regulatory rules in more than one currency and country from within the same platform.
• General ledger: the central accounting record that every financial transaction in the ERP ultimately posts to, forming the basis for all financial reporting.
• Chart of accounts: the structured list of every account category a business records transactions against, such as revenue, expenses, and assets; its design shapes how flexible future reporting can be.
• MRP (Material Requirements Planning): the manufacturing planning function that calculates what materials are needed, in what quantity, and by when, based on production schedules and existing stock.
• BOM (Bill of Materials): the structured list of components and quantities required to manufacture a finished product, used by manufacturing ERP modules to drive planning and costing.
• Middleware: software that sits between the ERP and other systems, managing the flow of data between them where a native, pre-built connector does not exist.
• API (Application Programming Interface): the technical mechanism that allows the ERP to exchange data with other systems automatically; the quality and openness of a vendor's API strategy affects how easily the platform integrates with the rest of your technology stack.
• Configuration versus customisation: configuration means adjusting the platform using its built-in settings and options, while customisation means writing new code to change how it behaves; heavy customisation increases cost and complicates future upgrades.
• Total cost of ownership (TCO): the full cost of an ERP over several years, including licence or subscription fees, implementation, training, data migration, ongoing support, and the cost of customisations, rather than the headline licence price alone.
• Go-live: the point at which an organisation begins using the new ERP for live business transactions, usually preceded by a period of testing and data migration.
• Data migration: the process of moving existing business data from legacy systems into the new ERP, typically one of the highest-risk and most time-consuming parts of an implementation.
How to Run an ERP Selection Process
The steps below cover a full ERP selection, from first requirements through to a signed contract. Each step links to a Viewpoint Analysis resource that can help you complete it.
1. Define requirements and success criteria
Before looking at any vendor, agree internally on your must-have functional requirements, expressed in terms of business outcomes rather than a generic feature checklist. How many legal entities do you need to consolidate, what is your current month-end close cycle, and do you need multi-currency support from day one? This step determines almost everything that follows, and skipping it is the single biggest reason ERP selections go wrong. It is also genuinely useful, reusable content for vendor conversations later in the process rather than only an internal planning exercise.
2. Build a longlist
With requirements agreed, build a longlist of vendors worth a closer look. The free Longlist Builder generates a tailored list of ERP vendors matched to your organisation's size, sector, and requirements in a few minutes, without registration.
3. Shortlist and issue an RFI or RFP
Narrow the longlist to three to five vendors and issue a structured RFI or RFP so responses can be compared on a like-for-like basis. See the section below on what to include in an ERP RFP.
4. Run demos and structured evaluation
Score each vendor demo against the same criteria, with input from finance, operations, IT, and any other function whose processes the ERP will run. Ask vendors to demonstrate your own scenarios, such as a real multi-entity consolidation or a production planning cycle, rather than a generic pre-built demo script.
5. Check references and completed implementations
Speak to at least one reference customer of a similar size, sector, and complexity to your own, and ask specifically about implementation timeline, data migration experience, and how closely the actual project matched the original plan and budget.
6. Negotiate and contract
Confirm the pricing basis (named users, active users, or consumption-based), what happens to pricing as the business grows, data export rights if you leave the platform, and support and service level commitments before signing. ERP contracts typically run several years or more, so it is worth the extra time at this stage.
7. Plan for implementation and adoption
Agree a realistic implementation timeline and internal resourcing plan, a data migration strategy for legacy systems, a change management and training plan for end users, and an owner for adoption once the system goes live. An ERP only delivers its business case once people across the organisation are actually using it correctly and consistently.
----
Viewpoint Analysis helps buyers find and select ERP solutions - if you would like our help, take a look at our various IT Buyer Help Services.
What to Include in an ERP RFP
An ERP RFP works best when it asks vendors to respond against criteria specific to running a business on a single integrated platform, rather than a generic software checklist. The sections below explain what to ask for and, just as importantly, why each one matters.
Financial management depth
Ask vendors to explain their general ledger structure, consolidation capability, and revenue recognition functionality in detail, with examples relevant to your accounting policies. This matters because financial management is usually the part of an ERP an organisation can least afford to get wrong, and depth here varies considerably between platforms that look similar on a feature list.
Multi-entity, multi-currency, and multi-jurisdiction support
If you operate more than one legal entity, currency, or country, ask vendors to demonstrate consolidation and local compliance handling specifically, rather than describing it in general terms. This matters because the difference between a platform that handles this natively and one that requires workarounds or add-on modules has a direct effect on month-end close time and audit risk.
Integration and API strategy
Ask vendors to set out their pre-built connectors to your existing HR, payroll, e-commerce, and CRM systems, and the openness and quality of their API where a native connector does not exist. This matters because integration gaps, not ERP functionality itself, are the most common cause of implementation delay and cost overrun.
Implementation partner network
Ask which implementation partners are certified on the platform in your region and sector, and request references specifically for the partner team that would deliver your project, rather than only the platform vendor. This matters because a weak partner delivering a strong platform consistently underperforms a strong partner delivering a second-choice platform.
Industry-specific functionality
Ask how much of your sector-specific process, such as manufacturing bill of materials, project costing, or field service management, is covered natively versus requiring customisation or a third-party add-on. This matters because heavy customisation increases both initial cost and the cost of every future upgrade.
Reporting and analytics
Ask for examples of standard reports relevant to your business, and how easily a non-technical user can build a new report without help from IT or the vendor. This matters because the value of a single integrated system depends on people across the business actually being able to get useful information out of it.
AI and automation capability
Where a vendor highlights AI features such as automated invoice matching, anomaly detection, or demand forecasting, ask them to explain specifically what data the feature uses and how mature it is in live customer environments, rather than accepting it as a line on a slide. This capability varies considerably in maturity between vendors even where the marketing language sounds similar.
Total cost of ownership and contract terms
Ask for a realistic five-year total cost of ownership model covering licence or subscription fees, implementation, training, data migration, ongoing support, and the likely cost of customisations and upgrades over time. This matters because licence fees are only the visible part of ERP cost, and a headline price comparison alone will miss material differences between vendors.
Common ERP Buying Mistakes
The same handful of mistakes account for most ERP selections that go wrong, and nearly all of them happen before a contract is ever signed. The most frequent is producing a requirements document that lists hundreds of features at the same level of importance, which makes it impossible for vendors to understand what actually matters to the business. The more effective approach is to separate genuine must-haves from nice-to-have preferences and to express requirements in terms of business outcomes, since a long undifferentiated feature list tends to reward whichever vendor demos best rather than the platform that genuinely fits.
Treating platform selection and implementation partner selection as the same decision is another common mistake. For every major ERP platform there is a wide range of implementation partners, from large systems integrators to boutique sector specialists, and quality varies significantly between them. Organisations that focus their evaluation entirely on the software and treat the partner as an afterthought frequently find that a strong platform is let down by a weak delivery team.
Integration is very often under-weighted during evaluation, only to resurface as the single biggest source of delay once implementation begins. The ERP will need to connect with HR, payroll, e-commerce, CRM, and specialist operational tools, and pressure-testing each shortlisted vendor's API quality and pre-built connectors at RFP stage is far cheaper than discovering integration gaps once the project is already under way and budget has been committed.
Total cost of ownership is frequently misunderstood, with buyers comparing headline licence or subscription prices without properly modelling implementation cost, training, data migration, ongoing support, and the cost of customisations and upgrades over the life of the contract. These additional costs often dwarf the initial platform price, and a vendor or partner unwilling to build a realistic multi-year cost model with you is worth treating with caution.
Reference checks are frequently skipped or rushed, usually because a selection process is already running late and a reference call feels like an easy step to compress. A short conversation with a genuinely comparable customer, focused on how closely their actual implementation matched the original timeline and budget, is one of the most reliable ways to catch problems a vendor's own answers will not surface.
Finally, many organisations select a platform and a partner well but under-invest in change management and training, assuming that a well-configured system will drive its own adoption. Usage and data quality are typically strongest immediately after go-live and drift over time without a named owner actively tracking adoption and correcting bad habits early. An ERP only delivers its business case once people across the organisation are using it correctly and consistently, and that requires ongoing ownership beyond a successful selection process.
It may be worth reading our Enterprise Software Selection Playbook if you'd like much more information.
Talk to Viewpoint Analysis
If you are currently evaluating ERP software and would value independent guidance through the process, or you are an ERP vendor interested in future content and matchmaking opportunities, we would be glad to hear from you. Request a call and we will be in touch promptly.
