A supplier’s collections team emails a statement showing $86,420 past due. Your AP ledger says you owe them $76,595, and half of that isn’t due yet. Before anyone pays the difference or tells the supplier they’re wrong, you need to know which of the two records is missing something.
Two records answer the question of what you owe. The supplier’s statement shows what they have billed, credited, and received. Your AP ledger shows what you have recorded. Neither is automatically right. A statement reconciliation compares them at the same cutoff, transaction by transaction, and gives every difference a cause and an owner.
Why statement reconciliation is worth the time
The AP subledger can tie perfectly to the general ledger and still be wrong about a supplier. Statement reconciliation is one of the few controls that compares your records with an outside party’s. It catches:
- Missing invoices: bills the supplier sent that never reached AP, which also means expenses missing from the period.
- Unrecorded or unapplied credits: credit memos the supplier issued that AP never booked, or booked but never applied.
- Duplicates: the same bill recorded twice in your ledger, often visible only because the supplier shows it once.
- Misapplied payments: your payment posted by the supplier against the wrong invoice, which then shows up as past due.
- Timing: payments and invoices in transit, which are expected but should be explained, not assumed.
Which suppliers to reconcile and when
You don’t need to reconcile every supplier every month. Pick by risk.
| Supplier type | Suggested frequency | Why |
|---|---|---|
| High-volume direct material suppliers | Monthly | Many invoices, credits, and partial shipments; errors compound |
| Suppliers with frequent credits, rebates, or returns | Monthly | Credits are easy to miss or misapply |
| Suppliers who send dunning notices | On receipt of the notice | A past-due claim needs an answer before the next run |
| Low-volume, single-invoice suppliers | Quarterly or at year-end | Low risk; check before audit |
| Any supplier with a debit balance in your aging | Immediately | Often a duplicate payment or unapplied credit |
Ask suppliers for statements as of your month-end date. A statement dated the 24th compared with a ledger at the 31st creates differences that are pure noise.
The method, step by step
1. Set the cutoff and scope
Note the statement date and confirm which vendor records it covers. If the supplier has several account numbers or invoices more than one of your subsidiaries or plants, map each supplier account to the right legal entity in your ledger. Run your vendor ledger detail at the same date.
2. Match transactions before comparing totals
Comparing totals first tells you there’s a difference but not where. Match line by line on invoice or credit number, currency, and amount. Keep the supplier’s original reference next to any normalized value (spaces and dashes removed, leading zeros stripped) so someone else can reproduce the match. If the same amount appears twice, ask for another identifier rather than matching on amount alone.
3. Sort the unmatched items
| Difference | Check before changing the ledger |
|---|---|
| Statement invoice missing from AP | Request the invoice; check its PO, receipt, or approval, and the intake queue |
| Credit missing or still open | Find the credit memo and confirm whether it was applied to the intended bill |
| Paid bill still open on the statement | Send the remittance reference; check when the supplier posted the payment |
| Same reference appears twice | Compare the original invoice, PO line, and payment history before approving either |
| Receipt without a recorded bill | Follow the receiving record; decide whether the bill is expected, missing, or disputed |
| Short payment you made on purpose | Find the dispute or debit memo that supports it and send it to the supplier |
4. Build the bridge
Reconcile from the statement balance to your ledger balance with each difference listed. If the bridge doesn’t close, there’s an item you haven’t found yet.
5. Assign and follow up
For each unmatched line, record the amount, likely cause, the evidence still needed, who can supply it, and when you will check back.
Worked example (illustrative)
The supplier’s statement at 30 September shows $86,420. Your AP ledger for that supplier at the same date shows $76,595. The difference is $9,825.
| Item | Effect | Running balance |
|---|---|---|
| Supplier statement balance | $86,420 | |
| Your payment sent 29 Sep, not yet posted by supplier | −$9,600 | $76,820 |
| Invoice on statement, not in AP | −$3,875 | $72,945 |
| Supplier credit memo on statement, not recorded in AP | +$1,250 | $74,195 |
| Bill recorded twice in your ledger | +$2,400 | $76,595 |
| AP ledger balance | $76,595 |
The net of the four items is $9,600 + $3,875 − $1,250 − $2,400 = $9,825, which matches the difference. Each item gets a different action:
- Payment in transit ($9,600): timing. Send the remittance reference and confirm it appears on the next statement. No entry.
- Missing invoice ($3,875): request the invoice and check the PO and receipt. Don’t record a bill from the statement alone. If the goods were received before cutoff, the controller decides whether it belongs in the period’s accruals.
- Unrecorded credit ($1,250): get the credit memo, record it, and apply it to the bill it relates to.
- Duplicate bill ($2,400): confirm with the source documents and void the duplicate before the next payment run. If it was already paid twice, it becomes a recovery item.
Check credits in more than one place
A credit can be recorded but not applied, applied to the wrong bill, or applied twice, so a single lookup rarely settles a credit difference.
In NetSuite, Oracle documents that a vendor credit can be applied on the credit transaction itself or on a payment transaction. When the statement and your ledger disagree about a credit, check both places before treating it as missing. Oracle’s vendor credit guide
In any ERP, look at three things for a disputed credit:
- Was the credit memo recorded at all?
- If recorded, is it applied, and to which bill?
- Did someone also reduce a payment manually for the same amount, so the credit was taken twice?
The third case means you underpaid the supplier by the credit amount, and it will show up on their next statement as past due. Returns, rebates, and debit memos each create credits with their own trail; see supplier rebates, returns, and debit memos.
How this works in NetSuite
| Statement difference | What to inspect in NetSuite |
|---|---|
| Supplier shows a bill you can’t find | Search by vendor, reference, and amount; then check the intake queue and PO |
| Supplier shows a credit | Open the credit and check whether it was applied on the credit or on a payment |
| Supplier still shows a paid invoice | Compare the payment date and remittance with the supplier’s posting date |
| Same reference appears twice | Inspect the source documents and payment status before approving either entry |
Check the subsidiary on each record if the supplier invoices more than one. A bill posted to the wrong subsidiary can make one entity look short and another look overpaid. For NetSuite bill handling more broadly, see the NetSuite AP and AR guide.
Manufacturing: receipts without bills
In a plant, a frequent statement difference is goods received and billed by the supplier but not yet recorded by AP, often because the bill is stuck on a quantity or price mismatch. The statement shows the invoice; your ledger shows only a receipt accrual. Follow the receiving record to the bill and find out why it hasn’t posted. That work overlaps with your receipt accrual review; see GR/IR and receipt accrual reconciliation.
Using the results at the payment run and at close
Before the payment run, review duplicates and unapplied credits first. Both change what you should pay this week. A supplier on the dunning list with an unapplied credit may not be owed what they think.
At close, separate ordinary timing differences from items that need an accounting decision. A missing invoice for goods received in the period may need an accrual. A supplier credit you haven’t recorded may reduce expense. Keep the explanation and evidence with the reconciliation so the reviewer, and later the auditor, can follow it. The month-end close guide covers how this fits the wider close.
What goes wrong
- Different cutoffs. The statement and the ledger are a week apart, and the team spends hours chasing timing.
- Booking from the statement. AP records a bill because it appears on the statement, without the invoice, PO, or receipt. That’s how duplicates and unsupported charges get in.
- Matching on amount alone. Two invoices of the same amount get crossed, and the real difference stays hidden.
- Unresolved list without owners. The same items appear month after month.
- Debit balances ignored. A vendor with a negative balance often means a duplicate payment or a credit nobody applied. See duplicate payments and vendor master controls.
Before you sign off the reconciliation
- Request statements dated at your month-end, not the supplier’s billing date
- Bridge closes with no unexplained remainder
- Duplicates and unapplied credits cleared before the next payment run
- Missing invoices for received goods flagged for the close accrual review
- Remittance details sent to the supplier for payments they haven’t posted