The cheque issue register — what to record, and why auditors ask for it (2026)
Audit season, a Tuesday afternoon. The article clerk across the table reads one line off the bank statement: cheque number 004312, ₹1,86,000, debited 4 March. Then the question. "What was this payment for?"
If the answer starts with "let me check" and ends forty minutes later with someone flipping through the counterfoils of three cheque books — two of them exhausted, filed in a drawer nobody has labelled — the problem isn't anyone's memory. The business simply has no cheque issue register.
This post is the unglamorous fix. What the register is, the exact columns it needs, how it pairs with the payment voucher, the controls around it that actually stop cheque misuse, and why the best version of it isn't maintained by hand at all. It's the accounts-desk end of cheque lifecycle management — knowing where every leaf stands between the book and the bank statement, on any day you're asked.
Three questions, one weak system
The auditor's cheque question always has three parts, even when it arrives as one sentence. What was cheque 004312 for? Who approved it? Has it cleared?
Now look at where your answers currently live. The ledger records ₹1,86,000 against a creditor's account — but usually not the instrument number, and never the approval. The bank statement says "debited on 4 March" — cleared, yes; why, no. The counterfoil, if it was filled in at all that morning, gives you a payee name in hurried handwriting and nothing else.
Three sources. None complete. And stitching them together is exactly the forty-minute hunt described above, repeated for every cheque the auditor samples.
A cheque issue register puts all three answers on one line. That's the entire idea. One running record, one row per leaf, from the day the cheque book arrives to the day its last cheque clears.
The counterfoil is not a register
Worth saying plainly, because most small businesses genuinely believe the counterfoil is their register.
It isn't, for five reasons. It's per-book — your history is scattered across every book you've ever finished. It's non-searchable — finding a payee means reading every stub. It records only what the writer bothered to scribble in a two-inch space, which after the tenth cheque of the day is often just an amount. It carries no status — a counterfoil looks identical whether the cheque cleared, bounced, or is still sitting in someone's drawer. And when the book is exhausted, it disappears into a cupboard, taking its ten seconds of history with it.
Counterfoils are a backup, not a system. Keep filling them in. Just don't confuse them with the record.
The columns that earn their place
Here's the format — every column below exists because some future question needs it. Ruled register, Excel sheet, or software: the fields are the same.
| Column group | What you record | The question it answers |
|---|---|---|
| Instrument | Date written, cheque number, bank + account | Which leaf, from which book, drawn on which account? |
| Payee and amount | Payee name exactly as written, amount in ₹ | Who gets paid, and how much? |
| Purpose | Purpose or invoice reference, payment voucher number | Why does this payment exist, and where's the approval? |
| People | Prepared by, authorised by | Who wrote it, and which signatory signed off? |
| Status + clearance date | Issued / handed over / presented / cleared / returned / cancelled / stopped | Where is this cheque right now? |
| Remarks | Post-dated, replacement leaf, stop-payment reason, anything odd | What will you have forgotten by next quarter? |
Two habits make the format work. One row per leaf — including cancelled ones, because a missing row is a missing cheque, and a missing cheque is a control failure. And the status column updated as the cheque moves, not reconstructed at year end. "Issued" means written and signed. "Handed over" means it left the office. "Presented" means it hit the clearing. Then cleared, or returned, with a date either way.
That status column is the register's whole personality. Without it you have a list. With it you have a live map of your outstanding liabilities, cheque by cheque.
The payment voucher — the register's other half
The register deliberately records why in only a few words. The full story lives on the payment voucher, and the two documents point at each other.
Division of labour: the voucher carries the approval — the invoice or bill stapled behind it, the account head, the sanctioning signature, the date. The register carries the instrument — number, payee, amount, status. The voucher number goes into the register's row; the cheque number goes onto the voucher. One link, written twice.
That link is precisely what an auditor traces. Pick a debit on the statement → find the cheque number in the register → read the voucher number off that row → pull the voucher → find the invoice and the approval signature behind it. Four hops, two minutes, done. When the chain is intact, cheque verification is the fastest part of an audit. When it's broken — no voucher number in the register, or vouchers filed by month while cheques are searched by number — every sampled payment becomes an excavation.
Numbering the vouchers sequentially, per financial year, is the small discipline that keeps the chain honest. A gap in voucher numbers gets asked about just as fast as a gap in cheque numbers.
Five controls that outrank the format
A beautifully ruled register with weak controls is decoration. These five matter more than any column layout:
1. Sequential numbering, no unexplained gaps. Cheque numbers run in printed sequence — so the register must too. If 004311 and 004313 are entered and 004312 isn't, someone explains it today, not in March.
2. Cancelled leaves are retained, marked, and entered. A spoiled leaf gets CANCELLED written across it, stays stapled in the book or filed with the vouchers, and gets its own register row. Never discard a cancelled cheque — a destroyed leaf is indistinguishable from a stolen one.
3. Blank books live away from the signatory. The person who signs cheques should not also hold the stock of unsigned ones. Basic separation, skipped in most small firms because "it's all one cupboard anyway". That cupboard is where misuse starts.
4. Dual authorisation above a threshold. Two signatures above, say, ₹1,00,000 — the figure is yours to set, and the board resolution defines who can sign. The register's "authorised by" column is where you prove the rule was followed.
5. Monthly tie-out to the bank statement. Reconcile the statement against the register — not against memory. Every debit matches a register row; every "issued" row older than a month gets a question mark. Thirty minutes monthly, or a lost week at year end. Your choice.
What the auditor will actually ask for
Having done a few year-ends, the requests are predictable. Five items, almost every time.
The unpresented cheque list as at 31 March — every cheque issued but not yet cleared. With a status column, this is a filter. Without one, it's the painful part of your bank reconciliation, rebuilt from counterfoils.
Cheques signed but not handed over. A cheque written on 30 March and still in the office drawer on 15 April raises a cut-off question: was the liability really discharged this year? The "handed over" status exists for exactly this.
Stale cheques still riding the reconciliation. More on this below — it's the one every SMB fails.
Cancelled leaves, physically. The auditor will pick cancelled rows from the register and ask to see the mutilated leaf. Produce it in ten seconds and the sample size stays small.
A sequence check. First and last cheque number used in the year, and an explanation for anything missing in between.
None of these are trick questions. They're all the same question — does this business control its cheques, or do its cheques control it? — asked five ways.
A register you update from memory is a register with holes in it. The record an auditor trusts is the one created at the same moment as the cheque — not the one reconstructed from counterfoils in the first week of April.
The stale-cheque cleanup nobody schedules
A cheque is valid for three months from its date. After that, the bank won't pay it — but the entry doesn't clean itself up. In firm after firm, the year-end reconciliation carries cheques issued eleven, fourteen, twenty months ago, dutifully listed as "unpresented" long after they died.
Quarterly, do the cleanup. Filter the register for "issued" rows older than three months. For each one, decide: the payee lost it, so reissue a fresh cheque (and mark the old row stale, with a stop-payment if there's any doubt); or the payment is no longer owed, so reverse the entry in the books and close the row. Either way the row gets an ending. A register where every cheque eventually reaches cleared, returned, cancelled, stopped, or stale-written-back is a register that reconciles itself.
It's twenty minutes a quarter. Almost nobody does it. Be the accounts department that does.
When the register writes itself
Everything above works on paper. Plenty of disciplined firms run a ruled register for decades. But notice what the whole apparatus depends on: a human remembering to write a row, at the busiest moment of the day, every single time. That's the hole in the system — not the format, the moment of entry.
Printing changes the economics completely. When cheques are printed through software instead of handwritten, the register stops being a separate chore: the record is created by the act of printing. Cheque number, date, payee, amount, account — captured at the moment the leaf goes through the printer, searchable forever, with the status tracked from issue to clearance and reconciliation run against the register instead of against anyone's memory. On a bulk run of thirty vendor cheques, that's thirty register rows nobody had to remember to write.
"What was cheque 004312 for?" becomes a two-second search. Which, if you think about it, is what the question always deserved.
The register that writes itself. Print your cheques with Cheqify and every leaf is logged the moment it's printed — number, payee, amount, status tracked from issue to clearance, searchable across 300+ Indian bank layouts. 100% free. Start at app.cheqify.app.
