Streamline your supplier relationships with AI.
Pay your suppliers on time. Karini AI agents classify each blocked invoice, ask the right party, and check the reply twice: does it reconcile, and does it meet your SOP?
- Written for
- AP Manager
- Also in the room
- Controller and procurement lead
- Governed by
- Accounts Payable Invoice Exception SOPAP-OPS
The invoice isn't the problem. Gathering the context is.
Missing POs, price and quantity variances, and charges with no reference all block payment.
Each needs a different answer from a different party, while a clerk rebuilds the context by hand and the invoice ages.
Two checks, because a reply can add up and still fall short.
A corrected price can fix the math and still lack what your SOP requires, such as a PO confirmation or a customs number.
Karini AI runs both checks and shows both results. That's what auditors look for.
| Exception type | What the agent needs | Asked of |
|---|---|---|
| Missing or unmatched purchase order | Purchase order number, and a purchase order confirmation statement | Vendor |
| Price variance | Corrected unit price, and the corrected line amount | Vendor, then the buyer who created the purchase order |
| Quantity or goods receipt mismatch | Corrected quantity, corrected goods receipt quantity, and the goods receipt confirmation number | Internal, receiving and the buyer |
| Freight and accessorials | Freight amount, carrier name, and the carrier rate reference | Vendor or carrier |
| Customs and duty | Customs amount, customs declaration number, and the jurisdiction | Vendor or customs broker |
| Fuel surcharge | Surcharge amount, the fuel clause reference, and the applicable period | Vendor or carrier |
| Miscellaneous charges | Charge amount, charge description, and the named approval authority | Internal, the charge owner |
| Tax determination | Corrected tax amount, corrected tax rate, tax code, and tax jurisdiction | Internal, tax, with the vendor where the invoice is wrong |
The agents, in the order they run.
Two agents, one on each side of the wait. The first classifies the exception, gathers the PO, receipt and contract price, and asks the right party, with a deadline.
The second reads the reply, records where each corrected value came from, runs both checks and proposes a resolution.
See it in action.
A blocked invoice opens with the PO, contract price, exception type and the query sent to the vendor. The reply arrives, the corrected price is extracted with its source, and both checks report.
The reviewer approves, and the approval is logged before the invoice posts.
How to get started.
Four steps. Only the first needs your process owner.
Review your SOP with a Karini AI engineer
Our forward deployed engineer works with your process owner and queue team to turn your SOP into a clear spec: rules, thresholds, approval levels and gaps.
The gaps matter most. Where your SOP is silent, the queue is being worked from memory.
You bring
The SOP that governs the process today, in whatever state it's in.
Connect the workflow and your ERP
Your SOP becomes the workflow the agents follow. We connect through APIs, governed screen access where there's no API, and email intake.
Your ERP stays the system of record. Nothing is migrated or replaced.
You bring
An environment to connect to, and the person who owns access.
Test against your own history
Every rule runs on your past exceptions first. You see which rule each case hit, and fix the SOP where it's wrong.
Fixing it here costs an SOP edit, not a reversal.
You bring
A sample of closed cases, including the awkward ones.
Deploy to production
Live in your environment, behind your approval levels, with the audit trail on from day one.
The next use case starts at step one with its own SOP, not a new project.
Bring your SOP. We'll run it against your queue.
Pick one use case. If the rules are written down, agents can follow them. If not, we write them together in the first session.
