Automated Bill.com PO Invoice Match Exceptions
Every morning, WebRun opens Bill.com, finds newly entered bills that reference a purchase order, compares the billed quantities and prices to the PO, flags any line items outside your match tolerance, logs the exceptions in Google Sheets, and posts a summary to Slack for the AP team to investigate.
How do I automatically flag PO and invoice mismatches in Bill.com?
WebRun opens Bill.com every morning, finds bills that reference a purchase order, and compares billed quantities and prices line by line to the PO. Exceptions outside your tolerance are logged in Google Sheets and summarized in Slack so your AP team can investigate and hold problem bills before any approval or payment.
- Overbillings are caught before payment, not after the money is gone
- Every PO-linked bill is checked automatically so no manual comparison is needed
- Exception history in Google Sheets makes vendor dispute patterns visible over time
Built for AP teams · procurement teams · controllers · finance managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.bill.comin a real browser with your saved login - no setup, no API keys. -
1
Bill.com - compare new bills to linked purchase orders
bill.com
WebRun opens Bill.com to compare new bills to linked purchase orders. - Open Bill.com and find bills entered in the last 24 hours that reference a PO number
- For each bill, read the billed line items and compare to the linked PO quantities and unit prices
- Flag any line item where the billed price exceeds the PO price by more than the tolerance, or where the billed quantity is higher than the PO quantity
- Note the vendor, the PO number, the billed amount, the PO amount, and the variance
Done when All new PO-linked bills have been compared and exceptions identified.
-
2
Google Sheets - log each mismatch exception with details
google.com
WebRun opens Google Sheets to log each mismatch exception with details. - Open the PO-invoice exception log sheet
- Append each exception with vendor, PO number, billed amount, PO amount, variance, and exception date
Done when All exceptions are logged in the sheet.
-
3
Slack - post daily exception summary to the AP channel
slack.com
WebRun opens Slack to post daily exception summary to the AP channel. - Post a summary to the AP Slack channel: total exceptions found, total variance dollar amount, and a list of vendors with exceptions
- Remind the team that each bill should be held in Bill.com pending resolution before approval
Done when The AP team has the exception summary in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will WebRun reject or hold a bill automatically in Bill.com?
No. WebRun flags mismatches and logs them. The decision to hold, dispute, or approve a bill is always made by a human in Bill.com.
How tight is the match tolerance?
You set the tolerance during setup, for example 2% or a fixed dollar amount. Anything within tolerance is treated as matched and not flagged.
What if a bill has no linked PO?
Bills with no PO reference are skipped by this check. If you want those flagged separately, the unapproved-bills worklist covers that workflow.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.