Ask a finance leader whether their AP is automated and most will say yes. Ask how many invoices actually finish without a human touching them, and the number drops fast. The gap between those two answers is exceptions, and in 2026 it is the single biggest bottleneck in invoice automation.

This guide explains what AP exceptions are, why they clog invoice automation in ERP systems, and how Dynamics 365 users remove them with embedded workflow controls.

What is an AP exception?

An AP exception is any invoice that cannot process on its automated path and has to stop for human attention. A clean PO invoice that matches its order and receipt flows straight through. An invoice with a price variance, a missing receipt, no PO reference, or an unclear coding decision falls out of the flow and lands on someone's desk.

The important number is not your straight-through processing rate. It is what the rest looks like. In most AP functions, exceptions are a minority of invoices and the majority of the effort. That is the bottleneck.

Why exceptions bottleneck invoice automation in ERP systems

Most invoice automation is built to handle the easy case well and the hard case badly. Three things turn exceptions into a bottleneck.

First, the automation only covers clean PO invoices. Non-PO invoices, contract and recurring invoices, and anything with a variance were never really automated, so they revert to manual handling the moment reality gets messy.

Second, the automation sits outside the ERP. When the tool that manages the invoice is a separate platform syncing back to Dynamics 365, every exception becomes a two-system investigation. The person resolving it has to reconcile what the automation tool says against what the ERP says.

Third, nothing learns. If the same vendor sends the same badly formatted invoice every month and it fails the same way every month, you have not automated anything. You have scheduled a recurring manual task.

The result is a finance team challenge that headcount cannot fix affordably: more invoices, more entities, more complexity, and an exception pile that grows with all of them.

The common AP exceptions in Dynamics 365

Exceptions are not random. They cluster into a handful of recognizable types, and naming them is the first step to removing them.

Price and quantity variances. The invoice does not match the PO on price or quantity. Most are small and safe to clear automatically, but without tolerance rules every one stops for review.

Missing goods receipt. The invoice arrives before the receipt is posted, so three-way matching cannot complete and the invoice waits.

Missing or wrong PO reference. The invoice cannot be matched to an order because the reference is absent, mistyped, or points to a revised PO.

Non-PO invoices. Utilities, leases, services, and subscriptions have no PO to match against, so they need coding rules rather than matching logic.

Duplicate invoices. The same invoice enters twice through different channels, creating payment risk if it is not caught.

Coding and classification errors. The invoice is captured but assigned to the wrong ledger account, dimension, or project, which surfaces later as rework.

Approval routing gaps. The system does not know who should approve the invoice, so it stalls or routes to the wrong person.

Tax and use-tax handling. Invoices that need use-tax treatment or specific tax logic fall out for manual correction.

How to remove AP exceptions with embedded workflow controls

The fix is not to chase exceptions faster. It is to build controls that resolve them without a person, or route the true edge cases cleanly. In Dynamics 365, the strongest results come from automation embedded inside the ERP rather than beside it, because the controls act on native D365 data with no sync lag and no second system to reconcile.

Tolerance matching. Set price and quantity tolerances so small variances clear automatically and only material ones stop for review. This alone removes a large share of the exception pile.

Rules-based holds and routing. When an invoice does need attention, it should go on hold with a clear reason and route to the right person automatically, not sit in a queue waiting to be noticed.

Pre-coding for non-PO invoices. Apply the correct ledger accounts, dimensions, and projects to non-PO invoices with rules, so they are coded on arrival instead of by hand.

Contract matching for recurring invoices. Recurring invoices like leases and utilities can match against contract criteria and process with no review, which removes a steady stream of monthly exceptions.

Learning from corrections. Automation that studies each correction turns today's exception into tomorrow's straight-through invoice. This is what stops the same failure from repeating every month.

Dynamic approval routing. Route invoices by amount, account, dimension, project, or PO match result, and update the route automatically when an approver changes a coding decision. Approvers should not need an ERP login, and every action should stay logged in Dynamics 365 for the audit trail.

Native reporting on exceptions. Track exception categories, rates, and resolution time on live dashboards built from ERP data. You cannot remove a bottleneck you cannot measure, and reporting tied to the ledger tells you which exception type to fix next.

What good looks like

Removing the exception bottleneck produces measurable results, not just a calmer inbox. In an independent value study developed by Avanade, embedded AP automation in Dynamics 365 delivered up to a 76 percent reduction in invoice processing time compared with standard F&O, alongside stronger control and audit readiness. The full findings are in the Avanade AP Automation Value Report.

This is the design principle behind Truvio AP Automation, which runs inside Dynamics 365 for both Finance & Operations and Business Central. It handles the clean invoices without a person and gives your team the controls to resolve the exceptions that remain, so AP stops being a queue and becomes a process you manage.

Where to start

Run one diagnostic before you change anything. Pull your last month of invoices and sort the ones that did not process automatically by reason. The pattern almost always points to two or three exception types doing most of the damage. Fix those with the right controls, in priority order, and the bottleneck clears faster than a full re-implementation ever would.