In a merchant cash advance, the funder purchases a fixed amount of future receivables at a factor rate and collects through a daily or weekly remittance, usually an ACH debit against the business's operating account. Because repayment is taken directly from cash flow, MCA underwriting rests on what the bank statements actually show: true revenue, average daily balance, existing debt positions, time in business, and the rhythm of deposits and debits across recent months. It differs from conventional lending in both pace and evidence. There is no long amortization schedule and rarely any collateral. The file is thinner, the term is shorter, and the bank account is the primary source of truth.

Why MCA underwriting differs from conventional lending

A conventional lender asks whether the business can service monthly payments over years. An MCA funder asks whether the account can carry a fixed debit every business day for months. That difference changes what the underwriter looks at. Long-term financial statements matter less than the last several months of activity, because the advance will be collected quickly. The credit report still informs the file, but the bank statement does most of the work.

The remittance structure changes the risk math too. Most advances collect a fixed ACH debit on each business day or each week, so the underwriter is really sizing a daily obligation against daily deposits. Some programs still split a percentage of card batches, which softens the fixed-payment risk but adds a verification step on the processor side. Either way, the question stays the same: does the account reliably generate enough cash to cover the payment and still run the business.

Because the file is thin, each document carries more weight. There is no three-year history of audited statements to lean on, so a missing statement month or an unexplained deposit does proportionally more damage to confidence in the deal. The compressed term also compresses the decision. Most MCA underwriting happens in hours or days, not weeks, which is why funders rely on screening rules applied the same way to every deal. Speed only works when the underlying checks are consistent: revenue measured the same way, positions counted the same way, exceptions documented the same way. The rest of this guide walks through each part of that review in the order most shops run it.

Bank statement analysis: the core of the review

MCA underwriting begins with the bank statements because the remittance will be drawn from that account. Most funders ask for the most recent three to six months, all pages, for every account the business operates. Four numbers do most of the work: true revenue, average daily balance, existing positions, and negative days.

True revenue vs. total deposits

Total deposits overstate what a business earns. A working month of deposits can include transfers between the owner's accounts, proceeds from another advance or loan, refunds, tax payments returned, and one-time items like asset sales. None of those are revenue, and counting them inflates the deal. True revenue is deposits minus everything that is not a sale: customer card settlements, invoices paid, checks from customers, recurring processor batches.

The distinction matters most on businesses that move money between accounts or hold multiple operating entities. A $150,000 deposit month can shrink to $90,000 of true revenue once inter-account transfers are stripped out, and those are very different deals. Sorting deposits into revenue and non-revenue is the most time-consuming step in manual underwriting, and it is where errors hide. Every exclusion should be defensible later, which means keeping a record of what was removed and why. For a deeper look at how this step works in software, see bank statement analysis.

Average daily balance

Average daily balance (ADB) is the sum of each day's ending ledger balance divided by the number of days in the period. It measures the cushion the account actually keeps, which is what a daily remittance draws against. A business can deposit strong revenue and still run a thin ADB if money leaves the same day it arrives. That pattern, deposits in and wires out within hours, leaves little room for a new daily debit.

Read ADB against the proposed remittance, not against revenue alone. A funder will ask whether the account's typical daily balance comfortably covers the daily payment, with room for the business's own operating swings. Low or volatile ADB is one of the most common reasons an otherwise healthy-looking deal gets a smaller approval or a decline.

Deposit count and rhythm

Revenue quality shows up in the count and cadence of deposits, not just the total. A restaurant or retailer may settle card batches most days; a contractor may deposit a handful of large checks a month. Neither is wrong, but the pattern should match the business described on the application. One or two large deposits carrying an otherwise quiet month deserves a second look, because lumpy revenue is harder to collect a daily remittance against than steady deposits.

NSFs and negative days

Negative days count the days the account ended below zero. NSFs count returned or rejected transactions, including bounced ACH debits. Both are stress signals, and both are easy to count once statements are parsed, which is why they appear in almost every screening rule set.

Frequency and timing matter more than a single event. One negative day in six months after a large quarterly expense reads differently than five negative days a month, and NSFs that cluster around existing funder debits suggest the current obligations are already straining the account. Underwriters also look at whether negative days are trending better or worse across the statement period.

Why statement months are weighted

Months are not equal in an MCA review. The most recent month carries the most weight because it is the closest picture of the account the remittance would hit next week. A deal that averaged $120,000 a month across six statements but dropped to $70,000 last month is not a $120,000 deal. Some funders weight the latest month explicitly, others simply read it first, but the practice is the same: recency wins.

Weighting cuts both ways. A strong recent month after a weak stretch may reflect a seasonal recovery or a one-time deposit spike, so underwriters check whether the recent deposits look like the business's normal revenue pattern. Consistency across months is often worth more than one exceptional month.

Position and stacking detection

A position is an existing advance the business is already paying. Positions show up on bank statements as fixed daily or weekly ACH debits, often from recognizable funder names or payment descriptors, and finding every one of them is a core underwriting task. The remittance schedule gives them away: a debit for the same amount every business day is almost always a funder, a lender on a fixed schedule, or an equipment payment. Each needs to be identified and counted before a new advance is priced.

Stacking is what happens when a business holds multiple advances at once. Each new remittance competes for the same deposits, so combined daily debt service climbs with every position. A first position priced against clean cash flow, a second added on top, and a third stacked behind that can leave the account paying out more per day than it reliably deposits. That is why most funders limit the positions they will fund behind, and why position count sits inside screening rules rather than being left to judgment.

The harder problem is undisclosed positions. An application may list one advance while the statements show debits to three funders. Some stacking happens in the gap between application and funding, when a merchant takes a new advance while the first file is still open. Comparing the disclosed positions on the application against every recurring remittance visible on the statements is the check that catches it. Any funder debit that does not appear on the application is a flag, not a rounding error.

Estimating combined debt service closes the loop. Add up the daily or weekly remittances already running, add the proposed new payment, and compare the total against true revenue and ADB. If existing positions already consume a meaningful share of daily deposits, the next position either needs a smaller payment or does not belong on the account at all.

Deal screening rules

Screening rules turn the review into a repeatable gate. Before an underwriter spends real time on a file, the deal is checked against a small set of thresholds: does it clear the bar, does it need an exception, or does it stop here. Most MCA shops screen on five numbers drawn straight from the statements.

  • Monthly revenue. A minimum true revenue floor, not total deposits. Minimums vary by funder and deal size; a common practice range for smaller advances is roughly $10,000 to $20,000 of monthly true revenue.
  • Average daily balance. A floor that keeps a real cushion in the account. Smaller programs often set it in the low thousands.
  • Existing positions. A maximum count. Many funders fund first or second positions only; some will not fund behind any position at all.
  • Time in business. Verified from formation records or the first deposits on the statements. Six to twelve months is a common minimum, with longer history expected for larger deals.
  • Negative days and NSFs. A cap per month or across the statement period. Zero to a few per month is a common tolerance, with the pattern reviewed rather than just the count.

Screening also sets size. Advance amounts are commonly set as a fraction of demonstrated monthly true revenue rather than the amount requested on the application, so a deal that clears the minimums may still come back smaller than the merchant asked for. Treating the approved amount as an output of the statements, not a negotiation, is what keeps the book consistent.

These ranges are illustrative rules of thumb, not universal policy. Every funder calibrates its own box by industry, deal size, and risk appetite. What matters operationally is that the rules are explicit and applied the same way to every file. When a deal fails a rule, the response should be recorded: declined, or approved as a documented exception with the reasoning attached. A screening rule that lives in someone's head is not a rule; it is a habit that breaks the first time that person is out. For more on how this runs in Lendquo, see deal screening.

Document intake and the deal book

MCA files are light compared to conventional lending, which makes completeness easy to verify and painful to miss. A typical deal book holds the application, three to six months of bank statements for each operating account, a voided check for the remittance account, a government-issued ID for the signer, and the merchant's credit pull. Larger deals add tax returns, and businesses that bill on invoices may include an AR report.

Intake has its own checks before analysis starts. Every statement month should be complete, with all pages present and the most recent statement recent enough to reflect current activity. The entity name should match across the application, the statements, the voided check, and the ID; a mismatch is either a clerical fix or a flag, but it has to be resolved, not absorbed. Stated revenue on the application gets compared against the statements early, because a large gap changes the conversation.

Files arriving from brokers and ISOs add one more variable: completeness varies by sender. Some shops grade their ISO partners on package quality, because a file that arrives with every account, every month, and a signed application underwrites in a fraction of the time a scattered submission takes. Naming what a complete package looks like, and asking for it the same way every time, removes a surprising amount of back-and-forth.

Organization is what lets the file survive handoffs. When documents land in one book with clear names and date ranges, the next reviewer can see what has arrived, what has been reviewed, and what is still missing without asking anyone. That discipline is covered in more depth in a clearer path from documents to decisions, and the handoff side is covered in building a book your whole team can follow.

Source-linked review

Every figure in an MCA file should trace back to a statement page. True revenue should point to the deposits it counted and the ones it excluded. Position counts should point to the recurring debits behind them. The reason is practical: any figure that cannot be traced gets recalculated, and recalculation is where underwriting time goes.

Source-linking also protects the deal after the decision. Funding partners, syndication participants, and internal reviewers will ask how a number was reached, and "the software said so" is not an answer that holds. When the source rides alongside the figure, a second reviewer confirms it in seconds instead of rebuilding the analysis. The fuller argument is in every insight deserves a source.

Common failure modes and red flags

Most bad MCA outcomes trace back to a short list of misses. These are the ones worth checking twice.

  • Counting gross deposits as revenue. Transfers between the owner's accounts, advance proceeds, and refunds inflate the top line. This is the most common error and the easiest to prevent.
  • Missing a position. A recurring funder debit that never made it onto the application, or a new advance taken while the file was open. Always reconcile disclosed positions against what the statements show.
  • Anchoring on the average instead of the latest month. A declining trend hides inside a healthy six-month average. Weight recent months.
  • Treating all NSFs as equal. One returned debit after a large tax payment is different from weekly rejections of existing remittances.
  • Statement edits. Missing pages, inconsistent fonts, running balances that do not reconcile line to line, or PDFs that arrive with no transaction detail. Verify page counts and check that balances carry forward.
  • Revenue concentrated at month end. A single large deposit late in the month can mask a thin operating pattern, and it deserves a closer look at what it actually is.
  • Entity mismatches. Different business names across the application, statements, and check, or deposits flowing to a different entity than the one applying.
  • Deposits in, money out, same day. High revenue with near-zero ADB means the account keeps no cushion for a daily debit.

None of these flags is automatically fatal. Each is a question the file should answer in the open, with the answer recorded where the next reviewer will find it.

The MCA underwriting checklist

A condensed pass through the whole review, in order. Adapt the thresholds to your own credit box.

  1. Confirm the entity name matches across the application, bank statements, voided check, and photo ID.
  2. Verify the file has the most recent three to six months of statements, all pages, for every operating account.
  3. Compare stated revenue on the application against what the statements show.
  4. Calculate true revenue for each month, excluding transfers, financing proceeds, refunds, and one-time deposits.
  5. Compute average daily balance for each month and note the lowest ending balances.
  6. Count negative days and NSFs per month and check whether they are trending better or worse.
  7. Identify every recurring daily or weekly remittance and match each one to a disclosed position.
  8. Flag any funder debit that does not appear on the application.
  9. Estimate combined daily debt service, existing positions plus the proposed payment, against true revenue and ADB.
  10. Verify time in business against formation records and the earliest statement activity.
  11. Run the deal against your screening rules and record every pass, fail, and exception.
  12. Trace each headline figure back to its statement page before the credit decision is signed.

How this looks in Lendquo

Lendquo was built for exactly this review. Statements, applications, IDs, and voided checks land in one book per deal, and bank statement analysis parses them into a source-linked bank sheet where true revenue, average daily balance, positions, and negative days each trace back to the transactions behind them. Your thresholds run as deal screening rules applied consistently to every file, and when a deal clears, contracts and funding steps carry forward from the same record. See MCA underwriting software for the full picture, or ask a deal a question in plain English and get an answer with the sources still attached.