How Much Does ERP Software Cost in 2026?
A cost model for ERP software in 2026, with the pricing models compared, the costs vendors do not quote, and a worked three-year total for a ten-person company under per-user and metered pricing.
ERP software in 2026 costs anywhere from a few hundred euros a year for a small company on a cloud product with standard modules to seven figures for an enterprise rollout, and the subscription is rarely the largest line. For small businesses, published list prices for cloud ERP and accounting suites are typically in the tens of euros per user per month. For mid-market companies, the implementation project typically costs more than the first year of subscription. For enterprises, licences, implementation and internal time together run to six or seven figures, spread over one to three years.
Those are approximate ranges drawn from vendor price lists and published implementation estimates, not a survey result, and the right question is not "what does the software cost" but "what does the system cost over three years, all in". This article gives you the cost components, the pricing models, the costs that are not on the quote, and a worked example with real published numbers for the metered case.
The cost components
| Component | What it covers | When it is paid |
|---|---|---|
| Licence or subscription | The right to use the software, by user, entity, tier or usage | Monthly or annually, for as long as you use it |
| Implementation | Design, configuration, project management by the vendor or a partner | Once, before go-live, sometimes in milestones |
| Customisation | Changes to standard behaviour: screens, workflows, reports, documents | Once to build, then again at every upgrade |
| Integration | Connecting bank, payroll, e-commerce, CRM, warehouse, tax systems | Once per connection, plus maintenance when either side changes |
| Data migration | Extracting, cleaning, mapping and loading master data and balances | Once, but it is the phase that most often overruns |
| Training | Preparing users by role; change management | Once at go-live, then for every new hire |
| Hosting and infrastructure | Servers, backups, security, monitoring | Included in cloud subscriptions; separate for on-premise |
| Upgrades | Testing and re-applying customisations on each version | Each release for on-premise; the vendor's job for standard cloud |
| Internal time | Your finance, IT and operations staff on the project | Throughout, and almost never in the vendor's quote |
For a traditional implementation, a common rule among implementation partners is that services cost between one and two times the first-year licence for a standard project, and more when customisation is heavy. That ratio is a planning heuristic, not a guarantee.
Pricing models and what they reward
| Model | How you pay | Grows with | Watch out for |
|---|---|---|---|
| Per user | A fee for each named or concurrent user per month | Headcount, including read-only users | Tier jumps when you add a module or a role; "full" versus "light" user definitions |
| Per entity or organisation | A fee for each company or legal entity | Number of entities | Consolidation sold separately; each entity may need its own subscription |
| Tiered by features | Fixed fee per tier; higher tiers include more modules | Which features you need, not how much you use | The one feature you need being in the next tier |
| Metered by usage | A fee per transaction, request, document or revenue band | Business volume | Understanding what counts as one unit; overage rates |
Per-user pricing is the industry default because it is easy to quote. It penalises companies that want many people to see the numbers. Per-entity pricing penalises groups. Feature tiers penalise the company that needs one advanced thing. Metered pricing is the only model in which the cost tracks the work the system does, and its risk is on the other side: you have to understand your volume.
Approximate ranges by segment
Small business, cloud ERP or accounting suite. Published list prices typically fall in the tens of euros per user per month per tier, with implementation done by the company itself or by an accountant for a few thousand euros. Three-year cost for a ten-person company is commonly in the low five figures when everyone needs a seat.
Mid-market. Subscriptions in the tens of thousands of euros per year are common, and the implementation project typically costs more than the first year's subscription, with integration and data migration as the largest services items. Three-year cost is commonly in the low-to-mid six figures.
Enterprise. Licences, multi-region implementation, customisation and internal staff together run to six and seven figures, over one to three years. The subscription is a minority of the total.
API-first accounting core. A different shape: the subscription is metered, implementation is an integration project done by your developers, and the compliance layer ships with the product. The cost moves from licence and services to developer time. The worked example below shows the numbers.
The costs that are not on the quote
- Internal time. Finance staff on the project instead of closing the books; IT staff on integrations. Usually the single largest unquoted item.
- Customisation re-testing at each upgrade. Paid once to build, then again every release.
- Second-tier pricing. The cost of the tier above the one you buy, which is where you will be in two years.
- Read-only users. Executives, auditors and advisers who need to look and cost a seat each.
- Additional entities. A new subsidiary that needs its own subscription and its own implementation.
- Localisation. Country packs, partner-built tax modules, and the filing format change that arrives in year two.
- Data egress. Export tooling or services when you leave.
- Storage and documents. Attachment storage, archive fees, document-scanning charges.
- Hypercare. The first month-end close, the first VAT return and the first payroll from the new system, which take longer than normal and sometimes need the partner back.
A worked three-year example
The company: ten people, one legal entity, in an EU member state, VAT-registered, around 400 sales invoices and 300 supplier invoices a month, one bank account with about 1,500 movements a month, monthly payroll, quarterly OSS reporting. Everyone on the team should be able to see the numbers; two people enter data; one developer is available part-time.
Per-user pricing (assumed figures)
The per-user price here is an assumption chosen to illustrate the model, not a quote from any vendor. Assume a mid-tier cloud suite at €40 per user per month, with all ten people needing a seat.
| Item | Amount |
|---|---|
| Subscription: 10 users × €40 × 36 months | €14,400 |
| Implementation by a partner (assumed, modest scope) | €6,000 |
| Integration of bank and e-commerce (assumed, two connectors) | €4,000 |
| Data migration and training (assumed) | €3,000 |
| Three-year total before internal time | €27,400 |
Reduce the seat count to the two people who enter data and the subscription falls to €2,880, but the other eight no longer see the system, which is usually the reason the company wanted an ERP.
Metered pricing (Nordlet's published plans)
Nordlet's pricing is public and metered by request. A request is any action performed through the API or the app: issuing an invoice, registering a purchase, adding a ledger entry, generating a report. Bank, Stripe and bank-connection imports count one request per ten imported movements. Every module and the full API are in every plan, with unlimited users and unlimited companies; plans differ only by included request volume, SLA and included storage.
| Plan | Monthly fee | Included requests | Extra request |
|---|---|---|---|
| Starter | €10 | 3,000 | €0.004 |
| Business | €50 | 30,000 | €0.003 |
| Scale | €300 | 200,000 | €0.002 |
Estimate the company's monthly volume: 400 sales invoices created and issued (about 800 requests), 300 purchase invoices (about 300, or 300 scanned pages at €0.005 each on top), 150 import requests for 1,500 bank movements, payment matching and reports (assume 700). Roughly 2,000 requests a month, inside the Starter plan with room to spare. If volume doubles to 4,000, Starter costs €10 plus 1,000 × €0.004 = €14, or the company moves to Business at €50 with 30,000 included.
| Item | Amount |
|---|---|
| Subscription: Starter, €10 × 36 months | €360 |
| Document scanning: 300 pages × €0.005 × 36 | €54 |
| Storage above the included 256 MB database and 1 GB files (assume none) | €0 |
| Integration by your developer (assumed: 15 days at an internal rate of €400) | €6,000 |
| Data migration using the importer (assumed: 3 days) | €1,200 |
| Three-year total before other internal time | €7,614 |
All ten people have accounts, because users are not metered. The implementation cost did not disappear; it moved from a partner invoice to developer time, and the assumption of fifteen days is yours to replace with your own estimate. What did disappear is the per-seat subscription and the feature tier, and the compliance work is in the product: the EU VAT engine resolves the OSS treatment and computes the quarterly return, and the filing calendar for the company's country is populated from the built-in rules listed on the filing support page.
Two things to weigh against that. Nordlet is a young product, in early access in 2026 and onboarding design partners. And if your company has no developer, the integration line becomes a contractor invoice, which narrows the gap.
What the example shows
Over three years the subscription is a minority of the cost under either model; the services and the internal time dominate. The structural difference is that per-user pricing grows with the number of people who look at the numbers, while metered pricing grows with the number of transactions the business generates. A company with ten readers and two hundred transactions pays very differently from a company with two readers and twenty thousand transactions, and you should run the numbers for your own shape rather than take either example as typical.
Questions to ask a vendor
- What counts as a user, and does a read-only viewer pay the same as a full user?
- Which modules are in the tier I am buying, and what does the next tier cost?
- Is each legal entity a separate subscription? Is consolidation included or separate?
- What does implementation cost for a company of my size, and what share of it is customisation?
- Which integrations are native, which are partner-built, and what does each cost to maintain when the other side changes?
- Which of my country's filings does the system produce, and can I see the generated file from a demo tenant?
- What are storage, document-scanning and archive charges?
- What does it cost to export everything and leave?
- Does the price change with headcount, with entities, or with transaction volume, and which of those will grow fastest in my business?
- Is there a sandbox I can test against before signing, and what does it cost? (With Nordlet, sandbox companies are unlimited and billed at the same metered rate as real ones; a new account starts with a 14-day trial and €5 of trial credits.)
FAQ
What is the average cost of ERP software for a small business?
For a small company on a cloud product with standard modules, published list prices typically run to tens of euros per user per month, plus a one-off implementation in the low thousands if a partner or accountant does it. Over three years that commonly lands in the low five figures when everyone needs a seat. Metered products change the shape: a ten-person company with a few thousand actions a month can run on a plan that costs €10 a month.
Why does implementation cost more than the software?
Because implementation is people's time: design workshops, configuration, data cleanup, integration, testing and training. Software is reproduced at no cost; a consultant's day is not. The ratio is highest when customisation is heavy and lowest when the company accepts standard processes.
What is a "request" in metered pricing?
In Nordlet, a request is one action through the API or the app: creating or issuing an invoice, registering a purchase, posting a journal entry, running a report. Imports of bank or Stripe movements count one request per ten movements. Nothing is blocked when you pass the included volume; extra requests are billed at the plan's per-request price.
How do I estimate my own three-year total?
Count users who need access, entities, countries, monthly transactions and integrations. Price the subscription under the vendor's model for year three, not year one. Add implementation, integration and migration quotes. Add your own staff time at an internal rate. Then ask for the price of leaving. The accounting software cost guide does the same exercise for accounting products without the wider ERP scope.