ERP Requirement Study, Selection & Implementation Support

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.

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.

It depends on the trigger, not just headcount. If you are opening a second GST registration, adding inventory or manufacturing complexity, preparing for a first external audit, or finding that Tally with manual workarounds is generating errors, a structured requirement study is worth the investment even at moderate scale. For a genuinely simple, single-state, low-transaction-volume business, a lighter-touch engagement — evaluating whether an upgraded accounting package like Tally Prime or Zoho Books meets your needs before jumping to a full ERP — may be more proportionate, and we will say so rather than oversell a larger scope.

A requirement study and vendor selection engagement alone — discovery, documentation, RFP, demonstrations, and a final recommendation, without implementation oversight — typically takes 6–10 weeks. A full engagement that includes chart of accounts design, implementation oversight, data migration validation, parallel run, and stabilisation support typically runs 5–9 months for a mid-sized single-entity business, and longer for multi-entity, multi-GSTIN, or India-UAE scope, or where manufacturing and inventory complexity is significant.

We evaluate against your documented requirements rather than a fixed list, but commonly shortlisted platforms include Tally Prime (for businesses needing a strong accounting core with lighter ERP functionality), Zoho Books and the broader Zoho One suite, SAP Business One, Microsoft Dynamics 365 Business Central, NetSuite, and Odoo, along with sector-specific platforms where relevant (for example, manufacturing- or distribution-focused ERPs). The right platform depends on your transaction volume, sector, budget, number of entities and GSTINs, and whether you need manufacturing/inventory modules or a purely finance-and-operations footprint.

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.

Not automatically — it depends entirely on correct configuration. E-invoicing under Rule 48(4) of the CGST Rules requires generating invoices in a prescribed schema and reporting them to the Invoice Registration Portal (IRP) to obtain an Invoice Reference Number (IRN) and QR code, and applies to businesses whose aggregate turnover crosses the government-notified threshold (this threshold has been progressively lowered over successive notifications, so businesses should verify current applicability rather than assume exemption based on an older threshold). Most modern ERPs support e-invoicing integration, but the configuration — correct GSTIN mapping, invoice schema fields, and IRP connectivity — must be verified during implementation, not assumed to work out of the box.

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.

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 to your payment types), 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.

We provide specific, named recommendations, not generic best-practice slides. Based on your transaction volume, number of GST registrations, entity structure, sector, and budget, we shortlist and compare actual products against your documented requirements. We do not accept referral commissions from ERP vendors or implementation partners, which keeps the recommendation aligned to your interest rather than ours.

ERP costs vary widely by platform, module scope, user count, customisation depth, and whether implementation is on-premise or cloud-hosted — from a modest per-user monthly subscription for a cloud accounting-led platform to a substantial multi-year investment for an enterprise ERP with manufacturing and multi-entity consolidation. Because the range is genuinely wide and situation-specific, PNPC does not quote a single figure without first understanding your requirement scope; instead, we build a structured total cost of ownership comparison across shortlisted vendors during the evaluation phase, covering licensing, implementation, data migration, training, and annual maintenance costs that are frequently under-quoted in headline vendor pricing.

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.

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.

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.

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.

Yes. PNPC has operating offices in Chennai, Bangalore, Hyderabad, and Dubai, and we regularly 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.

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 the single most common root cause we see behind ERP projects that go live successfully but fail to deliver the financial control the business actually needed.

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.

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.

ERPs can either strengthen or weaken internal controls depending entirely on how roles, approval workflows, and access rights are configured. A poorly configured ERP can inadvertently concentrate incompatible functions (for example, the same user able to create a vendor, approve a payment, and post the journal entry) in ways that a manual spreadsheet-based process, however inefficient, did not. We map your segregation-of-duties requirements into the user role and approval workflow design before configuration begins, and review the as-built access matrix before go-live.

The core engagement includes a formal 60–90 day post-implementation review to confirm the requirement study's original objectives were achieved and to identify adoption gaps. Many clients also engage PNPC on a continuing advisory basis — for periodic roadmap reviews at business milestones (new entity, new state, new statutory requirement, or significant transaction growth), for additional module rollouts, and for ongoing GST/TDS/payroll compliance services that run on top of the implemented ERP.

It depends on complexity, not just company size. A relatively smaller company with significant multi-entity, multi-currency, or manufacturing complexity may genuinely need an enterprise-grade platform, while a larger but operationally simple company may be well served by a mid-market platform. We evaluate this against your documented requirement study rather than against revenue or headcount alone, and we will recommend against an enterprise platform if a mid-market solution genuinely meets your needs at materially lower total cost of ownership.

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.

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 12–18 months after a poorly scoped go-live.

A vendor's implementation consultants are skilled at configuring their specific software, but they are not trained in, and are not incentivised to independently validate, Indian GST, TDS, and Companies Act compliance requirements, or UAE VAT and Corporate Tax requirements where relevant. PNPC is a practising CA firm. We are present at requirement definition, through vendor-neutral selection, through chart of accounts design, and through the build and stabilisation phases — with the statutory and financial-control lens as the throughline, not an afterthought.

Current-state assessment and stakeholder discovery. Formal requirement study documentation covering modules, transaction volumes, and statutory obligations. Vendor shortlisting, structured RFP process, and scenario-based demonstration evaluation. Total cost of ownership comparison across shortlisted vendors. Final selection recommendation report and commercial/contract terms review. Chart of accounts and tax mapping design aligned to GST, TDS, and Schedule III requirements. Process and controls redesign for segregation of duties and audit trail. Implementation oversight against the approved design through the build phase. Data migration validation and opening balance reconciliation. Parallel run coordination and reconciliation for at least one full compliance cycle. Go-live and stabilisation support for the first live compliance cycle. Formal 60–90 day post-implementation review.

Yes. ERP-to-ERP migration (for example, moving from Tally to a fuller ERP, or from one enterprise platform to another after an unsatisfactory first implementation, a merger, or an outgrown legacy system) follows a broadly similar structure to a first-time adoption — requirement study, vendor evaluation if the platform itself is changing, chart of accounts redesign, data migration, and parallel run — with the added complexity of migrating a larger volume of historical transaction data and often correcting configuration issues carried over from the legacy system.

Our accounting and compliance teams are trained across the major platforms we commonly recommend — Tally Prime, Zoho Books, SAP Business One, Microsoft Dynamics 365 Business Central, NetSuite, and Odoo among them — specifically so that platform familiarity is not a factor that could bias a recommendation. The requirement study and vendor evaluation criteria are documented and weighted before vendor demonstrations begin, and the final recommendation is scored against those pre-agreed criteria.

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.

Change management and user training are part of the full engagement scope, though the hands-on software training itself is typically delivered by the implementation partner or vendor, with PNPC ensuring the finance and compliance team specifically receives training on the GST/TDS-relevant workflows (not just generic software navigation) and validating that the team can independently operate the system correctly before we sign off on go-live readiness.

We say so. Part of the value of an independent requirement study is an honest assessment of readiness — sometimes the study reveals that the business's current process discipline, data quality, or organisational bandwidth is not yet sufficient to successfully adopt a full ERP, and that a phased approach (starting with a stronger accounting platform and revisiting a full ERP in 12–24 months) is the more realistic path.