Skip to content

GST Configuration

Applies to: e-Invoice · e-Way Bill · Which modules do I have?

Purpose

Configure the compliance layer — registrations, provider, routing, flags and printing — so that stages 6 and 7 are exercising modules rather than discovering configuration.

Audience

The implementation consultant, with the customer's tax lead.

Prerequisites

  • Role Assignment gate passed
  • The complete list of registrations, including dormant ones
  • Sandbox provider credentials issued and tested
  • The tax lead available for the routing and statutory decisions

Steps

1. Onboard every registration

Onboard each GSTIN in scope, with its legal name, address and state code exactly as registered.

Include dormant registrations. A dormant registration that later issues a single document, and was never onboarded, produces an out-of-scope rejection that is genuinely hard to diagnose — nobody thinks to check whether the registration exists.

2. Assign and test the provider

Assign the provider and run the connection test. See GSP Configuration.

Sandbox credentials only at this stage. Production credentials are applied at stage 10.

Then review the capability matrix against what the business actually needs. Do this now, not during testing: discovering that a required operation is unavailable at stage 9 is a schedule problem, and discovering it after go-live is an incident.

3. Confirm document type routing

Review every document type the customer issues against the routing table:

Question Owner
Is every type in use covered? Consultant
Does the default route match the business? Tax lead
Is any override genuinely required? Tax lead

An override commits you to more than it appears: a type routed to registration must carry every field registration requires, and its numbers become permanently consumed. See Document Type Routing.

4. Set feature flags per registration

Flag Decision
e-Invoice, e-Way Bill On, where in scope
Reconciliation On
Segregation of duties Per the stage 4 decision
Automatic registration Off for now. Revisit after validation quality is proven
Invoice Generation Only if licensed and in scope
Write-back Off until stage 8

Automatic registration stays off through implementation. Enabling it before validation quality is demonstrated converts a manageable review queue into a stream of rejections, each of which consumed a billed call.

5. Configure printing

Templates, branding and statutory declarations. Then print a document and scan the QR from paper — a code that scans on screen may not scan when printed. See Print Configuration.

6. Configure notifications

Notification Recipient
e-Way Bill expiry Logistics distribution list
Job failures Operations distribution list
Write-back failures Integration owner distribution list
Compliance alerts Tax distribution list

Distribution lists, never individuals. Set the e-Way Bill expiry horizon from the customer's actual dispatch lead times, not from a default.

7. Confirm the statutory parameters

With the tax lead, in writing:

Parameter Why
The applicable reporting window Enforced at ingest; a backlog outside it will quarantine
e-Way Bill thresholds and intra-state rules Vary by state
Exemptions and special cases Exports, special economic zones, reverse charge
How historical documents will be handled Decide before loading a backlog

Validation

Gate: this stage is complete when all of these pass.

Check Pass condition
Every registration onboarded Including dormant ones; names match registrations exactly
Provider assigned and tested Connection test passes, against sandbox
Capabilities reviewed Everything needed is supported, or has a tracked workaround
Routing confirmed Every type in use covered; overrides endorsed by the tax lead
Flags set per registration Every registration checked, not just one
Automatic registration off Deliberately
Print verified from paper QR scans from a printed copy
Notifications configured To distribution lists, with realistic horizons
Statutory parameters confirmed In writing from the tax lead

Rollback

Situation Action
A flag set on the wrong registration Unset it; effective within about a minute
Wrong routing configured Correct it. Documents already routed are not re-routed
Wrong provider assigned Reassign. Documents already issued stay with their original provider
A registration onboarded in error Disable rather than delete, if anything has been done under it
Print configuration wrong Correct and reprint. Nothing is lost

Everything here is reversible while no document has been processed. Once documents exist, routing and provider decisions attach to them.

Common mistakes

Mistake Consequence Avoid by
Omitting dormant registrations Unexplained out-of-scope rejections later List every registration
Legal names not matching registrations Rejections that look like mapping faults Match character for character
Production credentials at this stage A test document permanently registered Sandbox until stage 10
Enabling automatic registration early Rejections at volume, each billed Leave it off until quality is proven
Setting flags on one registration only Inconsistent behaviour nobody can explain Check every registration
Verifying print on screen A QR that fails on paper, found by an inspector Print and scan
Alerts to individuals Alerts nobody receives after they leave Distribution lists
Default expiry horizons Alerts arriving after the decision point Set from real lead times
Not confirming the reporting window A quarantined backlog nobody expected Confirm in writing

Troubleshooting

Symptom Cause Action
Provider connection test fails Credentials, network, or an untrusted proxy certificate See GSP Configuration
A flag change appears not to apply Brief cache, or wrong registration Wait a minute; confirm the registration
A document routes unexpectedly The mapped type is not what you expect Routing reads the mapped value
An operation is unavailable Provider capability Check the matrix; not a fault
The QR does not scan from paper Too small, cropped, or insufficient quiet space Adjust the template and retest on paper
Historical documents quarantined Outside the reporting window Expected. Agree the approach with the tax lead