Finance · Invoices & payments
Three-Way Match: PO, Receipt, Invoice
Starts when: A supplier invoice is received
Free plan · Outcome verification included · You approve every connection
How it runs
Six stages, from the moment it starts to the checks that keep running afterwards.
It starts
A supplier invoice is received
Awish plans it and asks for each app
The apps it needs are connected one at a time, with your permission, before anything runs.
It does the work
Exactly as the request below describes, across the connected apps.
It stops where a person should decide
Do not auto-approve missing receipts, duplicate invoices, unexpected vendors or variances outside policy.
It verifies the outcome
After each run, Awish checks that every entry reached the books and matches its source.
It keeps monitoring
Failures, silent failures and connection health are watched on every plan; anomalies, root cause and recommendations on Business.
The request it runs
This is what opens in chat when you use the template. Change any part of it before anything connects.
“Set up an automation that manages the three-way match of PO, goods receipt and invoice. Start it whenever a supplier invoice is received. It should match the invoice lines against the approved PO and the goods receipt, calculate the price, quantity and tax variances, auto-approve within tolerance, route the exceptions to the buyer and to AP, and create a payment-ready record after approval. Connect it with Coupa, NetSuite, Google Drive and Slack. Do not auto-approve missing receipts, duplicate invoices, unexpected vendors or variances outside policy.”
- Coupa
- NetSuite
- Google Drive
- Slack
Monitoring included
What Awish watches once this template is running.
- Outcome verificationEvery plan
- Silent-failure detectionEvery plan
- Connection healthEvery plan
- Hours saved and ROIEvery plan
- Anomaly detectionOn Business
- Root-cause explanationOn Business
- Recovery recommendationOn Business
Questions about this template
Can I change where it stops for approval?
Yes. Open the template in chat and say where you want it to stop. The plan updates before anything connects.
What if one of these apps is not connected yet?
Awish asks you to connect each app it needs, one at a time, before the workflow runs. You can decline any of them.
How does Awish know this workflow worked?
After each run it checks that every entry reached the books and matches its source, in the app where that should happen. If a run reports success but the result is missing, it flags a silent failure.
Run it on your own apps
It opens in chat with the request written. See the plan, approve each connection, and Awish verifies the outcome from the first run.
Free plan · No credit card required