Failed Projects, Contracts and Official Sources

Hidden ERP costs and buying mistakes: 15 lines missing from most quotes

The ERP costs Indian MSMEs most often miss: add-ons, transaction charges, storage, customisation upgrades, staff time, forex, exit and more, with illustrative sums.

Updated · 4 min read

Hidden ERP costs and buying mistakes: 15 lines missing from most quotes

The costs that sink an ERP budget are rarely the subscription itself. They are the lines that do not appear on the first quote: paid add-ons for features you assumed were included, transaction and storage charges that grow with volume, customisations that must be redone at upgrades, partner support sold separately, your own staff time, currency moves on USD plans, and the cost of leaving. Listing them before you sign, and asking each vendor to price them, is the cheapest protection you have. Amounts below are illustrative.

This guide belongs to why ERP projects fail and how to avoid it.

The 15 lines to ask about

#Hidden costWhy it is missedWhat to ask
1Add-on modules (e-way bill, multi-GSTIN, multi-currency, batch tracking, manufacturing)Assumed to be standard"Which of our requirements need add-ons, at what price?"
2E-invoice, e-way bill or API call charges above a quotaVolumes grow"What is included per month, and the price per extra call?"
3Storage and document limitsAttachments and history grow"What storage is included, and the price per extra GB?"
4Extra companies or GSTINsNew state registration or group company later"Price per additional entity or GSTIN?"
5Light vs full usersA role needs a function only full users have"Which functions can each licence type perform?"
6Minimum users or contract valueSmall teams pay above list per user"Is there a minimum, and can we reduce at renewal?"
7Partner support planSold as a separate contract"What does vendor support cover, and what does the partner plan cost?"
8Customisation upgrade workCustom code breaks at version upgrades"Who retests and fixes custom items at upgrades, at what cost?"
9Integration maintenanceBanks and marketplaces change their APIs"Who maintains each integration, and at what price?"
10Sandbox or test environmentNeeded for testing changes safely"Is a test environment included?"
11Training for new staffStaff turnover after go-live"Price of refresher and new-joiner training?"
12Forex and bank charges on USD plansNot on the invoice"Can we be billed in rupees by an Indian entity?"
13Old system kept read-onlyNeeded for history and audits"Can the old system be licensed read-only, at what cost?"
14Internal staff timeNever invoicedEstimate hours by role yourself
15Exit: data export and migrationSeems far away"Self-service full export? Price of assisted export?"

Illustrative sums: how small lines add up over five years

Hidden lineAssumption (illustrative)Five-year cost
E-way bill add-on₹25,000 a year₹1,25,000
Extra API calls1,500 a month × ₹1 × 12 × 5₹90,000
Storage above quota₹12,000 a year from year 3₹36,000
Partner support plan₹1,20,000 a year₹6,00,000
Customisation retesting at two upgrades6 days × ₹12,000 × 2₹1,44,000
Refresher and new-joiner training₹30,000 a year₹1,50,000
Old system read-only for two years₹20,000 a year₹40,000
Exit assistance8 days × ₹15,000₹1,20,000
Total₹13,05,000

On a subscription of ₹5,00,000 a year (₹25 lakh over five years), these lines add more than 50%. Not every business faces all of them, but each should be priced or ruled out. Add them to your TCO and the ERP TCO estimator.

Common buying mistakes

Buying for today's size only

A system that fits 10 users and one GSTIN may need replacing when you open a second state office. Ask for the price and feasibility of the next stage now.

Buying for an imagined future size

The opposite mistake: paying for an enterprise suite and a long implementation the business cannot absorb. A phased rollout of a mid-sized system is often safer.

Letting the vendor run the demo

A polished standard demo hides gaps. Insist on your own scenarios and data; see the requirements checklist.

Treating compliance features as interchangeable

Two products may both "support e-invoicing"; one generates IRNs automatically at billing, the other needs a manual upload. Under the 30-day limit for taxpayers at ₹10 crore AATO and above, that difference matters. See the e-invoicing integration guide.

Ignoring the partner

For most MSME projects, the implementation partner's skill matters as much as the software. Speak to two references of similar size and industry, and ask about problems, not just successes.

Paying in full upfront

Link implementation payments to milestones and keep a retention until after the first month-end close.

Signing without reading renewal terms

Auto-renewal with a 90-day notice window and an uncapped uplift is a common and expensive surprise. See the SaaS contract guide.

A quick self-check before signing

  • Have we asked each vendor to price lines 1–15 in writing?
  • Do we know our invoice, e-way bill and document volumes for the next three years?
  • Is there a contingency of at least 10–15% on one-time costs?
  • Have we estimated our own staff time?
  • Do we know what leaving would cost?

FAQ

Are hidden costs a sign of a bad vendor?

Not necessarily. Many charges are legitimate and published somewhere; they are "hidden" because buyers do not ask. The risk lies in not pricing them before deciding.

How much contingency should I keep?

There is no fixed rule. Many buyers keep 10–20% of one-time costs, more for projects with heavy customisation or poor data.

Does GST apply to these extras?

Yes, add-ons, support and services generally attract 18% GST, which is usually claimable as input tax credit by a registered business.

Sources

Related guides