MCA Servicing Best Practices: A Practical Guide to Protecting Yield After Funding

Origination teams get the spotlight. Marketing pays for the leads, sales chases the buy-rate, underwriting argues over the pricing. Then the deal funds, and quietly, the servicing team's decisions determine whether it actually delivers the modeled yield. After watching this play out across hundreds of millions in funded paper, I can say with confidence: most funders do not lose money on bad underwriting. They lose it on mediocre servicing.

This is a practitioner's guide to the servicing systems and policies that actually protect yield. None of it is revolutionary. All of it is harder to execute than it sounds.

1. Daily reconciliation is non-negotiable

For any funder collecting via ACH or split-funding, the foundation of servicing is reconciling expected payments against actual deposits, every business day. Late or missing reconciliation is how funders end up six weeks into a deal believing they are current when they are actually behind by four payments, usually because of a processor change, a bank-rejected debit, or a split-funding setup that quietly failed.

A minimum bar:

• Automated daily ingestion of the processor settlement file (or merchant bank ACH return file).
• Match each expected debit/holdback to an actual settlement line within 24 hours.
• Exceptions queue with clearly defined ownership and SLAs, typically a same-day phone call from a servicing rep.
• Aging report that surfaces any account where actual collections deviate from the schedule by more than a configurable threshold.

2. NSF and failed-payment response

An NSF is not necessarily a sign of a bad deal; it is most often a sign of bad timing. A well-designed NSF protocol distinguishes between the merchant who has a single off day and the one who is structurally distressed.

The pattern we deploy and recommend is three tiers:

1. Tier 1, automated retry. One retry on the next business day for the same amount, or a fractional retry depending on the deal's documented terms. Never spam retries: both NACHA rules and downstream merchant goodwill cap you here.
2. Tier 2, same-day outreach. If the retry also fails, the merchant gets a personal call within 24 hours from a named rep, plus an SMS and email. Goal: understand the cash-flow situation and either reschedule a single payment or set up a short, documented catch-up plan.
3. Tier 3, written restructure. If NSFs persist into a second cycle, escalate to a formal restructure offer with a redrawn payment schedule and clear documentation. This is the line between servicing and collections, and crossing it should be a decision, not a default.

3. Communication policy

Consistent, multi-channel communication is both a recovery driver and a compliance safeguard. The right merchants want to be told the truth about where they stand; the wrong ones will use silence to disengage. A modern servicing program includes:

• Daily or weekly automated balance updates, by email and SMS, with the remaining payback, payments to date, and projected payoff date.
• Proactive outreach when revenue trends suggest stress (declining deposits, increasing NSFs, processor changes).
• Defined call cadences for delinquent accounts with documented call attempts.
• A merchant self-service portal where the borrower can view their balance, download statements, and request a renewal.

4. The merchant portal is a servicing tool, not a marketing checkbox

A real merchant portal reduces inbound call volume, increases on-time payments, and dramatically improves renewals. Minimum feature set: current balance, full payment history, downloadable statements and tax documents, ACH bank-account update flow with verification, renewal request button, and a single document upload for any stips. We see ~25–40% deflection of routine servicing calls when the portal is built out properly.

5. Renewal capture is the highest-leverage servicing metric

An existing performing customer is the cheapest funded deal you will ever do: no broker commission, no marketing acquisition cost, fully de-risked underwriting because you have 60–90 days of paid-on-time history. The funders we see outperform on portfolio LTV are the ones who systematize renewal capture:

• Automated identification of renewal-eligible accounts (typically 50–70% paid back, no NSFs in last 30 days, clean bank activity).
• Pre-approved renewal offers presented in the merchant portal and pushed by SMS/email.
• Streamlined renewal underwriting: re-pull bank data, re-run the model, skip every doc you already have on file.
• Defined renewal-pricing playbook so reps don't reinvent the offer every time.

6. The metrics that actually matter

Many servicing dashboards drown in vanity numbers. The shortlist that actually predicts portfolio behavior (covered in more depth in our portfolio analytics article):

• On-time payment rate by vintage and by underwriting decile.
• NSF days per merchant per month, a leading indicator of stress 60+ days before default.
• Days to payoff vs. projected, separating slow-pay from default.
• Recovery rate on attempted-but-failed debits in the first 30 days after failure.
• Renewal capture rate on eligible accounts.
• Net charge-off rate by vintage, plus a forward-looking expected-credit-loss estimate.

7. Documentation as a discipline

Every restructure, every settlement, every modification to the original agreement must be in writing and signed. Verbal arrangements are how disputes turn into lawsuits. Beyond protecting you in litigation, clean documentation lets you cleanly sell paper or borrow against the portfolio, both of which depend on a buyer or warehouse being able to verify cash flows on each loan.

8. The technology floor

What "good" looks like in 2026 for the servicing platform: integrations with all major payment processors and ACH originators; an automated daily settlement file ingestion; a configurable NSF protocol engine; merchant portal with self-service ACH update and statements; rule-based renewal identification; an investor and bank reporting module (see our reporting product); and a full audit trail on every payment and modification event. The compliance side is covered in our compliance guide.

Building this stack from scratch is rarely the right call. Our team built a configurable servicing platform exactly because we ran portfolios where these capabilities were the difference between modeled and realized yield. See how we built it.

Frequently asked questions