Checklist

Month-end AP checklist: before and after supplier statements

Q: What order should month-end AP work follow?

Confirm cut-off and post all in-period bills, credits and payments first; then reconcile key vendor statements to AP detail; then tie the AP subledger (aging total) to the AP control account in the general ledger; finish with a written exception log and sign-off package.

Q: How do you prove a supplier statement balance mathematically?

Closing balance should equal opening balance plus period debits (typically bills) minus period credits (payments and credit notes). Any unexplained gap is a reconciling item, not a rounding mystery.

Q: Do I need to reconcile every vendor every month?

Prioritise high-volume, high-value or dispute-prone vendors monthly. Low-volume vendors can rotate on a longer cycle, but the overall AP subledger should still tie to the GL control account at close.

Month-end accounts payable is wider than ticking one vendor PDF. You need a clean cut-off, reliable documents, vendor statement matches where they matter, and a separate check that the AP subledger still equals the AP control account in the general ledger. This checklist puts those jobs in order so timing noise does not look like a real error.

Use this as a close scaffold. For the line-by-line matching method, see supplier statement reconciliation. For diagnosing leftover lines, see the six usual causes of unmatched lines.

What “done” looks like at close

A practical pass/fail bar for AP close (aligned with common close practice):

One agreed cut-off date and time for all AP reports.
Key vendor statements compared to your AP detail, with every material difference classified and owned.
AP aging / subledger total ties to the AP control account in the GL — or the gap is fully explained.
Exception log + supporting PDFs/exports saved for review.

Sage’s AP reconciliation guidance frames the same idea: match your records to supplier statements, and at period-end also confirm the AP subledger agrees with the AP balance in the general ledger (Sage Advice US, Accounts Payable Reconciliation Guide, refreshed 30 Sep 2026). Xenett summarises the three-way tie as vendor statements → AP subledger → AP control (Accounts Payable Reconciliation: Process, Examples, and Best Practices, 6 Feb 2026).

1. Before statements — cut-off and documents

Most “variances” at close are late postings. Fix the window before you tick invoices.

Confirm the AP cut-off (date and, if your team posts intraday, time). Every aging, detail and GL extract must use that same stamp.
Post in-period bills, credit notes and payments that belong before cut-off. Leave genuine late arrivals tagged for the next period rather than backdating to “fix” the statement.
Confirm bank / card / payment-file feeds that affect AP are current for the period (where your process uses them).
Roll forward the opening balance: this period’s opening for each vendor (and for AP overall) should equal last period’s signed-off closing. Sage lists “review your starting balance” as the first process step for a reason — a wrong opening poisons every later tick.
Assemble the document pack before reconciling: vendor statements for your priority list, AP ledger / detail, and Aged Payables (aging) for cash and stale-item review.

2. During close — reconcile statements that matter

You do not need every vendor every month. Prioritise by spend, invoice volume, credit complexity and dispute history; keep a stable “top” list and rotate a few others. Sage notes that not every vendor needs the same attention at the same frequency, while the overall AP balance still needs a proper close review.

Compare closing balances first. If the statement and your AP detail already agree for that vendor, spot-check old open items anyway, then move on.
Align period boundaries before hunting ghosts. A statement that starts mid-month or includes post-cut-off invoices will invent differences that are only timing.
Match by document reference (invoice / credit / payment number), not by amount alone. Offset errors cancel in a total and still leave both books wrong.
Classify every residue before posting a fix: timing difference, missing document, true error, or mapping / posting-method issue. Xenett’s month-end workflow emphasises this classification so you do not “fix” the wrong thing.
Write the reconciling items down (item, amount, whose books, owner, next action). An unspoken difference is not a control.

Bookkeepers who rebuild chronological supplier ledgers in Excel each month often cite the same missing pieces: opening balance, invoices, payments and a running close. That format is what a sendable statement needs when you are proving your side of the account (see community discussion on detailed supplier ledgers with running balance on Xero Product Ideas — treat that thread as demand context, not as a claim about any product’s roadmap).

3. Prove the arithmetic on each statement

A statement is only trustworthy if the running total is internally consistent. Sage’s reconciliation template uses the identity:

Closing = opening + invoices received − payments ± adjustments (credits and corrections sit in adjustments).

In debit/credit terms for a payable account (the form Statemint asserts on every generated statement):

Closing = opening + Σdebits − Σcredits (bills increase the balance; payments and credit notes reduce it). The last running-balance line must equal that closing figure with zero unexplained cents.

Example (illustrative only): opening 1,000.00; one bill 250.00; one payment 100.00 → closing must be 1,150.00. If the PDF footer says otherwise, stop matching lines and fix the opening, period filter or excluded items first.

When you generate a statement from your own CSV/XLSX export, set the opening to last period’s closing, set inclusive period dates, and record what the export deliberately leaves out (drafts, voids, post-period payments). Statemint’s default excluded note is exactly that reminder — it does not auto-filter your ledger; it prints what you decide to disclose.

4. After statements — subledger to GL and sign-off

Tie AP aging total to AP control. Same cut-off, same accounting basis. A mismatch here is often a journal posted directly to the control account, a mis-mapped bill, or an integration lag — not a vendor dispute.
Scan GL detail for direct postings to AP control before you chase vendors for a control-level gap.
Review aging hygiene: stale open invoices, negative vendor balances, unapplied credits. Assign an owner for each material item.
Post corrections only after research, with support attached. Do not invent balancing entries to silence a timing difference that will clear next week.
Package for review: timestamped reports, statement tick work, exception log, posted JEs, and a second-person sign-off when your team size allows (Sage recommends a reviewer separate from the preparer).

Copy-paste checklist

☐ Cut-off date/time agreed; all AP extracts use it
☐ In-period bills, credits and payments posted
☐ Opening balances roll forward from last close
☐ Priority vendor statements collected
☐ Statement lines matched by reference; residues classified
☐ Each statement satisfies closing = opening + Σdebits − Σcredits
☐ AP aging total = AP control (or variance fully explained)
☐ Exception log + close package saved; reviewer signed off

Where a local statement tool fits (and where it does not)

After you export payable detail as CSV or XLSX from your accounting system, a local browser tool can map columns, add the running balance, and print a sendable PDF without uploading the file. Statemint does that path. It does not connect to accounting APIs, does not run OCR on scanned PDFs, and does not replace the GL control tie-out or your judgment on accruals. Text-layer PDFs may import on a best-effort basis — always verify the Date mapping after import; prefer CSV/XLSX when you can.

Frequently asked questions

What order should month-end AP work follow?

Cut-off and posting first; then vendor statement matching for the priority list; then AP subledger-to-GL tie-out; then exception log and sign-off. Reversing that order turns timing differences into fake vendor disputes.

How do you prove a supplier statement balance mathematically?

Closing must equal opening plus period debits minus period credits (payments and credit notes). If the footer disagrees, fix opening / period / excluded items before adjusting individual tickets.

Do I need to reconcile every vendor every month?

No. Prioritise risk and volume monthly; rotate low-volume vendors. Still tie the whole AP subledger to the GL control account at close.

Sources

Sage Advice US — Accounts Payable Reconciliation Guide (refreshed 30 Sep 2026): process order, opening balance, vendor statements, subledger-to-GL, template identity.
Xenett — Accounts Payable Reconciliation (6 Feb 2026): cut-off discipline, variance classification, tie-out triangle.
Xero Product Ideas — detailed supplier ledger / statement (ongoing community request): demand for chronological bills, payments and running balance — cited as workflow context only.