GST is the single most common place that logistics software in India quietly fails. The tool handles GPS beautifully, dispatch is clean, the mobile app is great — then your accounts team spends 4 hours every day manually entering trip data into Tally to generate compliant invoices. That's not GST integration. That's a homework assignment.

Here's what GST-compliant logistics software actually needs to do natively in 2026, and how to evaluate whether a vendor really has it or is just claiming it.

The non-negotiables

1. GST-compliant invoicing

Every invoice generated from a trip must:

  • Follow GST invoice numbering rules (sequential, year-prefixed, by branch/series)
  • Show GSTIN, place of supply, HSN/SAC codes correctly
  • Calculate CGST + SGST or IGST based on intra/inter-state determination
  • Handle different rates for different services (transport at 5% without ITC, or 12% with ITC — the choice should be configurable)
  • Show reverse charge applicability where relevant
  • Generate as a PDF in standard GST invoice format

Most logistics software handles this for the simple case. Watch for vendors that fail on edge cases: mixed-state consignments, reverse charge to unregistered consignors, GTA service nuances.

2. IRN generation (e-invoicing)

For B2B invoices above the e-invoicing threshold (currently ₹5 crore aggregate turnover, but progressively lowering), every invoice must be registered with the Invoice Registration Portal (IRP) to get an Invoice Reference Number (IRN) and QR code.

What "real" e-invoicing integration looks like:

  • Direct API integration with IRP (via GSP or direct)
  • Automatic IRN generation when the invoice is created — no manual step
  • QR code embedded in the printed PDF
  • Failed IRN handling — retry queue, alert to ops, manual replay option
  • Cancellation workflow within 24 hours (regulatory window)
  • Reconciliation dashboard showing IRN status across all invoices

Vendors who say "you'll need to enter IRNs manually" or "we export a CSV for your e-invoicing provider" are giving you half a feature. The whole point is automation.

3. E-way bill integration

For movement of goods above the threshold (₹50,000 typical, but varies), an e-way bill must be generated. The logistics platform should:

  • Auto-generate e-way bill from trip data via API
  • Link the e-way bill number to the trip, the invoice, and the truck
  • Track validity period and alert before expiry — including delays that require extension
  • Handle changes — vehicle change, multi-vehicle journeys, transit through multiple states
  • Generate the printable e-way bill PDF on demand
  • Cancel and re-generate when trip changes happen

This is where consumer-grade fleet software typically fails. They give you a place to enter the e-way bill number manually after generating it externally. Useless.

4. Place of supply rules

For GTA services in India, place of supply rules can be subtle. Standard rule: place of supply is where the recipient is registered. But for unregistered recipients, it's the location where goods are delivered. For multiple-state consignments, it gets more nuanced.

Software that gets this right has the rules encoded in the invoicing engine, not in your accountant's head. Software that doesn't will silently generate incorrect CGST/SGST vs IGST splits — which can lead to credit denial during audits.

5. Reverse charge mechanism (RCM)

For transport services to unregistered persons, RCM may apply — the recipient pays GST instead of the transporter. The logistics platform should:

  • Identify RCM applicability based on consignor registration status
  • Generate invoices showing RCM applicability clearly
  • Track RCM events separately for reporting
  • Calculate transporter's tax liability correctly when RCM doesn't apply

6. TDS on transport contracts

For long-term transport contracts, TDS may apply on payments to the transporter. The logistics platform should:

  • Calculate TDS on invoices for contracts above the threshold
  • Generate TDS certificates
  • Track TDS deducted vs received for reconciliation

What good GST integration looks like in practice

Here's the workflow in a properly built logistics platform:

  1. Trip ends — driver marks POD via mobile app
  2. System generates draft invoice with all GST fields auto-populated (GSTIN, place of supply, CGST/SGST/IGST split, HSN, RCM flag)
  3. Operator reviews and confirms (or auto-confirms if rule-based)
  4. IRN generated automatically via API to IRP — typically within 5 seconds
  5. E-way bill (if applicable to onward journey) generated and linked
  6. Invoice PDF generated with QR code, IRN, e-way bill reference
  7. WhatsApp / email sent to customer
  8. Entry pushed to accounting system (Tally / Zoho) automatically
  9. Dashboard tracking shows invoice status, IRN status, payment status

Total operator time per invoice: under 30 seconds. Without good GST automation, the same workflow takes 5–10 minutes per invoice — and at scale, that's a full-time job worth of accounts overhead.

How to evaluate vendors on GST

Questions to ask on every demo:

  1. "Show me generating an invoice from a trip — the full flow, end to end."
  2. "What happens when IRN generation fails because the IRP is down?"
  3. "Walk me through handling a multi-state consignment with mixed RCM applicability."
  4. "How do you push invoices into Tally / our accounting tool?"
  5. "How do you handle a GST rate change announced by the council mid-month?"
  6. "Show me your reconciliation dashboard for IRN status."
  7. "Can I cancel and regenerate an invoice within the IRP window?"

If the vendor stumbles on more than two, the GST module is probably surface-level. Look elsewhere.

Common failure modes — and the cost

  • Wrong place of supply: CGST/SGST charged when IGST should apply. Customer's input credit denied. You're called in for the refund.
  • Missed IRN: invoice issued but not registered with IRP. Customer can't claim input credit. Audit risk.
  • Expired e-way bill: truck stopped at checkpost, ₹10,000+ penalty.
  • RCM miscategorisation: wrong party charged GST. Reconciliation nightmare in next month's GSTR filing.
  • Failed Tally sync: invoices generated in logistics tool but not in accounts — books don't tie out at month-end.

Each of these has a real rupee cost. Tools that get GST wrong don't just inconvenience your accounts team — they create regulatory liability.

Where Traxium fits

We built Traxium with native GST handling exactly as described above. Native IRN, e-way bill, RCM, place-of-supply logic, Tally / Zoho export. Because we run our own platform, we feel the pain of bad GST integration directly — which is why we made sure ours wasn't bad.

If your current logistics software is failing on any of the GST requirements in this article, it's worth a 30-minute conversation about how Traxium (or a custom alternative) would handle them differently. WhatsApp us.