Skip to content
ERP business case

ERP ROI calculator — payback, NPV and 3-year return

Build an ERP ROI case from your own numbers: hours saved, inventory and receivables released, rework avoided. Get ROI %, payback months and 3-year NPV.

Free · no signup · runs in your browserUpdated
Short answer

ERP ROI compares annual benefits against total cost: ROI % = (benefits − costs) ÷ costs. Benefits come from report and admin hours saved, inventory carrying cost avoided, receivables financing released and rework reduction. On the seeded example, $280,797 of annual benefit against a $240,000 implementation and $96,000 a year returns 38.3% over three years, paying back in 22.9 months.

An ERP ROI calculator is only as honest as the assumptions behind it. This one asks for the four benefit categories that survive a finance review — hours recovered, inventory carrying cost avoided, receivables financing released, and error correction that stops happening — then sets them against the money you will actually spend.

You get three numbers because they answer three different questions. ROI % tells you the size of the return, payback tells the CFO how long the money is at risk, and NPV tells you whether the project beats the hurdle rate once the timing of cash is priced in.

Before you present any of it: every benefit line needs a name against it. The person who owns the inventory number has to agree the reduction is achievable, in writing, or the line does not belong in the model.

Your numbers

Time recovered
hrs/wk

Total across everyone affected. Count hours that stop being worked, not hours redeployed to other work.

$

Salary plus employer taxes, benefits and overhead — typically 1.25 to 1.4× base pay.

Inventory
$
%

Back it with a named list of slow movers and excess, not a percentage someone liked.

%

Capital, storage, insurance, shrink and obsolescence combined. Most operations land in the high teens to mid twenties.

Receivables
$

Invoiced on terms. Exclude cash and card sales.

days

Days you expect to remove. One day releases one day of credit sales.

Errors and cost
$

Credit notes, re-picks, re-invoicing, expedited freight caused by bad data.

%
$

Everything spent to get to go-live, internal time included.

$

Subscription, support, hosting and the internal FTE time the system consumes.

Appraisal assumptions
%

Used to discount the cash flows and to value the receivables released. Ask finance which rate they apply to internal projects.

%

Share of the steady-state benefit you expect in the first year. Years two and three are modelled at 100%.

Result

Three-year return on investment
38.3%

Payback in 22.9 months · NPV $117,455 at 10%

Total annual benefit (steady state)$280,797
Net annual benefit after run cost$184,797
Payback period22.9 months
3-year NPV$117,455
Benefit per $1 of cost1.38×
One-off working capital released$620,932
Report and admin hours saved$124,384 · 44%
Inventory carrying cost avoided$73,920 · 26%
Receivables financing released$28,493 · 10%
Errors and rework avoided$54,000 · 19%
Implementation sits at t = 0 undiscounted. Years 1–3 discounted at 10%.
PeriodBenefitCostNet cash flowPresent valueCumulative PV
Year 0 — go live$0$240,000-$240,000-$240,000-$240,000
Year 1 (60% realised)$168,478$96,000$72,478$65,889-$174,111
Year 2$280,797$96,000$184,797$152,725-$21,386
Year 3$280,797$96,000$184,797$138,841$117,455
Hours: 46 × 52 × $52 = $124,384
Inventory: $4,200,000 × 8% = $336,000 released × 22% = $73,920
Receivables:$26,000,000 ÷ 365 = $71,233/day × 4d = $284,932 × 10% = $28,493
Rework: $180,000 × 30% = $54,000
Annual benefit = $280,797 less run cost $96,000 = $184,797
Cash flows: $72,478 / $184,797 / $184,797
NPV = -$240,000 + $65,889 + $152,725 + $138,841 = $117,455
ROI = ($730,073 - $528,000) ÷ $528,000 = 38.3%
A 38.3% three-year return with a 22.9-month payback and $117,455 of NPV is a defensible case. Before you present it, halve the benefit line you are least confident about and check the NPV still holds.

Everything is computed in your browser. Nothing you type is sent anywhere or stored.

The formula

ROI % = (Total benefits − Total costs) ÷ Total costs × 100 · Payback = Implementation ÷ Net annual benefit · NPV = −Implementation + Σ (Net cash flow in year t ÷ (1 + r)^t)
Total benefits
Sum of the annual benefit categories over the appraisal period, after applying the year-one realisation rate.
Total costs
One-off implementation cost plus the recurring annual cost for every year in the period.
Net annual benefit
Annual benefit minus the recurring annual cost. This is the figure payback is measured against.
r
Discount rate, entered as a decimal. Use your weighted average cost of capital or the hurdle rate finance applies to projects.
t
Year number, 1 to 3. The implementation spend sits at t = 0 and is not discounted.

Two things separate a business case that survives review from one that does not. First, benefits are discounted for realisation lag — year one rarely delivers the steady-state number. Second, the working-capital release from inventory and receivables is counted as the carrying cost avoided, not as income, so a one-off balance-sheet movement cannot be booked three times.

Worked example

Report and admin hours saved per week
46 hours at $52 loaded
Inventory reduction
8% of $4,200,000 at a 22% carrying rate
DSO improvement
4 days on $26,000,000 credit sales
Errors and rework avoided
30% of $180,000
Cost
$240,000 implementation, $96,000 a year
Discount rate / year-one realisation
10% / 60%
Result
38.3% 3-year ROI · 22.9 month payback · $117,455 NPV

Hours: 46 × 52 weeks × $52 = $124,384. Inventory: $4,200,000 × 8% = $336,000 released, × 22% carrying = $73,920. Receivables: $26,000,000 ÷ 365 = $71,233 a day, × 4 days = $284,932 released, × 10% cost of capital = $28,493. Rework: $180,000 × 30% = $54,000. Annual benefit $280,797, less $96,000 of running cost, leaves $184,797 a year. Year one delivers 60% of the benefit, so cash flows are $72,478, $184,797, $184,797. Discounted at 10% and set against $240,000 at t = 0, NPV is $117,455.

The four benefit categories, and who signs each one

Benefits that nobody owns get deleted in the second review meeting. Assign each line to the person whose budget or balance sheet changes if it lands, and record the evidence they accepted.

BenefitHow it is calculatedWho signs itEvidence that holds up
Report and admin hoursHours per week × 52 × loaded hourly costThe manager of the team losing the hoursA two-week time log, not a recollection. Count only hours that stop being worked, not hours redeployed.
Inventory carrying costInventory value × reduction % × carrying rateHead of supply chainA slow-mover and excess report showing the specific SKUs the reduction comes from.
Receivables financingDaily credit sales × days of DSO improvement × cost of capitalController or credit managerCurrent billing lag and dispute rate. If billing lag is the cause, the fix is process, not software.
Errors and reworkAnnual cost of errors × reduction %Ops or quality leadA count of credit notes, re-picks and re-invoices for the last quarter, with an average cost per event.

Why ROI, payback and NPV disagree

MeasureQuestion it answersWhere it misleads
ROI %How big is the return relative to the spend?Treats a dollar in year three as equal to a dollar today, and is sensitive to how you define 'cost'.
Payback monthsHow long is the money exposed?Ignores everything after payback, so it under-rates projects with long benefit tails.
NPVDoes this beat our cost of capital?Entirely driven by the discount rate and the benefit ramp. Change either and the answer moves.
A project can show a strong ROI % and still fail a hurdle-rate test, because ROI ignores when the cash arrives. Present all three and say which one your finance function decides on.

Cost lines people forget

  • Internal time during the project. Backfill, overtime and the opportunity cost of your best process people being in workshops for four months.
  • Integration maintenance, not just the build. Every interface needs owning after go-live.
  • Year-one productivity dip. Output falls before it rises. Model it as a cost or as a low realisation rate, but model it.
  • Data cleansing that has to happen whether or not the project does — be clear which side of the line you are putting it on.
  • Recurring subscription uplift. A flat annual figure across five years understates the run cost; the ERP TCO calculator applies an escalation rate properly.

Where an ERP ROI calculator gets its baseline numbers

The arithmetic takes a minute. Establishing the baseline is the work: current DSO, inventory value split by movement class, credit notes raised last quarter, and an honest count of hours spent assembling reports. Size the cost side with the ERP implementation cost estimator and the hours side with the reporting time savings calculator. You will need the same baseline again twelve months after go-live, measured the same way, so write down the queries you used now.

With you ask for the baseline in words — "DSO by month for the last 12 months, excluding cash sales" — and the answer comes back computed from your own account with the SuiteQL shown underneath, so the definition is auditable rather than remembered. Read-only by default, so nothing in the ERP moves while you build the case.

Frequently asked questions

How do you calculate ERP ROI?

Add up the annual benefits — labour hours saved at a loaded rate, inventory carrying cost avoided, receivables financing released, and error correction eliminated — then subtract total cost and divide by total cost. Over three years, $730,073 of benefit against $528,000 of cost is a 38.3% return. Use loaded hourly cost, not salary.

What is a good payback period for an ERP project?

Most finance functions want ERP inside 24 to 36 months, with anything under 18 months treated as suspiciously optimistic rather than good. The number matters less than whether the benefits are owned and measurable. A 14-month payback built on unsigned assumptions gets rejected faster than a 30-month one with evidence attached.

What discount rate should I use for an ERP business case?

Use whatever rate your finance team applies to internal projects — usually the weighted average cost of capital, sometimes a higher hurdle rate for discretionary IT spend. Ask before you model. If you have no guidance, run the NPV at two rates and show both, so the decision does not hinge on a number you picked.

Should working capital released count as an ERP benefit?

Count the carrying cost avoided, not the release itself. Freeing $336,000 of inventory saves the cost of carrying it, roughly 20–25% a year once capital, storage, insurance and obsolescence are included. The release is a one-off cash event worth reporting separately, but treating it as recurring income overstates the return several times over.

Why do ERP ROI projections usually miss?

Three reasons, in order. Benefits are assumed to start at full rate on day one when realisation takes two to four quarters. Internal labour cost during the project is left out. And headcount 'savings' are counted without anyone agreeing the headcount will actually go. Applying a year-one realisation rate fixes the first and is the cheapest credibility you can buy.

How is ERP ROI different from ERP TCO?

TCO is the cost side only — every dollar the system consumes over five years. ROI sets benefits against that cost. You need TCO first, because an ROI model built on licence and implementation alone ignores internal FTE, infrastructure and upgrade cost, which together often exceed the software line.

Related calculators

ERP business case
ERP implementation cost estimator

Estimate ERP implementation cost from licence, services, data migration, integrations, training and contingency, scaled by users, sites and complexity.

ERP business case
ERP TCO calculator

Model 5-year ERP total cost of ownership: subscription or licence, implementation, internal FTE, infrastructure, upgrades and support. Cloud vs on-prem.

ERP business case
Reporting time savings calculator

Reporting time savings calculator — price the hours your team spends building reports, the annual cost, hours recovered and the FTE equivalent.

Inventory & supply chain
Inventory carrying cost calculator

Build your inventory carrying cost rate from capital, storage, service and risk. Get the annual cost, the percentage rate, and holding cost per unit.

Read the background

ERP strategy
How to build an ERP ROI business case a CFO will approve

Build an ERP ROI business case a CFO will approve: benefit categories with named owners, payback and NPV mechanics, and honest sensitivity analysis.

ERP strategy
What does an ERP implementation cost?

What drives ERP implementation cost: scope multipliers, services-to-licence ratios, the internal time nobody budgets, and what to ask an integrator.

ERP strategy
ERP reporting tools compared: native, queries, BI and AI

ERP reporting tools compared: native reports, saved searches, a BI stack and conversational AI — with the real weaknesses of each, including ours.

All 50 ERP & finance tools

Stop calculating it by hand. Just ask your ERP.

This calculator needs you to find the inputs first. ERPray pulls them from your own ERP account and computes the answer live — with the exact query shown so you can check it.

Get early access — freeBrowse all 50 tools