E-Way Bill Accuracy in Bill-To / Ship-To Transactions

Goods and Services Tax treats the invoice and the movement of goods as two linked records. The tax invoice carries the billing GSTIN. The e-way bill carries the place of dispatch, the place of delivery, and, in a Bill-To / Ship-To supply, the GSTIN of the person to whom the goods are actually delivered. When those two documents disagree, the portal, the transporter, and later GSTR-1 all show a different story from the books.

A Bill-To / Ship-To supply is common in trading and in job-work or depot deliveries. Party A bills Party B, but the goods move from the supplier's godown to Party C's location. The e-way bill must carry Party C's GSTIN as the Ship-To party where the portal requires it, together with the correct PIN code and address of delivery. If the billing GSTIN is copied into the Ship-To field, the bill is generated, the vehicle moves, and the mismatch sits on the portal until a notice or an annual-return working brings it up.

What usually goes wrong

Masters in the billing software often store one GSTIN per customer. When the same customer has more than one place of business, or when goods are delivered to a principal's customer, the operator uses the first GSTIN on the master. Part-A of the e-way bill then carries the wrong destination. Part-B may still show a valid vehicle number, so the consignment travels. The invoice in GSTR-1 continues to show the Bill-To GSTIN. Three systems now hold three slightly different facts about one movement.

A second class of error is the unused or cancelled movement. An e-way bill is generated in anticipation of dispatch, the load is held back, and the bill is neither cancelled within the permitted window nor closed through the closure facility for bills that were never used. Those open bills remain on the portal and are later compared with invoices and with GSTR-1. The comparison does not fail because of tax evasion. It fails because the portal still thinks goods moved.

How to keep the three records aligned

Before an e-way bill is generated, the invoice should already state the Bill-To name and GSTIN and the Ship-To name, GSTIN, and address. The e-way bill should be typed from that invoice, not from memory of the customer master. Where the software generates both documents, the Ship-To GSTIN field must be a required field for this supply type, not an optional copy of the billing GSTIN.

After dispatch, Part-B and the actual delivery address should be checked once. After the period close, a simple three-way list helps: invoice number, IRN if e-invoicing applies, and e-way bill number, with Bill-To GSTIN and Ship-To GSTIN in separate columns. Rows where Ship-To is blank, where it equals Bill-To even though delivery was elsewhere, or where an e-way bill exists without an invoice (or the reverse), are the rows to correct in the next GSTR-1 amendment cycle, as the rules allow.

Unused bills should be cancelled within the time the portal allows, or closed through the e-way bill closure facility so that they do not remain as open movements. A weekly exception list of bills generated but not assigned to a vehicle, and of bills assigned but not matched to a signed delivery record, keeps that cleanup inside the month instead of inside the annual return.

Why this matters beyond the portal

Departmental comparisons now routinely place e-way bill value next to GSTR-1 and next to income-tax turnover. A pattern of Ship-To mismatches or of open unused bills does not, by itself, prove under-reporting. It does create a list of invoices that have to be explained one by one. Explaining them from a monthly workbook is a documentation task. Explaining them from memory at the time of scrutiny is a reconstruction task.

The same workbook supports the tax audit and the GST annual return, because both ask, in different words, whether outward supply as per books agrees with what was reported and with what moved. Accuracy at the transaction — GSTIN, PIN, vehicle, cancellation — is what makes those later statements short.