Solutions Invoices
Three way match
Invoice, order and delivery checked against each other, with only the disagreements reaching a person.
01 / What it looks like running
Start to finish, and where a person still comes in.
01 / Trigger Invoice arrives
02 / Automated Read and matched to the purchase order
03 / Automated Checked against what was received
04 / Decision Do all three agree?
They agree
05 / Automated Queued for payment
They differ
06 / Automated Held, and the difference itemised
07 / Automated Buyer notified with the evidence
08 / Automated Filed either way, with the trail attached
09 / Needs a person Resolving a genuine disagreement
Automated Needs a person 7 of 9 run without anyone
02 / What stops happening
7 steps become 1.
The struck lines are the ones nobody performs after this is live.
- Invoice arrives and waits in a mailbox
- Someone finds the matching purchase order
- They find the delivery note, or somebody who remembers it
- They compare three documents line by line
- They approve it, or they start an email thread about it
- The thread is the only record of what was decided
- Resolving a difference that is genuinely in dispute
03 / Built on
In your tenant, under your licences.
- Power Automate
- Power Automate Desktop
- Dataverse
- Python
Yours may differ. What a process runs on is decided by what it touches, not by what we prefer building with.
Does yours run like this?
It probably runs nearly like this, with two steps that are entirely your own. Those two are the interesting part.