What is an ERP system?

An ERP system is one platform that runs the operational and financial side of a business from a single shared database. Finance, purchasing, stock, sales orders, warehousing, projects and reporting all read and write to the same records, so a fact entered once is true everywhere.

That sounds unremarkable until you compare it with how most growing businesses actually operate. Orders live in one system, stock in another, costs in a spreadsheet, and the accounts package is updated afterwards by someone re-keying figures. Every one of those handoffs is a chance for the numbers to disagree, and reconciling them is where finance teams lose their month.

ERP stands for enterprise resource planning. The term is a leftover from manufacturing planning software of the 1990s, when the job was calculating what materials and capacity were needed to meet demand. Modern ERP inherited that planning engine but expanded well beyond it, and today the phrase simply describes an integrated business system rather than a factory tool.

The practical test of an ERP is whether the business can answer a question once. What did that job actually cost, which customers are profitable after service, how much stock is committed against open orders, what will cash look like in six weeks. In a connected system those are queries. In a disconnected one they are projects.

The most common question from businesses considering their first ERP is what it gives them that their accounts package does not. The honest answer is that accounting software is a record of what already happened. It is very good at that, and for a business whose operations are simple it is entirely sufficient.

An ERP manages the activity that produces those financial records. When a purchase order is raised, the commitment is visible before the invoice exists. When stock is received, valuation updates and the matching happens automatically. When a job is worked on, labour and materials land against it as cost, not as a monthly journal someone assembles from timesheets.

That difference shows up in the questions each system can answer. An accounts package will tell you gross margin for the period. An ERP will tell you margin by product, by customer, by job and by site, because the operational detail behind the figure is in the same database rather than in a spreadsheet somewhere.

The other difference is what happens as the business grows. Accounting tools are extended with bolt-ons: a stock app, a quoting tool, an approvals workflow, an integration to hold them together. Each is reasonable on its own, and together they become the reason month end takes two weeks. An ERP consolidates those functions rather than connecting them.

Cloud ERP is generally licensed per user per month, and the first thing worth understanding is the difference between user types. Full users who work in finance or operations day to day carry the highest cost. Light users who approve, enter timesheets or read reports are licensed at a fraction of that, and getting the mix right materially changes the annual figure.

Implementation services sit alongside licensing and are usually the larger first-year cost. They cover discovery, configuration, data migration, any integrations, testing and training. A single-entity finance-first rollout with clean data sits at the lower end. Multiple entities, warehouses, currencies or manufacturing processes push it considerably higher.

The variable most businesses underestimate is their own data. Time spent cleaning customers, suppliers, stock codes and opening balances before migration reduces consultancy hours and improves the outcome. The same work done mid-project costs more and delays go-live.

Budget for year two as well. Licensing recurs, support is normally a monthly retainer or a block of hours, and most organisations make further changes within twelve months as they discover what else the platform can automate. A quote that only covers the implementation is not a total cost of ownership.

Very few new ERP implementations are on-premise. Cloud platforms removed the server hardware, the upgrade projects and the capital cost, and replaced them with a subscription and a twice-yearly update cycle handled by the vendor. For most mid-sized businesses that trade is straightforwardly worthwhile.

The arguments that remain for on-premise are usually specific: data residency requirements that a vendor cannot satisfy, heavily customised systems where the cost of re-platforming is genuinely prohibitive, or operational environments with unreliable connectivity. Those are real constraints, but they are the exception rather than the rule.

The trade-off that does matter in the cloud is update cadence. Vendors ship regular releases, and your configuration and any extensions need to be tested against them. That is manageable and largely handled by an implementation partner, but it is a maintenance responsibility rather than something that disappears entirely.

If you have concluded that an ERP is the right direction, the next decision is not which product to buy. It is what you need the system to do, in enough detail that vendors are quoting against the same brief. Our guide to choosing an ERP system covers requirements gathering, shortlisting, demo scripts and the questions that separate vendors quickly.

If you would rather start from your own sector, we have written practical guides on what an ERP changes in specific industries, from manufacturing and construction through to professional services, wholesale and healthcare. Each one covers the processes an ERP takes over and where the value tends to land.

And if you already know you want to evaluate a specific platform, Microsoft Dynamics 365 Business Central is the cloud ERP we work with most often for small and mid-sized organisations, with finance, supply chain, projects and reporting in one system connected to the Microsoft tools most teams already use.