GST e-invoicing and e-way bills in Swynix ERP: what actually needs configuring

A general accounting module gives you strong bookkeeping, but Indian GST compliance, e-invoicing, e-way bills, GSTR filing formats, needs its own dedicated configuration layer. Treating GST compliance as an afterthought, or assuming a base ERP handles it out of the box, is the single most common setup mistake we see in India-based ERP rollouts.

What a proper compliance module actually adds

• GSTIN validation and HSN/SAC code management on items and parties
• E-invoice generation and IRN (Invoice Reference Number) fetching via the government's IRP
• E-way bill generation directly from sales invoices and delivery notes, above the mandated value threshold
• GSTR-1 and GSTR-3B report formats aligned to actual filing requirements
• TDS and TCS handling for the sections that apply to most trading and manufacturing businesses

Version parity is not optional

A compliance module needs to track closely with the core platform release it runs against, and running mismatched versions is the fastest way to hit migration failures or silently broken e-invoice generation. Before any upgrade, check that the compliance release you're pulling actually targets your platform version, not just the closest available option.

The e-invoicing threshold trap

E-invoicing is mandatory above a turnover threshold that has changed more than once, and it's easy to configure a company for e-invoicing generically without setting the actual threshold-based enforcement correctly, leading to either invoices missing a required IRN, or unnecessary IRN generation for exempt transactions. This should be verified against current CBIC notifications at setup time, not assumed from a template.

E-way bills need real logistics data, not placeholders

• Transporter ID and vehicle number need to be genuinely captured at dispatch, not left as optional fields nobody fills
• Distance calculation for the e-way bill should reflect actual transit distance, incorrect distance is a common cause of e-way bill validity disputes
• Part-A and Part-B of the e-way bill need clear ownership in your process: who generates Part-A at invoicing, who updates Part-B once the vehicle is confirmed

What breaks in practice

The most common production issue we've had to patch isn't the GST logic itself, it's migration-time crashes in edge cases like a system template record reference during a version bump. These are usually already fixed in a newer compliance patch release; the discipline is checking release notes before every upgrade rather than after something breaks.