Automated MCA Default Risk Worklist
Every morning, WebRun opens Centrex, reviews every active advance for risk signals such as consecutive failed ACH pulls, declining remittance frequency, and balance age, scores each deal, and posts a prioritised risk worklist to Slack while logging the full scoring detail to Google Sheets for your risk team.
How do I automatically identify MCA advances at risk of default?
WebRun reviews your entire active MCA portfolio in Centrex every morning, scoring each advance against risk signals like consecutive failed ACH pulls and payment gaps. It logs the full scoring detail to Google Sheets and posts a prioritised worklist to Slack so your risk team can intervene before any advance tips into default.
- At-risk advances are flagged before they tip into formal default
- Risk team starts each day with a scored, prioritised worklist
- Full portfolio risk log maintained in Google Sheets with no manual effort
Built for MCA risk managers · advance servicing teams · MCA funders · portfolio 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.centrexsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
Centrex - pull active advance risk signals
centrexsoftware.com
WebRun opens Centrex to pull active advance risk signals. - Open Centrex and load the active advance portfolio
- For each advance, collect consecutive failed ACH count, days since last cleared payment, and current remaining balance
- Flag advances with 2 or more consecutive failed pulls or no cleared payment in 7 days
Done when Every active advance has its risk signals captured and initial flags set.
-
2
Google Sheets - score and log each advance
google.com
WebRun opens Google Sheets to score and log each advance. - Append each advance to the risk-scoring log with its signals and a computed risk score
- Rank the sheet by risk score, highest risk first
- Highlight advances crossing your critical threshold in red
Done when The risk log is updated with today's scores and the critical-threshold advances are highlighted.
-
3
Slack - post prioritised risk worklist
slack.com
WebRun opens Slack to post prioritised risk worklist. - Post a risk worklist to your risk-management channel with the top at-risk advances
- For each advance, show the merchant name, risk score, consecutive failed pulls, and days since last payment
- Include a link to the full Google Sheet for the complete portfolio view
Done when Your risk team has today's prioritised worklist in Slack with every critical advance surfaced at the top.
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 take any action on at-risk advances automatically?
No. WebRun only surfaces the risk signals and posts the worklist. All intervention decisions, including pausing ACH or contacting the merchant, are made by your risk team.
How is the risk score calculated?
It uses consecutive failed ACH pulls, days since last cleared payment, and remaining balance age from Centrex. You can tune the weights and thresholds when setting up the workflow.
Does it alert us if an advance moves into formal default?
Yes. Any advance already marked as defaulted in Centrex is flagged separately at the top of the Slack worklist so your team can prioritise those records immediately.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.