Use caseAccounts payable

Supplier invoices

An invoice arrives by email. To pay it, a clerk hunts down the order and the goods receipt, and the day goes into the hunt more than the check.

The invoice is read and linked to its order on arrivalOrder, receipt and invoice are checked line by lineA person settles every exception and releases the payment

The assistantThree-way match

Prices match the order. The receipt shows 480 cartons delivered, and the invoice bills 500. Pallets match on all three documents.

source · order, receipt and invoice
Actions on this invoice
The verdict on the invoice

A gap outside tolerance · the check says which line, with its source

01

Where it stalls today

The short version

The Joliet warehouse signed for 480 cartons on October 29. The invoice that arrived on November 3 bills 500, and asks for payment to an account the company has never used. Neither shows in the arithmetic. They show only against the order, the receipt and the supplier record, and when that match is done by hand it happens after the payment run, or not at all.

With this setup the invoice is read and matched the day it lands. The AI extracts the header and the lines, finds the order and the receipt, and runs the rules finance wrote. Each exception goes to the person who can answer it. The clerk starts from a verdict and its reasons, and keeps the release.

Invoice FA-26-10377.pdfViewer
Read on November 3. The invoice on the left, and beside it the lines that do not agree with the order, the receipt or the supplier record.
Accounts payable, Nov 3Case management
The day's pile, sorted. 141 invoices read before Sandra logs in, and the 37 in the middle carry their reason.

On their own, the screens are what any payables team already uses. The difference is the order they come in: the invoice arrives already matched, each gap reaches the person who can answer it, and a clerk releases the payment on documents that agree. Invoice FA-26-10377 goes through it below and is released the next day.

02

The invoice, read

Invoice FA-26-10377 arrives on November 3. Before anyone opens it, it is read and its supplier checked.

Step 1Intake

The invoice lands next to its order

Summit Packaging sends a PDF to the accounts payable mailbox, like most suppliers. The few paper invoices are scanned by the mailroom. Both feed the same capture chain, and each invoice becomes a case.

The ERP is connected through the API. When a purchase order or a goods receipt is posted, it is filed in the repository under the order number.

Invoice FA-26-10377 · DocumentsCase management
Order and receipt are already filed when the invoice arrives.
Nobody hunts for the receiptThe three documents the match needs sit on one case. The clerk does not open the ERP in another window.
Step 2AI check

Header and lines are extracted

The AI extracts the header: supplier, EIN, invoice number and date, order reference, payment terms and remit-to bank account. Then the lines: 500 double-wall cartons at $1.84 and 12 pallets at $14.50. The order reference links the invoice to order 4500018832 on its content.

Invoice FA-26-10377.pdfViewer
Each extracted field keeps the line it was read on.
The invoice is never keyed inHeader and lines come off the PDF with their source. The clerk reads values on screen and checks the page when a rule asks.
Step 3AI check

The supplier rules stop on the bank details

The first rules compare the invoice with the supplier record. Name and EIN match. The bank account on the invoice belongs to a different bank than the one on file since 2021.

Is the supplier known?Does the EIN match?Is the bank account the one on file?

The status is Attention required. Processing stops on that point: the rule never accepts a new bank account from the invoice itself.

Supplier checksAI console
The check names the record it compared with. A person confirms any change.
A bank change cannot slip throughChanged bank details are the classic route of supplier fraud. Here the invoice stops until someone confirms, and the reason is written down.
03

The match

What was ordered, what was received and what is billed, compared line by line within finance's tolerances. The cartons do not add up.

Step 4AI check

The match finds a short delivery

Order 4500018832 asked for 500 cartons and 12 pallets. The receipt posted by the Joliet warehouse on October 29 shows 480 cartons and 12 pallets. Prices match. The invoice bills 500 cartons: 20 cartons, $36.80, are billed and not received.

The tolerance is part of the rule finance wrote: ten dollars per line.

Three-way matchAI console
Each line shows the three values side by side, and the one outside tolerance.
The gap is found before the payment runTwenty cartons are named with their amount on the day the invoice arrives, while the delivery is still fresh in the warehouse's mind.
Step 5Workflow

The quantity question goes to the buyer

Quantity gaps are routed to the buyer who owns the order. Thomas Garcia receives a task with the three lines. He asks the assistant whether anything else was delivered, then calls the warehouse: the 20 cartons are on backorder for next week.

Task for Thomas GarciaWorkspace
The buyer answers in the task. Accounts payable keeps the decision on the invoice.
The question reaches the one person who knowsThomas does not get an email with three attachments. He gets one task with the lines that differ, and his answer returns to the invoice.
Step 6Reporting

The clerk sees the day's exceptions

Sandra, an accounts payable clerk, opens her home page. One report counts the day's invoices by verdict, another lists the remittance detail changes waiting for a confirmation.

Complete: 98Attention required: 37Not eligible: 6
Accounts payable, Nov 3Case management
The verdict is a column you can sort and filter on.
Each exception has an ownerSandra sees who each invoice waits on. The clean ones are already in her release list.
04

The release

Two holds remain: the quantity and the bank account. Sandra settles both on Wednesday morning.

Step 7Assistant

Approve what was received, ask for a credit memo

Sandra reads Thomas's answer and approves the invoice for the quantity received. She asks the assistant for a message to Summit Packaging. The draft names the invoice, the 20 cartons and the amount. She adds the backorder date and sends it.

Invoice FA-26-10377Case management
The approved amount is Sandra's field. The draft only carries it.
The supplier gets a precise answerOne message with the line, the amount and the receipt behind it. No back and forth to work out what was short.
Step 8Workflow

The new bank details are confirmed by two people

The bank account hold follows the company procedure. Sandra calls the supplier on the number in the supplier record, never the one on the invoice. The supplier confirms and sends a bank verification letter, which she files on the case. Her team lead Oliver gives the second approval.

Remittance details changeCase management
The approval path has two people on it, and the case keeps both names.
For your next audit: if someone asked how a new bank account was accepted last spring, how long would it take to show who checked it?
The riskiest change has a written trailWho called, on which number, which bank letter, who approved. It is on the case, for anyone who asks.
Step 9History

The invoice is released with its full trail

With both holds cleared, Sandra releases the invoice for payment. The ERP reads the approved amount and the due date through the API, and pays it in its next run. The invoice, the order, the receipt, the buyer's answer and the bank letter stay together on the case.

Invoice FA-26-10377 · HistoryCase management
The trail is part of the case, readable by whoever opens it next.
Audit questions are answered from the caseWhat was billed, what was received, who decided what, and when. An auditor reads it on the case.
05

Where each file lands

Order, receipt and invoice either agree, differ on a line, or leave nothing to compare. The verdict says which, and who the invoice now waits on.

Complete

Order, receipt and invoice agree

Quantities and prices within tolerance, supplier details as on file. The verdict lists each match, and the invoice joins the release list.

Then: the clerk checks and releases it for payment.
Attention required

One line needs a person

A short delivery, a price that moved, new bank details. The check says which line, with its source.

Then: the question goes to its owner; the check runs again when the answer or the new document arrives.
Not eligible

Nothing to match against

No order found for the reference, or an unknown supplier. The AI lists what it read and where it looked.

Then: a clerk finds the order or sends the invoice back to the supplier.
Where the AI stops

It pays nobody. It accepts no new bank account. It decides no partial approval. Across the nine steps on this page, every release and every hold is decided by a person, with their own rights and their own trace.

The AI extracts, matches and drafts. The tolerances and the procedure are written by finance, so they hold when the month-end volume arrives.

06

The payoff

One Summit Packaging invoice gave these. Your suppliers, your tolerances and your share of paper will give your own.

0 lineskeyed in from the invoice. Header and lines are extracted with their source.
Day 1when the short delivery is named, before the payment run instead of after it.
2 nameson the remittance details change, recorded on the case with the bank letter behind them.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

The three principles behind those numbers

Zero wasted readingProductivityThe match runs before the clerk opens the invoice. She starts from the lines that differ.
Zero lost exceptionsProcess reliabilityQuestions, answers and bank letters live on the case. Nobody digs through email for it.
Decision supportA person decidesEach verdict cites its line and document. Approval and release stay with accounts payable.
07

For your teams

Payables, finance administration and IT all have a say before invoices are matched this way. Each finds something different below.

Business operations

Accounts payable clerks

Keying and hunting for receipts eat the day, and the real exceptions come last.

  • The invoice arrives read and matched.
  • Each exception says which line, and who it waits on.
  • The question to the supplier is drafted with the right amount.
  • Clean invoices sit in a release list.
Administration

Finance systems administrators

Every tolerance lives in a spreadsheet only one person understands.

  • Tolerances are part of rules written in plain language.
  • Finance edits a tolerance, and the next invoice uses it.
  • Exceptions are routed by owner and by kind.
  • The bank details procedure is a workflow with two approvals.
IT and architecture

CIOs and architects

Another invoice tool means another copy of your supplier data.

  • The ERP files orders and receipts through the API.
  • The ERP reads approved amounts back through the same API.
  • Each AI call is on record, with the model that answered.
  • Your servers or the cloud, whichever finance accepts.

Where to start

With one supplier category and the two rules that matter most: quantity received and bank details on file. One month of invoices is enough to judge it.

Price checks and other categories join the same match afterwards, one rule at a time.

Next step

Match your own invoices

Bring a month of anonymized invoices with their orders and receipts, and your tolerances. We will run the same match on them: the reading first, the release after.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.