Budgeting for an ERP Project: The Costs People Forget
ERP budgets often overrun because of costs that were real from the start but never made it into the budget. These are the lines to add before anyone signs.

The enterprise resource planning (ERP) proposal on the general manager’s desk shows licences and an implementation fee. It looks manageable. Eighteen months later the project has cost far more, and the overrun came from a long list of costs that were real from the start but never appeared in the budget.
Why ERP budgets are often incomplete
Vendors and partners quote what they will deliver. That is reasonable, but their quote covers only part of what the project needs. Your own staff time, data cleaning, hardware, integrations, extra training and the months of running two systems side by side all sit outside it. Because nobody owns those costs in the proposal, they are often missed until they arrive.
A realistic ERP project budget starts from the full picture: what you pay the partner, what you pay others, and what you pay in your own people’s time.
The costs that tend to be forgotten
| Cost area | What it includes | Why it is missed |
|---|---|---|
| Internal staff time | Key users in workshops, testing, data checks and training, often for months | It never appears on an invoice, but someone has to cover their daily work |
| Backfill or overtime | Temporary staff or overtime while key users work on the project | People are assumed to absorb it, until they cannot |
| Data cleaning and migration | Fixing customer, product and supplier records; reconciling opening balances | The partner’s quote may only cover loading data you have already cleaned |
| Integrations | Connecting point-of-sale (POS) systems, e-commerce, banks, payroll, e-invoicing or other systems | Listed as “to be confirmed” in the proposal |
| Reports and documents | Custom invoice layouts, Arabic documents, management reports | Assumed to be standard, then found to need work |
| Infrastructure and devices | Servers or hosting, scanners, label printers, tablets, network upgrades | Treated as an IT (information technology) matter outside the project |
| Change requests | Changes discovered during the project | Every project has them; few budgets allow for them |
| Parallel running | Keeping the old system and its licences alive during transition | Old contracts and renewal dates are not checked |
| Post-go-live support | An intensive support period straight after launch, extra consultant days, ongoing support contract | The budget ends at go-live; the problems do not |
| Annual running costs | Subscriptions or maintenance, hosting, support, upgrades | Project budget and operating budget are discussed separately |
Training deserves a separate mention. The partner’s quote usually covers training key users, who are then expected to train everyone else. That second round of training, often across shifts and branches, takes time from your key users and sometimes needs extra materials in Arabic. It is rarely in anyone’s plan.
A scenario: a distributor’s ERP budget
Consider a consumer goods distributor in Amman with around eighty staff, moving from an older accounting system and several spreadsheets to a modern ERP. The proposal covers licences, configuration and standard training.
During the project, several things happen that nobody priced. The product list turns out to contain hundreds of duplicate codes and discontinued lines, and cleaning it takes two people several weeks. The van sales team needs handheld devices and an integration with the ERP. The finance manager spends most of three months in workshops and testing, so the company hires a temporary accountant. The old system’s licence has to be renewed for another year because go-live moves.
None of this is unusual, and none of it would surprise anyone who has run an ERP project before. It was simply not in the budget, so each item became a difficult conversation with the owner, and each conversation cost the project a little more credibility.
How to build a realistic ERP budget
- Ask partners for a complete scope, in writing. Ask them to list what is excluded as clearly as what is included, especially data migration, integrations, reports and post-go-live support.
- Estimate internal time by role. For each key user, estimate the days needed for workshops, testing, data and training. Multiply by a realistic daily cost, and decide how their normal work will be covered.
- Assess your data early. A short data quality review before signing tells you whether cleaning is a few days or a few months.
- List every integration. Include anything the ERP must exchange data with, and get an estimate for each, including local requirements such as e-invoicing.
- Check your existing contracts. Know when current licences and support agreements renew, and how much notice they need.
- Add a contingency line. Hold a reserve for change requests and surprises, controlled by the sponsor and released only with a recorded decision.
- Budget at least the first year of running costs. Make sure the operating budget includes subscriptions, support and hosting from go-live onwards.
Cost control during the project
A complete budget is only useful if it is tracked. Review actual spend against each line monthly, including internal time where you can estimate it. Route every change request through a decision that names its cost. Keep the contingency visible, and report how much has been used and why.
When the sponsor sees early that data cleaning is consuming more than planned, there is still time to add people or adjust scope before go-live is at risk. When the same information arrives in the final month, the only options left are expensive ones.
Funding the whole project, not just the software
When ERP projects go over budget, a common cause is a budget that described only the software and the partner. Building a complete picture of costs, internal effort and data work is part of the requirements and planning stage of our Enterprise Systems service. When the full cost is understood at the start, owners can make a clear decision, and the project team can spend its energy on delivery instead of explaining overruns.



