Nanonets Platform:Exception Management

Exceptions handled.
Nothing falls through.

When an agent hits a new exception, it stops and pushes all relevant context to the relevant reviewer.

Exception Queue3 pending
AP Agent
Invoice #84291AP Agent

Price mismatch: PO says $4,200, invoice is $4,890

Pending
Agent context
Source: Acme_Invoice_84291.pdf · Vendor: Acme Corp · Matched PO: PO-2024-0441
Customer PO #3341Order Agent

“CUST-9912” not found in product catalog

Pending
Invoice #84187AP Agent

Duplicate invoice · Resolved 4 min ago

Resolved

How it works

Flag, route, resolve, resume

01

Agent flags it

When an agent hits a case it can't resolve on its own, such as a data mismatch, a missing field, or an approval threshold, it creates an exception instead of guessing or stopping.

02

Route to the right person

Exception type, dollar value, and document source determine who gets it. The right reviewer is notified directly, whether via Slack, Teams, email, or any channel they prefer.

03

Review with full context

Reviewers see the document, what the agent extracted, what went wrong, and what decision is needed. No hunting for context across systems.

04

Agent resumes

Once resolved, the agent picks up exactly where it stopped. Resolution logic feeds back so similar cases are handled automatically in future runs.

Exception types

Three kinds of exceptions, handled intelligently

Extracted fields
VendorAcme Corp
PO NumberNot found
Amount$4,890
Data exceptions

The data is wrong or missing

A field couldn't be extracted, a SKU has no match in the catalog, or a vendor name doesn't align with master data. The agent stops rather than proceeding on bad input.

SKU not foundDuplicate invoiceMissing PO numberVendor mismatch
Extraction confidence
Acme Corp. LLCbbox
Confidence score62%
0%Threshold: 85%
Low confidence

The data is present but uncertain

All extractions are anchored to document coordinates via bounding box and validated against context graph rules. When confidence falls below your threshold, the agent flags for review rather than guessing. Nothing is passed downstream silently.

Below thresholdAmbiguous layoutConflicting valuesUnclear field
Approval check
Invoice amount$14,200
$0Limit: $10,000$14,200
Requires manager approval
Approval gates

The data is right, but a human must decide

Business rules require sign-off before the agent can proceed. Invoice over limit, new vendor not yet onboarded, contract terms outside standard. The agent stops and waits.

Invoice over limitNew vendorNon-standard termsPrice variance

Why not a generic queue

Generic queues lose context. This one preserves it.

Generic task queues
Exception Management
Routing
Manual assignment or round-robin
Routed by exception type, value, and document source
Context for reviewer
None — reviewer hunts for the document and data
Document, extracted data, and agent notes delivered automatically
Notifications
Email to a shared inbox
Slack, Teams, email, or any channel the reviewer prefers
Agent behavior
Process stops until manually restarted
Agent resumes automatically once the exception is resolved
Works across agents
Separate queues per tool or workflow
One layer across every pre-built and custom agent you build

See it run on your process, with your documents.

Start free. No credit card. Or talk to our team about your workflow.