AI does the work. Controls move the money.
Controlled autonomous accounts payable on IBM watsonx Orchestrate. Seven agents read every invoice, code it and explain the risks. Deterministic controls decide whether money can move, and people own the exceptions.
Invoice in. Payment out, under control.
A new document is read, coded and decided in roughly 30 to 60 seconds, on real scanned invoices and Excel bills.
Arrive
Mailbox or clinic uploadEvery document is stored and fingerprinted, so a re-sent copy is caught.
Read
Capture AgentType, fields, lines and handwritten receipt notes, each with a quote and a confidence.
Code
Coding AgentGL per line, clinic, TDS and GST treatment, citing the evidence.
Decide
Policy engine (code)17 exception types, a risk score and four gates. The Risk and Exception Agents explain.
Approve
Maker, checker, DOAPeople clear exceptions. Approvals follow the delegation of authority.
Post
Posting AgentPosts to the ERP after its tool re-checks every control. It cannot pay.
Pay
TreasuryPayment runs happen only in the ERP, to the supplier master's bank account.
Four gates. All four must pass.
Confidence alone never makes an invoice touchless. Everything else goes to a person, with the reason.
Eligibility
A known, active supplier, in a lane the AP lead has given enough autonomy, with no pending master change.
Controls
No control exception: PO, receipt, price, GST, entity, totals and dates all check out.
Risk
Risk score under 40, and no duplicate, bank-change or high-risk flag.
Confidence
Key fields and coding read at 85% confidence or more.
Four invoices. Four outcomes.
Each one behaves the same as any new document. Nothing is special-cased.
A services bill in Excel
Facility services, monthlyAll four gates pass. TDS under 194C is worked out, and it goes straight to the clinic and area managers for approval.
The same invoice, again
Byte-identical copyCaught as an exact duplicate of an invoice already received, before anyone touches it.
"Our bank details have changed"
Bank account on the invoiceInvoice content can never change the supplier master. Two different vendor-master approvers must verify it.
"20PC are Not Received today"
Handwritten on the receipt stampThe note is read against the right line, and the clinic is asked to confirm before payment.
What you'll see.
Follow an invoice from arrival to payment.
Control Tower
Every invoice by stage and lane, touchless rate, exceptions by cause and owner, and payments back from the ERP.
The invoice file
The document beside every field's quote and confidence, coding with evidence, the four gates, exceptions, risk, approvals and audit.
Work Queues
Maker, checker, tax desk, vendor master and clinic queues, with segregation of duties built in.
Vendor Master
Bank changes and new vendors need two different approvers and an independent verification.
Learning & Autonomy
Every correction becomes a lesson the agents use next time. The AP lead sets autonomy per lane. Lessons never relax a control.
Audit Trail and AP Assistant
A hash-chained record of every step, and a chat that answers questions about any invoice or queue.
End to end, in AP Desk.
105 real invoices are already loaded and decided. Drop in a new one, watch the agents and the controls, approve it, and see it posted and paid in the ERP.
- 01Capture AgentReads every documentAgent
- 02Coding AgentGL, clinic, TDS, GSTAgent
- 03Policy engineExceptions, risk, four gatesCode
- 04Risk and Exception AgentsExplain and brief the makerAgents
- 05Maker, checker, DOAOwn the exceptions and approvalsPeople
- 06Posting AgentPosts to the ERP; cannot payAgent
- 07TreasuryReleases payment in the ERPPerson