Bank Statement Conversion for Merchant Cash Advance

What MCA underwriting reads from statements

A merchant cash advance is underwritten almost entirely off the bank statements, usually three to six months of them. The funder is not reading a credit report so much as a cash-flow story: how much revenue actually moves through the account, how much sits in it day to day, how often it runs dry, and what is already being pulled out. Reading those signals across several months of PDFs by hand is slow and inconsistent from file to file. Converting the statements to a CSV turns every deposit and debit into a row, so the metrics that decide the deal are computed from the data instead of estimated by eye.

Average monthly revenue, the true kind

The headline number is average monthly revenue, since the advance is typically sized at roughly 75 to 150 percent of it. But underwriters do not just total the deposits: they separate true operating revenue from transfers between the merchant's own accounts, loan proceeds, and advance fundings, which would inflate the figure. In a converted CSV you sort the deposits, exclude the non-revenue credits, and average what remains over the three- or six-month window. That gives a defensible revenue base for sizing the advance, and it is far more reliable than a raw deposit sum that quietly includes a transfer or a prior funder's deposit.

Average daily balance, NSFs, and negative days

Sizing is only half of it; the account has to be able to carry the remittance. Underwriters score the average daily balance, whether the merchant keeps enough in the account to cover a daily or weekly pull, with a common guideline of at least about five percent of monthly gross deposits. They count NSF and overdraft events, often looking for fewer than three in ninety days, and they want zero or few negative-balance days. A converted CSV lets you compute the average of the ending balances and filter for the fee and negative lines, so these risk scores come straight from the data rather than a page-by-page tally.

Spotting stacking: existing advance debits

The risk that sinks a file fastest is stacking, existing advances already drafting the account. Other funders pull a fixed daily or weekly amount by ACH, and several of those together can consume the cash flow before the new advance is ever repaid, which is why a stacked file is often a decline. Filtering the converted debits for recurring, same-amount daily or weekly withdrawals surfaces those positions immediately, along with the descriptor that names the funder. Catching them in the data, rather than missing one buried in a busy month, is what keeps the underwriting honest about how much room is actually left.

Fast files, applicant privacy

MCA underwriting runs on speed, and a converted statement set turns a submission into computed metrics in the time it used to take to skim one month. For a broker or funder processing many files a day, bulk conversion of an applicant's three to six months into one dataset is the difference between a quick decision and a backlog. Because these are a business owner's financial records, statements are processed to build the CSV and then deleted automatically, with nothing retained on a server afterward, so applicant account data does not sit in a third-party tool after the decision is made.

Frequently Asked Questions