Case study

Accounts payable automation: requisitions, orders and invoices from the mailbox

Purchase requisitions, orders and invoices collected from a shared mailbox, read by AI, coded to the ledger, routed for approval and matched, with a person confirming each one.

Build something like this

Client: a global listed groupSector: Accounts payable

The build

What the problem was, and what we did about it.

The problem

Requisitions, orders and invoices arrive in a shared mailbox, get captured twice, coded by guesswork and approved late, and nobody can match the three without a spreadsheet.

What we built

An automation that collects purchase requisitions, orders and invoices from the mailbox, reads each one, suggests the general-ledger account, cost centre and profit centre from the chart of accounts, routes it for the approval that coding demands, and matches the invoice to its order before anything is posted. A reviewer confirms every suggestion; the approval log keeps the rest.

Illustration: the AP agent's dashboard, requisitions by stage from finance review to an invoice matched to its purchase order

Illustration, close up: a requisition's extracted fields and AI-suggested mapping beside the request form, the clicked total highlighted in the PDF — A closer look
An illustration of the system, drawn for this page with demo data. Nothing shown is a client's own.

Built with

Power Automate
AI Builder
Power Apps
Dataverse

Start a conversation

Yours would be the next one on this list.

Tell us the problem. We'll tell you whether we're the right people, what it would take, and what it would cost before anybody starts building.

Talk to usHow we work