Merchant cash advance underwriting is how an MCA funder decides whether a merchant can repay from future receipts, using bank statements as the main evidence. The underwriter totals deposits, reads daily balances, finds existing advances, counts negative days and NSF items, then sizes a holdback and advance the account can carry.
What do merchant cash advance underwriting teams pull from statements?
Merchant cash advance underwriting teams pull deposits, daily balances, existing advance debits, negative-balance days, NSF items and the merchant's recurring obligations from three to six months of statements. Each item answers a question about how much cash the merchant has and how much of it is already spoken for.
An MCA is a purchase of future receipts, not a loan, and funders usually collect through daily or weekly debits from the merchant's account. Because repayment comes straight out of that account, the account is the file. Applications are short, the decision is fast and the statements do most of the work.
A typical pull covers these items:
- Monthly deposits. Gross credits per month, less transfers between the merchant's own accounts, loan or advance proceeds and refunds. The result is a qualifying deposit figure.
- Average daily balance. The mean of the closing balance for each day, which shows the cash cushion better than the month-end figure.
- Lowest balances. The low point in each month, and how often the account approaches zero.
- Negative days. The count of days the balance fell below zero.
- NSF and overdraft items. Returned payments and fees, by date.
- Existing advance debits. Recurring debits to other funders, with their daily or weekly amounts.
- Other fixed debits. Rent, loan payments, payroll and tax payments.
- Deposit sources. Card processors, cash deposits, checks and transfers, since MCA repayment often follows card receipts.
The statements also answer an identity question. The account holder should match the application, the opening and closing balances should connect month to month and no pages should be missing.
Doing this by hand across dozens of applications a day is the reason MCA shops look at tooling. When evaluating MCA underwriting software, test it on your own statements: does it find the recurring advance debits, does it separate transfers from revenue and can an analyst trace each total to its source line. TrueBankFlow calculates total and qualifying deposit averages, flags NSF fees and overdrafts, groups recurring items and links every total to the lines behind it; the funding decision stays with the underwriter.
Funders that also serve slower products can read how business loans based on bank statements are structured, including the revenue minimums and funding speed they trade on.
Daily balances and holdback sizing in MCA underwriting
Holdback sizing sets the share of the merchant's receipts the funder collects each day, and daily balances show whether the account can absorb that debit. The underwriter sizes the holdback so total advance payments fit inside deposits and the daily balance never has to run to zero.
The holdback is the percentage of receipts remitted to the funder. It can be a fixed daily debit, set as the equivalent percentage of average daily receipts, or a share of card sales taken at the processor. The advance size follows from the holdback: the funder decides how much daily payment the account supports, multiplies by the term in business days and divides by the factor rate to find how much cash to advance.
A worked example
These numbers are an example. Funder policies and rates vary widely, and the policy limit below is invented for the illustration.
A merchant shows $80,000 in average monthly deposits across six months. The statements show two existing MCA debits: one of $250 per business day and one of $150 per business day.
| Step | Calculation | Result (example) |
|---|---|---|
| Business days a month | Assumed | 21 |
| Average daily deposits | $80,000 / 21 | about $3,810 |
| Existing daily debits | $250 + $150 | $400 a day |
| Existing holdback share | $400 / $3,810 | about 10.5% |
| Policy limit on total holdback | Example funder rule | 15% |
| Room left | 15% less 10.5% | 4.5% |
| New daily payment | 4.5% x $3,810 | about $171 |
| Term | Example | 126 business days (about 6 months) |
| Total payback | $171 x 126 | about $21,500 |
| Factor rate | Example | 1.35 |
| Advance size | $21,500 / 1.35 | about $16,000 |
Total daily debits after funding are about $571, which is 15% of average daily deposits.
The next test is the daily balance. Suppose the account's average daily balance is $14,000 and its lowest day in the period was $3,100. A $571 daily debit total sits comfortably under both. Now suppose the lowest day was $600 and the account touched zero twice. The same holdback would add overdraft risk, and the underwriter might cut the advance or lengthen the term.
Two cautions apply to every sizing exercise.
Deposits are not net cash. A merchant that deposits $80,000 but spends $78,000 on inventory, rent and payroll has little to give. Balances tell more about spare cash than deposits do. Sizing by deposits alone is how funders overfund.
Averages hide the shape. The average daily receipt of $3,810 hides slow days and busy ones. If receipts cluster at month end and debits run daily, the account may run low mid-month. Check the daily series, not just the mean.
Many funders set their own limits on total holdback, advance size relative to monthly deposits and minimum average balance. Those limits are policy, and the example above shows the arithmetic, not a recommended number.
Stacked positions spotted in MCA underwriting
A stacked position is an advance taken while earlier advances are still being repaid. MCA underwriting spots stacking by finding recurring daily or weekly debits to other funders in the statements, then adding them to the merchant's existing holdback before sizing anything new.
Stacking matters because every advance claims a share of the same receipts. Two positions at 10% each leave 80% of receipts, and a third at 10% leaves 70%. The merchant's margin may not support that, and each new funder's repayment risk rises with every earlier one.
The signs are visible in the account.
- Recurring identical debits. A debit of the same amount every business day, or the same amount every week, to the same payee name. Funders appear under names that can be unfamiliar, so a repeating debit with a fixed amount is a better clue than the payee text.
- Matching credits followed by debits. A deposit from a funder, then a daily debit starting a few days later. The deposit is the advance proceeds and should not count as revenue.
- Debits that start mid-period. A new recurring debit that appears in month three means a fresh position the application may not mention.
- Rising debits against flat deposits. If the daily debit total grows while revenue stays the same, the holdback share is climbing.
- Payoffs and renewals. A large debit that ends one stream followed by a new credit often means a refinance, which resets the position.
The underwriter lists every position found and compares it with what the merchant disclosed. A merchant that discloses two and shows four has a credibility problem, which weighs on the decision whatever the numbers say.
Counting the existing share is mechanical. Add every recurring advance debit, convert weekly debits to a daily equivalent, and divide by average daily deposits. That total feeds the holdback room calculation shown under holdback sizing. This kind of pass is tedious to repeat on every file, and the recurring-item grouping in analysis tools exists to find those repeating debits.
The same pattern shows up in other loan files. Underwriters of larger loans who see daily advance debits treat them as undisclosed debt, as described in business loan underwriting errors that stall approvals.
Negative days and NSF limits in merchant cash advance underwriting
Negative days are days the account balance closed below zero, and NSF items are payments the bank returned for insufficient funds. MCA underwriting limits both, because a merchant that already runs short will struggle when a daily debit is added.
Funders usually set maximums per statement period. One common structure is a cap on negative days in each month, plus a cap on NSF items over the review window. The values differ by funder and by risk tier, and a stronger file may be allowed more latitude than a marginal one. The limits below are examples only.
| Test (example) | Example limit | Why it matters |
|---|---|---|
| Negative days in any one month | No more than 3 | Frequent negative days mean no cushion |
| NSF items over three months | No more than 2 | Returned items show missed payments |
| Lowest balance against new daily debit | Above the daily debit | A debit larger than the low point will bounce |
| Negative days after a prior advance began | Trend should not rise | Rising stress after funding signals overextension |
Counting needs rules in advance. Is a negative day counted when the balance dips below zero intraday and recovers, or only at close? Does one returned item with a fee count once or twice? Are NSF fees caused by a bank error excluded? These details change outcomes, so write them down. The guide on how lenders count NSF fees on bank statements covers the counting rules and common exceptions.
Context matters too. Three NSF items in one week after a customer's check bounced is different from one a month for six months. Timing also matters: stress that predates the existing advances might be the reason the merchant needed them, while stress that began after them points to an overloaded account.
One further check helps. If the merchant has negative days even without the new debit, the account has no slack, and adding $171 a day makes the problem worse. A policy that denies such files protects the funder and the merchant alike.
SBA lenders count these events with a different purpose and different thresholds, since their loans are longer and carry a different repayment test. For that approach, read SBA loan underwriting guidelines for 7a cash flow.
Seasonal merchants that break MCA underwriting averages
Seasonal merchants break MCA averages because their deposits rise and fall on a calendar, so a three-month average from the high season overstates capacity and one from the low season understates it. Underwriting a seasonal file means choosing the window and holdback with the whole year in mind.
Take a landscaping company. Deposits may run $120,000 in each of the three summer months and $20,000 in each of the three winter months. A funder reading the summer statements sees $120,000 a month and sizes accordingly. When winter arrives, the same daily debit takes six times the share of receipts and the account runs dry.
Three adjustments help.
- Ask for twelve months where possible. A full year shows the peaks and troughs. If only three months are available, ask when the business is busiest and slowest, and read the present months against that answer.
- Size on the low period. Use the weakest quarter or the average of the lowest months to set the holdback. This is conservative, and it protects both parties.
- Match the term to the cycle. A six-month advance funded in April and repaid through September mostly runs in the busy season. The same advance funded in September runs into winter.
Some funders use a split or percentage-of-receipts remittance, so the payment shrinks automatically when sales fall. That structure suits seasonal merchants better than a fixed daily debit, though the funder still needs a cap on the term so the balance does not linger.
Other merchants fall into the same trap without a calendar. A merchant that landed one large contract, or had a single promotional week, will show a high average that will not repeat. Compare the median month with the mean. If they differ widely, one event is dragging the average.
A month-by-month view of deposits makes seasonal swings obvious. The interpretation, such as whether a dip is a season or a decline, stays with the underwriter.
When should merchant cash advance underwriting decline a merchant?
Merchant cash advance underwriting should decline a merchant when the statements show the account cannot carry another daily debit: no room under the holdback limit, repeated negative days, NSF items over the cap, unexplained deposits, incomplete statements or disclosure that does not match the account.
Declines are easier to defend when they rest on stated policy tests. Common ones include:
- No holdback room. Existing advances already use the share the funder allows, so any new payment would break the limit.
- Negative days or NSF items over the cap. The account fails the stress tests above.
- Falling deposits. Three months of decline suggest the average overstates current capacity.
- Low balances. The lowest balances sit below the proposed daily debit.
- Concentrated or unverifiable deposits. Most receipts come from one source that cannot be confirmed, or from transfers and loan proceeds.
- Incomplete or altered statements. Missing pages, balances that do not connect and signs of editing.
- Undisclosed positions. The merchant shows more advances in the account than the application lists.
Not every weak file is a decline. Some can be counter-offered with a smaller advance, a longer term, a lower holdback or a requirement to pay off an existing position from the proceeds. The example earlier shows how a smaller daily payment keeps a marginal file inside the limit. Repeat the arithmetic with a lower holdback and see what advance remains.
Document the reason in the file in plain terms: "average daily balance of $2,400 against a proposed $571 daily debit; five negative days in the last month." That record helps a second reader, supports consistency across analysts and answers a merchant who asks why.
A final point on process. The decision belongs to the underwriter. Software can speed the counting and show every figure's source, but it does not replace the judgment on a borderline file. To see how TrueBankFlow prepares statement evidence for that judgment, request a spot; the team is onboarding lenders in small groups.