By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
All demos
Workflow orchestration

Three-way match on autopilot

Finance · Accounts payable · 1:40

Demo · fictional organization · real working software

The problem

Vendor invoices are still matched to purchase orders and goods receipts by hand, and the exceptions wait until someone has time for them.

How it's resolved

Claude reads each vendor invoice, whatever its layout or wording, and the written AP policy it must follow. Code matches every line against the purchase order and the goods receipt, in whole cents. For each exception, Claude explains it and drafts the credit request from the match's own figures, and a check rejects any amount the match did not compute. Nothing is recorded until the AP clerk approves.

What you'll see

  1. 01Twelve invoices from four vendors land in the AP inbox, each in its own layout
  2. 02Claude reads them all in seconds: nine match, three are exceptions
  3. 03One bills 40 cases of romaine; the receiving dock logged 36, and Claude drafts the credit request
  4. 04One approval records the invoice, the decision and the credit request in Traide; the nine clean invoices go in one click

Under the hood

Each business term in the video, and the Traide building block it runs on.

In the businessOn Traide
VendorSeller, approved on an agreement
Purchase orderOrder, with its PO number
Goods receiptFulfillment
Contract priceProduct price
AP policyPolicy page, read by Claude
ApprovalInvoice, document, order note and seller note
  • Document understanding
  • Policy reading
  • Matching in whole cents
  • Grounded drafting
Strategy call · 30 minutes

Have a problem like this one?

You'll talk to a senior engineer, not a sales rep, and leave with a clear first move — whether or not we work together.