ERP Selection & Implementation Support: The Process, Start to Finish
The mechanics of ERP Selection & Implementation Support are what clients ask about once they have decided to proceed. 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.
What exactly does 'ERP Requirement Study, Selection & Implementation Support' mean in a CA firm's context — is this a systems integration service?
It is advisory work focused on the finance, tax, and compliance layer of an ERP project — requirement definition, vendor-neutral evaluation and selection, chart of accounts and tax mapping design, and oversight of the implementation partner's build — delivered by a CA firm rather than a systems integrator. We do not write code, host servers, or perform the hands-on technical configuration ourselves. What we bring that a pure systems integrator typically does not is the statutory lens: how the chosen ERP and its configuration interact with GST, TDS, Schedule III presentation, and Companies Act compliance obligations.
In practice: We are frequently engaged after a first ERP attempt — selected and implemented by a systems integrator without CA involvement — produced a chart of accounts or workflow that does not reconcile cleanly with GST returns or the statutory audit. Getting the finance and compliance design right during selection is materially cheaper than remediating it after go-live.
How is this different from hiring an ERP implementation partner or systems integrator directly?
An ERP implementation partner or systems integrator is typically incentivised, directly or through vendor referral arrangements, to sell and configure a specific product, and their expertise is technical rather than statutory. PNPC's advisory is vendor-neutral — we run the requirement study and evaluation independently of any single vendor's interest, and we bring the compliance lens a technical implementation team is not trained to apply to Indian (and where relevant, UAE) tax and corporate law requirements. In most engagements, PNPC and the implementation partner work alongside each other rather than PNPC replacing that role.
In practice: We do not accept referral commissions from ERP vendors or implementation partners. Our recommendation is driven by fit against your documented requirements, not by which vendor has the most attractive partner margin.
How long does a typical ERP requirement study, selection, and implementation engagement take?
The timeline for a requirement study and vendor selection engagement alone — discovery, documentation, RFP, demonstrations, and a final recommendation, without implementation oversight — depends on scope and is confirmed at scoping. A full engagement that includes chart of accounts design, implementation oversight, data migration validation, parallel run, and stabilisation support takes longer, and longer again for multi-entity, multi-GSTIN, or India-UAE scope, or where manufacturing and inventory complexity is significant; timelines depend on the case.
In practice: A major timeline variable is often not the technical build — it is how quickly the client's internal team can make and stick to decisions on vendor selection, budget approval, and staff availability for user acceptance testing. We build a realistic project plan around your organisation's actual decision-making pace.
What is a chart of accounts, and why does PNPC say getting it right during ERP selection matters so much?
The chart of accounts is the structured list of every account category — assets, liabilities, income, expenses, and equity — that the ERP uses to classify every transaction. A chart of accounts designed without reference to your GST return heads, TDS sections, and Schedule III financial statement presentation format will require manual reclassification work at every filing and every audit. Designed correctly at the outset, transactions flow cleanly from ledger to GST return to financial statements with minimal manual intervention.
In practice: A chart-of-accounts structure that does not map to GST and TDS reporting requirements has to be reworked after go-live. The rework is always more disruptive than getting it right the first time, because by then live transaction history exists in the old structure.
Can the ERP handle multiple GST registrations (GSTINs) across different states?
Most mid-market and enterprise ERPs can be configured to handle multi-GSTIN operations, but this must be explicitly designed rather than assumed. Each GSTIN typically needs its own place-of-supply logic, its own GSTR-1/GSTR-3B mapping, and correct handling of inter-state stock transfers between the business's own GSTINs (which attract GST under Schedule I of the CGST Act as a deemed supply between distinct persons). We verify this capability during vendor evaluation and design the multi-GSTIN configuration explicitly during chart of accounts and process design.
In practice: Inter-branch stock transfer GST treatment is one of the most commonly misconfigured areas in multi-GSTIN ERP implementations we have reviewed.
How does PNPC handle TDS automation within the ERP?
TDS should ideally be computed and tracked automatically at the point of invoice or payment booking — by vendor, by applicable section (194C for contractors, 194J for professional fees, 194Q for purchase of goods above the threshold and others as relevant, under the Income-tax Act 1961 up to FY 2025-26; from tax year 2026-27 these are consolidated under Section 393 of the Income-tax Act 2025, so confirm the applicable entry for each payment type), with running threshold tracking so the system flags when a payment crosses the applicable TDS threshold for that vendor in the financial year. We design this logic into the chart of accounts and vendor master configuration during implementation, and validate it during parallel run before recommending cutover.
In practice: A common configuration gap we find in vendor-led implementations: TDS sections are set up generically at the ERP's default rates without reflecting the vendor-specific applicability rules or any lower/nil deduction certificates the business holds. We reconcile this vendor-by-vendor during our review, not as a blanket assumption.
How does an ERP implementation interact with our existing statutory audit?
Directly. A statutory auditor needs a clear, traceable path from source document to ledger entry to financial statement. An ERP configured without preserving that audit trail — for example, batch-processed transactions with no individual approval record, or system-generated journal entries with no supporting documentation link — creates audit queries and can affect the audit opinion. We design the control and documentation framework into the requirement study and configuration oversight specifically so the resulting system supports, rather than complicates, the annual statutory audit.
In practice: We ask 'how will your auditor verify this transaction six months from now' about every proposed configuration choice. It is a simple question that catches a surprising number of well-intentioned but audit-unfriendly designs before they go live.
How does PNPC handle ERP selection for a manufacturing business with inventory and production complexity?
Manufacturing requirements — bill of materials, work orders, production costing, batch/lot tracking, and multi-stage inventory valuation — significantly narrow the realistic platform shortlist compared to a pure trading or services business. We document your specific production process during the requirement study (make-to-stock versus make-to-order, single-stage versus multi-stage production, whether batch traceability is regulatory-driven as in food or pharma) and evaluate platforms specifically against that complexity, in addition to the standard finance and GST/TDS requirements.
In practice: Manufacturing ERP selection is where generic accounting-software vendors most often over-promise capability they do not genuinely have. We insist on a live, scenario-based demonstration of your actual production process before any platform is shortlisted for a manufacturing client.
Can PNPC support ERP selection and implementation across both an Indian entity and a UAE entity?
Yes. PNPC has operating offices in Chennai, Bangalore, Hyderabad, and Dubai, and we support ERP engagements spanning an Indian company and a UAE Free Zone or Mainland entity — whether that means a single ERP instance with multi-entity/multi-currency consolidation, or separate but integrated systems with a defined consolidation and intercompany process. UAE-side considerations include VAT registration and return configuration, UAE Corporate Tax reporting needs, and WPS-compliant payroll integration, coordinated with the India-side GST/TDS/Companies Act requirements under one engagement.
In practice: The interaction between the Indian entity's GST/TDS reporting and the UAE entity's VAT/Corporate Tax reporting has consolidation and intercompany-transaction implications that only a firm present in both jurisdictions can advise on coherently. We handle both sides directly rather than referring the UAE component to a separate, uncoordinated partner.
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.