Automated NEMT Broker Claim Reconciliation
Every Monday, WebRun opens NEMT Cloud Dispatch, pulls the prior week's completed trips, compares each against broker remittance data in Google Sheets, flags underpaid or unmatched claims, and posts a reconciliation summary to Slack so the billing team knows exactly where to follow up.
How do I automatically reconcile NEMT broker trips and claims each week?
WebRun pulls the prior week's completed trips from NEMT Cloud Dispatch every Monday, compares each one against broker remittance data in Google Sheets, and flags underpaid and unpaid claims. A reconciliation summary is posted to Slack so the billing team can follow up on variances immediately.
- Underpaid and unpaid claims are surfaced every Monday without manual spreadsheet work
- Billing team sees the largest variances by broker at a glance in Slack
- Every completed trip has a documented match status for audit purposes
Built for NEMT billing managers · medical transport operators · paratransit 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
app.nemtclouddispatch.comin a real browser with your saved login - no setup, no API keys. -
1
NEMT Cloud Dispatch - pull prior week completed trips
nemtclouddispatch.com
WebRun opens NEMT Cloud Dispatch to pull prior week completed trips. - Open NEMT Cloud Dispatch and filter trips completed in the prior 7 days
- Export trip ID, broker, billed amount, service date, and rider for each completed trip
- Note any trips already marked paid or denied
Done when All completed trips from the prior week are captured with billing and broker details.
-
2
Google Sheets - cross-reference broker remittance data
google.com
WebRun opens Google Sheets to cross-reference broker remittance data. - Open the broker remittance Google Sheet and locate the prior week's payment rows
- Match each remittance line to a trip ID from the completed-trip export
- Flag trips with no matching remittance as unpaid
- Flag trips where the remittance amount is less than the billed amount as underpaid
- Log the match status and variance for each trip in a new reconciliation tab
Done when Every completed trip has a match status: paid-in-full, underpaid with variance, or unpaid and flagged.
-
3
Slack - post reconciliation summary with flagged gaps
slack.com
WebRun opens Slack to post reconciliation summary with flagged gaps. - Post a reconciliation summary to the billing Slack channel: total trips, paid-in-full count, underpaid count, unpaid count, and total variance
- Link to the reconciliation tab in Google Sheets
- Highlight the largest variances by broker
Done when Billing team has a Slack summary with totals and a direct link to the flagged reconciliation 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
Does it submit disputes or contact the broker automatically?
No. WebRun only reads and reconciles data internally, then surfaces gaps for your billing team in Slack. Any dispute or follow-up is initiated by your staff.
What if the broker remittance file is not yet in Google Sheets?
WebRun checks for the prior week's data in the linked Google Sheet. If the remittance has not been imported yet, it flags those trips as unmatched so your team knows to upload the file.
Which brokers does it work with?
It works with any broker whose remittance data you have loaded into the Google Sheet. The reconciliation logic matches on trip ID, so any broker that issues trip-level remittance reports is supported.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.