
AP Reconciliation
Vendor Credit Memo: How Bookkeepers Apply Returns and Adjustments to AP (2026)
Credits appear unannounced. Record them wrong once and your AP aging lies to you for the rest of the month.
11 min

It's the 8th of the month. You're closing May for a restaurant client. The owner emails a PDF from their main food distributor. It's a monthly statement. You pull up the AP subledger and start comparing line by line.
Two minutes in, you find a $340 invoice from May 3rd that never made it into QBO. Then a $217 payment from May 19th that posted twice. Then a $95 credit from a returned order that's just sitting on the vendor's books, never applied. Three variances in the first vendor statement you touched.
That's not unusual. That's what happens when bank-feed bookkeeping is the only check on your AP process.
Bank feeds catch what clears your client's account. They don't catch what the vendor says is outstanding, what got double-posted in a workflow slip, or what credit is sitting unapplied on the vendor's side. Vendor statement reconciliation closes that gap. For most small-firm bookkeepers, it runs about 30 minutes per client when you have the right workflow.
What is vendor statement reconciliation?
Vendor statement reconciliation is the monthly process of comparing a vendor's account statement (what the vendor says you owe) against your AP subledger (what your books show as open). The goal is to identify every variance: missed bills that never got entered, duplicate payments, unapplied vendor credits, and billing errors. Small firms running this process on their top 10 recurring vendors catch 3-5% of AP spend in errors per month (roughly $150-$800/month in recoverable overpayments or missed liabilities for a typical $2,000-$15,000/month AP client).
The process has four steps: request, tie, compare, resolve. Each step is specific enough to hand off or systematize. Done consistently, it takes 25-35 minutes for a client with 10 active vendor accounts.
Here's the overview before we go deep on each step.
Step | What You Do | Time |
|---|---|---|
1. Request | Email or portal-download monthly statements from top 10 vendors | 5 min |
2. Tie | Match statement total to AP subledger open balance | 5 min |
3. Compare | Line-by-line diff of statement vs. AP ledger | 10-15 min |
4. Resolve | Categorize and fix each variance | 10 min |
Most vendors send monthly statements automatically if the account is set up for it. Many don't unless you ask. Start by building a list of your client's top 10 vendors by annual spend. Pull this from the AP aging report or a spend summary in QBO.
What to request:
Three ways to get statements:
Frequency and format: Monthly statements are the standard. If a vendor only offers quarterly, request a transaction-level report instead so you can match individual invoices. CSV beats PDF for large accounts because you can compare it against an AP export without manual line counting.
What about automating this? Some accounts payable platforms (Bill.com, Ramp) pull statement data directly from vendor portals. We'll cover tooling options in Step 10.
Before line-by-line work, check whether the ending balances agree at the summary level. This tells you immediately whether you have a big problem or a few small ones.
How to tie:
If they match: You may still have offsetting variances (a missed bill plus an unapplied credit of the same amount), but it's a good sign. Do the line-by-line to confirm.
If they don't match: The dollar gap tells you the scale of the problem before you dig in. A $12 gap probably means a credit you haven't applied. A $1,400 gap likely means at least one missed invoice. Note the variance amount before moving to Step 3.
Common QBO tip: Make sure you're comparing the statement to the AP subledger, not the bank register. The subledger shows what's owed to vendors regardless of whether payment cleared your account yet. That distinction matters for reconciling bills that are entered but not yet paid.
This is where most of the work happens. You're looking for three categories of discrepancy: items on the statement but not in your AP ledger, items in your AP ledger but not on the statement, and items on both with different amounts.
How to run the comparison:
Export the vendor's statement as a CSV (or type up key columns if PDF-only). Export the vendor's open transactions from QBO as a CSV. Sort both by invoice number or transaction date. Diff them side by side.
What you're flagging:
Finding | What It Means |
|---|---|
Statement has invoice; ledger doesn't | Potential missed bill |
Ledger has open bill; statement shows paid | Possible recording error or unapplied payment |
Same invoice number, different amount | Billing error or price dispute |
Statement shows credit; ledger doesn't | Unapplied vendor credit |
Payment shows twice in ledger, once on statement | Possible duplicate payment |
Time-saving shortcut: If the vendor provides statements in CSV, paste both exports into a spreadsheet and use VLOOKUP or MATCH to auto-flag rows that don't pair. For PDF-only vendors, focus on any statement line without a matching QBO transaction number.
Every variance you flag in Step 3 falls into one of four buckets. Each has a specific resolution path.
What it is: A vendor invoice appears on the statement but has no corresponding bill in QBO.
Why it happens: The bill never arrived in the client's inbox, got lost in email, or was routed to someone who didn't forward it. Also happens when vendor invoices mid-cycle and the bookkeeper's monthly import didn't catch it.
Resolution: Request a copy of the invoice from the vendor or client, enter it into QBO with the correct bill date, code it to the right expense account, apply any aging bucket logic for the AP aging report workflow.
What it is: Your AP ledger shows two payments applied to the same invoice (or two bills entered for the same invoice number), but the vendor's statement shows only one.
Why it happens: Double-entry during a sync, a bill paid manually AND through a bill-pay system, or a recurring payment that auto-posted the same month as a manual entry.
Resolution: Confirm with the vendor that only one payment cleared. If the vendor confirms one payment, reverse the duplicate transaction in QBO and request a refund or credit if both payments actually cleared the bank. Cross-check against the bank register before requesting a refund.
What it is: The vendor's statement shows a credit memo on account (from a return, overpayment, or pricing adjustment) but your AP ledger doesn't reflect it.
Why it happens: The credit memo arrived via email and wasn't entered. Or it was entered but not applied against an open invoice. For more on how vendor credits work, see how vendor credit memos affect your AP balance.
Resolution: Locate or request the credit memo. Enter it in QBO (Vendors → Credit). Apply it to the oldest open invoice for that vendor. If no open invoice exists, leave it as an open credit and flag it in your month-end notes.
What it is: The same invoice appears on both the statement and in QBO, but the amounts don't match.
Why it happens: Price changed after PO was issued, quantity discrepancy, incorrect pricing tier applied by the vendor, or a manually entered bill with a typo.
Resolution: Pull the original invoice and purchase order (if applicable). If the vendor's amount is correct and your entry is wrong, edit the bill in QBO. If your amount is correct and the vendor is wrong, contact the vendor to dispute and request a corrected invoice. Document the dispute in the bill memo field.
You can't reconcile every vendor every month. Not at 8+ clients with dozens of vendors each. The 80/20 rule applies directly here: for most small business clients, the top 10 vendors by annual spend represent 75-90% of total AP activity.
How to identify your client's top 10:
Pull a Vendor Expenses by Month report in QBO for the trailing 12 months. Sort by total. The top 10 are your reconciliation targets. Set this list in your client file at year-start and update it in Q3 (spend patterns shift).
Criteria for adding a vendor to the top-10 list:
What about the rest? For lower-spend or sporadic vendors, a lighter-touch check is sufficient: confirm the vendor balance in QBO against any statement that comes in automatically. Don't request statements for vendors with fewer than 3 invoices per year.
Your tooling choice changes how fast you can run the Step 3 comparison.
Manual PDF compare: You download the statement PDF, open the QBO vendor balance detail, and compare line by line. Works fine for vendors with 5-10 transactions per month. Breaks down above 20 transactions. Too slow, too error-prone.
Bill.com auto-match: Bill.com can ingest vendor statements (where supported) and flag discrepancies against recorded bills. It's faster than manual, but it only covers vendors who support Bill.com's inbox or integration. Doesn't catch entries that exist in QBO but are absent from the statement.
Growthy AI-surface: Growthy surfaces statement-vs-ledger discrepancies as part of the month-end workflow. When you upload a vendor statement, Growthy compares it against the AP subledger and flags line-level variances (missed bills, unapplied credits, amount mismatches) without you running the VLOOKUP manually. The comparison is automatic; your job is to review the flagged items and resolve them. It handles the 80% (routine comparison), so you focus on the 20% (judgment calls on disputes and credits). See how the AI-bookkeeping feature set works for more on what Growthy surfaces in the month-end close.
Here's a downstream benefit that most bookkeepers don't connect to vendor statement recon until January. By then, it's too late.
Your vendor statements carry year-to-date payment totals. If you've been reconciling those statements monthly, you have a running confirmed total of what your client actually paid each vendor. When 1099 season arrives, you're not pulling QBO reports and hoping they're right. You've already verified the numbers against vendor-side records twelve times over.
The 1099 filing workflow requires accurate YTD vendor payments to determine who clears the threshold and what goes on each form. Any missed bill or unapplied credit that skews those totals shows up as a 1099 discrepancy: a form that goes out with the wrong amount, or a form that doesn't get filed for a vendor who crossed the threshold mid-year. Monthly statement recon is the cleanest upstream fix for clean 1099s.
It also feeds directly into the accounts payable reconciliation process. The AP reconciliation checklist for month-end close relies on an accurate open-balance figure, which vendor statement recon validates.
For clients with multiple vendor payment methods (ACH, check, credit card), cross-referencing vendor statements with payment reconciliation data gives you a complete picture: the vendor confirms what they received, and your payment records confirm what left the client's account.
Vendor statement reconciliation runs best when it's a scheduled task with a defined trigger, not a reactive fix. Here's how to operationalize it.
Trigger: Add "request vendor statements" as a recurring task that fires the 1st business day of each month for each client on the top-10 list.
Workflow: Request → wait 2-3 business days for receipt → run Steps 2-4 → document findings in a running memo in the client's folder → send a 3-line summary to the client of any action items (disputes to authorize, refunds to pursue, credits to apply).
Client communication: Frame it as a monthly AP health check, not a list of errors. Clients don't need to understand the mechanics. Tell them: "We found a $340 missed bill, a $217 duplicate payment, and a $95 credit. Here's what we're doing with each."
Tracking resolved vs. unresolved: Keep a running spreadsheet or task note per client. Flag any variance that requires client decision (a dispute authorization, a refund request). Don't let variances age past 30 days without resolution.
For a complete picture of how this fits into the AP reconciliation workflow, vendor statement recon is the month-level check that feeds your AP subledger accuracy before you run aging, do the 3-way match, or close the period.
If you've never run vendor statement reconciliation systematically, don't try to deploy it for all 8+ clients in week one. Pick your highest-AP client, pull the statement from their top vendor, and run Steps 2-4 once.
You'll almost certainly find something. A missed bill, a credit sitting idle, a payment posted twice. That finding makes the case for the rest of the workflow better than any explanation.
For reference, explore the AP and bookkeeping glossary if you hit terminology questions as you work through the comparison.
Ready to streamline the comparison step? Get started with Growthy so you spend 30 minutes resolving, not hunting.
Free during alpha. Read-only access. You review every sync.
CPA firm partner who got tired of watching bookkeepers click categorize 500 times a day. Built Growthy to fix it.
View all articles →Growthy is dedicated to helping businesses of all sizes make informed decisions. We adhere to strict editorial guidelines to ensure that our content meets and maintains our high standards.

Credits appear unannounced. Record them wrong once and your AP aging lies to you for the rest of the month.

Most small-biz AP doesn't need three-way match. Here's the actual cutoff and when the overhead finally pays off.
