GST SOP Preparation & Compliance Manual

Knowing the GST rules tells you what the law requires. An SOP tells your specific team, in your specific business, exactly which steps to follow, in what order, with whose sign-off, using which forms or system screens, to comply with that law consistently — even after the person who originally understood the rules has left the company. A GST SOP names actual roles (who verifies a vendor's GSTIN before booking a purchase, who reconciles ITC against GSTR-2B, who signs off the return before filing) and ties each step to the underlying CGST Act provision or notification, so the document stays defensible and is not simply a restatement of the law in different words.

Yes, and it should be corrected without delay. The GST Council rationalised rates effective September 2025, moving from the earlier multi-slab structure to a simplified structure with two principal slabs (5% and 18%) and a separate 40% demerit/luxury rate reserved for a narrow, specifically notified list of goods such as tobacco products, pan masala, and certain luxury items. A rate master, pricing sheet, or invoicing template still built around the pre-rationalisation slabs will misclassify transactions, generate incorrect invoices, and create ITC disputes for your customers when their GSTR-2B does not match what they expect. Reconciling your HSN/SAC-to-rate mapping against the current notified schedule is one of the first steps in any GST SOP engagement PNPC undertakes today.

A checklist tells you what to do. An SOP tells you how to do it, who is responsible at each step, what happens when something does not match, and what the underlying legal basis is — so it survives staff turnover and holds up under audit or departmental scrutiny. A checklist item that says 'reconcile ITC with GSTR-2B' is not the same as a documented protocol specifying which report to pull, what tolerance for mismatch is acceptable before escalation, who investigates a mismatch, and how the resolution is recorded. PNPC frequently upgrades an existing checklist into a full SOP rather than starting from zero, where the underlying process logic is sound but under-documented.

Yes — RCM identification is one of the most common gaps PNPC finds during the as-is walkthrough. Under Section 9(3) and 9(4) of the CGST Act, RCM applies to specified categories including goods transport agency services, sponsorship services, legal services received from an advocate or firm of advocates, services from certain government authorities, and specified purchases from unregistered suppliers in notified categories. A business that has never mapped its actual vendor base against these categories is very likely under-reporting RCM liability, which is a self-assessed tax obligation — the recipient must self-invoice and pay the tax, not wait for the vendor to charge it. The SOP includes a vendor-category-specific RCM identification checklist built from your actual purchase ledger, not a generic list of RCM categories that may not match your vendor mix.

The SOP documents a specific, repeatable matching protocol: which report is pulled from the GST portal, how it is compared line-by-line or in bulk against the ITC claimed in the books and in GSTR-3B, what constitutes an acceptable timing difference (for example, a vendor filing their GSTR-1 a period late) versus a genuine mismatch requiring investigation, who is responsible for chasing a vendor whose invoice does not appear in GSTR-2B, and how the eventual resolution — claim, reversal, or provisional carry-forward — is recorded and reviewed before the return is filed.

The core process logic — how ITC is reconciled, how RCM is identified, how a return is reviewed before filing — is usually consistent across GSTINs, but state-specific elements (officer jurisdiction, any state-specific administrative practice, the specific team responsible for that state's filing) need to be documented per GSTIN. PNPC builds a single master SOP framework with a per-GSTIN annexure capturing the state-specific details, rather than either a single generic document that ignores state differences or entirely separate, disconnected manuals per state that drift out of consistency with each other over time.

At minimum: the process owner (typically the finance controller or GST-in-charge) who understands the intended process design, and at least one hands-on operator (the person who actually raises invoices, books purchases, or files the return day to day) who can describe how the process is actually performed — which is not always identical to how management believes it is performed. For companies with an Audit Committee, that Committee is typically the body that formally reviews and signs off the finalised manual, giving it organisational standing.

For a single-entity, single-state business covering the core processes — invoicing/HSN classification, ITC/RCM identification, and return filing — a typical engagement runs 8–10 weeks from the initial scoping workshop to a signed-off, version-controlled manual, assuming reasonable availability of your process owners for walkthrough sessions. Multi-state or multi-GSTIN businesses, or those also documenting e-invoicing workflows and a departmental notice-response protocol in the same phase, typically run 10–14 weeks. Larger manual libraries spanning many product lines or entities are phased over successive quarters rather than attempted in a single sweep.

The manual itself is a version-controlled document with a defined review cadence — typically annual, or triggered immediately by a GST Council rate notification, a Finance Act amendment, an e-invoicing or QRMP threshold change, or a material ERP change. Beyond the document itself, PNPC clients typically retain us for ongoing GST return filing, notice response, or an annual retainer, in which case the SOP becomes the working reference we use in delivering those services — creating continuity rather than a document that sits unused after handover.

Yes, where applicable. E-invoicing under Rule 48(4) of the CGST Rules is mandatory once a registered person's aggregate turnover in any preceding financial year (from 2017-18 onwards) crosses the currently notified threshold — the threshold has been progressively lowered by successive notifications since e-invoicing's introduction, so PNPC confirms your current applicability against the latest notification rather than assuming a historical figure still applies. Where applicable, the SOP documents the IRP registration, the invoice upload and IRN/QR-code generation workflow, and the internal check that no manual invoice series bypasses the mandatory e-invoice process. E-way bill generation triggers (based on consignment value and distance) are documented separately as part of the logistics/dispatch-linked GST process.

A well-documented SOP becomes the primary evidentiary support for your response. It demonstrates that ITC was claimed following a defined reconciliation protocol against GSTR-2B rather than arbitrarily, that RCM liability was assessed against a documented vendor-category checklist, and that returns were reviewed and signed off under a defined process before filing — all of which materially strengthens your position when responding to an ASMT-10 scrutiny notice or a departmental audit query, compared to reconstructing 'what we normally do' from memory under a statutory response deadline.

There is no standalone statutory provision under the CGST Act that mandates a written GST SOP for every registered person. However, for companies, a documented GST process is one of the concrete internal financial controls that a statutory auditor and, where applicable, an internal auditor test as part of their assessment under the Companies Act 2013 framework for financial reporting controls — and the absence of any documented process is itself a control observation an auditor may raise. It is best understood as a strong best practice with real governance weight for companies under statutory or internal audit, rather than a standalone legal filing obligation.

Yes. A properly documented GST process directly supports GSTR-9 (the annual return reconciling outward supply totals, ITC claimed, and tax paid across the year against the monthly/quarterly GSTR-1 and GSTR-3B filings) and, for taxpayers above the notified turnover threshold requiring GSTR-9C (the reconciliation statement), by ensuring that the underlying monthly data was captured consistently throughout the year rather than needing reconstruction at year-end. PNPC's SOP includes a year-end reconciliation checklist specifically feeding into GSTR-9/9C preparation.

Yes, though the SOP will look different from a manual-process business. Even a well-configured ERP requires documented governance around it — who has authority to change the HSN/rate master in the system, what happens when the ERP's automated GST logic does not correctly classify an unusual transaction, who reviews the system-generated return before submission, and how exceptions flagged by the ERP are investigated and resolved. The SOP for an ERP-driven process focuses more on configuration governance, exception handling, and review controls than on manual step-by-step data entry instructions.

RACI stands for Responsible (who performs the task), Accountable (who is ultimately answerable for its correctness), Consulted (who provides input before it is finalised), and Informed (who needs to know the outcome). For a GST process like ITC reconciliation, a RACI matrix makes explicit, for example, that the accounts executive is Responsible for pulling the GSTR-2B report and performing the initial match, the finance controller is Accountable for approving any mismatch resolution, the department head may be Consulted on a disputed vendor invoice, and the CFO is Informed of the reconciliation status each period. Without this clarity, responsibility for a mismatch often falls through the gap between two people who each assumed the other was handling it.

Yes. Section 17(5) of the CGST Act specifically blocks ITC on certain categories regardless of whether the underlying purchase is otherwise eligible — motor vehicles (with limited exceptions for specified uses), food and beverages, outdoor catering, club memberships, health and life insurance (with limited exceptions), works contract services for construction of immovable property (with an exception for plant and machinery), and goods or services used for personal consumption, among other categories. The SOP includes a specific blocked-credit screening step within the ITC booking process so these categories are excluded at the point of booking rather than discovered and reversed later, along with interest, at the time of a reconciliation or audit.

Place-of-supply rules under the IGST Act determine whether a transaction is intra-state (attracting CGST + SGST) or inter-state/export (attracting IGST, or zero-rated for qualifying exports under a Letter of Undertaking). Incorrect place-of-supply determination is a recurring source of error — particularly for services, where the recipient's location, not the supplier's, often governs the applicable rule. The SOP documents the specific place-of-supply logic applicable to the business's actual transaction types (goods versus the specific categories of services it provides or receives), with worked examples drawn from the business's own transaction history rather than abstract textbook scenarios.

PNPC has operating offices in Chennai, Bangalore, Hyderabad, and Dubai, and for groups with both an Indian GST-registered entity and a UAE VAT-registered entity, we can align the India GST SOP with the UAE VAT compliance process where the two interact — for example, cross-border invoicing between the two entities, or a shared finance team handling both jurisdictions. The GST SOP itself remains an India-specific CGST Act document; the alignment work ensures your finance team is not working from two disconnected, inconsistent manuals for what is functionally one integrated operation.

A large consulting-firm GST SOP project is typically comprehensive and well-researched, but scoped and priced for large enterprise engagements, and often ends at a formal handover with limited ongoing availability for interpretation queries once the project team disengages. PNPC builds the same disciplined structure — RACI matrices, statutory grounding, version control — but scoped proportionately to your actual size and risk profile, and with continuity: the same CA relationship that built the manual typically continues into your periodic return filing, annual compliance retainer, or notice-response support, so the manual is used and maintained by the people who understand why each step exists.

PNPC scopes and quotes each engagement individually based on the number of GSTINs, transaction volume, product/HSN complexity, and how many of the four functional areas (registration/master data, transaction processing, periodic returns, year-end/audit-facing processes) are in scope. We do not publish a flat fee because a single-entity, single-state business with straightforward transactions costs meaningfully less to document than a multi-state group with RCM exposure and e-invoicing obligations. A written scope and fee proposal is provided after the initial scoping conversation, before any engagement begins.

Not every notification requires a full rewrite. Minor procedural clarifications or portal-interface changes are typically absorbed as a note in the SOP's version log without restructuring the document. A rewrite (or a targeted section revision) is warranted for changes with structural impact — a GST rate change affecting your product mix (such as the September 2025 rationalisation), a change in the e-invoicing or QRMP eligibility threshold that shifts your obligations, a new return form, or a material change to your own business (new state, new product line, new ERP). PNPC's annual review distinguishes between the two and scopes the update accordingly, rather than treating every change as requiring the same level of rework.

This is common, and the SOP should reflect it explicitly rather than force a single narrative across genuinely different operations. Factory or warehouse-level GST processes typically centre on e-way bill generation for goods dispatch, stock transfer documentation between GSTINs of the same entity, and inward goods receipt matching against purchase invoices for ITC. Head-office processes typically centre on return consolidation, ITC reconciliation, and RCM identification for services procured centrally. PNPC documents these as distinct process modules within the same overall manual, with clear handoff points between them (for example, how a stock transfer at the warehouse level feeds into the head office's consolidated return).

Yes, though the SOP is scoped differently. Where the team is genuinely too small for full segregation of duties (for example, the same person raises and approves an invoice), the SOP documents compensating controls instead — a periodic independent review by an external accountant or by PNPC, a defined escalation for transactions above a value threshold, or a monthly management review of a sample of transactions. The goal is not to force an unrealistic organisational structure onto a small team, but to document the actual control environment honestly, including its limitations, so anyone reviewing it (an auditor, a lender, a future investor) understands the compensating measures in place.

During the as-is walkthrough, PNPC reviews actual sample invoices, purchase records, and filed returns — not just a verbal description of the process — to ensure the documented SOP reflects what is genuinely happening in the books and filings, not an idealised version of it. Where a discrepancy is found between the described process and the actual filed returns (for example, a rate applied in practice that does not match the stated policy), this is raised explicitly during the drafting phase and resolved with management before the SOP is finalised — the manual is not permitted to simply describe an aspirational process that the actual filings contradict.

Rollout and training briefing sessions for the finance and billing teams who will use the manual are included as part of PNPC's standard SOP engagement — these are scoped as short, practical sessions covering how to use the manual, not formal classroom-style GST training. If your team also needs broader foundational GST training (for new joiners, or a team with limited prior GST exposure), that is available as a separate training engagement that PNPC can scope alongside or after the SOP project.

PNPC documents the gap and the recommendation in writing regardless of management's immediate decision — this creates a clear record that the risk was identified and flagged, which matters both for governance purposes and for the business's own future reference. The SOP itself will describe the current (imperfect) process honestly rather than describing an unimplemented ideal state, with the flagged recommendation noted separately as an open item for management's tracking. We do not withhold a flagged risk simply because it is inconvenient to act on immediately.

Where relevant to the business, yes — refund processes (export under Letter of Undertaking without payment of IGST, or inverted duty structure refunds where the input tax rate exceeds the output tax rate) are documented as a distinct process module, covering the specific forms (RFD-01 and supporting statements), the documentation required to substantiate the claim, and the internal review checkpoint before a refund application is filed. This module is scoped in only where the business's transaction profile actually generates refund claims — it is not included by default for businesses with no export or inverted-duty exposure.

Yes. Flagging a control gap and helping implement the fix are naturally sequential parts of the same relationship — whether that means PNPC advising on a system configuration change to enforce a maker-checker control, assisting with a fresh GST registration or amendment if a jurisdictional gap is found, or taking on the periodic return filing itself if the internal team's capacity is the underlying constraint. The SOP engagement and any follow-on implementation work are scoped and quoted separately, but PNPC's continuity as your CA firm means the same team that identified the gap can also help close it.

GST return filing services are the ongoing, periodic execution of GST compliance — preparing and filing GSTR-1, GSTR-3B, or the annual GSTR-9/9C for a specific period. A GST SOP and compliance manual is the underlying process documentation that governs how that execution (whether done by your internal team or by PNPC on retainer) is meant to happen consistently, with defined roles, reconciliation protocols, and escalation paths. Many clients engage PNPC for both — the manual sets the standard, and the ongoing filing retainer executes against it — but they are distinct services that can also be engaged independently.

It depends on how far along the transition is. If the new system's GST configuration (rate master, e-invoicing integration, approval workflow) is still being actively finalised, it is usually more efficient to wait a short period so the SOP documents the actual, stabilised system workflow rather than a configuration still in flux. If the system is live and being used for real transactions, even imperfectly, PNPC generally recommends starting the SOP engagement now — the as-is walkthrough itself often surfaces configuration issues worth fixing before they become entrenched habits, and the documentation can be finalised once the system settles rather than starting from zero afterward.

Yes, directly. For companies, GST-related processes are frequently one of the transaction cycles tested as part of Internal Financial Controls over Financial Reporting under Section 134(5)(e) and Section 143(3)(i) of the Companies Act 2013. A documented, control-aware GST SOP — with a RACI matrix, defined approval points, and a reconciliation protocol — gives the statutory auditor concrete evidence of control design, and the operating-effectiveness testing (sample transactions checked against the documented process) becomes materially easier to satisfy when the process was actually followed as written, rather than reconstructed after the fact for the auditor's benefit.

Yes. PNPC finalises SOPs in a clear, consistently formatted document — typically with a cover index, a numbered SOP for each process, embedded RACI tables and flowcharts, and a version-control log — and can adapt the visual house style, numbering convention, and branding to match your organisation's existing document templates where you have one, rather than imposing a PNPC-branded format on your internal library.