Vendor reconciliation is the process of matching your ledger for a supplier with the supplier’s own statement for the same period and explaining every difference. Left unchecked, the gap hides a bill booked twice, an invoice you never received and so never claimed input tax credit on, or a debit note the vendor never accepted.
In OneFinOps, the Payables Agent reconciles each vendor statement and classifies every difference, so you start from a short list.
Key takeaways
- Reconcile critical and MSME vendors monthly, all others at least quarterly.
- Most gaps are payments in transit, unbooked invoices, TDS or debit notes.
- You are done when the unexplained difference is zero.
What is the vendor reconciliation process?
- Get the vendor statement for the same period as your ledger.
- Agree the opening balance. If it differs, reconcile the prior period first.
- Match invoices by number and amount, and payments by date, UTR and amount.
- Match TDS, debit notes and credit notes on both sides.
- List what is left. Each unmatched line is a timing difference, missing document, dispute or error.
- Prepare the statement, act on each item, and have a reviewer sign it into the month-end close pack.
What are the common reasons for differences?
| Reason | Which side is higher | Typical fix |
|---|---|---|
| Your payment not yet recorded by vendor | Vendor’s | Send payment advice with UTR |
| Vendor invoice not yet booked by you | Vendor’s | Get the invoice, match to PO and GRN, then book |
| TDS deducted by you, not booked by vendor | Vendor’s | Clears once vendor sees Form 168 (earlier 26AS) credit |
| Your debit note not accepted by vendor | Vendor’s | Get vendor’s credit note or resolve the dispute |
| Vendor credit note not yet booked by you | Yours | Book it and check its GST impact |
| Invoice booked twice or at wrong amount | Yours | Reverse or correct the entry |
Vendor reconciliation format with example
Start from the vendor’s balance, adjust for each item, and land on yours. At 30 June 2026 a housekeeping vendor says you owe ₹5,90,000. Your books say ₹1,62,200.
| Particulars | Amount (₹) |
|---|---|
| Balance as per vendor’s statement (A) | 5,90,000 |
| Less: payment of 25-06-2026 not recorded by vendor | (3,48,000) |
| Less: TDS on two invoices not recorded by vendor | (9,000) |
| Less: debit note DN-07 not recorded by vendor | (11,800) |
| Less: INV-121 in vendor’s statement, not booked by us | (59,000) |
| Adjusted balance (B) = Balance as per our books (C) | 1,62,200 |
| Unexplained difference | 0 |
The payment and TDS are timing items. The debit note is a dispute: the vendor should issue a credit note under section 34 of the CGST Act so the ₹1,800 GST is adjusted on both sides.
How OneFinOps handles vendor reconciliation
Statements come in by upload or through the vendor portal. The Payables Agent matches them line by line against the account and classifies each difference, with missing, duplicated and disputed items separated. Nothing that moves money happens alone: a price or quantity outside tolerance goes to the buyer who raised the order, and the payment run is released by the person who holds the mandate.
In the usual setup someone matches an emailed statement against an exported ledger by eye. In OneFinOps the order, receipt, invoice, payment and statement sit in one record.
See how the Payables Agent works
