Talk to us →AP Exceptions
From mismatch to resolution.
Resolvd identifies invoice issues, investigates the root cause, coordinates with vendors and internal teams, and closes the loop in your ERP.
Talk to us about this workflow →THE PROBLEM
The queue refills faster than the team can clear it.
One health system went live on a new ERP carrying a 28,000-invoice discrepancy backlog. Their team ground it down to a few hundred a month, and the queue still refills within days of every cleanout. Traditional systems surface the exception. The work that follows is still yours.
OBSERVED IN PRODUCTION
What the work actually looks like.
Documented from AP and purchasing teams during implementation. The operating conditions on the left are theirs, not a generic category description.
Today without Resolvd
- 01
No-PO invoices never reach the ERP at all. They stall in the imaging system.
- 02
Buyers search the ERP by hand for a matching PO, described by one team as a needle in a haystack, with a success rate they put at “probably pretty low.”
- 03
When a PO is finally found, nothing syncs. The buyer notes it on the invoice and pushes it back to AP manually.
- 04
Missing receipts, the bulk of all match exceptions, are worked off a system-wide report through manual email chains across several teams.
- 05
One contracted specialist clears every contract-match exception with an override rather than a price correction. PO history looks clean; the leakage only shows up in invoice history.
- 06
Buyers touch only the non-contract exceptions, and mostly accept the invoiced cost as-is.
- 07
Auto-generated POs bypass buyers entirely and issue straight to suppliers, producing duplicate shipments.
With Resolvd the worker owns the loop
- ✓
Invoices arrive directly to the worker and are digitized line by line at intake. No drip folders, no manual keying, no image without metadata.
- ✓
Duplicate and supplier validation run before anything reaches a queue.
- ✓
Approvals route over email on dollar thresholds and your delegation-of-authority rules. Approvers never log into anything.
- ✓
Contract terms are checked against the invoice rather than the PO, where the leakage is actually visible.
- ✓
Cases that can't be resolved route to a defined exception queue with full context, instead of back into an inbox.
- ✓
Approved non-PO invoices batch into one daily export instead of dozens of separate templates.
With no approval workflow on non-PO invoices, the submitter becomes the de facto approver, often without knowing it. At one system, a $5M payment went to the wrong supplier.
Documented during implementationExceptions at an ~11% rate on ~40,000 monthly invoices. After a backlog cleanout, the queue refills within days.
Large regional IDNBuyer time spent working that queue, at roughly 15 minutes of research per invoice.
Same systemShare of invoice volume arriving with no PO. Before Resolvd, no approval workflow of any kind.
Top 25 academic research centerHOW RESOLVD WORKS THIS WORKFLOW
Detect
Find the exception across invoice, PO, receipt, or contract.
Investigate
Gather documents and transaction data.
Determine
Understand the cause and decide the next path.
Act
Take the right action: send requests, create credits, update records.
Coordinate
Communicate with vendors and stakeholders.
Follow up
Persist until responses arrive and issues close.
Update
Write back changes to the ERP and related systems.
Verify
Confirm the outcome and close the exception.
Completed work.
Closed loop.
You stay in control
Approve exceptions, credits, and adjustments where you need to.
See every action, decision, message, and system update.
Unusual cases escalate to your team with full context.
Workers operate only within defined workflows and access.
WORKS ACROSS YOUR SYSTEMS
MEASURE COMPLETED WORK
Outcomes your team can see.
Have this type of work in your queue?
Let’s show you what it looks like when Resolvd owns it.
Talk to Resolvd →