Automated LoanPro Portfolio Exception Detection
Every night, WebRun scans LoanPro for portfolio exceptions including duplicate payments, unexplained balance movements, misapplied fees, and loans with unusual transaction patterns, cross-checks them against your QuickBooks general ledger, and posts a flagged exception report to the operations Slack channel for next-day investigation.
How do I automatically detect payment anomalies and portfolio exceptions in LoanPro each night?
Every night, WebRun scans LoanPro for payment anomalies including duplicate transactions, unexplained balance changes, and fee discrepancies, cross-checks payment totals against your QuickBooks general ledger, and posts a ranked exception report to your operations team's Slack channel. No correction is made automatically.
- Duplicate payments and balance anomalies are detected and reported the same night they occur
- Operations staff start the day with a ranked exception list instead of discovering problems mid-day
- QuickBooks and LoanPro totals are cross-checked nightly so reconciliation differences never compound
Built for consumer lending operations teams · loan servicers · finance controllers · fraud and risk 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
loanpro.ioin a real browser with your saved login - no setup, no API keys. -
1
LoanPro - scan for payment and balance anomalies
WebRun opens LoanPro to scan for payment and balance anomalies. - Open LoanPro and review today's transaction activity across the full portfolio
- Flag any loan with two or more payments posted on the same day as a potential duplicate
- Identify loans where the outstanding balance changed without a corresponding payment or disbursement
- List any fees applied today that differ from the fee schedule for the loan product type
Done when All payment anomalies, balance exceptions, and fee discrepancies from today are captured.
-
2
QuickBooks - cross-check against general ledger
- Open QuickBooks and check the lending general ledger for today's loan payment entries
- Cross-reference the total payment receipts in QuickBooks against the LoanPro payment totals for the day
- Flag any difference between the two systems as a reconciliation exception requiring investigation
Done when QuickBooks and LoanPro totals are compared and any reconciliation differences are captured.
-
3
Slack - post exception report to operations team
WebRun opens Slack to post exception report to operations team. - Post the exception report to the loan operations Slack channel listing each flagged item with loan ID, anomaly type, and amount
- Rank exceptions by dollar impact so the largest discrepancies appear first
- Post a clean confirmation message if no exceptions were found that night
Done when Operations team has the nightly exception report in Slack before the next business day starts.
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 reverse or correct any anomalies automatically?
No. It only identifies and reports exceptions. Every correction, reversal, or write-off is actioned by your operations team after reviewing the flagged items.
How does it distinguish a legitimate same-day payment from a duplicate?
It flags same-day payments for human review rather than automatically treating them as duplicates, since some borrowers legitimately make two payments in one day. Your team makes the final call on each flagged item.
What if the operations team fixes an exception before seeing the Slack report?
The next nightly run re-scans LoanPro and only reports items that are still unresolved. Fixed exceptions are automatically excluded from subsequent reports.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.