Accounts Payable Workflow for Bookkeepers 2026 | Growthy
AP Reconciliation
The monthly AP discipline that keeps vendor ledgers clean and January 1099s accurate, built for bookkeepers managing 8-25 clients.
6 articles
Accounts Payable Workflow for Bookkeepers: 2026 (3-Way Match, AP Aging, Vendor Recs, 1099 Roll-Up)
It's Tuesday morning. You open your email and there's a vendor statement from Office Depot waiting for your client: the landscaping company with 11 vendors and a habit of paying bills in batches whenever the owner "gets around to it."
You pull up the QuickBooks AP subledger and start matching line by line. Three bills from February never got entered. There's a duplicate payment on March 14. Your client paid invoice #4417 twice because the vendor resent it with a different header and the owner approved it again without checking. Two credits from returned supplies in January are sitting on the vendor's ledger but never got applied. The vendor statement shows a balance of $2,840. Your subledger shows $1,190 owed. That's a $1,650 gap before you've even looked at the other 10 vendors.
This is bookkeeper-AP. Not purchase orders, not approval matrices, not three departments signing off on a requisition form. It's you, a vendor statement, a subledger that's drifted, and the quiet knowledge that if you don't catch this now, it'll either blow up a vendor relationship in April or leave a 1099-eligible vendor under-reported in January. This pillar covers the end-to-end AP workflow built for bookkeepers managing 8-25 client portfolios: the monthly discipline that keeps ledgers clean and makes year-end 1099 filing a batch job instead of a fire drill.
What is the AP workflow for bookkeepers?
The bookkeeper AP workflow is the monthly cycle of keeping a client's accounts payable ledger accurate and vendor-ready. It covers five core steps: (1) weekly bill entry and coding to the right GL account, (2) vendor statement reconciliation to catch missed bills, duplicates, and unapplied credits, (3) AP aging review to flag the 0-30/31-60/61-90/90+ buckets, (4) payment authorization and recording, and (5) 1099-eligible flagging at the transaction level. The cadence is weekly bill entry, monthly vendor recon and aging review, and a Q1 1099 batch that draws on the full year's clean data. Bookkeeper AP differs from enterprise AP in one key way: there's no PO system and no procurement gating. The whole job is recon accuracy and 1099 readiness: catching what the owner missed, not approving what the purchasing team requested.
Key Takeaways
Vendor statement recon catches a 3-5% leak rate - missed bills, duplicate payments, and unapplied credits that don't surface in the subledger alone; one unreconciled vendor is all it takes to blow a monthly close.
AP aging beyond 90 days is a vendor relationship signal, not just a reporting artifact; a balance in the 90+ bucket usually means a dispute, a lost invoice, or an owner avoiding a call, and each needs a different fix.
See It Work on Your Data
Free during alpha. Read-only access. You review every sync.
Flag 1099-eligible vendors at onboarding, not December - collect the W-9, set the 1099 flag, assign the default GL account; doing this in December means chasing 8 vendors in a week instead of capturing it once at setup.
3-way match is overkill for sub-50-vendor small business clients - for most bookkeeper clients, a 2-way match (invoice + receipt or invoice + owner approval) is the right level of control; 3-way adds a PO step most small businesses don't generate.
The AP subledger must tie to the GL control account every month - if AP in the subledger doesn't match the AP account on the trial balance, something is posted incorrectly; this tie-out catches coding errors before they compound.
Clean AP data makes January 1099 filing a batch job - every correctly flagged, correctly coded, correctly reconciled vendor transaction feeds the 1099 roll-up automatically; skip the monthly discipline and January becomes a forensic exercise.
The Bookkeeper-AP Workflow at a Glance
Enterprise AP content talks about approval chains and procurement gating. If you're a bookkeeper at a 12-client firm, that's not your world. Your AP workflow has five steps and they repeat every month.
Step 1: Weekly bill entry. Bills come in by email, by mail, sometimes as a photo from the owner's phone. Enter each one within 2-3 business days of receipt. Code it to the right GL account on entry, not at month-end when you've forgotten the context. Mark the due date. Set the 1099-eligible flag if the vendor qualifies.
Step 2: Vendor statement reconciliation. Once a month, request or collect statements from any vendor with more than 2-3 transactions in the period. Match every line to the subledger. Catch missed bills, duplicate payments, and credits the owner accepted but you never entered. This step is covered in detail in Vendor Statement Reconciliation: The Step Most Firms Skip.
Step 3: AP aging review. Run the AP aging report after reconciliation, not before. Review the 0-30, 31-60, 61-90, and 90+ buckets. Flag anything in 90+ for follow-up. Confirm the total ties to the GL control account.
Step 4: Payment authorization. For clients where you handle payments, batch the current period's approved bills. Get sign-off before paying. Record the payment method (check, ACH, credit card) accurately. Credit card payments need to land in the credit card liability account, not an expense account.
Step 5: Monthly close tie-out. AP subledger total must equal the AP control account on the trial balance. If it doesn't, you have a coding error or a transaction that bypassed the subledger. Find it before you move on.
Vendor Onboarding Done Right
Every 1099 problem in January traces back to a vendor onboarding decision made months earlier. The fix is a 10-minute setup conversation at the start of the vendor relationship, not a December scramble.
Three things to get right at vendor onboarding:
W-9 first. Don't enter a single bill for a new vendor without a W-9 on file. For U.S. vendors paid for services, the W-9 gives you the TIN for 1099 filing. No W-9 means potential backup withholding at 24%, which your client probably doesn't want to do and definitely doesn't want to explain. The W-9 collection workflow covers how to make this friction-free for the vendor.
1099 flag at setup. Set the 1099-eligible flag in your accounting software at vendor creation. The threshold is $2,000 for 2026 (previously $600). For any unincorporated vendor receiving payment for services, check the box now. Checking it in December when you're doing the 1099 batch means you've already lost the easy path. You'll be reconstructing eligibility from transaction history. See the full 1099 filing workflow for the annual process this feeds.
Default GL category. Assign the vendor's default expense category at setup. Office Depot defaults to Office Supplies. The electrician defaults to Repairs & Maintenance. This isn't just bookkeeping hygiene. It's reconciliation speed. When you can match 80% of a vendor's transactions on code alone, you're spending your time on exceptions, not data entry.
Bill Entry: Coding for Reconciliation Accuracy
Coding errors compound. A bill coded to the wrong account in January is a misstatement in the P&L, a reconciliation problem in March, and a potential 1099 error in January of the following year.
Three rules that prevent most coding errors:
Match the vendor, not just the category. Every vendor has a primary account. Code deviations intentionally and note why. If your client's HVAC company invoiced for a capital improvement instead of routine maintenance, that's a different account. It should be a conscious decision, not a default.
Catch the credit card. The most common AP coding error isn't a wrong expense account. It's a bill paid on a credit card that gets posted directly to the expense account instead of being entered as an AP bill, paid against the subledger, and then captured in the credit card liability. This creates a duplicate expense and a subledger that never clears. If your client uses a credit card for vendor payments, your AP workflow needs a step for it.
Use the chart of accounts as the source of truth. If a new expense type comes up and you're not sure where it goes, reference the COA before picking the closest-sounding account. Two bookkeepers guessing independently will often pick different accounts for the same type of expense.
Vendor Statement Reconciliation: The Step Most Firms Skip
Vendor statement reconciliation is the AP discipline that most bookkeepers do for one or two large vendors and skip for the rest. It's also the step that catches the 3-5% leak: the missed bills, duplicate payments, and unapplied credits that don't surface in your subledger alone.
The process: request the vendor's statement (or log into the vendor portal). Line-item match against your AP subledger. For each line on the vendor statement, confirm it exists in your subledger with the same amount, the same date, and the same open/paid status.
What you're looking for:
On vendor's statement, missing from subledger: bill was never entered. Enter it now, back-dated to the invoice date.
On subledger, missing from vendor's statement: possible duplicate entry on your side, or a bill the vendor has already credited that you haven't received yet.
Duplicate payments: same invoice number paid twice. Credit the client's account and request a refund or apply it as a credit against the next invoice.
Credits not applied: vendor issued a credit memo you never entered. Enter the credit and apply it to the oldest open balance.
AP Aging: 0-30/31-60/61-90/90+ Buckets and What to Do
The AP aging report is the most useful one-page summary in accounts payable, and the most ignored. Run it after vendor statement reconciliation so the numbers are current.
0-30 days (current): Bills within terms. No action needed other than scheduling payment before the due date.
31-60 days (approaching late): Bills that are past due or approaching late-fee territory. Contact the vendor if there's a payment hold. Confirm whether the client approved the payment. If it's sitting here because the client hasn't approved it, escalate.
61-90 days (late): These need a direct conversation with the client. Why hasn't this been paid? Is there a dispute? A cash flow issue? A lost invoice? Each has a different resolution path.
90+ days (problem bucket): A balance in the 90+ bucket is almost never just a slow-pay situation. It's usually a dispute the owner is avoiding, an invoice the client is contesting, or a vendor they've stopped working with and assumed the balance would go away. It won't. Address each one individually.
One metric to track: the percentage of total AP sitting in the 90+ bucket. If it's above 10% for a client, AP discipline has broken down and you need to reset the process. Full bucket analysis: AP Aging Report: What the Buckets Tell You.
Three-Way Match: When Small Business Actually Needs It
Enterprise AP content treats 3-way match as standard operating procedure: purchase order + vendor invoice + receiving report, all three match before payment is authorized. For a company running $50M in procurement, that process exists for good reason.
For the clients in your 12-firm portfolio? Most of them don't generate purchase orders. The owner orders something, it arrives, they pay for it. The matching question isn't PO-to-invoice-to-receipt. It's invoice-to-approval or invoice-to-receipt.
When 2-way match is enough: Service vendors (contractors, consultants, marketing agencies) where there's no physical receipt. Recurring vendors (utilities, software subscriptions) where the amount is predictable. Any transaction under $500 for a client with no formal procurement process.
When 3-way match matters for small business: Inventory-heavy clients. Construction clients buying materials against a project estimate. Any client where a vendor overbilling is both financially meaningful and plausible. In these cases, match the PO (even an informal email estimate counts), the invoice, and a receiving confirmation before posting the payment.
The practical rule: if your client calls a vendor to order something and the vendor could plausibly bill them for more than what was ordered, that's where 3-way match earns its overhead. Full breakdown: Three-Way Match: When Small Business Needs It.
Vendor Credits and Returns
Vendor credits are the accounts payable equivalent of a bank reconciliation timing difference: they exist, they're real, and they disappear if you don't track them.
When a client returns merchandise or a vendor issues a credit for an overbilling, two things need to happen in the AP module. First, enter the credit memo as a negative bill (or use the credit memo transaction type in your software). Second, apply it against an open invoice. If you enter the credit and never apply it, it sits as an unapplied credit forever and distorts the vendor balance.
Three common scenarios:
Returned merchandise credit: Client returns $340 in materials. Vendor issues a credit memo. Enter it against the vendor, apply it to the oldest open invoice. If there's no open invoice, leave it applied as a credit and note it for the owner. The next bill will net against it.
Overbilling credit: Vendor charged $2,100 but the agreed price was $1,800. Vendor issues a $300 credit. Enter the credit, apply it to the original invoice's remaining balance, confirm the vendor's statement reflects the net.
Disputed charge pending resolution: Don't enter a credit until the vendor confirms it in writing or on their statement. A verbal agreement isn't a ledger entry.
Most bookkeeper clients don't use formal purchase orders. But when they do, the PO and the invoice arrive at different points in the transaction, and they need to be handled differently.
Purchase order: Created before the goods or services are delivered. It's a commitment, not a liability. Don't enter it as a bill. If your accounting software supports open POs, track it there. If not, keep the PO in a pending folder and match it when the invoice arrives.
Invoice: Created by the vendor after delivery. This is the document that triggers the AP entry. When the invoice arrives, match it to the PO (if one exists), confirm the amounts agree, and enter the bill.
The common error: entering the PO as a bill, then entering the invoice when it arrives and creating a duplicate liability. Your AP subledger ends up showing the obligation twice.
For clients who reference email quotes or estimate documents as their POs, treat those the same way: match the estimate to the invoice before entering. If the invoice exceeds the estimate by more than 10%, that's a conversation for the owner before you post. Full doc-matching guide: Purchase Order vs Invoice: AP Timing for Small Business.
The Monthly Reconciliation: AP Subledger to GL Control Account
This step is non-negotiable. The AP subledger must tie to the AP control account on the trial balance at the end of every close cycle. If it doesn't, something is wrong and it compounds.
Run this as the last step in your monthly AP cycle, after vendor statement reconciliation and aging review.
How to do it: print or export the AP aging summary (total of all open balances across all vendors). Pull the AP control account balance from the trial balance. They should match to the penny.
If they don't match, here's where to look:
A bill or payment entered directly to the expense account instead of through the AP module (bypassed the subledger)
A journal entry posted to the AP control account that didn't flow through vendor records
A beginning balance entry that didn't get coded to a vendor
The tie-out also tells you whether your vendor statement reconciliation was complete. If you still have a gap after resolving the items above, at least one vendor's subledger balance is wrong. Full procedure: Accounts Payable Reconciliation: How to Tie Your Subledger to the GL.
1099 Roll-Up: How AP Recon Feeds January Filing
This is where the monthly discipline pays off. If you've done the AP workflow correctly all year, the 1099 batch in January is mechanical. Pull the 1099-eligible vendors, confirm the amounts, file.
If you haven't, January is a forensics project.
The connection is direct: every bill you entered through the AP module (not directly to expense) has a vendor record. Every vendor record has a 1099 flag. Every flagged vendor accumulates a running total of payments by fiscal year. When January arrives, the report is already built. You're reviewing it, not building it.
Three things that break the 1099 roll-up when AP is done poorly:
Bills entered directly to expense accounts. These bypass the vendor subledger and don't accumulate against the vendor's 1099 total. A vendor who received $4,800 in payments might show only $2,100 on the 1099 report because $2,700 was posted directly to an expense account without going through AP.
Vendors with the 1099 flag missing. A vendor setup without the flag checked won't appear in the 1099 report regardless of how much was paid. This is the December scramble problem. You're retroactively setting flags and hoping the totals are right.
Credit card payments not attributed to vendors. Payments made by credit card that weren't run through the AP module don't attach to the vendor record. If your client paid a contractor $3,600 by credit card over the year, and none of those transactions went through AP, the vendor's 1099 total is zero.
The fix for all three: run the full AP workflow every month, not just at year-end. The 1099 filing workflow covers the complete January batch process. AP recon is the input; 1099 filing is the output.
Also worth noting: vendor payments via Stripe, PayPal, or Venmo may qualify for separate 1099-K reporting by the payment processor. Those don't run through your AP module, but they reduce what you report on 1099-NEC. The payment reconciliation workflow covers how to net these correctly so you're not double-reporting the same payments.
Software Stack: Bill.com vs Ramp vs Melio for Bookkeepers
Enterprise AP software (Tipalti, Coupa, SAP Ariba) is built for procurement teams with approval chains. These three tools are what bookkeepers actually use with small-business clients.
Bill.com is the most bookkeeper-friendly option if your client has both AP and AR. The two-way QBO sync is stable. Approval workflows are easy to configure for clients who want to approve bills before you pay. The bill inbox handles email bill capture reasonably well. Downsides: pricing is per user, which adds up when you're managing 15 clients; the multi-client workflow isn't designed for bookkeepers running a portfolio. It's designed for a controller at one company.
Ramp is the right choice when your client's primary payment method is credit cards and the owner wants spend controls. It handles bill payment but its core strength is corporate card management with built-in receipt matching and policy enforcement. If you're tired of chasing receipts for a client's card transactions, Ramp solves that. The AP module is lighter than Bill.com.
Melio works well for smaller clients with simple AP: one-person businesses or clients with fewer than 20 vendors per month. Free for ACH, fee for credit card payments. The interface is simpler than Bill.com. It syncs to QBO. For clients who don't need approval workflows, Melio is lower friction.
For bookkeepers managing 8-25 clients: you'll likely run different tools for different client profiles. Bill.com for larger clients with more complex AP; Melio for simpler clients with low volume. Ramp only when the client is already card-first and wants spend controls.
What none of these tools do well: they don't flag 1099-eligible vendors automatically or reconcile the AP subledger to the GL control account without manual steps. That's where an AI categorization layer adds actual bookkeeper-time savings. Growthy's AP features flag 1099-eligible vendors at 85% accuracy on first import (90%+ on returning clients), and the monthly subledger tie-out runs as part of the close workflow rather than a separate manual step.
Managing AP Across a Multi-Client Portfolio
One thing enterprise AP content never addresses: you're not managing AP for one company. You're managing it for 12.
That changes the workflow in a few ways.
Standardize the monthly cadence. Every client gets the same five-step AP cycle on the same schedule within their close window. You're not reinventing the process for each client. You're running the same process at 12 different companies. Variations in software or client behavior are accommodated within the framework, not by abandoning it.
Build checklists, not habits. Habits fail when you're context-switching between clients at different stages of close. A written AP close checklist for each client (bill entry complete, vendor statements collected, aging reviewed, GL tie-out done, 1099 flags confirmed) takes 2 minutes to review and prevents the kind of silent error that shows up three months later.
Know which clients need vendor statement recon every month vs quarterly. High-transaction vendors (utilities, main suppliers, recurring service vendors) warrant monthly reconciliation. Low-transaction vendors with stable amounts (annual software subscriptions, quarterly contracts) can run quarterly.
The AP workflow isn't complicated. Five steps, monthly cadence, weekly bill entry. The discipline is in doing all five steps every month, for every client, without skipping the vendor statement reconciliation because it "seems fine."
Bookkeepers who run a clean AP process don't dread January. Their 1099 batch is a report, not a reconstruction. Their vendor relationships stay intact. Their GL tie-outs close clean.
If you want to see how Growthy handles AP categorization, 1099-eligible vendor flagging, and the monthly GL tie-out for bookkeeping firms managing 8-25 clients, get started here. Alpha pricing is $99/mo (5 firm cap). Standard pricing starts at $149/mo annual.
