How to Build a Funder-Ready Merchant File: Documents, Payments and Handoff

An MCA broker preparing a funder-ready file needs application and document workflows, statement analysis, exception notes and a record of the package shared with the funder. A CRM can handle some of that work if it is configured for it. The buying test is whether a second reviewer can reconstruct the file from its records without searching the first rep’s inbox.

Keep the receiving funder’s requirements beside the application. Forward Financing’s application process asks for business information and recent business bank statements, with identification, a voided check and bank verification also required. It may request tax returns or proof of ownership. These are one provider’s requirements, not a universal MCA checklist. Software should help a team meet the applicable requirements without treating every available document as mandatory.

A complete package gives an underwriter evidence to review. It does not guarantee approval, establish the merchant’s ability to pay or eliminate questions about unusual activity. The broker still needs someone to check the documents and explain unresolved issues before sharing the file.

Build the file around evidence, not attachment counts

Start with the legal business name, DBA, ownership, contact information, requested amount and use of funds. Identify the relevant application and bank accounts. Keep a new funding request distinct from the merchant’s earlier applications so a prior approval or expired document cannot be mistaken for current evidence.

For statements, record the account and period covered, check that every requested page is readable and confirm that the account name fits the application. Preserve the original PDF. A screenshot of an account balance cannot replace a full statement when the funder requires transaction history. If a DBA differs from the account name, attach the explanation and supporting evidence rather than silently changing the name.

Review deposits before describing them as revenue. Transfers between accounts, owner contributions and financing proceeds can increase deposits without representing sales. Keep the treatment of those entries visible in the analysis. the bank-statement underwriting guide explains deposit quality, returned payments and negative-balance days. If the documents cover only one operating account, label that limit.

Existing advances need a separate record of the funder or observed payee, payment amount, frequency and evidence date. Flag uncertain identifications. Ask for current agreement or payoff information where the decision depends on terms that the statement cannot establish. A funding deposit near month-end may indicate a new position before any repayment appears.

Use a short handoff note that distinguishes verified facts from merchant explanations and open requests. In a hypothetical file, the bank account uses a DBA, one statement is missing its last page and a recurring withdrawal has an unfamiliar description. The note should identify the ownership evidence, request the complete statement and leave the withdrawal unresolved until checked. Calling the file complete because three PDFs arrived would hide all three issues.

Collect documents without repeating requests

Name the account and statement periods needed, request all pages and specify the acceptable format. An original PDF downloaded from the bank is preferable to cropped screenshots when the review requires a complete statement. Tell the merchant how to use the supported upload path. Do not ask them to give a rep their banking password.

Use separate states for requested, received, needs correction and accepted. These can be maintained through a product’s supported checklist or a controlled team procedure; the labels alone imply no automation. Record the reviewer and date of acceptance. A file upload confirms receipt, while acceptance requires a check that the document satisfies the stated request.

At receipt, confirm the file opens, belongs to the intended business and covers the right period. Check page numbering and legibility. If the account uses a different business name, preserve that name and request an explanation. Avoid overwriting the application just to make two fields match.

For a hypothetical correction, suppose a merchant uploads the first pages of September’s statement and a complete August statement. Ask for the complete September PDF, not another copy of every document. Keep August accepted if it meets the requirement. Record the remaining request against September so a second rep can avoid repeating the same call.

When a corrected copy arrives, identify which copy supports the current review and retain earlier material only under the applicable records policy. If the application waits long enough for the funder to require another period, explain that as a new freshness requirement. Do not describe the previously accepted statement as missing.

Check likely MCA payments before the handoff

Software can identify likely MCA payments by grouping recurring withdrawals and comparing descriptions, amounts and dates. A broker must still check the result against the source transactions and current supporting records. The statement can support an estimate of payment commitments at period end; it cannot establish a live payoff balance or prove that every obligation has been found.

Payment cadence helps find candidates, but it cannot identify the legal product. Forward Financing’s application process describes automatic daily or weekly payments for both revenue-based financing and business loans. Classify an obligation from the supporting evidence rather than assuming every frequent debit is an MCA. Keep other recurring operating expenses out of the MCA total.

Preserve the description printed on the statement separately from the proposed funder name. A processor or collection agent may use a different name. Similar descriptions can help group transactions, but the merchant’s agreement or current servicing information should confirm the relationship when the identification affects the funding decision.

Inspect returns and reversals before calculating cash paid. A failed debit and a later successful retry should not be treated as two completed payments. Fees need their own classification. If amounts or timing change, retain the actual dates and ask whether the series reflects an adjustment, catch-up payment or another arrangement. Do not force irregular activity into a fixed schedule merely to produce a tidy total.

Keep uncertain groups visible. A repeated withdrawal could be payroll, tax, rent, a vendor payment or financing. Ask the reviewer to confirm it, correct it or leave it unresolved with a specific evidence request. A recognizable name is useful evidence, but a name match alone cannot establish the remaining balance or contractual payment terms.

New funding also matters. In a hypothetical month-end file, an advance reaches the account on the last statement day and its first debit falls in the next period. A review based only on recurring withdrawals would miss the new commitment. Retain the funding evidence and request the agreement and payment schedule rather than treating the absence of a debit as evidence of no position.

Historical cash paid and estimated ongoing payments answer different questions. A position paid off during the statement period may contribute to cash paid but no longer require future payments. A recently funded position may require future payments even though the statement contains none. Record the evidence date and the reason each position is included in the ongoing estimate.

Withhold compares estimated monthly MCA payments with average monthly net deposits. Show the numerator, denominator and months used. Check the treatment of transfers and financing proceeds so non-operating deposits do not distort the comparison. If the denominator is zero or negative, flag the limitation instead of presenting an ordinary burden percentage.

Ask the software vendor to demonstrate the handoff

Run a trial with synthetic documents rather than a real merchant’s financial records. Have one tester add the application and statements, another identify an incomplete page set, and a third take over the review. Ask the vendor to show which copy is current, who owns the correction and what remains open. These are acceptance tests, not capabilities to assume from a product label.

Then ask for the exact package a permitted funder would receive. Check its contents against the internal record. Record the recipient and the version shared, and keep later corrections distinguishable. A vendor’s demonstration should establish whether that record is built in, requires configuration or depends on a manual procedure. Confirm any integration with a funder before buying on the strength of it.

Include access and retention in the evaluation. the Federal Trade Commission’s information-security guide recommends collecting only necessary sensitive information, restricting access and defining a written retention policy. Ask how the product handles source PDFs, extracted transactions, reports and backups. Establish who can share a file and how access ends when a colleague leaves.

Plutus’s cash-flow analysis page describes PDF statement analysis that separates deposits, transfers, advances and payments, with estimated current MCA commitments. Its published merchant-file guidance describes application information, documents, notes and shared review context. Test those workflows in the account you intend to use. Do not infer automatic delivery to every funder, a live payoff balance or a replacement for your sales system. the CRM and funding-workflow comparison covers the CRM buying decision.

Explore merchant-file workflows and cash-flow analysis at Plutus.