Why manufacturer billing is different
A retailer bills at the moment of sale. A manufacturer does not — the sale was agreed weeks ago on an order, the goods leave the factory on a delivery challan today, and the tax invoice may be raised the same evening or at the end of the week. That gap between dispatch and invoice is where manufacturer billing goes wrong: material ships and is never billed, the same dispatch gets billed twice from two registers, or a part-supplied order loses track of what remains to be invoiced. If you are new to the documents themselves, start with the pillar guide what is GST billing software — this page assumes those basics and focuses on the factory.
The discipline that fixes it is simple to state: every tax invoice is raised against a specific dispatch or order, and a quantity that has been invoiced once is locked so it can never be invoiced again. Invoicing becomes a financial event layered on a physical event that already happened — the invoice attaches value and GST to goods that left the gate, rather than being a free-floating document someone types from memory.
The dispatch-to-invoice flow, stage by stage
A clean manufacturing billing run moves through six stages, and each stage produces a document that references the one before it.
1. Order acceptance. A confirmed customer order — with items, quantities, rates and delivery terms — is the commercial source of everything that follows. Part supplies are normal in manufacturing, so one order will typically be served by several dispatches and several invoices over weeks.
2. Dispatch on a delivery challan. Finished goods leave the factory on a delivery challan or packing slip that carries item, quantity, vehicle and transporter details — the data an e-way bill needs. The challan moves goods; it charges no tax and creates no receivable.
3. Tax invoice against the dispatch. The GST tax invoice is raised by picking the dispatch (or order), which pulls the lines in automatically — item, HSN, quantity, rate. CGST/SGST or IGST is computed from the buyer's state and your item and party tax settings, freight and packing charges are added, the total is rounded and spelled out in words. Exporters raise the export variant with zero-rated or LUT treatment.
4. Reconcile. Order-vs-invoice reconciliation shows what has been billed against each order and what is still pending — covered in the next section.
5. Collect. Receipts are booked against invoices, advances adjusted, and overdue parties chased — see payments, receipts and follow-up.
6. Post to accounts. The confirmed invoice posts to Tally as a sales voucher with GST; receipts and notes follow as their matching vouchers.
Pending-to-bill: order vs invoice reconciliation
The report a factory owner should look at every week is not the sales register — it is the order-vs-invoice reconciliation. For every open order it answers three questions: how much was ordered, how much has been invoiced, and how much remains. The same logic at dispatch level catches shipped-but-unbilled material, which is the most common silent leak in manufacturing.
| Failure mode | What it looks like | What prevents it |
|---|---|---|
| Shipped, never billed | Challan exists, no invoice references it; revenue silently lost | Pending-to-bill report — every dispatched quantity not yet invoiced, per party |
| Billed twice | Two invoices raised for the same dispatch from separate registers | Double-bill guard — invoiced quantity is locked against its dispatch line |
| Part supply lost | Order 60% supplied; nobody knows what remains to invoice | Order vs invoice report — ordered vs billed vs balance, per order line |
| Cancelled invoice re-billed wrong | Voided invoice leaves quantity stuck, or double-released | Controlled cancel — cancelling releases exactly the billed quantity for re-billing |
Notice that every row depends on the invoice being linked to its dispatch. A standalone invoicing tool — however pretty its templates — cannot produce a pending-to-bill report, because it has no idea what was dispatched. That link is the heart of what the manufacturing billing profile of Fast Billing Software does, with the UsedItemQty guard tracking, per dispatch line, exactly how much has already been invoiced.
HSN, e-invoice and e-way bill for manufacturers
Manufacturers carry a heavier GST compliance load than most businesses, because their invoices are almost all B2B and their consignments move on trucks.
HSN codes on every line
Every manufactured item needs the right HSN code and GST rate on the invoice. If your aggregate turnover exceeds ₹5 crore you must show 6-digit HSN codes on B2B invoices; smaller firms show 4-digit codes. Mapping item → HSN → rate once in the item master — with bulk import for large catalogues — is what keeps a 40-line invoice correct without anyone looking codes up by hand.
E-invoicing above ₹5 crore
If aggregate turnover in any year from 2017-18 onward crossed ₹5 crore, B2B invoices must be registered on the government Invoice Registration Portal (IRP), which returns an IRN and a signed QR code that must appear on the printed invoice. In practice that means your billing system must produce the invoice data in the prescribed structure the moment the invoice is confirmed — thresholds have only moved downward over the years, so confirm the current one with your CA. See GST, e-Way Bill & e-Invoice.
E-way bills on dispatches
Consignments worth more than ₹50,000 generally need an e-way bill before the vehicle moves (some states set different intra-state limits). The data — items, HSN, values, GSTINs, vehicle and transporter — is exactly what a linked challan-plus-invoice already holds, so a connected system fills the e-way bill from documents instead of re-typing.
See manufacturer billing running against real dispatches
The manufacturing billing page shows the full profile — invoice against dispatch, pending-to-bill, HSN and GST automation, Tally posting — or get a live demo on your own items.
Rejections, returns and rate corrections
Factories live with quality rejections and rate revisions, and GST handles both through formal notes tied to the original invoice — never by editing the invoice.
- Customer rejects a lot. The returned goods come back, and a credit note — auto-raised against the dispatch — reverses the invoiced value and GST, keeping the customer ledger and your GSTR-1 in step.
- Rate revised upward after supply. A price amendment agreed after dispatch (a steel escalation clause, say) is billed through a debit note referencing the original invoices — a routine event on long-running supply schedules.
- Invoice raised wrong. Cancelling the invoice releases the dispatched quantity it had consumed, so the same dispatch can be re-billed correctly — no orphaned quantities, no double count.
If your factory also sends material out for outside processing — heat treatment, plating, machining — that movement is not a sale and follows completely different rules; see the companion guide on job-work billing under GST.
Receivables — advances, retention and follow-up
Manufacturer receivables are lumpy: 30–60 day credit terms, advances taken against large orders, and sometimes retention held until commissioning. Managing them needs three things recorded against invoices, not in a diary. First, every receipt booked against its invoice, so party-wise outstanding is real. Second, advance adjustment — an on-account advance taken with the order must be applied to the invoices it funds, or your outstanding overstates. Third, ageing and follow-up: overdue invoices surfacing automatically, with reminders going out over WhatsApp, email and SMS rather than depending on someone remembering. Firms that bill by project milestones rather than dispatches — plant builders, fabricators on turnkey jobs — should read the construction and project billing guide for the progress-billing variant of this flow.
Posting manufacturer billing to Tally
Almost every Indian manufacturer keeps statutory books in Tally, and the correct architecture is to keep it that way: Tally stays the book of record, and the billing system posts finished documents into it. A confirmed tax invoice posts as a sales voucher with CGST/SGST/IGST on the right ledgers; a receipt posts as a receipt voucher; credit and debit notes post as Cr/Dr notes; and approved supplier bills post as purchase vouchers on the buy side. Items, parties and tax heads map to Tally ledgers once, after which posting is routine — no re-keying, no month-end data-entry marathon, and books that already agree with the billing register. The Tally integration page covers the mapping in detail.
What billing software for a manufacturer must do
Evaluating tools? A manufacturer's checklist is different from a shop's — template beauty matters far less than document linkage.
- Invoice raised against a dispatch or order, never free-floating
- A hard guard against billing the same dispatched quantity twice
- Order-vs-invoice and pending-to-bill reports
- Item ↔ HSN ↔ GST mapping with bulk import
- E-invoice (IRN/QR) and e-way bill data from the same documents
- Auto credit note on sales return, debit notes for escalations
- Receipts with advance adjustment and overdue follow-up
- Posting to Tally as vouchers with GST — not exports to re-type
Fast Billing Software for manufacturing is exactly this profile, proven in engineering deployments where invoices are raised against dispatches, the double-bill guard is enforced at the line level, and Tally receives the vouchers. Pricing is indicative and in INR — see billing software pricing and confirm GST specifics with your CA.
Frequently asked questions
What is the best way for a manufacturer to raise GST invoices?
Raise every tax invoice against a specific dispatch or confirmed order, so the invoice lines, quantities and HSN codes come from a real document rather than memory. The system should lock quantities that have already been invoiced, compute CGST/SGST or IGST from the buyer's state, and post the confirmed invoice to Tally as a sales voucher. This dispatch-linked approach is what makes pending-to-bill reports and double-billing prevention possible.
How do I make sure nothing ships without being billed?
Link invoices to dispatches and run a pending-to-bill report: every dispatched quantity that no invoice references yet. Because each invoice consumes quantity from its dispatch, the unbilled remainder is always computable per party and per challan. Without that link — for example when invoices are typed in a standalone template — shipped-but-unbilled material is invisible until a stock-take or an annoyed auditor finds it.
Does a manufacturer need e-invoicing?
If aggregate turnover in any financial year from 2017-18 onward exceeded ₹5 crore, yes — B2B invoices must be registered on the Invoice Registration Portal, which returns an IRN and QR code for the printed invoice. Most established manufacturers cross this threshold. The billing system must supply invoice data in the prescribed structure at confirmation time; confirm the current threshold with your CA, as it has been lowered repeatedly.
How are customer rejections handled in GST billing?
Through a credit note tied to the original invoice, not by editing the invoice. When a rejected lot returns, a credit note reverses the invoiced value and its GST, correcting the customer ledger and flowing to your GST returns. Good software raises it automatically against the dispatch, and if an entire invoice must be voided, cancellation releases the dispatched quantity so it can be re-billed correctly.
Will billing software replace Tally in a factory?
No — and it should not try. Tally remains the statutory book of record. Billing software is the operational front end that raises invoices against dispatches, guards against double-billing, and tracks receivables, then posts each finished document to Tally as the matching voucher — sales, receipt, credit/debit note or purchase — with GST on the right ledgers. The two together eliminate re-keying without disturbing your accountant's workflow.