Automated QuickBooks Bank Feed Review
Every morning, WebRun opens QuickBooks, works through the bank feed transactions still sitting in the For Review queue, notes which ones a bank rule already covers and which need a human category decision, posts the queue to Microsoft Teams, and queues a Twilio text when the backlog crosses your limit.
How do I keep the QuickBooks For Review queue from piling up?
Every morning WebRun opens QuickBooks, works through the bank transactions sitting in the For Review queue, notes which ones a bank rule already covers and which need a human category decision, then posts the list to Microsoft Teams and queues a Twilio text when the backlog crosses your limit.
- The For Review queue is counted every morning, not at month end
- Transactions needing a human decision are separated from rule matches
- Nothing older than two weeks sits in the queue unnoticed
Built for bookkeepers · small business owners · accounting firms · finance admins
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.qbo.intuit.com/loginin a real browser with your saved login - no setup, no API keys. -
1
QuickBooks - read the For Review queue
WebRun opens QuickBooks to read the For Review queue. - Open QuickBooks and go to the banking For Review queue
- Count the transactions waiting on each connected account
- Note the date, description, vendor, and amount for each one
- Mark which ones an existing bank rule already suggests a category for
- Flag the rest as needing a human decision, oldest first
Done when Every unreviewed bank transaction is listed with a suggested category or a reason it needs a decision.
-
2
Microsoft Teams - post today's review list
WebRun opens Microsoft Teams to post today's review list. - Post the count of transactions still for review, split by bank account
- List the ones with no matching rule and no obvious chart of accounts match
- Call out any transaction older than two weeks so nothing ages into month end
- Leave the categorizing to your bookkeeper. WebRun never accepts or edits a transaction on its own
Done when The bookkeeper has today's review list in Teams.
-
3
Twilio - queue a text when the backlog grows
WebRun opens Twilio to queue a text when the backlog grows. - Check the queue size against the backlog limit you set
- If it is over, prepare a short text to the bookkeeper with the count and the oldest date
- Leave the message queued in Twilio for a human to approve and send
- Skip the text entirely on days the queue is under the limit
Done when A backlog text is queued for approval, or the day passes with no text needed.
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 it categorize or accept transactions for me?
No. WebRun reads the For Review queue and reports it. Accepting a transaction, changing a category, or creating a bank rule stays with your bookkeeper, and the Twilio text is only queued for a human to approve.
Does it cover more than one bank account?
Yes. WebRun counts the queue on every connected account in QuickBooks and splits the Teams post by account, so a busy card feed does not hide a quiet one.
What stops the same transaction being reported forever?
It reads the live For Review queue each morning, so anything your bookkeeper accepted or excluded yesterday is gone from today's list automatically.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.