We've automated accounts payable. We've automated invoicing. Payroll practically runs itself. But somehow, in 2026, posting a payment against an open invoice in QuickBooks Online is still a manual, click-heavy grind. If you're a bookkeeper, you already know exactly what I'm talking about.
According to DocuClipper, 86% of SMBs still manually enter invoice data (2025). That stat covers AP, AR, and everything in between. The Receive Payment step in QBO sits right in the middle of that problem, and it's one of the most tedious things we do every week.
This post is bookkeeper-to-bookkeeper. No pitch to business owners, no "why you need a professional" angle. Just an honest look at a workflow that hasn't kept up.
TL;DR: QBO's Receive Payment workflow forces bookkeepers to manually match remittances to open invoices, one at a time. With 86% of SMBs still doing manual data entry (DocuClipper, 2025) and the average manual invoice taking 10-15 minutes to process, the bottleneck is real. The fix isn't working faster. It's removing the data entry entirely.
What does the Receive Payment workflow actually look like?
Manual bookkeeping tasks take an average of 10-15 minutes per transaction (DocuClipper, 2025). For the Receive Payment workflow specifically, that estimate is generous. The actual process involves more steps than most people outside bookkeeping realize.
Here's what a single payment posting looks like in practice:
The step-by-step reality
You get a remittance. Maybe it's a PDF attached to an email. Maybe it's an Excel file. Maybe the client just wrote the invoice numbers in the body of the email. You open QBO. You search for the customer. You click Receive Payment. Now you're looking at a list of open invoices.
You cross-reference the remittance against that list. You find the matching invoice number. You enter the amount. You save. Done, right? That's one invoice on one remittance.
The batch version is worse
Now imagine a remittance with 15 line items. That's 15 lookups. Fifteen times scrolling through open invoices, matching numbers, entering amounts. Some invoices are on page two of the list. Some have numbers that don't quite match what the client wrote.
I have clients who send 30-40 payments a month. Each one with multiple invoices. The math isn't complicated: 40 payments at 10-15 minutes each is somewhere between 6 and 10 hours a month. On one client. That's not bookkeeping. That's data entry. And we're supposed to be past this by now, aren't we?
The real cost isn't just time. According to DocuClipper, the average cost of processing a single invoice manually is $15 (2025). Multiply that across a full client book and you start to see why this workflow deserves attention.
Why hasn't Intuit fixed the Receive Payment workflow?
Intuit's 2025 Accountant Technology Report found that 95% of accountants have adopted some form of automation. But only 46% have automated AR/AP processes, and just 43% have automated data entry. The gap between adoption and actual workflow coverage is wider than it looks.
QBO optimizes for collection, not posting
Think about what QBO's AR automation actually does. It sends invoices. It accepts online payments. It fires off automatic reminders when invoices go past due. All of that helps the business owner get paid faster. That's valuable. But none of it helps the bookkeeper record that payment once it arrives.
The Receive Payment screen hasn't meaningfully changed in years. It still assumes a human will open it, find the right invoices, type in the amounts, and click Save. The automation stops the moment the money lands.
The bookkeeper is treated as the bottleneck
Here's what's frustrating. Intuit's design assumes we're the slow part of the system, and the solution is to make us click slightly faster. A better search bar. A slightly cleaner invoice list. But the fundamental model - human opens remittance, human matches to invoices, human enters data - hasn't changed.
Intuit optimizes for the business owner's experience of getting paid. The bookkeeper's experience of recording that payment is treated as solved. It isn't. The 46% AR/AP automation stat from Intuit's own survey mostly reflects invoicing and collections tools, not payment application. The posting step sits in a dead zone between what QBO automates and what third-party tools address.
What does a remittance actually look like?
Roughly 39% of invoices contain errors (DocuClipper, 2025). Remittances are worse. They're created by the payer, not the bookkeeper, and they come in every format imaginable.
The format problem
One client sends a clean PDF with invoice numbers, amounts, and a total. The next sends an Excel spreadsheet with their internal reference numbers. A third pastes everything into the body of an email. And then there's the client who photographs a check stub with their phone and texts it over.
Every format requires a different reading strategy. There's no standard. No consistency. You're a human parser running different extraction logic for every client.
The matching problem
Even when the remittance is clean, the matching isn't. The client writes "Inv 1847" on their remittance. QBO shows "INV-1847." Or they reference a PO number that doesn't appear anywhere in your invoice records. Or they combine two invoices into one payment line and you have to split the amounts manually.
The edge cases are the normal cases
Partial payments. Short pays. Overpayments. Credits applied. These aren't rare. For bookkeepers managing construction companies, medical practices, or any B2B operation with complex billing, these are Tuesday. Each one requires judgment. But the data entry around that judgment - finding the invoice, entering the amount, calculating the remainder - doesn't require a human at all.
So why are we still doing it by hand?
What would a better payment posting workflow look like?
The AR automation market is projected to reach $3.8 billion in 2026, up from $3.4 billion in 2025 (Mordor Intelligence). That's real money flowing into the problem space. But almost none of it reaches the bookkeeper sitting in QBO with a stack of remittances.
The workflow that should exist
Upload the remittance. Any format - PDF, Excel, CSV, image, forwarded email. The system extracts the payer name, invoice numbers, and amounts automatically. It matches those against open invoices in QBO. You review the matches, approve with one click, and the payments post to Undeposited Funds.
That's it. The bookkeeper reviews and approves instead of entering and searching. The judgment stays with you. The data entry doesn't.
Why doesn't this exist yet?
The tools being built for this $3.8 billion market are designed for enterprises running NetSuite, SAP, or Sage. They assume ERP-level data structures, API access that's already configured, and IT departments to manage the integration. Bookkeepers running 5-20 QBO files? Nobody's building for us. The market is big enough to attract investment, but the investment flows to enterprise buyers with enterprise budgets.
According to DocuClipper, 56% of respondents spend 10 or more hours per week processing invoices (2025). That's not an enterprise-only problem. That's a bookkeeper problem. And it needs a bookkeeper-shaped solution.
We built the fix
According to DocuClipper, 85% of business owners say data entry and reconciliation hurt their growth (2025). We felt the same pain from the bookkeeper side. So we built a tool to fix it.
Ground Control Payments came out of our own client work. We hit this wall - the same one described in every section above - and built a way through it. Upload a remittance, extract the data automatically, match it against open QBO invoices, review, approve, post. The bookkeeper stays in control. The data entry goes away.
It's not a platform. It's not a suite. It's one tool that does one job: get payments out of remittances and into QBO without the manual grind. Bookkeepers are already using it in production.
If you're a bookkeeper who's tired of the Receive Payment workflow, Ground Control Payments fixes it. Try it free - 10 uploads, no credit card required.
Want a monthly heads-up on what to watch in your books? The Monthly Numbers Check-In is one short email a month - plain-English tips, seasonal reminders, and a free checklist of 5 numbers every business owner should check every month. No spam, no sales pitch.
Frequently asked questions
Can't you just use QBO's batch import for payments?
QBO's import tools handle transactions like bank feeds and journal entries. They don't handle payment application, which is the process of matching an incoming payment to specific open invoices. There's no built-in way to upload a remittance and have QBO apply payments across multiple invoices automatically. The Receive Payment screen is still a one-at-a-time, manual process.
What about using the QBO API directly?
The QuickBooks Online API does support creating payment objects programmatically. But the API is just the delivery mechanism. Someone still has to build the extraction layer (reading remittances in different formats), the matching layer (finding the right invoices despite inconsistent numbering), and the review interface. The API alone doesn't solve the problem. It's the last 10% of the solution.
How is this different from AR automation tools like Tesorio or HighRadius?
Most AR automation platforms focus on the collection side: dunning, cash forecasting, payment portals. They help businesses get paid faster. They don't help bookkeepers record those payments once they arrive. And they're priced for mid-market and enterprise companies, not independent bookkeepers managing QBO files. Ground Control Payments focuses specifically on the posting step that these tools skip.
If your QBO file needs cleanup before you can even think about automation, check out our guide on how to clean up messy QuickBooks books.
How much time does manual payment posting actually waste?
With 10-15 minutes per transaction (DocuClipper, 2025) and clients sending 30-40 payments monthly, a single client's payment posting can consume 6-10 hours per month. Across a full book of clients, it's often the single largest time sink that isn't billable work. And because it's repetitive data entry rather than actual bookkeeping judgment, it's the most obvious candidate for automation.
The Receive Payment workflow is broken. Here's what's next.
The core problem is simple. Nobody's been building for the bookkeeper. The AR automation market is growing to $3.8 billion (Mordor Intelligence), but the investment goes to enterprise tools. QBO's own automation stops at collections. The posting step, the part we actually do every day, sits untouched.
That's changed. If you've felt the friction of manual payment posting, you're not alone. And you don't have to keep grinding through it.
Try Ground Control Payments free - 10 uploads, no credit card.