Vendor reconciliation in audit compares the balance recorded for a supplier in the client's books with the balance that supplier says is due, and explains every difference. It is the principal test of the existence, completeness and valuation of trade payables. The key design point is that payables risk runs towards understatement, so vendors must be selected on the risk of an unrecorded liability rather than on the size of the recorded balance — a zero balance on an active account is more interesting than a large one.

Why the selection basis is the whole test

Receivables are tested for overstatement, so a sample of the largest balances is sensible. Payables are the opposite. A client that has omitted a liability shows a small balance or none at all, and any selection driven by recorded balance size will systematically avoid exactly those accounts.

The right population to select from is the vendors the client transacted with during the year, not the vendors with a balance at the year end.

Selection criteria for vendor reconciliation
Select	Why
High purchase volume during the year, regardless of closing balance	Activity indicates an ongoing relationship where a liability is likely to exist. A nil closing balance on a vendor with substantial annual purchases is the signal to look for.
Nil or negative closing balances on active accounts	A debit balance on a trade payable is usually an advance, a duplicate payment or a credit note never adjusted, and all three are worth finding.
Accounts with unusual activity near the year end	Large adjustments, round-sum journals, or a flurry of debit notes in the last fortnight.
Long-outstanding balances with no movement	Either a real liability nobody is chasing, or a balance that should have been written back. Both need a decision.
Vendors named in the related-party list	Reconciliation supports the disclosure. Identify these by PAN and directorship rather than by name.
A sample of the remainder	So that a conclusion can be drawn about the population and not only about the targeted items.

Selection criteria for vendor reconciliation

Statements and confirmations are different evidence

A supplier statement obtained from the client's own file is evidence created by a third party but delivered through the client. A confirmation requested by the audit team and returned directly to the team is evidence received from the third party. Under SA 500 the reliability of evidence depends on its source and the circumstances in which it was obtained, and evidence obtained directly from an external source is generally more reliable than the same evidence passed through the entity.

Both are legitimate evidence and neither is automatically sufficient. Which you use should follow from your risk assessment, and the working paper should record which one you actually had. A statement the client printed is not a confirmation, and describing it as one overstates the strength of the file.

Running the reconciliation

01Fix the cut-off date and use it on both sidesSuppliers frequently send statements as at their own month end or as at the date of the request. A statement as at 5 April reconciled against a ledger as at 31 March generates differences that are nothing but the date.
02Agree the opening balanceIf last year's confirmed balance does not carry forward, the difference arose in a prior period and the reconciliation for this year will never close.
03Match transaction by transaction, not by totalA reconciliation that arrives at the right total through offsetting errors is worse than one that does not balance, because it hides two findings instead of showing one.
04Categorise every unmatched itemUse the seven categories below. An uncategorised residue means the reconciliation is unfinished, whatever the totals say.
05Test the reconciling items to evidenceGoods in transit to the dispatch document, payments in transit to the bank statement of the following period, disputed items to the correspondence. A reconciling item accepted on explanation alone is not audited.
06Look at the direction of the unexplained residueConsistently understated balances across several vendors is a systemic finding about the recording of purchases, not a collection of individual differences.

The seven difference categories

Vendor reconciliation differences and what each means
Category	Typical cause	What it implies
Goods or invoices in transit	Supplier has invoiced; the client has not received or not recorded	Genuine timing if the goods arrive shortly after. If control had already passed, this is an understated liability and belongs in cut-off testing.
Payments in transit	Client has paid; the supplier has not applied the receipt	Timing. Agree to the bank statement of the following period. Cheques issued but not presented at the year end need separate consideration.
Debit notes not accepted	Client has raised a claim for rate difference, shortage or quality; the supplier disputes it	The liability may be understated by the disputed amount. This is a valuation question and often needs a provision decision.
Credit notes not recorded	Supplier has issued a credit; the client has not taken it	Liability overstated. Also affects the input credit position, since a credit note reduces credit.
Tax component treatment	One side shows the invoice gross, the other net of recoverable tax	Not a difference once identified. Establish the basis of each statement before reconciling anything else.
Advances and retentions	Advances paid sitting in a separate ledger, or retention money held back	Presentation rather than measurement. Confirm advances are not netted against payables in the balance sheet where they should be shown separately.
Unexplained	Everything not in the six categories above	This is the category the conclusion actually turns on. It should be small, quantified, and individually investigated rather than accepted as a residue.

Vendor reconciliation differences and what each means

Non-responses

Suppliers do not always reply, and some reply with a statement that arrives too late to be useful. A non-response is not a result; it is an absence of evidence, and it requires alternative procedures that give evidence about the same assertion.

Examine payments made after the year end that settle balances outstanding at it. A subsequent payment of the exact balance is strong evidence the liability existed.
Examine the invoices and receipt records making up the balance, and test them as you would a sample of purchases.
Review the vendor's activity in the following period for credit notes or adjustments referring back to the year under audit.
For a nil or negative balance where no reply came, review the following period's purchases from that vendor for invoices dated before the year end.

Record non-responses as non-responses. A working paper listing forty vendors circularised and showing results for twenty-six, with no mention of the other fourteen, reads on review as though the fourteen were never sent. Where alternative procedures were performed, cross-reference them; where the balance was left unaudited, say so and quantify it.

Where vendor reconciliation connects to other work

This procedure is unusually well connected, and planning it in isolation duplicates effort across three sections of the file.

Connections worth exploiting
Procedure	What it contributes	What it takes back
Purchase cut-off testing	Identifies the goods-in-transit and unrecorded-invoice population	Confirms which reconciling items are genuine timing and which are understatement
Duplicate invoice detection	A supplier statement showing one invoice against two client entries settles a duplicate immediately	Duplicate pairs explain otherwise puzzling overstatements on specific accounts
Input credit reconciliation	Supplier-filed data gives an independent view of what each vendor invoiced during the year	Vendors appearing in the credit statement with no corresponding purchases are a completeness lead
Related-party disclosure	The confirmed balance supports the disclosed amount	Confirmations sent to related parties are weaker evidence and should be identified as such

Connections worth exploiting

Concluding on trade payables

Population identified as vendors transacted with, not vendors with a closing balance.
Selection basis recorded, including the criteria used for targeted selections.
Statement or confirmation distinguished for every vendor, and its source recorded.
Every difference categorised, with the unexplained residue quantified separately.
Reconciling items tested to evidence rather than accepted on explanation.
Non-responses listed, with alternative procedures cross-referenced or the gap stated.
Debit balances on trade payables examined and reclassified where appropriate.
A conclusion on completeness specifically, since that is the assertion this procedure exists to address.

How we think about this

Matching two ledgers line by line, applying a date cut-off consistently and sorting differences into categories is deterministic work that should not consume an audit senior's week. Deciding whether a disputed debit note needs a provision, or whether an unexplained residue is small enough to leave, is not. Lekhya does the matching and the categorising; the provision decision and the conclusion stay with the auditor who signs.

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.

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.

Vendor reconciliation in statutory audit