The confession
It was a Thursday, two meetings back to back, a payment file waiting with six vouchers I had supposedly reviewed. I flipped, saw totals that looked right, signed. Voucher four had no GRN. The goods had arrived short, the storekeeper's count sat in a different pile, and we paid the full bill. Unwinding it took a week: credit note negotiations, a sheepish call, my signature on every page of the mess. The error was not in the voucher. The error was a tired person performing a control designed for an alert one.
That week is why I am stubborn about this: no voucher should depend on one person's alertness. Maker-checker is the dullest control in finance and the one I would keep if I had to burn the rest. One person prepares. A different person confirms. The preparer never approves their own work, however senior, however rushed the Thursday.
Maker-checker splits every voucher into two jobs held by two people. The maker assembles: documents, entry, narrations. The checker verifies against the file and owns the confirm-or-return decision. Separation, not seniority, is the control. It catches what tired eyes miss, including its own.
Meet the two chairs
Let me introduce them the way I do with customers, as people with sentences they own.
The maker is usually your AP clerk. She gathers the invoice, the PO, the GRN, keys the entry, writes the narration naming the numbers. Her owned sentence is: this file is complete. Not this file is correct, complete. Every paper present, every number keyed as printed, every mismatch flagged rather than smoothed over. A maker who flags is doing the job. A maker who quietly fixes a rate to make the total close is forging, however helpfully meant.
The checker is the accounts head, and his owned sentence is different: I verified quantity, rate, GSTIN, and 2B status, or I sent it back with the reason named. Verified, not glanced. The checker re-performs the match, all three legs, against the file, not against the maker's summary. Trust the maker and verify the file. The day the checker starts approving summaries, you have one chair with extra steps.
Then the third chair, who visits monthly: your CA. Judgment calls live here. Debit notes with odd references, RCM lines, composition suppliers, job-work challans past their diary date. The CA does not recheck arithmetic. The CA rules on meaning. Our review queue page is the software mirror of this: the queue is the product, not a failure, because some vouchers need a human with context no rulebook holds.
What does a good send-back look like? Specific, dated, and kind: rate differs from PO 447 by ₹15, please get purchase to amend or take a credit note. GRN missing for lot received Tuesday, please attach before Friday close. That is the whole art. Vague rejections, check again or not ok, teach the maker nothing and breed resentment. A checker who writes reasons trains a maker who stops needing them. Six months of good send-backs and your amber lane starts emptying itself.
What moves through which lane
Not every voucher needs the full ceremony, and pretending otherwise is how controls die. I draw three lanes:
Green is earned per vendor by history, not granted by default. New vendors start amber.
The lane idea does two quiet things. It keeps green vouchers fast, so nobody resents the control, and it forces every amber voucher to carry its reason in writing. A voucher that cannot say why it is amber is red until it can.
The three-person version
"Lovely," says every three-person accounts team, "and who are my two chairs?" You, split differently. The clerk makes. The head checks. Small-value routine bills get batch spot-checks so the queue moves; everything amber or red gets the full treatment regardless of amount. Size changes the throughput, never the separation. The day the head starts approving their own emergency entries is the day the control dies, and emergencies are exactly when it matters most.
Software helps at the edges and I will place it precisely. Our gate is a tireless maker-side assistant: it proves the document before a human spends eyes on it, and parks the doubtful in NEEDS_REVIEW with reasons attached. What it will never be is the checker. A gate checks documents against rules. The checker exercises judgment on everything rules cannot see: a supplier suddenly billing a new item, a rate that matches the PO but smells wrong, a Thursday signature offered between meetings. Different jobs. Keep them in different chairs.
- EntryLedgerNEEDS_REVIEW: the queue
The software mirror of the checker: doubt, parked with reasons.
- EntryLedgerPO vs GRN vs invoice
The match the checker re-performs. All three legs, every time.
What is maker-checker in AP?+
One person prepares the voucher, a different person confirms it. The preparer never approves their own work. That separation, not seniority, is the entire control.
We are a three-person team. Can we run it?+
Yes. Clerk makes, head checks, batch spot-checks for small routine bills. The CA is the third chair for judgment calls. Size changes throughput, never separation.
Does software replace the checker?+
No. I sell voucher software and I am telling you this. A gate checks documents against rules. The checker judges what rules cannot see. Buy the gate, keep the chair.
What should the checker actually say?+
One owned sentence: verified quantity, rate, GSTIN, and 2B status, or sent back with the reason named. Verdicts without reasons are decoration.