Automated Clover Batch Settlement Mismatch Alerts
Every morning, WebRun opens Clover, reads the previous day's batch settlement total and compares it to the sum of completed transactions, flags any gap above your mismatch threshold, and appends the result to a Google Sheet so your bookkeeper has a daily settlement audit trail.
How do I automatically flag Clover batch settlement mismatches each day?
WebRun reads your Clover batch settlement total every morning and compares it to the sum of completed transactions from the previous day. Any variance above your threshold is flagged and logged to a Google Sheet with a Clean or Mismatch status, giving your bookkeeper a daily settlement audit trail without manual number-checking.
- Settlement mismatches caught the morning after, not at month-end
- Daily audit log in Sheets gives bookkeepers a clear reconciliation trail
- Clean days are logged too, building a verifiable history of settlements
Built for restaurant owners · retail merchants · Clover merchants · bookkeepers and accountants
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
www.clover.com/dashboardin a real browser with your saved login - no setup, no API keys. -
1
Clover - read batch settlement and transaction totals
clover.com
WebRun opens Clover to read batch settlement and transaction totals. - Open Clover Dashboard and navigate to Reporting or Payments
- Capture the previous day's batch settlement total
- Capture the sum of all completed transactions for the same period
- Calculate the variance between settlement total and transaction total
- Note the settlement batch ID and closing time
Done when Settlement total and transaction total are captured and variance is calculated.
-
2
Google Sheets - log settlement comparison and flag mismatches
google.com
WebRun opens Google Sheets to log settlement comparison and flag mismatches. - Open the batch settlement log Google Sheet
- Append a row with date, settlement total, transaction total, variance, and batch ID
- Highlight the row in red if the variance exceeds your configured mismatch threshold
- Add a status column noting Clean or Mismatch for easy filtering
Done when The settlement comparison is logged and any mismatch is flagged in the Google Sheet.
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
What causes a batch settlement mismatch in Clover?
Common causes include a transaction that completed after the batch closed, a void processed post-settlement, or a tip adjustment that shifted the total. Catching these daily lets you report them to your processor before month-end.
Will WebRun contact my payment processor automatically if a mismatch is found?
No. WebRun flags the mismatch in Google Sheets for your review. Contacting the processor, disputing an error, or correcting the accounting entry is done by you or your bookkeeper.
How do I set the mismatch threshold?
During setup you configure the dollar amount that triggers a flag. Many merchants use one dollar to catch anything meaningful while ignoring rounding differences of a few cents.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.