An invoice approval workflow: match it to the order, then approve it for payment
SynaptaGrid8 min read
In short
An invoice approval workflow is the path a supplier invoice takes from the day it arrives to the day it is approved for payment, queried with the supplier or rejected. Two questions matter and they belong to different people. Accounts payable asks whether the invoice matches what was ordered and delivered. The budget owner asks whether the cost is theirs and the work was done. A good workflow keeps those questions separate, gives the invoice that does not match its own route back to the supplier, and writes the outcome onto a record so the invoice can be found later. We built a small version in our own test workspace in which an AI tool, written for this job and used as an action in a normal step, reads the text of the invoice and pulls out the supplier, the amount and the order number, and the workflow writes them onto the invoice record before accounts payable matches it. The tool works on text; reading the attached invoice file itself is not available yet, so our test invoice arrived as text. We ran it three times, once to approval, once queried because it did not match and once rejected by the budget owner, and we checked the invoice records afterwards.
What an invoice approval workflow is
A supplier invoice is a request to be paid. Before paying, a company wants to know that it ordered the goods or services, that they arrived or were done, and that the amount is right. An approval workflow writes down who checks each of these, in what order, and where an invoice goes when a check fails.
It does not replace the people. It makes sure the right person sees each invoice, that an invoice with a problem has somewhere to go that is not a pile on someone’s desk, and that every invoice ends in a state anyone can look up.
The version we built
The steps to include, and who owns each
- Record the invoice
- When an invoice arrives, a record is created with the supplier, the invoice reference and a status of received. Every later step reads from and writes to that record.
- Read the invoice
- This is where an AI tool helps. It reads the text of the invoice and returns the supplier, the total and the order number, and says which of them the text does not state. The next step writes them onto the invoice record, so accounts payable starts from filled-in fields instead of retyping them. In our version the tool reads text only; it does not read an attached invoice file yet.
- Match to the order
- Accounts payable checks the supplier, the amount and the goods or services, starting from what the AI tool wrote on the record, against the purchase order and the delivery. Many companies call this a three-way match, because it compares the invoice, the order and the receipt.
- Query the supplier
- An invoice that does not match is not rejected outright. It goes back to the supplier with a question, and the record says it is queried, so nobody pays it by mistake while the question is open.
- Budget owner approval
- The person who owns the budget confirms the work was done or the goods received and that the cost belongs to their budget. This is a different question from the match, so it is a different step.
- Reject
- The budget owner can refuse an invoice that matches the order but should not be paid, for example work that was not completed. The record is marked rejected.
- Mark the result on the record
- Each ending sets the status: ready to pay, rejected or queried. The workflow does this itself, so the status does not depend on someone remembering to update it.
- Hand off to payment
- Paying the invoice usually happens in another system. Decide where an approved invoice goes next and who is told, and add that as its own step.
Where approvals and checks belong
Put a check where a mistake is expensive. Paying an invoice twice, or paying one for work that was never done, is hard to undo, so the match comes first and the budget owner’s approval comes second. Neither person can do the other’s job well: accounts payable has the order and the delivery records, and the budget owner knows whether the work was good.
Name each approver by role, such as accounts payable and the owner of the budget, rather than by person. If you need a further approval for large invoices, add it above a set amount on your own policy; we did not build that.
The old way and the new way
The table compares invoices handled by email and paper with the same invoices run as a workflow.
- Getting the invoice into the system
- The old way: Someone types the supplier, amount and order number
- The new way: An AI tool reads the text and fills them in for checking
- Where an invoice is
- The old way: In someone’s inbox or tray
- The new way: At a named step, with an owner
- An invoice that does not match
- The old way: Held until someone chases it
- The new way: Its own route, marked queried on the record
- Whether it can be paid
- The old way: Ask accounts payable
- The new way: The record says ready to pay or it does not
- A rejected invoice
- The old way: An email, often not recorded
- The new way: Marked rejected and ended with a written result
- Finding an invoice later
- The old way: Search inboxes and folders
- The new way: Open the record and read its status
- Judgement
- The old way: Still accounts payable’s and the budget owner’s
- The new way: Still theirs: whether it matches, whether it should be paid
How we decided
We built the version in the diagram in our own test workspace in SynaptaGrid Automation, with a small record type in SynaptaGrid Data for the invoice, and ran it three times in November. The AI part is a custom tool we wrote for the job: a prompt that says what to pull out of an invoice, an input that takes the invoice text, and an output with the supplier, the amount as written, the order number and a short note. In the workflow it is an action in an ordinary step, set up like any action that calls another system, and the next step writes its result onto the record. In the first run accounts payable marked the invoice as matching and the budget owner approved it. The workflow created the invoice record with the status Received, then updated the same record to Approved, ready to pay with the ready flag set, and the run finished with the approved result. In the second run accounts payable said the invoice did not match: the run skipped the budget owner, marked the record Queried with the supplier and ended with a queried result. In the third run the invoice matched and the budget owner rejected it, and the record ended as Rejected.
We checked the three records in Data afterwards. The approved one showed Approved, ready to pay with the ready flag set. The queried one showed Queried with the supplier, and the rejected one showed Rejected, both not ready to pay. All three carried what the tool read from the invoice text: the supplier, the total and the order number exactly as the invoice text gave them. The tool did not work first time: our earlier attempts to call it failed until we named the model in full in the tool’s settings, and our first version did not use its output in a later step. The version described here is the one that ran three times.
We chose a separate route for the invoice that does not match, and a budget owner approval after the match, because those are the places where invoices usually go wrong. The choice of steps is ours and a judgement; it is not a standard.
Six limits, so this guide does not claim more than the runs showed. The tool read a clean line of invoice text, so we did not test messy text, several line items or an invoice with a missing order number, and it cannot read an attached invoice file yet. One test account held every human step, so the runs show the sequence and the branching, not hand-offs between different people. The match was a person’s decision: the workflow does not compare the invoice with the order for you, and we did not connect it to an order, receipt, accounting or payment system, so nothing was paid and the ready flag is a stand-in. We did not build an approval above a set amount, a check for a duplicate invoice, or a way to send an invoice back after the supplier replies. We did not test reminders when an invoice waits too long or notifications to the supplier. And the template carries one test account as every approver and the actions tied to our test record type and our test AI tool, so to reuse it you would change each step to a role and point the actions and the tool at your own, which we did not do.
Standards and accepted practice behind this
These are the practices the guide rests on. We align with them. This page does not claim a certification.
- Three-way match
- A widely used control in accounts payable that compares the invoice, the purchase order and the goods receipt before payment. The match step in this guide is where that comparison is recorded.
- Human oversight of AI
- Where AI helps with a decision, accepted practice is to keep a person accountable for it and to let them see the AI’s input and output. Here the tool reads and fills in fields, and accounts payable and the budget owner decide.
- Source: EU AI Act (Regulation 2024/1689), Article 14: human oversight (opens in a new tab)
- Segregation of duties
- The person who places the order, the person who checks the invoice and the person who pays it should not all be the same. Separate steps with separate owners support that.
- Source: NIST glossary: separation of duty (opens in a new tab)
- Documented approval
- Auditors expect to see who approved a payment and when. A step that records the decision and a record that carries the status are that evidence.
- BPMN
- The standard notation for drawing a process. The diagram above is a plain flowchart, and a BPMN diagram of the same steps would show the same decisions.
- Source: OMG: BPMN 2.0 specification (opens in a new tab)
Where SynaptaGrid fits
SynaptaGrid Automation lets you write the steps as a workflow, assign each decision to a person, use an AI tool you wrote as an action in a step, pass its result to the next step, create and update records in SynaptaGrid Data as part of the run, and see where every invoice stands. You can start from the version above, change the steps to match your own policy, and keep the result as a template.
Check the limits above before you rely on it: whether each step is assigned to a role rather than a person, whether the match needs to read your order and receipt data, whether invoices must reach a payment system, and who should be told when an invoice waits.
Frequently asked questions
- What are the steps of an invoice approval process?
- Record the invoice, match it to the order and delivery, send a query to the supplier if it does not match, get the budget owner’s approval, and record the result on the invoice.
- What is a three-way match?
- A check that compares the supplier invoice with the purchase order and the goods receipt before payment. All three should agree on what was bought and how much.
- What should happen to an invoice that does not match the order?
- It should go back to the supplier as a query and be marked as queried, so it is not paid while the question is open.
- Can AI read an invoice?
- It can read the text of an invoice and pull out the supplier, the amount and the order number, and say what is missing. Reading an attached invoice file is not available yet. In our test run it filled the fields from invoice text, and accounts payable still did the match.
- Can a workflow update the invoice record for me?
- Yes. In our test run the workflow created the invoice record when the invoice arrived and set its status at each ending. You need a record type for the invoice and each action pointed at it.
SynaptaGrid
Build your invoice approval steps
Start with the steps above in a test workspace and run one invoice through each outcome before you use it for real.