# MCA ISO Submission: What a Complete Deal Package Holds

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

> What an MCA ISO submission must include for a fast decision: the application, bank statements, processing history and the notes funders want.
An MCA ISO submission is the deal package an independent sales organization sends a merchant cash advance funder: a signed application, the most recent bank statements, card processing statements where relevant, a list of open advances and a short note on the merchant. A complete package gets a decision or an offer, while gaps get a pend.

## What belongs in a complete MCA ISO submission?

A complete MCA ISO submission holds everything an underwriter needs to price the deal without asking a question: the signed application, owner identification, recent bank statements, processing statements for split-funded deals, a disclosure of open advances and the ISO's notes. Funder requirements vary, so start with each funder's own submission guidelines.

The checklist below covers the items most funders expect. The reasons column is what an ISO should keep in mind when a merchant pushes back.

| Item | What to send | Why the funder needs it |
| --- | --- | --- |
| Signed application | Legal business name, DBA, address, tax ID, start date, industry, owner details and ownership percentages | Identity checks, industry screening and guarantor details |
| Owner identification | Copy of a government ID for each guarantor | Matches the guarantor to the application |
| Business bank statements | The most recent full months the funder asks for, often three to six, every page | Revenue, balances, stress events and existing debits |
| Month-to-date activity | A current transaction history or a portal export since the last statement | Shows nothing has changed since the last statement closed |
| Card processing statements | The most recent months, if the deal will be split funded or card revenue is large | Confirms card volume and the processor who would split |
| Open advance disclosure | Each funder, original amount, payment, frequency and estimated balance | Position, payoff and stacking checks |
| Voided check or account details | For the account the funder will debit | Sets up collection |
| Requested amount and use of funds | What the merchant wants and why | Sizing and context |
| ISO notes | A short summary of anything unusual in the file | Saves the underwriter from guessing |

Some funders also ask for a landlord contact, a business license or tax returns on larger deals. Ask before sending, rather than attaching everything the merchant has. A file that includes six unrelated documents is slower to read, not faster.

Each funder has its own submission address or portal, and many reject submissions that arrive in a different format. Keep a short sheet per funder listing what it wants.

## Bank statements in an ISO submission: months, pages and recency

Bank statements in an ISO submission should be the most recent complete months the funder asks for, for the account that receives the business's revenue, with every page included and no gap between the last statement and today. Statements are the evidence the deal is priced on, so missing pages or stale months stop the review.

The common problems are easy to prevent:

- **Missing pages.** A statement sent without its last page often lacks the daily balance summary or the final transactions. Count pages against the "page x of y" marks before sending.
- **Wrong account.** A merchant with two accounts sometimes sends the quieter one. Ask which account the card processor and main customers pay into.
- **Stale statements.** A funder reviewing a file in late October with statements through July will ask for August and September. Send them first.
- **Screenshots and partial exports.** Funders want the bank's PDF statement. Screenshots or spreadsheets the merchant typed are often refused or treated as unverified.
- **Edited files.** Any sign of alteration, such as fonts that do not match or balances that do not connect, ends the deal and can end the ISO's relationship with the funder.

Before sending, the ISO can run a quick self-check. Do the closing balance of one month and the opening balance of the next agree? Do deposits look roughly like the revenue on the application? Are there recurring debits the merchant did not mention? Answering these before the funder does lets the ISO fix the file or explain it in the notes.

That review is the kind of reading [TrueBankFlow](/) speeds up: it lines up months of statements by account, totals deposits per month and flags statements that fail a balance check, so an ISO or funder can see a gap before the deal goes out.

## Listing open advances in the ISO submission

Listing open advances in the ISO submission means naming every advance or revenue-based product the merchant is still paying, with the funder, the original amount, the payment and frequency and the estimated balance left. Funders find undisclosed positions in the statements anyway, so a full list protects the deal and the ISO's credibility.

Ask the merchant directly, then check the statements. Merchants sometimes forget a small weekly debit or describe a renewal as the same advance. Look for:

- Fixed debits on every business day or every week, to the same payee.
- A large incoming deposit from a funder name, followed a few days later by a new recurring debit.
- A recurring debit that stopped, followed by a larger one with the same payee, which usually means a renewal.

An example disclosure line might read: "Funder X, funded $25,000 in May, $310 daily ACH, merchant estimates $11,000 remaining." If the merchant has a payoff letter, attach it.

Position disclosure also tells the funder whether the deal is a first, second or third position, and whether any open contract forbids further advances. Many first-position contracts do. An ISO that submits a stacking deal without saying so wastes the funder's time and risks putting the merchant in breach.

Merchants applying for other credit carry the same debts into those files. Mortgage underwriters, for example, count recurring obligations against income, as covered in [the debt-to-income ratio on a bank statement loan](/blog/bank-statement-loan-debt-to-income-ratio), and daily advance debits can surprise a merchant who did not expect them to count.

## The ISO submission cover note funders read first

The ISO submission cover note is a few lines at the top of the email or portal entry that tell the underwriter what kind of deal this is and anything unusual in the file. A good note answers the questions the statements will raise before the underwriter has to ask them.

A useful note covers:

- **The request.** Amount, preferred term and whether the merchant wants split funding or ACH.
- **Position.** First position, or the list of open advances.
- **Use of funds.** Inventory for a season, equipment repair, a payroll gap.
- **Explanations.** A low month, a one-time large deposit, a returned item caused by a customer's bounced check or an account switch.
- **Merchant constraints.** For example, the merchant is changing processors next month, or the owner is out of the country for two weeks.

Here is an example of a short note. All details are invented: "Restaurant, 6 years in business, owner at 100%. Requesting $35,000 for a kitchen refit, prefers weekly ACH. First position. August deposits are low because the restaurant closed for two weeks of renovation; September is back to normal. One NSF on 9/14 was a supplier's double debit, refunded 9/16."

Each line saves a round of questions. The note should never contradict the documents. If the statements show two advances, the note cannot say first position.

Commission terms belong elsewhere, not in the note. How ISO compensation is set and when it can be clawed back is covered in [MCA ISO commission structures](/blog/mca-iso-commission).

## Why do funders pend or decline an ISO submission?

Funders pend an ISO submission when something they need is missing or unclear, and decline it when the documents show a merchant outside their guidelines. Most pends come from preventable gaps: missing statements, unsigned applications, undisclosed advances and unexplained deposits.

Typical pend reasons include:

- Statements missing a month or a page.
- No month-to-date activity when the last statement closed weeks ago.
- An application missing the tax ID, ownership percentages or a signature.
- Deposits that do not match the revenue on the application, with no note.
- A recurring debit to an unknown payee that could be another advance.

Typical decline reasons include:

- An industry the funder does not fund.
- Too many negative days or returned items under the funder's policy.
- Existing advances that already take as much of revenue as the funder allows.
- Signs of altered statements.
- Time in business or monthly revenue below the funder's minimum.

A pend is a request, not a rejection. Answering it the same day, completely, often decides whether the funder makes an offer before another funder does. Answering it piecemeal turns one pend into three.

## When an ISO should hold a deal back from submission

An ISO should hold a deal back from submission when the file is incomplete, when the merchant has not been honest about open advances, when the deal plainly falls outside the funder's guidelines or when the merchant's account is in active distress. Sending a weak file wastes the underwriter's time and can cost the ISO standing with that funder.

Shopping a deal to many funders at once creates a separate problem. Funders often see the same merchant arrive from several ISOs within days, sometimes with different figures. That looks like a merchant shopping for anyone who will fund and can lead funders to decline. Choose the funders that fit the profile and send a complete file to them first.

Distress deserves particular care. A merchant whose deposits are falling and whose account is overdrawn every week may want money badly, but another advance can turn a slow business into a default. If the merchant already has an advance, the better first step may be asking that funder for a reconciliation under the contract, covered in [the MCA reconciliation clause](/blog/mca-reconciliation-clause), rather than stacking a new one.

Holding a deal back is also the right call when the merchant will not provide a current month or explain an obvious problem. A funder will ask the same questions, and an ISO that has the answers sends better deals. Funders who want to see how statement analysis fits their intake can [request a TrueBankFlow spot](/get-started).