GST Process Review & SOP Design

A GST audit (whether a departmental audit under Section 65, a special audit under Section 66, or the GSTR-9C reconciliation statement review) examines whether your past-filed returns are accurate and whether the correct tax has been paid — it looks backward at outcomes. A GST Process Review looks at how those outcomes are produced: who does what, in what order, using which system, and what controls exist to catch errors before they become filed returns. The review's output is not an opinion on past compliance — it is a redesigned, documented process (the SOP) intended to prevent the errors that an audit would otherwise catch after the fact.

Outsourcing execution does not eliminate process risk — it relocates it. If your outsourced accountant is the only person who understands how your ITC is reconciled, how RCM transactions are identified, and how your HSN codes are mapped, your business has full dependency risk on a single external party, with no internal visibility or control. A process review documents the process regardless of who executes it, so your business retains institutional knowledge, can verify the work being done on your behalf, and can transition providers without losing continuity if needed.

For a single-GSTIN SME with one accounting system and a straightforward transaction profile, the full engagement — from scoping to SOP delivery and staff training — typically takes 4 to 6 weeks. For a multi-GSTIN group with several ERP systems, multiple business units, or complex transaction types (RCM-heavy, significant capital goods, multiple e-commerce channels), the engagement typically takes 7 to 10 weeks. The timeline depends significantly on how quickly the business grants document and system access and makes staff available for interviews.

Read-only access to your actual accounting/ERP system materially improves the quality of the review, because we can verify how the tax-rate master, HSN mapping, and vendor/customer masters are actually configured — not just what the exported reports show. Exported reports (GSTR-1, GSTR-3B, GSTR-2B, ledgers) are the minimum baseline and allow a meaningful review, but system-level access lets us identify configuration-level root causes, such as an incorrect default tax code, that a report alone would not reveal.

Not necessarily, but scale matters. If your GST filing already runs smoothly with no recurring notices, a full-scale multi-week process review may be more than you need — a lighter GST Health Check covering a reconciliation of the last few return periods may surface the same insights at lower cost. A full Process Review & SOP Design becomes clearly worthwhile once you have recurring errors, a single point of dependency on one staff member, plans to grow into a new state, or are preparing for external scrutiny (audit, due diligence, or fundraising).

Effective from September 2025, the GST Council rationalised the earlier four-slab rate structure (5%, 12%, 18%, and 28%) into a simplified structure of 5% and 18% as the two principal slabs, with a separate 40% rate applied to specified demerit/luxury goods (such as tobacco products, pan masala, and select luxury/sin goods). This changed the applicable rate for a wide range of HSN/SAC codes. A process review specifically checks whether your billing system's tax-rate master, pricing templates, and quotation formats have all been updated to reflect the current structure — because an outdated tax master silently continues to apply the old rate on new invoices until someone notices, usually far too late for easy correction.

Section 16(2)(aa) of the CGST Act conditions your entitlement to input tax credit on the invoice details being furnished by your supplier in their GSTR-1 and being communicated to you via GSTR-2B. In practice, this means ITC should be claimed in GSTR-3B only for invoices that actually appear in your GSTR-2B for that period — claiming ITC on an invoice your supplier has not yet reported (even if you have a valid physical invoice) exposes that credit to reversal, interest, and potentially penalty if it is later found to be unsupported. A well-designed process builds GSTR-2B matching into the monthly workflow before ITC figures are finalised in GSTR-3B — not as an afterthought reconciliation done weeks later.

We test whether your accounts team can correctly identify every category of transaction that attracts RCM under the CGST Act and the applicable rate notifications — common triggers include Goods Transport Agency (GTA) freight payments, fees paid to advocates and arbitral tribunals, sponsorship services, director sitting fees paid to non-employee directors, and import of specified services. RCM requires the recipient (not the supplier) to self-invoice, pay the tax directly, and then separately claim eligible ITC — a mechanism that is easy to miss entirely if nobody has mapped which of your specific vendor categories trigger it.

Yes — this is a common and effective structure. We design a common core SOP covering the process steps that are identical across all states (procurement-to-ITC logic, RCM identification rules, reconciliation cadence, general escalation structure), with state-specific annexures capturing what genuinely differs — the specific officer jurisdiction, any state-specific procedural nuance, and the local team's reporting line. This avoids both extremes: a single rigid document that ignores real state differences, and four entirely separate documents that create group-level inconsistency.

The SOP is deliberately role-based — 'Accounts Executive — Accounts Payable', 'Finance Manager', 'Authorised Signatory' — rather than naming specific individuals. This is a design choice, not an oversight: an SOP that names 'Priya handles GSTR-2B reconciliation' becomes obsolete the day Priya changes role or leaves the company. A role-based SOP survives staff turnover because the next person appointed to that role inherits a documented process rather than an undocumented one.

The SOP is built around your existing ERP/accounting system by default — a process review is not a systems-selection exercise, and most businesses do not need to change platforms to achieve a well-controlled GST process. If, during the review, we find your current system genuinely cannot support a necessary control (for example, no way to flag HSN codes without a valid rate mapping, or no API-based e-invoicing integration when you are above the mandatory threshold), we will flag this specifically as a limitation — but the default design goal is to make your current system work better, not to recommend a system change.

E-invoicing under Rule 48(4) of the CGST Rules requires specified categories of registered persons — currently those whose aggregate turnover has crossed the applicable notified threshold in any financial year from 2017-18 onwards — to report every B2B invoice to the Invoice Registration Portal (IRP) to obtain an Invoice Reference Number (IRN) and QR code before the invoice is issued to the customer. If your business is above the threshold, or approaching it, the SOP must include e-invoicing as a mandatory step in the sales-to-filing process, because an invoice issued without a valid IRN is treated as not having been issued at all for GST purposes, and the recipient cannot claim ITC on it.

A change in reconciliation process itself does not trigger any ITC adjustment — the process review changes how you verify and document ITC claims going forward, not the substantive tax position on stock already held. However, if the review surfaces that ITC was incorrectly claimed in a prior period (for example, credit claimed on an invoice that never appeared in GSTR-2B, or credit claimed on a blocked category under Section 17(5)), that specific historical position may need correction through the appropriate GSTR-3B adjustment or disclosure in the next GSTR-9, separate from the process fix itself.

Yes — a process review conducted a few months before your GSTR-9 due date is one of the most effective ways to prepare, because it surfaces discrepancies between GSTR-1, GSTR-3B, GSTR-2B, and your books while there is still time to investigate and correct them, rather than discovering them for the first time during annual return compilation. Businesses that run a process review with annual-return timing in mind typically find their GSTR-9/9C preparation considerably smoother, because the underlying data has already been reconciled through the year rather than all at once at year-end.

PNPC quotes a fixed, agreed fee for the engagement after the scoping call, based on the number of GSTINs in scope, the number of ERP/accounting systems involved, transaction complexity (RCM exposure, e-invoicing obligations, multi-state supply flows), and whether the engagement includes staff training and a post-implementation review. The fee is confirmed in writing before work begins — there are no open-ended hourly arrangements that create billing uncertainty for a scoped deliverable like an SOP document.

The SOP belongs entirely to your business once delivered — it is your operating document, not a PNPC-dependent tool. Your internal team can update it as roles change or minor process details evolve. We recommend engaging PNPC (or any qualified CA) specifically when a material trigger occurs — a GST rate change, a new GSTIN, an ERP migration, or crossing a compliance threshold — because those events typically require technical GST knowledge to assess correctly, not just document editing.

This is a common and expected outcome of a thorough process review — finding gaps is the point of the exercise, and it is far better to discover them through a planned internal review than through a departmental audit. When a genuine compliance gap is found (for example, unpaid RCM liability on a transaction category that was never identified), PNPC advises on the appropriate corrective path — which may include voluntary payment with applicable interest, disclosure in the next return where the mechanism allows, or a considered risk assessment if the amounts are immaterial — always with the objective of putting the business in the strongest possible compliance position going forward.

Both are included as standard. PNPC conducts a structured walkthrough session with your finance team and any relevant operational staff (procurement, dispatch, sales administration) after the SOP is finalised — this is a live session, not just an emailed document, because a written SOP alone is rarely followed correctly from Day 1 without a walkthrough that lets staff ask questions about their specific role. We also prepare role-specific quick-reference sheets for staff who need the essential steps of their part of the process without reading the entire document.

A documented, followed SOP materially strengthens a business's position during a GST departmental audit or scrutiny, because it allows the business to demonstrate a consistent, defensible internal control for its classifications, ITC claims, and RCM payments — rather than reconstructing the reasoning from scattered records and memory during the audit itself. It is not a guarantee against every finding, since an SOP that is well-designed but poorly followed offers limited protection — which is why PNPC builds in a control checklist and recommends periodic review to verify actual adherence, not just documented intent.

Yes. GST touches procurement, sales, and finance operations broadly, and businesses undertaking a wider internal controls review or business process re-engineering exercise often find it efficient to fold the GST-specific process review into that broader scope, since much of the document review and staff interview work overlaps. PNPC's Risk Advisory practice offers broader Business Process Re-engineering and SOP Design services, and we coordinate closely with our GST team where a client's need spans both.

A Composition Scheme taxpayer's process is structurally simpler in some respects — no ITC claiming, no GSTR-2B reconciliation, and quarterly CMP-08 payment with an annual GSTR-4 rather than monthly/quarterly GSTR-1 and GSTR-3B. The review instead focuses on verifying continued eligibility (aggregate turnover has not crossed the ₹1.5 crore threshold for traders, or ₹75 lakh in special-category states, or the ₹50 lakh threshold for the services-focused composition option), correct classification of turnover for the applicable composition rate (1% for traders, 5% for restaurants/eateries, 6% for other eligible service providers), and ensuring the business has not inadvertently engaged in an activity — such as inter-state supply or e-commerce sales — that would disqualify it from the scheme.

We document this clearly as a named limitation with a description of the workaround available (often a manual checklist step to compensate for what the system cannot automatically flag) alongside the estimated cost and effort of a system-level fix, so management can make an informed decision on timing. We do not recommend a system replacement lightly, since ERP migrations carry their own significant cost and risk — the SOP is designed to work within your current system wherever a reasonable manual control can substitute for an automated one.

We recommend a periodic review at least annually, and additionally whenever a material trigger occurs — a GST rate change (such as the September 2025 rationalisation), a new GSTIN or state registration, an ERP migration, crossing the e-invoicing or QRMP eligibility threshold, or a significant change in business model (new product lines, new sales channels). An SOP that is never revisited gradually drifts out of sync with both the regulatory environment and the business's actual operations.

For businesses that fall within the categories required to deduct TDS under GST Section 51 (notably government departments, local authorities, and certain notified entities), the process review includes verifying correct TDS deduction, deposit, and GSTR-7 filing as part of the sales/procurement process, since this is a distinct compliance stream from regular outward-supply GST reporting. For most private-sector businesses outside the notified categories, GST TDS is not applicable and is confirmed as out of scope during the initial scoping call.

Yes — this is one of the most valuable times to commission a process review, because investor due diligence teams specifically examine GST compliance discipline as part of financial and legal diligence, and a documented, followed SOP is a positive signal of operational maturity. Cleaning up ITC reconciliation gaps, RCM identification, and rate-mapping issues before diligence begins is considerably less disruptive than discovering and explaining them mid-diligence, when timelines are tight and every finding invites additional investor questions.

A process finding identifies a control gap — for example, RCM transactions not being systematically identified — which may or may not have resulted in an actual unpaid tax liability, depending on whether any RCM-triggering transactions actually occurred in the review period. A genuine tax exposure is the quantified, real liability that results when a control gap did in fact cause a transaction to be misclassified or under-taxed. PNPC distinguishes these clearly in the findings report: process gaps are fixed prospectively through the SOP, while any quantified historical exposure is addressed through its own corrective path — voluntary payment, disclosure, or documented risk acceptance where amounts are genuinely immaterial.

Yes, where relevant to your business model. GST on advances received for services (and for specified categories of goods, subject to the notifications in force) is a common area of process weakness, because it requires tracking receipt of advance separately from invoice issuance and ensuring the tax point is correctly identified. For businesses that regularly receive advances — project-based service providers, real estate-adjacent businesses, or custom manufacturing — this is built into the sales-to-filing section of the SOP as a specific sub-process, not treated as a niche exception.

The SOP is drafted only after the document review, system access review, and staff interviews are complete — every process step references your actual ERP screens or field names (or a close functional description if we could not obtain direct system access), your actual role titles, and your actual transaction types identified during the walkthrough. A findings report specific to your business is presented and discussed with management before drafting begins, precisely so the SOP reflects agreed priorities and reality, not a generic best-practice checklist with your company name inserted at the top.

Very relevant for services businesses. While e-way bills and HSN-code-for-goods issues are less central, services businesses face their own significant process risks: SAC code classification, place-of-supply determination for inter-state services (which follows different rules than goods), RCM on professional fees and imported services, ITC eligibility on input services, and — for export-of-services businesses — LUT (Letter of Undertaking) compliance and correct zero-rating documentation. The process review is scoped to your actual transaction profile, whether goods-heavy, services-heavy, or mixed.

The compliance calendar embedded in the SOP is specific to your business — reflecting your actual filing frequency (monthly or QRMP), the number and location of your GSTINs, your e-invoicing obligations if applicable, and any state-specific due-date variations. It goes beyond a generic 'GSTR-1 due on the 11th, GSTR-3B due on the 20th' calendar by building in your internal deadlines — when the reconciliation must be complete for review before the actual filing deadline, when RCM self-invoices must be raised, and when management sign-off must occur — so the external statutory deadline is never the first internal deadline anyone is working against.

An internal team writing its own SOP tends to document the process as it is currently understood by the people already closest to it — which means existing blind spots (a missed RCM category, an outdated rate mapping, an ITC-claiming practice that does not actually match GSTR-2B) get documented and formalised rather than caught and fixed. An external CA-led review brings a structured, evidence-based diagnostic — document sampling, system verification, and independent staff interviews — before anything is written down, so the SOP reflects a corrected process, not simply the current process in writing.

Initial scoping call and engagement confirmation. Document and read-only system access review covering 12 months (or a full financial year) of returns, books, and master data. Structured process walkthroughs across procurement-to-ITC, sales-to-filing, RCM identification, and e-invoicing/e-way bill configuration. Sample-period reconciliation across GSTR-1, GSTR-3B, GSTR-2B, and books. Staff interviews and role mapping. A findings report presented to management before drafting begins. A complete, process-area-by-process-area SOP document with named roles, system steps, and escalation paths. An embedded, business-specific compliance calendar. A control checklist for ongoing internal or statutory verification. A structured staff training walkthrough with role-specific quick-reference sheets. Availability during the first 1–2 filing cycles under the new SOP for implementation questions.

A software vendor's implementation team is focused on configuring their specific platform correctly — valuable, but narrower than a full GST process review, and they are generally not positioned to advise on the underlying tax-law questions (RCM applicability, ITC eligibility, rate classification) that determine what the system should be configured to do. A generic compliance consultant may document a process without the depth of current GST law knowledge needed to identify subtle but material gaps — such as a Section 16(2)(aa) mismatch or a composition-scheme eligibility breach. PNPC combines both: practising CA judgement on the substantive tax questions, and the operational discipline to translate that judgement into a document your team will actually follow.