Compliance Guide 14 min read

GST, e-way bills and warehouse management in India

How a WMS turns dispatch into GST-compliant invoices and e-way bill data — thresholds, validity, stock transfers, and the clean hand-off to Tally.

14 min read Updated July 2026 Pillar guide
Dispatch to compliance — the chain
01
Pick & confirm
Pallet quantity deducted at scan
FIFO/FEFO
02
Dispatch / gate-out
Bin balance deducted, challan made
Stock leaves
03
Tax invoice
CGST/SGST/IGST applied
No stock change
04
E-way bill data
Invoice, HSN, value, transporter
Portal feed
05
Tally sync
Sales voucher, GST ready
Automatic

Why GST and e-way bills are a warehouse problem, not just an accounts problem

In most Indian businesses, GST is treated as something the accounts team handles at month-end. But GST and the e-way bill are triggered by a physical event — goods leaving the warehouse — and the details they depend on (which items, which HSN codes, what taxable value, which vehicle, from which place to which place) are created on the warehouse floor. When the floor and the books are disconnected, you get the familiar problems: e-way bills generated for the wrong quantity, invoices that do not match the challan, stock that shows in Tally but is not physically there, and vehicles held at check-posts because the paperwork does not line up with the load.

A warehouse management system closes that gap. Fast WMS treats dispatch, tax invoicing and e-way bill data as one connected chain that starts at the barcode scan and ends at a Tally voucher — so the compliance document is built from the real movement, not re-keyed from memory hours later.

The core idea
The e-way bill describes goods that are physically moving. If your system knows exactly what left the bin, on which vehicle, at what value, the e-way bill writes itself. If it doesn't, someone is guessing.
A WMS makes the dispatch the single source of truth — the invoice and the e-way bill both draw from it.

Where GST touches the warehouse workflow

GST is not a single step at the end. It threads through the whole inbound-to-outbound flow. Fast WMS holds tax configuration per company and per document type, and applies the correct treatment automatically at each point where tax is relevant.

01
Inbound GRN
Purchase tax (input GST) captured against the PO and supplier
02
Item & party master
HSN, tax rate per item, place of supply per party
03
Dispatch
Delivery challan created as goods physically leave
04
Tax invoice
CGST/SGST or IGST split, amount in words, HSN summary
05
E-way bill
Data feed for the portal above the Rs 50,000 threshold
06
Return filing
Tally holds vouchers ready for GSTR-1 / GSTR-3B

The important design point is that the tax is derived from masters — the item's HSN and rate, the party's state and GSTIN — not typed by the person raising the invoice. That is how you get a consistent CGST/SGST versus IGST decision every time, and an accurate HSN-wise tax summary at the foot of every invoice.

The e-way bill: thresholds, Part A / Part B, and validity

An e-way bill (EWB) is an electronic document generated on the GST e-way bill portal before goods worth more than a threshold are moved. Knowing exactly when it is required, and how long it lasts, is what keeps a consignment from being detained.

When is it required?

  • Consignment value above Rs 50,000 (including GST) — for a supply, a stock or branch transfer, an inward supply from an unregistered person, or a return.
  • For inter-state movement above the threshold, and for intra-state movement where the state has adopted the same limit (some states set their own).
  • Even without a sale — job-work, line sales, exhibition, SKD/CKD, and own-warehouse transfers all count as movement of goods.

Part A and Part B

An e-way bill has two parts. Part A carries the consignment details — GSTINs of supplier and recipient, place of dispatch and delivery, invoice or challan number and date, HSN code, item value and the tax amounts. Part B carries the transport details — the vehicle number (or transporter document number). The bill is only valid for movement once Part B is filled, and validity is counted from that moment.

Part A is what the warehouse already knows the instant a dispatch is confirmed. That is precisely the data a WMS captures — so filling the portal becomes a copy, not a re-entry.

Validity

Validity is distance-based, counted from the time Part B is generated: broadly one day for every 200 km of approximate distance for regular cargo, with a longer factor for over-dimensional cargo. If a truck breaks down or a journey runs long, the transporter can extend validity before it expires. Because a WMS stamps the exact gate-out time and the true consignment details, the validity window is calculated from an accurate starting point rather than a rough guess.

How a WMS handles dispatch, invoicing and e-way bills

Here is the sequence Fast WMS runs when an order ships, and where each compliance artefact is produced.

1
Pick and scan-confirm. Eligible pallets are allocated by FIFO or FEFO, and pallet quantity is deducted at the scan. This is the first inventory commit — the goods are earmarked and removed from available lot stock.
2
Dispatch / gate-out. A delivery challan and the delivery movement are created. The bin balance is decremented and an immutable ledger row is written. The goods have now physically left — this is the second inventory commit.
3
Tax invoice. The invoice is raised from the un-invoiced dispatch balance, applying the correct CGST/SGST or IGST from the item and party masters, with amount-in-words and an HSN summary. It is a financial document only — it moves no stock.
4
E-way bill data. The dispatch and invoice together carry every field the e-way bill portal needs for Part A — GSTINs, invoice number and date, HSN, taxable value, tax split and transporter details — ready to push or hand to the portal.
5
Tally posting. The dispatch posts a sales voucher; the GRN earlier posted a purchase receipt. GST returns are then built from vouchers that already match the physical movement, with no double entry.

Want to see dispatch → invoice → e-way bill → Tally in one flow?

We can run a live 30-minute walkthrough on your own item masters, HSN codes and GST rates — and show exactly where each compliance document comes from.

See Fast WMS live

Why invoicing never touches your stock

One principle in Fast WMS matters more than any other for GST accuracy: invoicing is financial only, and never changes stock. Physical stock leaves in two legs — pallet quantity at pick-confirm, and the bin balance at dispatch or gate-out. The tax invoice is raised afterwards from the un-invoiced dispatch balance.

This separation is not a technicality. It is what keeps physical stock and book stock reconciled. If invoicing moved stock, then a cancelled or amended invoice would silently change your on-hand quantity, and a part-invoiced dispatch would leave stock in limbo. By keeping the goods movement (challan) and the money movement (invoice) as distinct events, both the e-way bill (which follows the goods) and the GST return (which follows the invoice) rest on clean, independent records.

EventMoves stock?Compliance artefact
Pick confirmYes — pallet qtyInternal allocation
Dispatch / gate-outYes — bin balanceDelivery challan + e-way bill (Part A data)
Tax invoiceNoGST tax invoice → Tally sales voucher
Sales returnYes — stock re-addedAuto credit note

Stock transfers and branch movements

A common trap is assuming an e-way bill is only for sales. It is not. Any movement of goods above the threshold needs one — including moving your own stock between two locations that have different GSTINs, such as shifting finished goods from a factory store to a regional distribution warehouse in another state.

Fast WMS records such a movement as a store transfer, producing the delivery challan and the stock-journal data that both the e-way bill and Tally require. Because the transfer is a first-class document in the system — not an invoice pretending to be a transfer — the value used for the e-way bill and the accounting treatment (a stock journal, not a sale) are both correct. For businesses running multiple warehouses or plants, this keeps inter-branch movement fully traceable and audit-ready.

Representative flow — multi-state distributor

Factory store in Pune to distribution hub in another state

Finished goods are picked and gated out of the Pune store on a delivery challan. Because the receiving hub is a different GSTIN and the consignment crosses Rs 50,000, an e-way bill is generated from the challan's Part A data. Fast WMS posts a stock journal in Tally at both ends — no sale, no GST liability created wrongly — and the goods stay traceable pallet-by-pallet from gate-out to gate-in.

1
challan drives both e-way bill and stock journal
2
GSTINs reconciled — sender and receiver
0
wrongly-raised sales / GST liability

The Tally hand-off

Fast WMS integrates with Tally ERP 9 and TallyPrime through a store-to-godown mapping. The rule is simple: every warehouse transaction posts the matching accounting voucher automatically, so the accounts team never re-keys a movement.

Warehouse event to Tally voucher
1
GRN confirmed → Purchase receipt voucher
Input GST captured, supplier ledger and godown correct from the master — ready for GSTR-2B reconciliation.
2
Dispatch → Sales voucher
Customer, items, HSN, GST split and challan reference posted together — the basis of GSTR-1.
3
Stock transfer → Stock journal
Inter-godown or inter-branch movement recorded without creating a sale or a tax liability.
4
Sales return → Credit note
Stock re-added in the warehouse, an auto credit note raised for the accounts — both in step.

Deeper detail on the mechanism is in our WMS and Tally integration guide, and the dispatch document itself is covered under Dispatch & Invoicing.

Common compliance mistakes a WMS prevents

Challan and invoice don't match

When goods move on one document and are billed on another, quantities drift. A WMS builds both from the same confirmed dispatch, so the e-way bill matches the invoice exactly.

Prevented at dispatch

Expired e-way bill at the check-post

Validity is missed when the start time is fuzzy. A scan-stamped gate-out gives an accurate clock, so validity is planned from a real dispatch time.

Accurate gate-out time

Transfers billed as sales

Branch movements wrongly invoiced create phantom GST liability. A WMS records the transfer as a stock journal, not a sale.

Correct document type
Keep learning about warehouse management in India
Part of the Fast WMS learn hub — practical guides written for Indian manufacturers, distributors, 3PLs and cold-storage operators.

Frequently asked questions

When is an e-way bill required for warehouse dispatch in India?

An e-way bill is required whenever goods worth more than Rs 50,000 (single consignment value, including GST) move — whether for a sale, a branch or stock transfer, a job-work movement, or a sales return. It is needed for inter-state movement and, above the state threshold, for intra-state movement. Fast WMS captures the dispatch and invoice details the portal needs — invoice number, HSN, taxable value, GST split and transporter details — at the moment goods leave the warehouse.

Does creating a GST invoice reduce warehouse stock?

No. In Fast WMS invoicing is a financial event only — it never changes stock. Physical stock leaves in two legs: pallet quantity at pick-confirm, and the bin balance at dispatch or gate-out. The tax invoice is raised from the un-invoiced dispatch balance afterwards. Separating the goods movement from the invoice keeps physical stock and book stock reconciled, and keeps the e-way bill tied to the actual dispatch.

How long is an e-way bill valid?

E-way bill validity is distance-based: roughly one day for every 200 km of approximate distance for regular cargo (and one day per 20 km for over-dimensional cargo), counted from the time Part B (vehicle details) is generated. If the vehicle cannot complete the journey in time, the transporter can extend validity before it expires. A WMS helps by stamping the exact dispatch time and consignment details, so validity is calculated from an accurate start point.

Do I need an e-way bill for stock transfer between my own warehouses?

Yes, if the consignment value crosses the threshold. A branch or stock transfer between two GSTINs — for example moving finished goods from a factory store to a distribution warehouse in another state — is a movement of goods that requires an e-way bill even though there is no sale. Fast WMS records the transfer as a store movement and produces the delivery challan and stock-journal data the e-way bill and Tally both need.

How does Fast WMS hand GST data over to Tally?

Fast WMS holds tax configuration per company and document type and applies the correct CGST/SGST/IGST split on every dispatch invoice. When a GRN is confirmed it posts a purchase receipt voucher to Tally; when goods are dispatched it posts a sales voucher with the customer, items, GST and challan reference; a stock transfer posts a stock journal. The accounts team never re-keys a warehouse transaction, so GSTR returns are built on data that already matches the physical movement.

Make GST and e-way bills a by-product of dispatch

A 30-minute Fast WMS demo shows the full chain — pick, dispatch, GST invoice, e-way bill data and Tally sync — live on your own items and tax rates.

Get a free demo
No commitment. No slides. Your warehouse on screen.