Paying vendors by cheque — the accounts payable workflow that doesn't break (2026)

Friday, 4:10 pm. Forty-two invoices cleared for payment. Three more stuck with the purchase head, who walked into a meeting at two and hasn't come out. The cheque book has eleven leaves left. The second signatory — the only other name on the bank mandate — leaves at five for a wedding in Rajkot. And two vendors have already called this afternoon, politely, to ask where their money is.

Every payables person in a 10–200 person Indian business has lived this exact Friday. Not because cheques are hard. Because vendor payment without a workflow is hard — every invoice becomes its own negotiation, every cheque its own little event, and by month-end nobody can say with confidence which invoice cheque number 417230 actually paid.

This is the operating procedure. A weekly payment run, six controlled steps from invoice to clearance, the two failures the controls exist to stop, and the handover discipline almost everyone skips. It assumes cheques — because your vendors ask for them, and because a cheque run done properly writes its own audit trail as it goes. (For what happens to a single leaf after it leaves your hand, the cheque lifecycle guide covers the full journey.)

Pay weekly, not on demand

The single biggest upgrade to any payables desk costs nothing: pick one day, and pay only on that day.

A weekly run turns forty scattered payment events into one. One approval sitting, where every invoice going out is reviewed together. One signing session, so the signatory blocks thirty minutes instead of being ambushed eight times. One trip to the bank, one courier batch, one entry session in the books. And one dated record — "the run of 6 February" — that an auditor can reconstruct in minutes.

Paying whenever someone shouts is the opposite of all of this. It's how firms end up with cheques written from memory, vouchers raised after the fact or never, and a leaf missing from the book that nobody remembers signing. Untraceable cheques are almost never stolen. They're issued in a hurry, on a Tuesday, between two phone calls.

Yes, exceptions exist — a statutory payment with a deadline, a transporter who won't release goods without payment. Fine. Route them through the same steps, just faster, and log them as exceptions. If exceptions cross five a week, your run day is wrong, not your vendors.

The run, stage by stage

Here's the full procedure, written the way an SOP should be — each stage with an owner and a paper trail.

1. Invoice in, matched. Every invoice gets checked against the purchase order and the goods receipt note before it enters the payment queue. Quantity billed vs quantity received vs quantity ordered. The three-way match is boring and it is the single control that catches short deliveries and inflated bills.

2. Approved per the delegation matrix. Who can approve what, in writing. Up to ₹50,000 the purchase manager; above that the director — whatever your thresholds are, they exist on paper, not in memory. An invoice without approval doesn't enter the run. No exceptions for "he told me on the phone."

3. Scheduled into the run. Approved invoices queue for the next run day, sequenced by due date. This is also the moment for the duplicate check — more on that below.

4. Cheque prepared, voucher attached. One payment voucher per cheque: payee name exactly as the vendor's bank account reads, amount, invoice numbers being settled, cheque number, date. The cheque itself is crossed "account payee" — for vendor payments this should be reflex, because it forces the money into the payee's own account.

5. Signed per the mandate. The signatory signs against the voucher and its attached invoices — never against a verbal summary, and never a blank leaf, ever. If your board resolution requires two signatures above a threshold, the run is where that actually gets enforced. The authorised signatory rules are worth a read if your mandate hasn't been reviewed since the company was incorporated.

6. Handed over, recorded, tracked. The cheque goes out against an acknowledgement, the invoice is stamped paid with the cheque number, and the cheque enters a tracking register until it clears — which is where reconciliation picks it up.

Six steps. None of them clever. All of them skipped somewhere, every week, in firms that then spend March reconstructing February.

One table to pin above the desk

Notice the column that matters most is the third one. Every stage leaves paper. That's the whole design.

The two failures the controls exist for

Strip away the theory and only two things go seriously wrong on a payables desk.

Duplicate payment. The vendor sends the invoice by email, then the hard copy arrives, then a statement — and the same ₹1,85,000 gets paid twice, four weeks apart, by two different people. The fix is mechanical, not heroic: before the run, sort the queue by vendor and invoice number and eyeball repeats; and at the moment of issue, stamp the invoice PAID, with the cheque number and date written on its face. A stamped invoice can't re-enter the queue. An unstamped one will, eventually.

Cheque misuse. The person who prepares the cheque is never the person who signs it — that separation is the entire game. Blank leaves are never pre-signed, not even "just two, for emergencies, since sir is travelling." That habit has funded more small-company frauds than any hacker. And above your threshold, two signatures, genuinely applied — not one real signature and one applied by whoever holds the second stamp.

Neither control slows a well-run desk down by even five minutes. Both are the first things an auditor checks. And most of the cheque mistakes businesses actually make trace back to skipping one of these two.

The handover everyone skips

Here's the uncomfortable one. A cheque handed over with no acknowledgement is a cheque you cannot prove you paid.

The vendor's accountant says the cheque never arrived. Your dispatch register says a peon carried it somewhere on the 14th. Between those two sentences sits a ₹3,40,000 dispute with no evidence on either side.

The fix takes ten seconds per cheque. Physical handover: a signed and dated receipt line — name, signature, cheque number — in a handover register or on the voucher copy. Courier: the POD filed with the voucher. Or the easiest of all: an email to the vendor the same day — "Cheque no. 417230 dated 06-02-2026 for ₹3,40,000 against invoices 881 and 887, handed to your representative today." Now the acknowledgement writes itself into your outbox.

Skipped by almost everyone. Regretted at exactly the wrong moment.

Tell the vendor what you issued

That same email solves a second problem: the chasing calls.

Vendors don't call because they're impatient. They call because they're blind — they have no idea whether their payment is approved, written, signed, or stuck. Tell them at issue: cheque number, date, amount, invoices covered. Now "when will it clear" answers itself — they know the clearing takes a working day or two once they deposit — and the Friday afternoon calls simply stop. A vendor who knows the cheque number never calls to ask if the cheque exists.

One line of communication, sent at the moment of issue. Cheapest vendor-relationship tool there is.

Lost cheques, unpresented cheques, stale cheques

Three months after your tidy February run, three cheques still haven't cleared. One vendor says theirs was lost in an office move. What now?

Lost or disputed: stop payment first, re-issue second — in that order, always. Instruct the bank to stop the specific cheque number, get the confirmation (net banking makes this same-day), and only then write the replacement. Re-issue before the stop is confirmed and you've created the possibility of both cheques being presented — congratulations, you've built your own duplicate payment. The validity and stop-payment rules cover the mechanics and the charges.

Simply unpresented: a cheque is valid for three months from its date. At each quarter-end, pull the register, list everything unpresented past 60 days, and call those vendors. Either they deposit, or you stop-and-reverse the entry. Stale cheques floating around inflate your bank balance in the books and understate what you actually owe — a small lie that compounds quietly.

Fifteen minutes a quarter. Do it.

A payment run is a control, not a convenience. Forty cheques signed in one sitting, against forty vouchers, leave one clean record. Forty cheques signed on demand leave forty separate stories — and by March, nobody can retell them.

Where printing beats the pen

Now the honest arithmetic. A vendor cheque needs a payee name copied exactly, a date, figures, the amount in words, and a crossing. Hand-written, that's two to three careful minutes — call it 100 minutes of pure writing for a forty-cheque run, before a single voucher. And the amount-in-words line is precisely where a tired Friday hand slips, which is a return, a charge, and an apology call.

Printing the run changes the shape of the work. Payee names come from a vendor master, spelled the same way every week. Amounts in words are generated from the figures, so the two cannot disagree. Alignment on the bank's leaf is a solved problem, not a per-cheque prayer. And — the part that matters for everything above — the record is created as a by-product: every printed cheque exists in a register the moment it's printed, numbered, dated, tied to its payee. The tracking step stops being clerical work you do afterwards and becomes something the run produces on its own.

At five cheques a month, hand-writing is fine. At a weekly run of twenty or forty, it isn't — the bulk cheque printing guide walks the batch workflow end to end, the how to print a cheque in India post covers the setup basics, and the online cheque printing page shows what it looks like on your own bank's layout.

The run checklist

Pin this next to the table:

• Every invoice in the run is three-way matched and carries an approval.
• Queue sorted by vendor + invoice number; duplicates eyeballed out.
• Every cheque crossed account payee, voucher attached, invoice numbers on the voucher.
• Preparer ≠ signatory; two signatures above the threshold; zero pre-signed leaves.
• Every invoice stamped PAID with cheque number at issue.
• Every handover acknowledged — receipt, POD, or same-day email with the cheque number.
• Register updated; unpresented cheques reviewed at quarter-end.

Seven lines. That's the entire control environment most 50-person firms are missing.

Friday's payment run, done in minutes. Cheqify prints your whole vendor run on 300+ Indian bank layouts — payee names from your list, amount in words generated automatically, every cheque tracked from issue to clearance. 100% free. Start at app.cheqify.app.