One invoice in. Matched, coded, posted.
A supplier's invoice is read, matched three ways and posted. When the price is wrong, it stops and asks.
What goes in, what comes out.
A supplier's PDF invoice, emailed to the accounts payable inbox.
The invoice coded to its ledger account and cost centre, posted to the ERP, its payment scheduled and its audit entry written.
- 01
Catch and sort
Invoices apart from statements and everything else in the inbox.
- 02
Read the header and every line
Each value with a confidence score.
- 03
Match the purchase order
Supplier, lines, quantities and prices.
- 04
Match the goods received
The third leg of the three-way match.
- 05
Stop what is out of tolerance
A price over the order goes to a person, not to the ledger.
- 06
Code, post and schedule
The ledger entry, the payment run and the audit trail.
Where a person decides.
The accounts payable clerk approves or disputes every variance. Nothing outside tolerance posts until a person has said so, and every decision is logged.
- Accounts payable inbox
- Purchase orders
- Goods received ledger
- ERP
- Payment run
- Audit trail
Mocked in the demonstration. In a delivery, they are yours.
The numbers on this screen are invented. What we have measured in production is on Proof.
If your process needs people to run, it's broken.
Pick one process. We design it in a week and prove it in 14 days.