If accounts payable were honest, exception handling would be the job. Everything else is just admin around it.
Straight-through invoices are easy. They flow. They behave. They barely need you. But exceptions - that’s where time disappears. That’s where bookkeepers earn their keep. And that’s where most invoice automation tools quietly tap out.
You know the feeling. An invoice hits the inbox and something’s off. The total doesn’t match. The tax looks wrong. The supplier changed the layout again. Or worse, it’s freight: multiple accounts, multiple tax treatments, no PO in sight. So you pause. You investigate. You message someone. You wait.
Multiply that by 50 invoices a week and suddenly your “automation” tool is just a document inbox with extra steps. Understanding the real cost of manual AP makes the scale of this problem visible.
What does “exception handling” mean?
Exception handling is everything that stops an invoice from being processed cleanly. It’s not just errors. It’s uncertainty. Any time a human has to stop and think, ask, check, or chase - that’s an exception.
Most bookkeeping teams don’t track this time. They just feel it: the drag, the backlog, the late nights. And exceptions don’t arrive evenly. They cluster. They spike at month-end. They show up when you’re already busy. That’s why they hurt.
The Most Common AP Exceptions
1. Missing or mismatched purchase orders
The invoice says PO 4567. The PO says a different amount. Or there’s no PO at all. Or it exists but no one can find it. Now you’re checking emails, ERP, accounting system, Slack, someone’s inbox.
Typical resolution time: 5 to 20 minutes per invoice. Longer if the approver is offline.
PO data usually lives somewhere else. Most invoice automation tools extract the invoice but don’t actually reason about the mismatch, so the bookkeeper becomes the detective.
2. Freight invoices with multiple accounts and tax treatments
Ask any bookkeeper what invoice type they dread. Freight always comes up. One invoice, multiple shipments, some GST-free, some taxable, some to COGS, some to clearing, some to landed costs. OCR might grab the total but it won’t understand the split.
Typical resolution time: 10 to 30 minutes per invoice. Sometimes longer.
This requires context: what was shipped, where, under what incoterms, whether GST applies to international legs. Most tools weren’t built with physical goods logic in mind.
3. Incorrect or inconsistent tax coding
Tax errors don’t always look like errors. The invoice “looks” right, but GST is applied where it shouldn’t be, or missing where it should be, or split across lines inconsistently. If you miss it, the BAS pays the price later.
Typical resolution time: 5 to 15 minutes per invoice.
Tax rules depend on supplier location, goods type, service type, and sometimes history. Simple automation can’t infer that.
4. Supplier invoice format changes
A supplier you’ve processed hundreds of times suddenly tweaks their layout - new columns, new descriptions, new totals position. Now the extraction breaks. Fields map incorrectly. Line items merge.
Typical resolution time: 3 to 10 minutes. Unless it cascades across dozens of invoices.
OCR systems rely on patterns. Suppliers don’t care about your patterns. And most tools don’t adapt quickly without manual intervention.
5. Duplicate invoices and credit confusion
Same invoice number, slightly different total. Or a credit note that looks like a bill. Is it a duplicate? A correction? A partial credit? You don’t want to double-pay, but you also don’t want to block real bills.
Typical resolution time: 5 to 15 minutes.
Duplicate detection is fuzzy, especially when suppliers reuse invoice numbers or issue adjustments mid-month.
6. Approval bottlenecks
The invoice is fine. The coding is fine. The system is fine. But the approver is busy, on leave, or just slow. So the invoice sits.
Typical resolution time: Anywhere from a day to two weeks.
This isn’t a data problem. It’s a workflow problem. And most tools stop at “sent for approval” and call it done.
The Hidden Cost No One Calculates
Say a bookkeeper processes 300 invoices a month. If even 30 percent are exceptions, that’s 90 invoices. If the average exception takes 10 minutes, that’s 900 minutes - 15 hours every month. Almost two full workdays spent not on bookkeeping, but on fixing broken flows. And that’s conservative.
Scale that across a practice, or an e-commerce business with freight-heavy operations, or a wholesaler juggling multiple entities. Suddenly exception handling isn’t a side task. It’s the workload. Businesses processing wholesale and distribution invoices at volume feel this acutely.
Why do most invoice automation tools struggle here?
Tools like Dext and Hubdoc do a solid job capturing documents. But exception handling isn’t about capture. It’s about judgment - understanding why something doesn’t line up and what to do next.
Most tools follow a simple path: extract, push, let the human fix the rest. Which means the messiest invoices still land squarely on the bookkeeper’s desk. That’s not a failure of effort. It’s a limitation of design.
Exception handling is also cognitively expensive. Each exception forces context switching - from routine processing to problem solving, from autopilot to focus mode. You have to remember supplier history, tax rules, past decisions, client preferences. And because exceptions are unpredictable, you can’t batch them cleanly. That’s why even a few exceptions can make a day feel heavy.
What Better Exception Handling Looks Like
Good exception handling doesn’t mean eliminating exceptions. It means catching them early, classifying them correctly, giving the bookkeeper context rather than just data, and reducing the thinking required to resolve them.
That’s where accounting AI starts to matter - not just OCR, not just extraction, but systems that understand confidence, patterns, and risk:
- Flagging a freight invoice because it doesn’t match known freight patterns
- Suggesting likely account splits based on prior invoices
- Highlighting tax treatments that differ from historical behaviour
- Escalating only the truly uncertain cases for review
When that happens, the bookkeeper isn’t fixing everything. They’re supervising. That’s a very different job.
The Real Buying Decision
When bookkeepers say “this tool saved me time,” they’re rarely talking about straight-through invoices. They’re talking about exceptions - how fast they could resolve them, how little thinking was required, how few emails they had to send.
That’s why demos that only show clean invoices miss the point. The freight bills, the messy supplier PDFs, the multi-entity invoices - that’s where trust is built.
More bookkeeping firms are starting to evaluate tools differently. Not “does it capture invoices?” but “how does it behave when things go wrong?” Because things always go wrong. And as invoice volumes increase, especially for physical-goods businesses, exception handling becomes the constraint - not headcount, not clients, but cognitive load.
Exception handling is not a corner case. It’s the core of accounts payable. If you’re evaluating invoice automation, don’t ask how many invoices it can process. Ask how it handles the ones that don’t behave.
For more on how Pulsify handles validation and exception review, see the feature overview.
Sources: ACCC Targeting Scams Report 2024 · ATO record-keeping for business
Further reading: Best AP Automation Software Australia 2026 · What a Modern AP System Needs to Do · The Real Cost of Manual AP