The servicing side of the portal
The deal flow side of the broker portal — the part most articles describe — handles intake, underwriting, and funding. The servicing side handles everything that happens between when the funds wire and when the merchant either pays off, renews, or defaults. It is where you live as a long-running row of daily ACH events for 6–18 months.
What the broker and funder see on the servicing dashboard is more granular than most merchants realize. Daily ACH success or fail, NSF events, average daily balance trend, deposit volume changes, stacking-detection alerts, reconciliation request history, on-time-payment streak, projected payoff date, renewal eligibility flag. All of it updates in near real time, and all of it drives decisions — when to call you about a renewal, when to escalate to collections, when to flag your file as at-risk.
This article walks through what the servicing dashboard tracks, how it is used, and what you as the merchant should ask for and monitor on your own side.
What the servicing dashboard tracks
1. The daily ACH ledger
Every business day, the funder's ACH origination engine submits a debit against your business bank account for the contracted daily payment amount. The result — cleared, NSF, returned, or held — is logged within 1–3 business days and surfaced in the servicing dashboard. The broker can see:
- Date of each debit attempt
- Amount attempted
- Status (cleared, NSF, returned for other reason, holdback adjusted, reconciliation in progress)
- Running paid-to-date total
- Running balance remaining
- Percent paid down (paid-to-date divided by total payback)
- Days remaining at current pace
2. NSF and exception events
When an ACH debit fails, the system records an exception. NSF (non-sufficient funds) is the most common; others include account-closed, customer-stopped-payment, invalid routing number, and ACH-disputed. The dashboard color-codes these events red and adds a count to the rolling NSF tally.
- 1 NSF in 30 days. Usually a one-off, no action taken.
- 2 NSFs in 30 days. An automated email or call from the funder's servicing team to confirm everything is okay.
- 3+ NSFs in 30 days. File moves to "watch" tier. Collections team assigned. Broker notified. Default-acceleration clauses in the merchant agreement become enforceable depending on the contract language.
3. Reconciliation request workflow
The merchant agreement almost always includes a reconciliation clause permitting the merchant to request a temporary reduction in the daily ACH if revenue drops. To file a reconciliation request, the merchant typically must:
- Submit a formal request in writing (email or portal form)
- Provide 30–60 days of recent bank statements showing the revenue drop
- Quantify the drop as a percentage of the underwriting baseline
- Wait for funder review (typically 1–14 business days, depending on funder)
The dashboard tracks each reconciliation request with status (submitted, in review, approved with new daily amount, denied, expired) and a history of all prior requests. Our reconciliation policy ranking covers which funders process requests fastest and most fairly.
4. Bank-feed continuous monitoring
Most modern funders maintain continuous read-only access to the merchant's business bank account via Plaid, Heron, MX, or a similar bank-data aggregator. The authorization was granted in the merchant agreement (often buried as "account monitoring consent" or "ongoing financial information access"). This lets the servicing system see, in near real time:
- Daily ending balance trend
- Weekly deposit volume trend
- New ACH debits appearing (stacking detection — if a new MCA shows up, an alert fires)
- Cash withdrawal trend (proxy for under-the-table revenue diversion)
- Closing of the bank account (immediate red flag, often triggers an acceleration notice)
5. Stacking-detection alerts
The single most-watched alert on the servicing dashboard is "new MCA position detected" — a daily or weekly ACH debit pattern matching a known competing funder appears in the merchant's bank statements. Stacking is the #1 predictor of default. When the alert fires, the funder typically:
- Notifies the broker immediately
- Pauses renewal eligibility
- Reviews the merchant agreement for anti-stacking violations (most A-paper contracts have them)
- In some cases, declares an event of default and triggers acceleration
See our stacking walkthrough for the merchant side of this — what triggers it, what it costs, and the honest way out.
6. Renewal eligibility scoring
The dashboard runs a weekly job that scores every active merchant on renewal eligibility. Inputs: percent paid down (50%+ is the typical floor), on-time-payment streak, NSF count, deposit-volume trend, stacking-detection clean status, paper grade, owner FICO trend. The output is a binary flag — "renew now" or "not eligible" — and a projected eligibility date for those who are not yet eligible. The broker gets a CRM task the moment the flag flips to "renew now".
7. Default-watch tiers
Files are graded by risk tier on the servicing side: green (on track, renew when eligible), yellow (1–2 NSFs in 30 days, monitor), orange (3+ NSFs or material deposit drop, contact merchant), red (5+ NSFs, account closure, stacking detected, or skipped payments, collections engaged). The broker sees the tier in the dashboard and is notified on every tier change.
How brokers use the servicing data
Renewal timing
The most lucrative use of servicing data for the broker is renewal timing. The moment you cross 50% paid down with a clean on-time streak, the renewal task fires and the broker calls. Brokers who watch the dashboard religiously call within 24 hours of the flag flipping. Brokers who do not call within 7 days are typically less attentive — or have lower-scored merchants in the queue ahead of you.
Early-warning intervention
A good broker intervenes when your file moves from green to yellow. They call to understand what changed, suggest a reconciliation request if appropriate, and help you communicate with the funder's collections team. A bad broker either ignores yellow-tier files (they are not a renewal target right now) or pivots to "let me get you another MCA to bridge this" — which is exactly how merchants stack and spiral.
Cross-sell triggering
Servicing data also feeds cross-sell decisions: a merchant with a clean payment streak and improving deposit trend becomes a candidate for a line of credit or SBA referral. A merchant with deteriorating trends becomes a candidate for a "debt consolidation" MCA, which is almost never actually consolidating — it is rolling existing debt at a worse effective rate.
What you should monitor on your side
- Your own daily ACH reconciliation. Check your bank app every day the first month, then weekly. Confirm the daily amount matches your contract. ACH amount errors do happen.
- Average daily balance trend. If your balance is trending down even as you are paying on time, you are eating into reserves and the funder's monitoring system has already noticed.
- NSF count. Two NSFs in a 30-day window is a warning. Three is an emergency. Get on the phone with the funder before they call you.
- Revenue trend. If your monthly revenue is 20%+ below underwriting baseline for two consecutive months, file a reconciliation request proactively. Do not wait for the funder to call.
- Renewal pressure. When the broker calls you at 50% paid down with "we can get you more money," the answer is almost never yes. Run the math through our factor-rate calculator and our renewal mistake walkthrough before signing anything.
What to ask your broker for
Three concrete asks that a reputable broker will fulfill:
- A monthly payment statement. Most funders generate one automatically; brokers can request it on your behalf. It shows every ACH event, running balance, and projected payoff date.
- An on-demand status check. Email or text the broker for the current paid-to-date number, remaining balance, and tier color. A good broker has it in under 5 minutes.
- An honest renewal-vs-payoff conversation. Ask the broker to model the math both ways — paying off as scheduled vs renewing at 50% paid down. The renewal math is almost never as attractive as the broker frames it.
Frequently asked questions
- Can my broker see whether my daily ACH payment cleared yesterday?
- At most funders, yes. The servicing side of the broker portal — sometimes a separate tab, sometimes a separate URL — surfaces daily ACH success or fail status, current outstanding balance, percent paid down, days remaining in term, and reconciliation request history. Brokers monitor this to know when to trigger renewal pitches and to flag at-risk merchants for early intervention.
- What happens when my daily ACH bounces?
- The funder's servicing system records an NSF (non-sufficient funds) event, the broker portal shows a red flag on your account, and most funders retry the ACH 2–3 days later. Some funders charge a $25–35 NSF fee per failed attempt. Three NSFs in a 30-day window typically triggers a default-watch flag inside the portal and a phone call from the funder's collections team.
- What is a reconciliation request and how do I file one?
- If your business revenue drops materially (typically 20%+ from the underwriting baseline), you can request a reconciliation — a temporary reduction in the daily ACH amount, proportional to the revenue drop. The funder requires recent bank statements to verify the drop. Some funders process reconciliations in 1–5 business days; others stretch it to 14+ days or deny outright. The broker portal shows the request status.
- How do funders flag early warning signs of default?
- Most servicing systems monitor a basket of signals — NSF count rolling 30/60/90 day, average daily balance trend, deposit volume trend (parsed from continuous bank-feed access via Plaid or Heron), stacking detection alerts (new MCA appearing in your statements), and on-time-payment streak. When the basket crosses a threshold, the file moves to a 'watch' tier and the funder's risk team contacts the broker.
- Can the broker help if my payments are at risk?
- Sometimes. A good broker has a working relationship with the funder's underwriting and collections teams and can advocate for a reconciliation, a forbearance, or a refinance into a longer-term product. A bad broker will pivot the conversation to 'let me get you another MCA to bridge this' — which is exactly how merchants spiral into stacking. Know the difference.