Weighbridge, Tonnage and GST e-Invoicing in a Steel ERP

In most steel plants the weighbridge sits in its own world. An operator notes the gross, tare and net on a slip, someone keys a rounded figure into a register, and hours later an invoice is typed from yet another number. By the time finance raises the GST e-invoice, three different weights may be in play — the slip, the register and the billed tonnage — and none of them quite match. Every mismatch is a leak: under-billed tonnage, disputed short weight, or a rejected e-way bill because the invoice weight and the transporter's weight differ.

A steel processing business cannot run on approximations when the base unit of trade is the tonne. The fix is not more discipline at the weighbridge — it is an ERP where the weighbridge reading is the single source of truth that flows, unedited, into inventory, dispatch and the GST e-invoice.

In Pixel ERP a weighment is a structured transaction, not a scribbled slip. Whether the reading is captured from an integrated weighbridge or entered at the cabin, the system records gross, tare and net weight against the vehicle, the material, the heat or coil, and the grade. That single weighment then drives whatever happens next — a goods receipt, an internal transfer, a process issue or a dispatch — so the same net weight carries through untouched.

What a Pixel ERP weighment records:

• Gross, tare and net — captured in kilograms and tonnes, with two-trip (loaded and empty) weighments handled automatically.
• Vehicle and transporter — number, driver and transporter tied to the weighment for the e-way bill.
• Material, heat, coil and grade — so weight is always attached to what was actually weighed.
• Direction — inward, outward or internal, linking the weighment to the right document.
• Tamper-evident trail — who weighed what and when, with an audit log for disputes.

Because the reading is captured once and reused everywhere, the argument over whose number is right simply disappears.

Tonnage in Pixel ERP is not re-typed at each stage; it flows. An inward weighment becomes a weight-based goods receipt that adds exact tonnage to stock by grade and heat. A process issue draws down tonnage and, on completion, adds finished coils, off-cuts and scrap back by weight — the raw material for true yield and weight-based costing. An outward weighment becomes a dispatch that reduces stock by the precise net weight loaded.

The result is that stock in tonnes actually ties to the yard, purchase liability matches received weight, and the sales invoice is built on the exact tonnage that left the gate. Finance, stores and logistics finally read from the same number instead of reconciling three.

This matters most on the buy side too. In a steel plant, scrap, billets and HR or CR coils are all bought by weight, and a two or three kilogram drift per truck across hundreds of loads a month is real money. When the goods receipt is the weighbridge net rather than a rounded register figure, you pay suppliers for exactly what arrived, catch short weights at the gate, and hold a purchase ledger that reconciles to the tonne against the yard.

This is where the weight discipline pays off at the counter. In Pixel ERP the tax invoice is generated from the outward weighment, so the taxable value is calculated on the actual dispatched tonnage at the agreed grade-wise rate. From that same document the system produces the GST e-invoice with its IRN and QR code and the e-way bill for the movement — all carrying the identical weight, value and vehicle details, because they are built from one source, not typed three times.

The compliance flow covers:

• GST e-invoice — IRN and QR generated from the dispatch, with correct HSN, rate and taxable value on actual weight.
• e-Way bill — raised from the same transaction with matching weight, value, vehicle and transporter, so it clears without contradiction.
• Grade-wise rates and rounding — pricing and weight rounding rules applied consistently to every line.
• Test certificate — generated alongside the invoice from the heat and coil data, matching the material shipped.
• Automatic accounting — sales, GST and receivables posted straight into Pixel ERP accounts from the same dispatch.

Because every document draws from one weighment, an e-way bill is never rejected for a weight that quietly disagrees with the invoice.

Here is the outward flow in the steel ERP, from empty truck to filed e-invoice:

• Tare — the empty vehicle is weighed in; tare is recorded against the trip.
• Load and allocate — coils or bundles of the ordered grade are loaded and allocated from stock by heat and grade.
• Gross and net — the loaded vehicle is weighed; the system computes net dispatched tonnage automatically.
• Invoice — the tax invoice is built on that net weight at the grade rate, with GST and rounding applied.
• e-Invoice and e-way bill — IRN, QR and e-way bill are generated from the same document with matching details.
• Certificate and posting — the test certificate is issued and the ledgers are posted, all from the one dispatch.

Every figure on the invoice traces straight back to the weighbridge reading, and every coil to its heat — the traceability described in our guide on managing heats, coils and grades.

Pixel ERP watches the weight data for the things that quietly cost money. It flags weighments where net looks wrong against the vehicle's usual tare, dispatches where billed weight and loaded weight drift apart, and invoices sitting un-generated against completed loadings. You can also just ask — "total tonnage dispatched today", "which invoices are pending e-way bill", "net received against this purchase order" — and get the figure instantly.

That turns the weighbridge from a blind spot into a monitored control point, and keeps the tonnage you bill matching the tonnage you actually ship.