ERP Selection & Implementation Support: Where It Goes Wrong
The failures on ERP Selection & Implementation Support repeat, which means they are avoidable if you know what to watch. The questions below are the ones raised most often in practice; the full scope of the service is on the ERP Selection & Implementation Support page.
We are preparing for our first institutional funding round. Does ERP selection help with investor due diligence?
Yes — financial systems and data quality are a recurring diligence focus area, and manual or fragmented systems are a common source of delay or valuation friction. A clean, well-configured ERP with reliable, timely MIS materially improves the diligence experience. Where a funding round is on the near-term horizon, we design the requirement study and reporting output with investor-grade MIS and dashboard needs explicitly in mind.
In practice: Term sheets can be re-priced or delayed if a target company cannot produce reliable historical MIS on request during diligence. Addressing this proactively, months before a fundraise, is far less disruptive than a rushed ERP clean-up during an active diligence process.
Our existing ERP is already live but generating GST or TDS mismatches. Can PNPC help without a full re-implementation?
Yes. This is a common trigger for engaging us — a remediation review rather than a fresh selection. We assess the existing configuration, identify the specific gaps causing GST or TDS mismatches (commonly incorrect place-of-supply mapping, missing TDS section assignment, or a chart of accounts that does not reconcile to return heads), and recommend targeted reconfiguration rather than a full re-implementation where the underlying platform is otherwise fit for purpose.
In practice: Where the root cause is configuration rather than platform choice, a remediation review is usually cheaper and faster than a full re-implementation.
What is a requirement study, specifically, and why can't we just ask a vendor to demo their product and decide from there?
A requirement study is a structured document that defines what your business actually needs from an ERP — transaction volumes and types, statutory obligations by module, integration needs, reporting requirements, and user roles — before any vendor is engaged. Skipping this step and going straight to vendor demos means you are evaluating vendors against their own idea of what you need, which is shaped by what their product does well rather than by your actual requirements. It is a common root cause of ERP projects that go live successfully but fail to deliver the financial control the business actually needed.
In practice: Where an ERP selection process consists entirely of vendor demos with no independent requirement study, the eventual gap usually traces back to a requirement that was never documented and therefore never tested during vendor evaluation.
What does data migration involve, and what typically goes wrong?
Data migration is the process of moving historical transaction data, opening balances, outstanding receivables and payables, inventory valuation, and fixed asset registers from the legacy system into the new ERP. Common failure points include incorrect opening balance reconciliation, inventory valuation method mismatches between old and new systems, and TDS/GST data (such as outstanding lower-deduction certificates or pending input tax credit reconciliations) not being carried forward accurately. We reconcile migrated data against the legacy system's known-correct figures before recommending sign-off on the migration.
In practice: Opening balance errors are quiet — they do not always throw an obvious system error, but they compound silently through every subsequent period until a reconciliation exercise (often at the first statutory audit on the new system) surfaces the discrepancy. We treat opening balance reconciliation as a mandatory, signed-off checkpoint, not an assumption.
What is a parallel run, and is it really necessary?
A parallel run means operating the legacy system and the new ERP side by side for at least one full compliance cycle — a GST return period, a payroll run, a month-end close — and reconciling the outputs before fully retiring the old system. It adds time and some duplicated effort, but it is the primary safeguard against a configuration error reaching a filed GST return, an incorrect payroll disbursement, or a misstated Board-reported financial statement. We consider it a near-mandatory step for any business above modest transaction complexity.
In practice: Skipping the parallel run to accelerate go-live risks a GST place-of-supply misconfiguration being discovered only after the return is already filed — requiring a correction filing and, in some cases, interest exposure. A parallel run is a small cost against that risk.
What happens if the implementation partner and PNPC disagree during the build phase?
This occasionally happens, most often around configuration shortcuts that speed up go-live but compromise the tax mapping or control design PNPC has recommended. Our role is to flag the statutory or control risk clearly to you, the client, with the reasoning, so the final decision remains yours with full information — we do not have contracting authority over the implementation partner, and we are transparent about that boundary from the outset of the engagement.
In practice: We put our design recommendations and any points of disagreement with the implementation partner in writing, specifically so that if a shortcut is taken against our advice and causes a problem later, the trail is clear and the fix is faster to identify.
How much does PNPC charge for ERP requirement study, selection, and implementation support?
PNPC charges a fixed, agreed professional fee, scoped to the specific engagement — a requirement study and selection engagement alone is priced differently from a full engagement including chart of accounts design, implementation oversight, and post-go-live support. The exact fee is discussed and confirmed in writing before any work begins, based on your business's scale, entity count, and module scope. We are not the cheapest option relative to going directly to a vendor's own consultative sales process, but we do not carry a vendor's referral bias, and the design and oversight we provide is intended to avoid the far larger cost of a remediation project after a poorly scoped go-live.
In practice: Ask us for a written scope and fee letter before engagement. We provide one for every client, broken down by phase, so you can choose to engage us for the full journey or for a narrower scope such as requirement study and vendor selection alone.
What is the risk of doing ERP selection entirely in-house without any external advisory support?
It is entirely possible to run a successful ERP selection in-house, particularly with an experienced CFO or ERP-experienced finance leader on staff. The risk, in businesses without that specific in-house expertise, is usually not a bad-faith decision but a blind spot — a requirement that seems obvious to an outsider (multi-GSTIN handling, TDS section-wise tracking, audit-trail preservation) is missed because no one on the internal team has been through an ERP implementation and a subsequent statutory audit or GST assessment on the resulting system.
In practice: We are not suggesting every ERP decision needs external advisory support — many well-run finance teams handle this competently in-house. Where we add the most value is specifically where that in-house ERP-and-compliance-combined experience does not yet exist.
Where this sits in the wider engagement
ERP Selection & Implementation Support rarely arrives on its own. The statutory basis and the current requirements are set out on the ERP Selection & Implementation Support service page, and the related services are grouped under Business Transformation.
What PNPC does
PNPC Global has practised since 1986 across India and the UAE. On ERP Selection & Implementation Support we take the work end to end — reviewing the facts, preparing and filing what is required, and dealing with the authority through to closure.