Manual vs automated exception resolution

There are two ways to clear an invoice exception. A person can investigate it, or a system can resolve it by reading the same context that person would. Most enterprises still rely almost entirely on the first. The second is what changes the economics, because it removes the human step from the routine cases while keeping it for the ones that genuinely need judgment.

The distinction that matters is whether the resolution of a failed match still requires a person, since the matching itself has been automated for years.

The manual loop was never designed to scale

Manual resolution is the familiar path. The invoice fails a check. A clerk opens it, reads the purchase order and the receipt, and looks for the discrepancy. If the answer is not on the documents, they email the buyer or the supplier and wait. A reply comes back a day or two later, and they update the record and re-run the match, sometimes clearing it and sometimes starting another round. The work is investigative and depends on context held in other systems and other people's heads.

Manual resolution burns time now and knowledge later

The manual loop does not scale well. Each exception takes real time, the queue grows with volume, and the usual lever is to add clerks or expand an outsourcing contract. It also loses knowledge: the judgment that lets an experienced analyst clear an exception quickly lives in that person, and it walks out the door when they do. The cost of exceptions page covers the full picture.

Rules hit their ceiling fast

The first attempt at automation is usually rules. If a variance is under a set amount, auto-approve. If a supplier is on a list, allow a wider tolerance. Rules help with the most predictable cases and are worth setting. They hit a ceiling quickly, because most exceptions are not uniform enough to encode. Writing a rule for every situation becomes its own maintenance burden, and the long tail of odd cases, which is where most of the time goes, does not fit any rule.

Autonomous resolution reads context the way an analyst does

Autonomous resolution takes a different path. Instead of routing every failed match to a person or trying to pre-write a rule for it, a system reads the same context an experienced analyst would: the purchase order, the receipt, the contract, prior approvals, the supplier's history, and the email trail. It works out what the discrepancy is and resolves the routine cases directly. The genuinely ambiguous ones, and only those, are escalated with the full context attached, so the person who picks them up is not starting from scratch. Pricing is the honest tell here – a vendor that licenses agentic software per seat is planning for people in those seats, and genuinely autonomous resolution has no seats to sell.

Autonomy moves people to the work that needs them

The effect is a shift in where people spend their time. The mechanical exceptions, which make up most of the queue, clear without a person. The AP team moves to the cases that need judgment and to the work of removing root causes, and the same team absorbs far more volume as the business grows. The exception queue stops being the thing that limits how much the operation can handle.

People stay in the loop for judgment alone

Autonomy still leaves work for people. They are reserved for the exceptions that actually need them: a genuine dispute, a supplier problem, a judgment call with no clear precedent. The goal is a system that clears the routine work quietly and brings a person in only when their judgment adds something a machine cannot supply.

Fragment is the autonomous option: it reads the same context an AP analyst would and clears the routine exceptions on its own, escalating only the ambiguous ones. See how it works or request a demo.