Transitioning under the GST regime — a workflow checklist covering registration, HSN mapping, e-way bills, and reconciliation for operational businesses.
It is the Monday morning before cutover at a 200-employee distribution business with branches across Maharashtra, Karnataka, Delhi, and Tamil Nadu. The finance head, Arvind, is walking the accountant through one screen — the vendor master. Three GSTINs out of 187 have trailing spaces. Two more carry incorrect state codes. One vendor's PAN doesn't match the GSTIN format at all. None of these would have surfaced before the previous quarter. All of them will block input tax credit claims the moment the first GSTR-2B reconciliation runs after cutover. The transition has not yet started, and the team is already discovering work that should have been signed off six weeks ago.
Transitioning under the GST regime is a workflow problem before it is a tax problem. The regulatory shift from VAT, CENVAT, or service tax to a single unified structure changes how invoices flow from sales order to GSTR-1, how purchase records reconcile against GSTR-2B, how inter-state movement is documented through e-way bills, and how input tax credit accumulates against eligible supplies. The cutover succeeds when each of these workflows holds end-to-end. It fails when any one of them is left to "we'll fix it after go-live." The rest of this guide is the checklist Arvind's team should have completed six weeks earlier — sequenced in the order operational businesses can actually execute.
The transition sequence — when and why this checklist applies
This compliance checklist applies to operational businesses moving onto GST, restructuring multi-state registrations, adding branches with new GSTINs, or shifting between regular dealer and composition scheme classifications. Each item below names a specific regulatory requirement and the operational handoff that supports it; the broader ERP subject area discussion treats GST configuration as the highest-leverage decision in any compliance-led rollout. Run through each item against a named owner before the cutover date — not after.
The transition runs through five linked workflows the team has to validate before the first post-cutover invoice is raised. Registration and threshold confirmation. Master data preparation across items, customers, and vendors. Tax engine configuration for place-of-supply, reverse charge, and rate slabs. Document workflow setup for invoices and e-way bills. Reconciliation and reporting cadence for GSTR-1, GSTR-3B, and GSTR-2B. The checklist below tracks each through to a signed checkpoint.
The compliance checklist for the transition
Confirm aggregate turnover against the registration threshold.
GST registration thresholds split by state category. Aggregate turnover at INR 10 lakh for special category states — Arunachal Pradesh, Assam, Manipur, Meghalaya, Mizoram, Nagaland, Sikkim, Tripura, Himachal Pradesh, Uttarakhand — and INR 20 lakh for the rest of the country. Aggregate turnover is computed across the entire country under the same PAN, not state-by-state. A clothing manufacturer with units in Maharashtra (₹20 lakh), Karnataka (₹20 lakh), Delhi (₹10 lakh), and Tamil Nadu (₹15 lakh) sums to ₹65 lakh for the threshold test. The finance head signs off this computation against last year's audited financials.
Identify every category that requires registration regardless of turnover.
Registration is mandatory irrespective of turnover for taxable persons making inter-state supply, casual and non-resident taxable persons, businesses liable to pay tax under reverse charge, agents supplying on behalf of a taxable person, input service distributors, sellers on e-commerce platforms, e-commerce operators, persons outside India supplying online information or database access services to unregistered Indian recipients, aggregators supplying services under their own brand, and TDS deductors. Map the business activities against these categories before the registration form is submitted. Miss this and the registration may be incomplete even when turnover-based logic suggests otherwise.
Register afresh — do not assume legacy carry-over.
Existing dealers registered under VAT, CENVAT, excise, or service tax must register afresh under GST. The earlier registration does not carry over automatically. Dealers under the central or state tax in the previous regime need PAN verified through the GST portal, alongside a mobile number and email ID validated through OTP. The provisional certificate of registration arrives as Form GST REG-25. Multiple registrations requested under a single PAN result in a single provisional registration; centralised registration is granted in the state of prior registration. The finance head signs off this provisional certificate before any post-cutover invoice goes out.
Complete the documentary submission within the three-month statutory window.
Form GST REG-24 must be submitted to the GST portal within three months of provisional registration, along with supporting documents. Form GST REG-6 covers additional information if the initial submission is unsatisfactory. A show-cause notice under Form GST REG-27 follows if the additional information still doesn't satisfy the authority, with an opportunity for a hearing. Failure to respond results in cancellation through Form GST REG-26. A registered dealer can also voluntarily cancel provisional registration during transition through Form GST REG-28. The accountant maintains the submission tracker weekly; the finance head reviews acknowledgments before the window closes.
Decide between regular dealer and composition scheme before tax masters are configured.
The composition scheme allows eligible dealers under defined turnover and category limits to file simpler quarterly returns at a lower effective rate, but without the ability to claim input tax credit on inward supplies. Regular dealers file monthly returns and can claim input tax credit. The decision changes invoice format, purchase register treatment, return cadence, and customer-facing pricing. The owner and finance head sign off scheme classification before any tax master is configured. A switch between schemes after cutover is operationally expensive — the cost shows up across customer pricing, vendor reconciliation, and the next two months of returns.
Map HSN codes against every active item master.
Each item in the inventory master needs an HSN code mapped against the correct GST rate slab — 0%, 5%, 12%, 18%, or 28% with any applicable cess. HSN code length depends on annual turnover: four digits below a defined threshold, six or eight digits above. The stores head signs off the HSN audit two weeks before cutover. The finance head reviews the rate-slab mapping for items where category interpretation could go either way. Wrong HSN flows directly into wrong GST computation on every invoice that item appears on — which then flows into wrong GSTR-1 entries and scrutiny notices three months later.
Validate place-of-supply rules in every customer master.
Each customer master needs the correct billing-to state and ship-to state recorded against the dispatch address. Place-of-supply determines whether the transaction attracts CGST plus SGST (intra-state) or IGST (inter-state). Branches dispatching to multiple states need the correct branch GSTIN mapped against the relevant ship-to. The sales head signs off the customer master audit before the first invoice. Errors here produce invoices that may need to be cancelled and re-issued through credit-note workflow — each creating GSTR-1 reversal entries the accountant has to reconcile next month.
Verify every vendor GSTIN against the GST portal.
Each vendor master needs a GSTIN validated through the GST portal — not just visually checked. Trailing spaces, incorrect state codes, invalid PAN-linked formats, or inactive GSTINs all produce GSTR-2B mismatches that block input tax credit claims. The purchase head signs off the vendor master; the finance head signs off the input tax credit configuration. Late catching of vendor GSTIN errors typically costs ₹2–4 lakh per quarter in deferred or denied input credit for a mid-size manufacturer. This is the single item in the checklist most operations under-test before cutover.
Configure reverse charge mechanism for applicable inward supplies.
Reverse charge applies on specific categories — services from unregistered suppliers, goods or services notified under reverse charge, and certain imports. The tax engine has to auto-trigger reverse charge entries at the moment of vendor invoice posting rather than relying on the accountant to remember each case. The finance head reviews the reverse charge configuration against the company's last six months of actual transactions before sign-off. Missed reverse charge entries surface during scrutiny and carry interest under Section 50 of the CGST Act on the underpaid tax.
Configure e-way bill generation inside the dispatch workflow.
Every inter-state movement of goods above the e-way bill threshold needs an e-way bill generated against the dispatch — with vehicle number, transporter ID, and the correct consignee state. The dispatch supervisor's pick-confirmation workflow has to trigger the e-way bill from the same screen, not a separate portal session. Errors here delay dispatches by hours, sometimes a full day. The dispatch supervisor and finance head jointly sign off the e-way bill configuration against a representative dispatch from each plant or depot before cutover.
Run a complete GST cycle in UAT against actual previous-quarter numbers.
The accountant runs the previous quarter's actual invoices, purchase entries, credit notes, reverse-charge transactions, advance receipts, e-way bills, and TDS adjustments through the configured system. The output — GSTR-1, GSTR-3B, and GSTR-2B reconciliation — has to match what was actually filed in the previous regime within a 0.5% tolerance. The finance head signs off the UAT result. If the tolerance fails, cutover is deferred. This single discipline removes more post-go-live compliance risk than any other practice in the transition.
Hold the cutover sign-off review and lock the first-month review cadence.
All eleven items above need to be cleared with documented evidence — sign-off pages, audit logs, UAT reports — before the cutover date is authorised. The accountant presents; the finance head reviews; the owner signs the cutover authorisation. The team also locks the first-month review cadence: GSTR-1 draft review by the 3rd, GSTR-2B reconciliation by the 12th, GSTR-3B filing by the 20th. Without this cadence, the first month after cutover produces gaps that compound into the next quarter. With it, the first three months typically run without statutory penalty exposure. Where deeper reporting matters for the CFO, BI for ERP reporting over the GST-clean transaction data starts to represent reality from the first quarter.
Facing similar operational challenges?
See how exactllyERP manages inventory management, financial operations, and operational reporting — built for operational businesses.
See how exactllyERP handles operational complexity →How exactllyERP handles this automatically
exactllyERP eliminates GST filing errors and input tax credit mismatches by holding each checklist item as a configured workflow rather than a manual control point. HSN-mapped item masters from Item 6 flow through to every invoice and GSTR-1 entry without re-entry. Place-of-supply logic from Item 7 determines CGST/SGST or IGST treatment at invoice posting. Vendor GSTIN validation from Item 8 runs against the GST portal at master-creation, which catches the input tax credit mismatches before they reach the quarterly reconciliation. Reverse charge from Item 9 auto-triggers on vendor invoice posting. E-way bill generation from Item 10 runs inside the dispatch workflow, with vehicle and transporter capture on the same screen the supervisor confirms the pick from.
The three items that most often produce post-cutover compliance pain — HSN mapping, vendor GSTIN validation, and e-way bill workflow integration — sit inside the standard transaction flow rather than as a localisation add-on the accountant has to stitch together. The GSTR-1, GSTR-3B, and GSTR-2B reconciliation pull from the same chain that produced the invoice, so the commercial record matches the warehouse record matches the GST return. exactllyERP also handles incorrect GSTR filing and HSN code mapping errors automatically through statutory rate-change updates that absorb GST council changes within weeks rather than months, which is how the kind of trailing-space vendor GSTIN that Arvind found on Monday stops being a Monday-morning discovery. See it live in a free demo against your own previous quarter's actual GSTR numbers.
