Automated Daily Sales to Deposit Reconciliation
Every morning, WebRun reads yesterday's net sales and tenders per location in Toast, pulls the deposits that landed in the bank through Plaid, reconciles both against the Restaurant365 sales GL, and posts you a Slack list of any deposit that is short, late, or missing by location.
How do I reconcile daily POS sales to bank deposits automatically?
Every morning, WebRun reads yesterday's sales and tenders per location in Toast, pulls the deposits that landed in the bank through Plaid, and reconciles both against the Restaurant365 GL. It posts you a Slack list of any deposit that is short, late, or missing, so a delayed settlement is caught the next day.
- Missing or short deposits surface the next morning, not weeks later
- Sales, tenders, and bank cash reconcile without manual spreadsheets
- Cash shrinkage and settlement delays get caught while they are still traceable
Built for restaurant controllers · multi-unit operators · restaurant bookkeepers · franchise finance teams
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
pos.toasttab.comin a real browser with your saved login - no setup, no API keys. -
1
Toast - read sales and tenders
- Open Toast and read yesterday's net sales, tips, and tender breakdown per location
- Capture the cash, card, and third-party delivery totals expected to settle
- Note the expected deposit and settlement date for each tender type
Done when Yesterday's expected deposits by tender and location have been captured from Toast.
-
2
Plaid - pull settled deposits
plaid.com
WebRun pulls the deposits that landed in the bank through Plaid. - Use Plaid to read the deposits and card settlements that landed in each location's bank account
- Match each settled deposit to the Toast tender it should cover
- Note deposits that are short, delayed, or have not arrived yet
Done when Every landed deposit has been read and matched to its expected tender.
-
3
Restaurant365 - reconcile against the GL
restaurant365.com
WebRun reconciles sales and deposits against the Restaurant365 GL. - Open Restaurant365 and compare the matched sales and deposits to the sales and cash GL
- Identify any variance between recorded sales, expected deposits, and what actually landed
- Read only, never post a journal or adjust the GL on its own
Done when Sales, deposits, and the GL have been reconciled and every variance identified.
-
4
Slack - flag short or missing deposits
slack.com
WebRun posts short, late, or missing deposits to Slack. - Post a per-location list of any deposit that is short, late, or missing with the amount
- Put the largest variances first with the tender type and expected date
- Confirm the locations that fully reconciled so the team sees the clean ones too
Done when The team has yesterday's deposit reconciliation 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
Does it post journals or touch the bank?
No. WebRun only reads sales in Toast, deposits through Plaid, and the GL in Restaurant365. It never posts a journal, moves money, or changes a bank record, so it reconciles and reports without altering anything.
How does it know a deposit is missing?
It matches each Toast tender to the deposit that should cover it and checks Plaid for what actually landed. If the expected deposit is short or has not arrived by its settlement date, WebRun flags it by location.
Does it handle third-party delivery payouts?
Yes. WebRun captures delivery tenders from Toast and matches them to the payouts landing in the bank, so a delayed or short delivery settlement shows up alongside card and cash variances.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.