Catch TPA remittance mismatches as payments land
When a payment lands, WebRun opens Verity Solutions, checks the TPA remittance against the replenishment cost each claim should have generated, logs any mismatch in Smartsheet with the dollar difference, and posts a Slack alert with a drafted dispute note held for your team's review before it goes to the TPA.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch TPA remittance mismatches in my 340B program automatically?
WebRun checks every TPA remittance the moment it lands. It compares the paid amount against the replenishment cost each claim should have generated in Verity Solutions, logs any mismatch with the dollar difference in Smartsheet, and posts a Slack alert with a drafted dispute note, so your team can review and send it to the TPA before the dispute window closes.
- Remittance mismatches are caught the day they land instead of at reconciliation time
- Every claim in the batch is checked, not just a sample
- Disputes get drafted before the TPA's dispute window closes
Built for 340B program managers · contract pharmacy administrators · covered entity finance teams · pharmacy purchasing 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.verity-solutions.comin a real browser with your saved login - no setup, no API keys. -
1
Verity Solutions - check the remittance against expected cost
verity-solutions.com How to Automate Verity Solutions
WebRun opens Verity Solutions to check the remittance against expected cost. - Open Verity Solutions when a new TPA remittance lands
- Compare the remittance amount against the expected replenishment cost for each claim in the batch
- Flag any claim where the paid amount does not match what was expected
Done when Every claim in the remittance batch has been checked against its expected replenishment cost.
-
2
Smartsheet - log the mismatch
smartsheet.com How to Automate Smartsheet
WebRun opens Smartsheet to log the mismatch. - Log each mismatched claim with the expected amount, the paid amount, and the difference
- Total the batch's mismatch amount
- Carry any unresolved mismatch forward until it is cleared
Done when The remittance log reflects every mismatch in the batch and the running total.
-
3
Slack - alert your team
slack.com How to Automate Slack
WebRun opens Slack to alert your team. - Post an alert summarizing the batch's total mismatch amount
- Draft a dispute note to the TPA for the largest mismatches and leave it unsent for your team to review
- Tag your team so the dispute window does not lapse
Done when Your team has been alerted to the mismatch total and has a drafted dispute note to review.
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 dispute a remittance with the TPA on its own?
No. It drafts the dispute note and leaves it unsent. Your team reviews the mismatch and decides whether to send it to the TPA.
How is the expected replenishment cost calculated?
From the 340B acquisition cost each claim should have generated in Verity Solutions, compared line by line against what the TPA actually paid.
Does it check every remittance or just large ones?
Every remittance, checked claim by claim as it lands, so a small mismatch does not slip through just because the batch total looks right.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.