Purchase invoice vouching means tracing a recorded purchase back to the supplier invoice and its supporting documents, to establish that the entry is genuine, authorised, correctly measured and in the right period. It is a directional test that runs from the books to the document, which makes it evidence of occurrence and not of completeness. Done properly it examines eight things on the face of the invoice and three things around it, and the record of what was checked has to survive without the person who checked it.
Vouching and verification are not the same test
Vouching examines a transaction against the documentary evidence behind it. Verification examines the existence, ownership and valuation of a balance. Purchases are vouched; the closing payables balance and the stock it produced are verified. Files that blur the two typically end up with a well-vouched purchase section and no work at all on the liability that the same purchases created.
The direction of the test is what determines what it can prove. Starting from the ledger and finding the invoice shows that what was recorded happened. It cannot show that everything which happened was recorded, because an unrecorded purchase has no ledger entry to start from. That requires the reverse test, from the goods inward records and supplier statements into the books.
What to examine, in order
The order matters because the early checks are the ones that make the later ones pointless if they fail. Establish that the document is the right document before recomputing what is on it.
- 01Is this a tax invoice addressed to the clientThe entity name and, where GST applies, the GSTIN on the invoice must be the client's own registration for the state in which the credit was taken. A multi-state client billed at the wrong registration is a genuine and common problem, and it is invisible if you only check the name.
- 02Is it an invoice at allProforma invoices, quotations, delivery challans and account statements routinely find their way into a voucher file. A proforma is not evidence of a purchase and carries no input credit.
- 03Does the period stated match the period recordedCompare invoice date, the date of receipt of goods or services, and the voucher date in the books. Where they straddle the year end, stop and apply the cut-off procedure instead of the routine one.
- 04Recompute the arithmeticQuantity times rate, less discount, plus freight and other charges, plus tax at the stated rate, equals the invoice total. Recompute it rather than reading the total. Rounding, a discount applied after tax instead of before, and a rate applied to the wrong base are all found this way.
- 05Agree the amount and the split to the ledger postingThe taxable value should reach the expense or asset ledger and the tax should reach the input credit ledger. A single posting of the gross amount to the expense account means credit was not taken or was taken elsewhere, and both are worth knowing.
- 06Agree to evidence of receiptGoods receipt note, gate inward entry, signed delivery challan or a stock ledger movement for goods. For services, a certified completion note, a timesheet, a milestone certificate or a report. Establish what the client actually produces before the season starts, and agree what you will accept.
- 07Agree to the order or contractRate, quantity and terms against the purchase order, work order or rate contract. Where none exists, identify who authorised the purchase and confirm their authority against the client's own delegation.
- 08Check the classificationThe ledger allocated should match the nature of the item. Pay attention to anything that could be an asset: repairs that are actually a replacement, software licences, tooling, and improvements to leased premises.
Three checks sit around the invoice rather than on it: whether the supplier is a related party, whether the credit taken is of a kind blocked under section 17(5) of the CGST Act, and whether the invoice appears in the input credit available per GSTR-2B for the relevant period. The third is normally handled in the input credit reconciliation rather than item by item, but a vouching test that ignores it entirely will raise exceptions the reconciliation has already explained.
Regulatory requirement
Section 16 of the CGST Act sets the conditions for taking input tax credit, which include possession of a tax invoice, receipt of the goods or services, tax having been paid to the government, and the return having been furnished. Section 17(5) lists supplies on which credit is blocked. These are statutory conditions, not audit conventions, and they change: check the current text before concluding.
Tickmarks worth using
A tickmark legend is not a formality. It is what makes a vouching schedule reperformable by someone who was not there. A legend of four or five marks, each meaning exactly one check, beats a single tick that means the item was looked at.
| Mark | Means | What must be true |
|---|---|---|
| A | Agreed to supplier tax invoice | Vendor, invoice number, date and amount agree to the original document |
| R | Arithmetically recomputed | Quantity, rate, discount, charges and tax recomputed to the invoice total |
| G | Agreed to evidence of receipt | The document named in the legend, not just any paperwork, was seen |
| O | Agreed to order or contract | Rate and quantity agree; where no order exists, the authorisation was identified |
| L | Agreed to ledger posting | Amount, split and account agree to the entry in the books |
| X | Exception | Cross-referenced to the line on the exception schedule |
Common practice, not a requirement
Tickmark letters are a firm convention, not a requirement of any standard. What SA 230 requires is that an experienced auditor with no previous connection to the engagement can understand what was done. A private legend achieves that; a tick with no legend does not.
Recording the test so it survives review
A vouching schedule should carry, for every selected item, enough identifying detail to find the document again: vendor, invoice number, invoice date, amount, voucher number, and where the document is held. If the client provided a scanned file, record the file name. A reviewer who wants to reperform one line should be able to do it without asking anyone a question.
Record the items that passed as well as the ones that did not. A schedule showing only exceptions gives no evidence of the extent of the work, and extent is one of the four things SA 230 requires the documentation to make clear.
What goes wrong most often
| Failure | Why it matters | Instead |
|---|---|---|
| A single tick per row, no legend | Nobody can tell whether the amount was agreed, recomputed or merely seen | A short legend where each mark carries one meaning |
| Vouching to a photocopy or a scan without saying so | The evidence in the file is weaker than it appears, and SA 500 treats the reliability of evidence as depending on its source and nature | State what was examined. A scan examined is still evidence; a scan described as an original is a misstatement in the file. |
| Accepting a delivery challan as proof of the amount | A challan evidences receipt, not price. It supports one assertion, not two. | Pair it with the invoice and the order. One document rarely covers two assertions. |
| Treating the tax difference as an exception | Most apparent invoice-to-ledger differences are the tax component posted to a separate input credit account | Recompute the split before raising it. Real exceptions are the ones left after that. |
| Vouching only large items | A conclusion about the whole population drawn from a sample containing none of it | Cover the population in layers, and describe each layer separately. |
| No record of what was not available | A reviewer cannot distinguish a document that passed from one nobody could find | Record unavailable documents as exceptions with a reason, never as blanks. |
Where the hours actually go
On a purchase section of any size, most of the time is spent on three activities: finding the document that corresponds to a ledger line, agreeing four or five fields between two documents, and recomputing arithmetic. All three are mechanical. The judgement is concentrated in a small number of decisions, and those decisions are the part that has to be written down in the auditor's own words.
How we think about this
Lekhya matches invoices to ledger entries and to evidence of receipt across the whole population, recomputes the arithmetic, and shows each figure next to the document and page it was read from. An auditor still decides whether what it surfaced is an exception worth pursuing, and writes the conclusion. Extraction and matching are repetitive work; judging what a difference means is not.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Purchase & AP auditPurchase testing in statutory audit: procedures, samples and exceptionsAgreeing the population, choosing a sample basis that survives review, the procedures that address each assertion, and what to do with what they throw up.
- Purchase & AP auditPurchase testing: a complete exception taxonomyEvery category of finding a three-way match can produce, what each usually means in an Indian mid-market client, and which are worth escalating versus documenting and moving on.
- Audit documentationAudit evidence: what makes it sufficient, appropriate and traceableSufficiency and appropriateness without the textbook circularity, a reliability hierarchy for Indian practice, and what has to be recorded for evidence to be traceable.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.