# MCA Renewal Underwriting: When a Merchant Can Renew

- Author: TrueBankFlow (https://truebankflow.com)
- Published: 2026-10-17
- Category: MCA deals and funding
- Canonical: https://truebankflow.com/blog/mca-renewal-underwriting

> How MCA renewal underwriting works: paydown thresholds, payment history, fresh bank statements and how funders size the second advance.
MCA renewal underwriting decides whether a merchant who is partway through an advance can take a new one, and how large it should be. The funder checks how much of the first advance is paid down, how the payments performed, and what fresh bank statements show, then nets the remaining balance out of the new advance.

## When is a merchant eligible for MCA renewal underwriting?

A merchant usually becomes eligible for MCA renewal underwriting once a set share of the first advance's payback has been collected. Many funders use a paydown threshold somewhere around half, though the exact figure is a policy choice that differs by funder, merchant tier and how the first advance has performed.

The paydown threshold exists because a renewal pays off the old balance from the new advance. If the merchant renews at 10% paid down, most of the new money goes straight back to the funder, and the merchant walks away with little cash and a much larger obligation. A higher threshold means more of the renewal reaches the merchant as working capital.

Paydown is measured against the payback amount, not the cash advanced. On a $30,000 advance at a 1.40 factor rate, the payback is $42,000. Half paid down means $21,000 collected, regardless of how much of that was cost and how much was principal.

Funders also look at time, not only dollars. A merchant who reaches 50% in six weeks because sales spiked is a different case from one who took the full planned term to get there. Some funders pair the dollar threshold with a minimum number of payments, so a single lump sum cannot trigger an early renewal.

Eligibility does not mean approval. It only opens the file. The renewal is then underwritten again, with the first advance's performance as new evidence.

## Payment history the funder reviews in an MCA renewal

The payment history in an MCA renewal is the funder's own record of the first advance: how many scheduled debits cleared, how many bounced, whether the merchant asked for a payment change and whether collections followed sales. It is the strongest evidence the funder has, because nobody had to report it.

The funder's servicing system already holds this data. A renewal reviewer typically pulls:

- **Cleared and returned payments.** A count of debits that cleared against those returned, with dates.
- **Payment modifications.** Any request to lower or pause the daily amount, and why it was granted.
- **Reconciliation requests.** Whether the merchant asked to adjust payments to actual sales, and what the sales showed.
- **Pace against plan.** Collected payback compared with what the original term projected for this date.
- **Contact history.** Missed calls, changed bank accounts or a new processor without notice.

Returned payments deserve a closer look than a raw count. Two returns in one week after a bank holiday mean less than one return every month. A merchant who called ahead to explain a slow week is in a different position from one who went quiet.

A clean history pushes the renewal toward better terms. A messy one may still renew, but often at a lower amount or with a reconciliation adjustment first. A history with a default, a stop payment or a switched account usually ends the conversation.

## Fresh bank statements in MCA renewal underwriting

Fresh bank statements in MCA renewal underwriting cover the months since the first advance funded. The funder re-reads the account because the merchant's finances may have changed in ways the payment history alone does not show, such as new advances from other funders, falling deposits or a thinner balance.

The reviewer compares the new months with the original file. The questions are direct:

1. **Have deposits held up?** Average monthly deposits since funding against the averages used to size the first advance.
2. **Have balances thinned?** Average and lowest daily balances, and how often the account now gets close to zero.
3. **Did new positions appear?** Recurring daily or weekly debits to funders that were not in the account before.
4. **Are NSF items and negative days rising?** A count per month, and whether the trend started after the first advance.
5. **Is the account still the same account?** Account holder, number and processor should match.

New positions are the most common surprise. A merchant who took a second advance from another funder mid-term has stacked against the first, and the renewal funder now shares the same receipts with a competitor. Some funders decline those files outright, others require the other position to be paid off from the renewal proceeds.

Because renewals come back on a cycle, the same merchant's statements get read again and again. A tool that keeps the monthly totals and flags consistent helps. [TrueBankFlow](/) lines up statements month by month, recalculates deposit averages when you exclude an item and flags overdrafts with their dates, which makes the before-and-after comparison faster to check.

## How do funders size the second advance on an MCA renewal?

Funders size the second advance on an MCA renewal from the fresh statements, the same way they size any advance, then subtract the remaining balance on the first one. What the merchant actually receives is the net funding: the new advance minus the payoff, minus any fees the contract allows.

A worked example shows the arithmetic. Every figure is invented for illustration, and the policy choices are examples, not recommendations.

| Step | Example value | Note |
| --- | --- | --- |
| First advance | $30,000 | Cash funded at the start |
| Factor rate on first advance | 1.40 | Example |
| First payback | $42,000 | $30,000 x 1.40 |
| Collected to date | $25,200 | 60% paid down |
| Remaining balance | $16,800 | $42,000 less $25,200 |
| Payoff on renewal | $16,800 | No early payoff discount in this example |
| New advance approved | $45,000 | Sized from six fresh months of statements |
| Net funding to merchant | $28,200 | $45,000 less $16,800 |
| New factor rate | 1.35 | Example, reflecting a clean first advance |
| New payback | $60,750 | $45,000 x 1.35 |

Read the bottom of the table carefully. The merchant receives $28,200 in new cash but takes on $60,750 of new payback. Part of the new factor rate is being charged on the $16,800 that simply retires the old balance. That is why the paydown threshold matters: at 30% paid down, the payoff would be $29,400 and the net funding only $15,600 on the same $45,000 advance.

Some funders soften this by discounting the old balance when it is paid off through a renewal. Others keep the full remaining payback. Whether the contract offers a discount, and how it is worked out, is a contract term to read before quoting the merchant.

The new daily payment follows from the new payback and term. If the renewal runs 160 business days, $60,750 works out to about $380 a day. The reviewer checks that figure against the fresh average daily balance and the lowest balance days, just as on the first file.

## Renewal churn and the MCA renewal that should not happen

Renewal churn is the pattern where a merchant renews again and again at the paydown threshold, so the balance never falls and most new money retires old payback. An MCA renewal should not happen when it only keeps the merchant afloat, when deposits are falling or when the account shows positions the merchant did not disclose.

Churn is easy to miss because each renewal looks fine on its own. The merchant hits 50%, the payments are clean, the deposits are steady, and the file renews. Lay the renewals end to end and the picture changes: the total payback keeps climbing while net funding per renewal shrinks.

Warning signs a renewal reviewer can check:

- **Net funding falls renewal over renewal.** The merchant receives less fresh cash each time.
- **The merchant asks at the threshold, every time.** A renewal request on the first eligible day, three cycles running, suggests the business depends on it.
- **Deposits are flat or falling while advance size grows.** The funder is lending into a business that is not growing.
- **Balances are lower at each renewal.** The account is getting thinner even as payments clear.
- **Fees are a growing share of each renewal.** Origination fees taken from net funding add to the cost without adding cash.

When these signs appear, the reviewer can decline, offer a smaller renewal, or wait until the first advance is paid off in full. A merchant who is stretched may be better served by restructuring the existing balance than by a fresh advance at the threshold. Either way, the reason belongs in the file in plain words so the next reviewer sees the history.

## ISO handling of an MCA renewal file

An ISO handling an MCA renewal file sends a shorter package than on the first deal, usually a renewal request, the latest bank statements and any change in ownership or processor. The ISO's role in a renewal is smaller, and how much commission it earns depends on the agreement with the funder.

On the first deal the ISO assembled the whole package. For the steps and documents in a first-time file, see [what an MCA ISO submission package should include](/blog/mca-iso-submission). A renewal package typically needs:

- **A renewal request** naming the merchant and the original advance.
- **Bank statements since funding**, plus the latest month to date if the funder asks.
- **Notice of any change** to ownership, the business bank account or the card processor.
- **Disclosure of other advances** taken during the term.

Renewal commission is a frequent point of friction. Some funders pay the original ISO on renewals for a set period, some pay a reduced rate, and some pay only when the ISO brings the renewal in. The terms and how they are calculated are covered in [how MCA ISO commission is paid on new deals and renewals](/blog/mca-iso-commission).

One edge case is worth flagging for ISOs. A merchant whose deposits come mostly from gig platforms, such as a sole proprietor driving for delivery apps, may apply for an advance through a business account that looks thin. Funders underwrite that income differently, closer to the approach in [gig worker income verification from platform deposits](/blog/gig-worker-income-verification), and a renewal will re-check that the platform deposits are still arriving.

The renewal decision stays with the funder's underwriter. A clean, quick package makes that decision easier, and it is the part of the process the ISO controls.