The Complete Funding File: A Checklist Before You Submit
Half the back-and-forth after a submission comes from something missing. Build the whole file once, check it against a list, and send it clean.
It is Thursday afternoon. You have a merchant who is ready, a funder whose guidelines fit, and an itch to submit before the weekend. Then the underwriter replies: missing page two of the March statement, the ID is expired, and the application lists a different business address from the one on the statements. Monday becomes Wednesday, and the merchant starts returning someone else's calls.
Incomplete files are the most avoidable delay in business funding. Underwriters work through queues, and a file that needs three follow-ups sits behind the files that arrived complete. A short, consistent checklist, run before every submission, fixes most of it.
Requirements differ by funder and by deal size, so treat this as a baseline and add whatever each lender on your panel asks for.
Pre-flight summary
- Incomplete files are the most avoidable source of funding delays.
- Every document is checked against the application, so the application must be right.
- Collect full statements, every page, and read them before submitting.
- Request slow documents such as ownership and lease paperwork early.
- A short broker summary that names weaknesses makes the file more credible.
Leg 01Layer one: the application itself
The application is the spine of the file, and every other document gets compared to it. Fill it in carefully with the merchant rather than letting them rush it, and read it back before they sign.
- Legal business name and any trade name, matching the bank account
- Business address, phone, entity type, tax identification number and start date
- Each owner's name, ownership percentage, home address and contact details
- Requested amount and stated use of funds
- All existing funding positions, disclosed fully
- Signature and date from every required signer
Leg 02Layer two: bank statements
Collect complete statements, every page, for the number of months the funder requires, plus the most recent month-to-date activity if they ask for it. Partial statements and cropped screenshots are the most common reason a file bounces back.
Before you attach them, read them. Check that names and account numbers match the application, that months are consecutive, and that balances carry over from one statement to the next. Note your true revenue estimate, NSF and negative-day counts, and every existing position. If FundPilot's statement underwriting has processed them, check its figures against the pages they link to and correct anything that needs correcting before the file leaves your desk.
Leg 03Layer three: identity and banking verification
Funders need to know who they are dealing with and where funds and remittances will go. These documents are simple, which is exactly why they get forgotten until the last minute.
- Current, unexpired government-issued photo ID for each owner who signs
- Voided check or bank letter for the account that will receive funds
- Confirmation that the account on the voided check matches the statements
- Any processor statements the funder requests for card-heavy businesses
Leg 04Layer four: ownership and location documents
Many funders want to confirm the business exists, who owns it, and where it operates. Depending on the funder and the deal, that may include formation documents, a business licence, proof of ownership percentages, and a lease or landlord contact for the business location. Some ask for a mortgage statement if the merchant owns the property.
Ask for these early. A merchant digging out formation documents on the day you want to submit is a merchant who now has a reason to wait. A branded merchant portal makes this easier: in FundPilot, merchants upload documents directly to their deal through your portal instead of emailing attachments, and you can see at a glance what is still outstanding.
Ask for the slow documents first and the quick ones last.
Leg 05Layer five: your notes
The file is not only documents. It is your read of them. A short broker summary at the top of the submission saves the underwriter time and signals that you have done your work.
Include the merchant's industry and time in business, your true revenue estimate with the adjustments you made, the existing positions and total burden, NSF and negative-day trends, any seasonality, and anything unusual along with the merchant's explanation. If there is a weakness, name it. Underwriters trust brokers who point out problems rather than hoping they go unseen.
Keep the summary factual and short enough to read in a minute. A hypothetical example: a four-year-old plumbing contractor, true revenue around $52,000 a month after removing a $6,000 owner transfer, one disclosed position at $210 per business day, two NSFs in the oldest month and none since, and a slower January the merchant attributes to weather. That paragraph answers most of an underwriter's first questions before they open a single PDF.
Leg 06The final pass before you hit send
Run the same short pass on every file, no matter how rushed the day is. It takes a few minutes and saves days.
When the checklist lives in your CRM as required items on a pipeline stage, nobody has to remember it. FundPilot's custom stages can hold that checklist, so a deal does not move to submitted until the pieces are there.
- Confirm every name, address and account number matches across application, statements and voided check.
- Check every statement is complete, consecutive and readable.
- Verify IDs are current and match the signers.
- Confirm all existing positions are disclosed on the application and in your notes.
- Re-read the lender's guidelines and confirm the file fits them.
- Attach your broker summary and send only to funders whose criteria match.
Questions from the floor
Do all funders need the same documents?
No. Requirements vary by funder, deal size, industry and time in business. Larger requests often need more, such as additional months of statements or financial documents. Keep each lender's current document requirements on record in your CRM and check them before every submission, rather than relying on memory or an old email. Treat this checklist as a baseline, not a universal list.
How should merchants send sensitive documents?
Avoid ordinary email attachments where you can, since statements and IDs contain sensitive data. A secure upload portal tied to the deal is a better route, ideally with access limited to people who need it and a record of who viewed or downloaded each file. Explain to the merchant why you use it; most appreciate knowing their information is being handled carefully.
How recent do the bank statements need to be?
Most funders want the latest full month included, and many ask for month-to-date activity close to funding so they can see anything that changed since the application, such as a new position or a run of returned items. Exact expectations vary by lender. If a deal stalls for a few weeks, assume you will need fresh statements and tell the merchant early so it does not feel like a surprise request.
What if a merchant cannot provide a requested document?
Find out why. Sometimes a document genuinely does not exist, such as a lease for a home-based business, and the funder may accept an alternative. Ask the funder what they would accept instead and note the substitution in your summary. Never create, alter or fill in a document on the merchant's behalf; that crosses a line and can unravel the whole deal.
General information only — not legal, tax or financial advice. Rules for telemarketing, texting, recording, disclosures and data retention vary and change; confirm current requirements with qualified counsel.
Connecting flights