Invoice hygiene: the invoice that gets paid

Need this handled rather than explained? Talk to a practitioner →

Where late payment starts

Before a customer decides not to pay, a customer's payables team decides it cannot process the invoice: the PO number is missing, the rate differs from the order, the quantity differs from the challan, the GST details are wrong, the invoice went to the buyer rather than to accounts. Each of these puts the invoice in a queue that no reminder reaches. In our diagnostics, a meaningful share of what a client calls "slow payers" is invoicing that gives the customer a reason to wait.

What a B2B invoice needs

• The customer's references: purchase order number, vendor code, contract or rate-agreement reference — whatever the customer's system matches against.
• The delivery reference: challan or e-way bill number, date, and the signed proof of delivery attached or tagged. An invoice matched to a signed delivery cannot be disputed on receipt.
• The agreed rate and quantity, matching the order exactly; any variance explained on the invoice itself.
• Tax details complete and correct — GSTIN of both parties, HSN/SAC codes, place of supply, tax split.
• Terms: due date stated as a date, not "net 45"; the interest clause on late payment, if your contract has one; bank details for transfer.
• A contact for queries — a name and a number, so a query goes to someone who resolves it rather than into an inbox.

When and to whom

The day the goods leave or the service milestone is accepted — not at month-end in a batch. To the person who processes payables, with the buyer copied; not the other way round. And confirm receipt: an invoice the customer says it never received is an invoice that was never due.

E-invoicing and the record

Where e-invoicing applies, the IRN and QR code are part of what makes the invoice valid for the customer's input credit — an invalid invoice will be rejected, correctly. Keep the e-invoice, the delivery proof and the acceptance together on the account; that bundle is the file that later decides a dispute, a demand notice, or a summary suit on written instruments.

Credit notes and corrections

Corrections happen. Issue a credit note and a fresh invoice rather than an amended one; date both; reference the original. An unexplained amended invoice is a dispute waiting to be raised. And never let a promised credit note sit unissued — the customer will hold the whole invoice until it arrives, and be right to.

Why this is a collections topic

Because an invoice is the first document in the file, and the file is what recovers money. The dispute management guide covers what to do when a dispute is raised; this page is about giving the customer no dispute to raise. The accounts receivable process starts here.

Sources and regulation

Thresholds, limitation periods and procedures change. This guide describes the position as generally understood at the time of writing and is not legal advice; confirm the current rule before acting.