Accounts payable is where a document pipeline pays for itself fastest and where a silent mistake costs the most. Tessera is built around that asymmetry: it reads quickly, it says how sure it is, and it refuses to guess on the fields that move money.
What the agent does with an invoice
An invoice arrives at a workflow address or lands in a storage folder. The agent reads the supplier, number, dates, line items, tax and totals, then looks up the purchase order it references and compares quantities and prices line by line. A match inside your tolerance becomes a draft ledger entry with the original attached.
Anything that does not match is not rejected; it is explained. The review lane shows the page region, the extracted value, the expected value and the rule that held it, so a reviewer answers one question instead of rereading the invoice.
The fields that deserve a second look
Bank details are the classic target of invoice fraud, so Tessera treats a changed account as its own category. It compares every extracted account to your vendor master, and a mismatch is always held, whatever the confidence score. A blurry digit and a deliberately altered one look the same to a model; they must not look the same to your payment run.
Duplicates, credit notes and partial deliveries
- Duplicates are detected on supplier, number and total across a window you choose, including near-matches such as
INV-20418andINV20418-A. - Credit notes are linked back to the invoice they reduce, and the ledger entry carries the negative amount.
- Partial deliveries are matched against open order lines, leaving the remainder open instead of failing the whole invoice.
Rolling it out
Most teams begin with one high-volume supplier group and a review threshold of 0.90. After two weeks they look at what landed in review, tighten the schema for the fields that kept slipping, and move the threshold. The audit log shows every decision, so the controller can answer an auditor’s question with a link instead of a spreadsheet.