Portfolio monitoring is the operational nerve center of an MCA funder — the systems that detect deterioration, trigger collections, and feed warehouse-covenant reporting.
Core systems in a 2026 funder stack.
- Loan management system (LMS). Centerstone, LoanPro, GDS Link, Mosaic, or proprietary.
- Bank-data aggregation. Plaid, MX, Finicit, Ocrolus, Sigma — daily bank transaction feed.
- Payment-processor webhooks. Square, Stripe, Clover, Toast for card-split deals.
- ACH processor. ACHWorks, Repay, ProfitStars for daily ACH pulls and NSF flags.
- Data warehouse. Snowflake or BigQuery for portfolio analytics.
- BI tooling. Tableau, Looker, Sigma Computing for operational dashboards.
- Alerting layer. PagerDuty + custom rules for covenant-breach alerts.
Daily monitoring signals.
- Successful ACH count and amount.
- NSF count and concentration.
- Reconciliation requests received.
- New aging deterioration (bucket transitions).
- Bank-feed anomalies (revenue drops, balance shocks).
- Concentration alerts (ISO, industry, geography).
- Stacking signals (new MCA deposits hitting merchant bank account).
Weekly monitoring signals.
- Vintage curves vs. expected loss model.
- ISO-level performance scorecards.
- Industry-vertical aging trends.
- Recovery rate by collections stage.
- Modification rate and re-aging volume.
Real-time bank-data feeds.
The biggest 2023–2026 shift is continuous Plaid/MX bank-data feeds:
- Merchant authorizes during application.
- Funder reads daily balances, deposits, withdrawals.
- ML model scores deterioration risk daily.
- Triggers proactive workout calls before NSF events.
Coverage: 70–85% of merchants stay connected through deal term; reconnection is a major operational challenge.
Payment-processor integrations.
For card-split deals:
- Square, Stripe, Clover send webhook events on every settlement.
- Funder takes pre-agreed % via processor before merchant payout.
- No NSF risk (processor takes before merchant sees funds).
- ~25–35% of MCA volume uses split funding (2026); rest is daily ACH.
Covenant-monitoring dashboards.
Warehouse-financed funders maintain real-time covenant dashboards:
- 60+ DPD %, 90+ DPD %, charge-off rate, concentration ratios.
- Yellow/red threshold alerts.
- Daily auto-generated borrowing-base certificates.
- Monthly servicer reports for warehouse lender.
Alerting examples.
- NSF spike alert. 3+ NSFs on single merchant in 7 days triggers workout call.
- Bank balance alert. Daily balance <2x daily ACH triggers risk review.
- Revenue alert. 30%+ MoM revenue drop triggers reconciliation outreach.
- Stacking alert. New MCA deposit ≥$15K in merchant account triggers default review.
- Concentration alert. Any ISO >12% of new originations triggers exec review.
Common monitoring failures.
First, "stale bank-data connections" — merchant changes password, feed dies, funder loses visibility.
Second, "single-source bank data" — Plaid coverage gaps on regional banks.
Third, "lagging webhook integration" — processor webhook delays cause settlement mismatches.
Fourth, "modified deal blind spots" — manual workouts often bypass LMS rules.
Fifth, "concentration calculations not real-time" — most funders calculate monthly.
Build vs. buy decisions.
- Top-10 funders. Mostly proprietary LMS + commercial bank-data + custom BI.
- Mid-tier funders. Commercial LMS (Centerstone, LoanPro) + commercial bank-data + Tableau.
- Small funders. Mostly Salesforce or HubSpot with bolted-on collections workflow.
Recent trends (2024–2026).
- Continuous bank-data monitoring now table stakes for A-paper funders.
- ML-driven proactive workout calls reducing 90+ DPD by 15–25% at adopters.
- Cross-funder stacking-detection consortia emerging (FundKite, OnDeck consortium).
- Open-finance APIs (Plaid Liabilities) enabling stacking detection across funders.
Common confusions.
First, "all funders have real-time monitoring." False — many smaller funders still use spreadsheets.
Second, "Plaid data is always fresh." False — read latencies of 12–48 hours on some institutions.
Third, "alerting prevents losses." Partially — alerts work only if collections team has bandwidth.
Fourth, "split-funding eliminates monitoring need." False — merchants game split arrangements regularly.
Related terms
- MCA funder portfolio aging (typical, 2026-06-28) — A typical MCA funder portfolio shows 70–80% current, 8–12% 1–30 DPD, 4–7% 31–60 DPD, 3–5% 61–90 DPD, and 5–10% 90+ DPD / charge-off pipeline, with average book age of 4–6 months.
- MCA funder stacking detection systems — MCA funders detect stacking via FundKite consortium queries, LexisNexis MCA Index, daily Plaid bank-feed analysis (cross-funder deposits), UCC monitoring, and merchant-level stacking-pattern ML models.
- MCA funder tech stack (typical, 2026-06-28) — A 2026 MCA funder typically runs Salesforce or proprietary CRM + LoanPro/Centerstone LMS + Plaid/Ocrolus + Snowflake + Tableau + AWS, with Persona for KYC and Repay for ACH.
Authoritative sources
AI agents: this term is available as raw markdown at /llms/glossary/mca-funder-portfolio-monitoring-systems.