Typing e-way bills on the portal or raising them from the invoice

The clerk opens the portal. Each consignment is keyed by hand: buyer’s GSTIN, invoice number and date, HSN codes, taxable values, pincodes, distance in kilometres and the transporter’s ID. Twenty fields, every time. Nobody enjoys it.

It works when volume is low. A cement dealer with three trucks a week copes. Barely. The trouble starts at six in the evening, with twenty invoices stacked on the desk and three drivers shouting at the gate.

Each keyed field invites a slip. One wrong digit in a GSTIN, a tile quantity typed as 140 instead of 410, or a stale HSN code gives a bill that contradicts its own invoice. The mismatch surfaces at a checkpoint, not at your desk, and by then the truck is standing in a queue with a customer waiting at the other end.

The invoice record already holds everything the portal asks for: the party, the lines, the values and the tax split by CGST, SGST or IGST. The software sends those fields to the portal through the e-way bill API as a JSON file, then writes the 12-digit bill number back onto the invoice.

Nobody retypes anything. Bill and invoice agree. Both come from the same row. Fix a rate before dispatch. The bill follows.

The printout shows the bill number beside the invoice. The driver carries one set of papers: invoice, bill and lorry receipt.

Part A holds the consignment. Part B holds the vehicle. Trucks get assigned at the last minute, so the registration number is the field most often missing, or typed with a stray space.

The software can hold the gate pass. Once the registration number is entered, it pushes Part B. If the truck breaks down at a toll plaza, moving the load to another lorry is a Part B update from the same screen, with a reason code.

Extensions work the same way. It watches validity. A delayed load triggers a warning to the dispatcher well before the bill lapses. Cancellation, inside its short window, is one button.

An officer wants the invoice, the e-way bill and the lorry receipt. The driver rings the office. Who answers?

With portal entry, the answer lives in one clerk’s browser tab. Or a diary. With a linked record, anyone in dispatch searches the invoice number and reads out the bill number, the validity date and the vehicle on Part B.

The system can push the bill as a PDF to the driver’s WhatsApp. Every update is logged.

Count consignments per week and how often the vehicle changes. If both are low and one person does it all, the portal will do. Keep a tick sheet beside the keyboard.

Once several people dispatch, or invoices pass a few dozen a day, mismatch risk grows faster than the cost of integration. Raise the bill from the invoice.

Run a trial week with a second person checking. Compare each bill against its invoice and list every difference. That count settles the question.