Bank statement analysis for MCA underwriting: a practical guide

The core metrics underwriters evaluate

The fundamental question in MCA underwriting is whether the merchant's cash flow can sustain the daily or weekly remittance without impairing business operations. The primary metrics drawn from bank statements are: average daily balance (ADB) over three to six months, total gross monthly deposits, revenue consistency month-over-month, NSF (non-sufficient funds) and overdraft frequency and recency, and the presence of existing advance remittances or loan payments being swept from the account.

Deposit consistency matters as much as volume. A merchant with $100,000 in average monthly deposits concentrated in two payments from a single customer is a different risk profile than one with $100,000 spread across daily consumer transactions. Underwriters assess the deposit pattern, not just the total. Significant month-to-month variation without a clear seasonal explanation warrants a deeper look at the underlying business activity.

Red flags to document

Common red flags in bank statement analysis include: large, round-number deposits that do not match the stated business type; a spike in deposits in the most recent month inconsistent with prior months; evidence of stacking (regular outflows to multiple MCA funders in overlapping periods); NSFs in the most recent 30 to 60 days; large unexplained transfers out of the account; and a significant gap between gross deposits and net cash balance that suggests high fixed costs or external obligations not disclosed on the application.

Each red flag should be documented in the case file at the time of underwriting — not reconstructed after a default. The underwriter's note should state the observation, the data it is drawn from (specific months), and the disposition: whether it was cleared by additional documentation, escalated, or accepted as a known risk. A case file that shows the underwriter saw a red flag and documented the reasoning is far more defensible than one that is silent.

Building a defensible underwriting record

A defensible MCA underwriting record links the bank statements as submitted, the underwriter's analysis, the specific data points relied upon, and the final decision — in a way that can be reconstructed months later if the advance defaults. This means the case file should retain the original statements (not just a summary), the underwriter's contemporaneous notes, any questions sent to the merchant and the responses received, and the final approval or denial with the stated reasons.

When an AI or automated tool assists with bank statement analysis — for example, extracting deposit totals or flagging NSF patterns — the tool's output and the human reviewer's action on that output should both be in the record. Funders who can show a documented, consistent underwriting process across their portfolio have a materially stronger position in collections disputes, investor audits, and regulatory examinations.

FAQ

Bank statement analysis for MCA underwriting — common questions

Related