How to check a supplier’s statement against SQL Accounting
Print the supplier’s account from SQL Accounting for the same date as their statement, then tick each line on both by the supplier’s invoice number. Every line left unticked is one of five differences, and each has its own fix. Key a missing invoice only from the invoice itself, never from the statement line.
Last checked against eStream’s SQL Accounting documentation (the Supplier usage guide and its Reports page).
What a statement is
A supplier’s statement lists what the supplier thinks you owe, up to a date: their invoices, debit notes and credit notes, and the payments they have received. It is their record, not a bill. Your record is the supplier’s account in SQL Accounting. Checking one against the other each month is how you find an invoice you never received, one keyed twice, or a payment that went to the wrong invoice, before the supplier chases you for it.
Print your side for the same date
SQL Accounting’s supplier reports include Print Supplier Statement, a statement of account between you and that supplier. eStream lists its types as Default, Open Item, Detail, Brought Forward and Summary. Print it for the same date as the supplier’s statement, and pick the type whose layout is closest to theirs.
Two other supplier reports help with the unpaid side: Print Supplier Aging Report shows unpaid invoices and how long each has been outstanding, and Print Supplier Due Document shows what is overdue and what is not yet due.
Tick line by line
- Compare the closing balances first. If they agree, the rest is a quick look down both lists.
- Tick by the supplier’s invoice number, not by the amount. Two invoices can be for the same amount.
- Tick on both papers: each line on their statement, and the same line on your print.
- For payments, eStream’s guide notes that the Supplier Statement shows which invoices each payment was knocked off against. Check that each payment on their statement is on yours, against the same invoices.
The five differences, and what to do
| What you find | Usually means | What to do |
|---|---|---|
| On their statement, not in SQL Accounting | An invoice you never received, or one not keyed yet | First search for it under another number, so it does not go in twice. Then ask the supplier for the invoice and key it from the invoice |
| In SQL Accounting, not on their statement | Keyed twice, keyed under the wrong supplier, or dated after their statement | Look for a duplicate and check the supplier code. If neither, ask the supplier |
| The same invoice, a different amount | A keying slip, or a credit or debit note on one side only | Compare with the paper. A missing note is covered in supplier credit and debit notes |
| A payment that does not match | Paid near the statement date and not yet received by them, or knocked off against the wrong invoice | Note a payment in transit. If the knock-off is wrong, the invoices it should have cleared still show as unpaid in the aging report |
| A difference that clears next month | Goods or invoices in transit at the statement date | Write it down and check it is gone on next month’s statement |
Write it down, do not force it
Keep one short note per supplier per month: their balance, your balance, and each difference with its reason and what you did about it. Do not key an adjustment just to make the two balances agree, and do not delete an entry on your own. Ask the person who looks after your accounts how they want a wrong entry reversed, because a payment may already be knocked off against it.
How often
Every month for your main suppliers, and before you pay a large batch. A statement is also a good checklist for what you have keyed: tick each line against your books, and key a missing invoice only from the checked invoice itself.