Underwriting document intake is the work of collecting every file a deal needs into one organized deal file before review begins: several months of bank statements, the credit report, tax returns where the product requires them, the signed application, and whatever stips the funder asks for. In small-business lending and MCA underwriting, that package rarely arrives complete. It comes in pieces, from a broker, an ISO, or the merchant directly, and the speed of the deal depends on how quickly the team can tell what has arrived and what is still missing.
This note covers the intake half of that problem. For the process that follows, from first parse to funded deal, see MCA Underwriting: The Complete Guide.
What a complete deal file looks like
Every deal starts with the same questions: what do we have, and what are we still waiting on? Bring the related files into one book before reviewing individual results, and use clear names and date ranges so another underwriter can tell what has arrived, what belongs together, and what is still missing without a walkthrough. A complete book also keeps the review honest. When the full record sits in one place, a missing statement month or an unsigned application shows up as a gap in the file, not as a surprise two days before the credit decision.
What counts as complete depends on the product. A typical MCA or working capital file might be three to six months of business bank statements, a signed application, a voided check, and a credit pull. A larger facility adds tax returns, financial statements, or an AR aging on top. Whatever your credit box requires, write the list down once and hold every deal to it, so completeness is a checklist rather than a judgment call that changes with whoever opened the file first.
A useful test is to open the file and count how many clicks it takes to answer a simple question: are we missing anything? If the answer requires searching an inbox or asking a colleague, the structure is not finished yet. Getting intake right is quiet work, but it is what lets everything downstream move quickly.
Where intake usually breaks
Most intake problems are not dramatic. Statements arrive spread across three email threads and a shared-drive link. The most recent month is missing its last page. Two versions of the application are floating around, and nobody is sure which one was signed. The merchant's legal name on the application does not match the name on the statements, which matters later when deposits and existing positions get reconciled. None of these are hard to fix, but each is cheap to catch at intake and expensive to catch at decision time.
The pattern behind most of them is the same: review started before the file was ready. Once someone has already read the numbers, missing pieces feel like interruptions instead of gaps, and the follow-up request goes out late, or not at all. Broker-submitted packages deserve the same check as direct ones: a file that arrives pre-assembled is convenient, but the sender's definition of complete and yours are rarely identical.
An intake checklist that catches gaps early
A short checklist, run the same way on every deal, does most of this work. A solid version looks like this:
- Request the full statement run up front, whatever your credit box requires, instead of underwriting whichever months happen to arrive first.
- Confirm every expected document is in the book: bank statements, signed application, credit report or authorization, tax return if required, voided check, and any deal-specific stips.
- Check statement coverage: consecutive months, every page present, no gaps or overlaps in the date range.
- Name and date each file consistently, so coverage is visible at a glance rather than buried in filenames like "scan-final-v2".
- Mark the status of each document: received, parsed, or still needs review.
- Record missing items on the deal itself, with the follow-up assigned, instead of in an inbox.
- Run the completeness check one more time before the file moves to review.
None of these steps is slow. Together they take minutes on most deals, and they turn "did we get everything?" from a hallway question into a property of the file. They also give brokers and ISOs a consistent answer when they ask what else you need.
Collection is not the same as review
Receiving a file and understanding its contents are different steps in underwriting, and they deserve different states in the book. Keep the original document alongside the information extracted from it, and make the review status explicit. A bank statement that has been parsed should not look the same as a revenue figure your team has already checked against that statement. This separation protects reviewers from anchoring on unfinished work, and it shows at a glance which parts of a book still need attention.
In MCA underwriting the distinction matters doubly, because parsed numbers feed screening rules for revenue, average daily balance, negative days, and existing debt positions. Screening an unreviewed file produces a confident-looking result on numbers nobody has verified. The derived figures deserve the same discipline: each one should point back to the transactions behind it, a practice we cover in our note on source-linked underwriting.
The next action stays with the deal
A useful handoff tells the next person where to begin. Capture open questions, identify the documents they relate to, and leave a short summary of what has already been reviewed. If a credit report is still marked needs review, that status should sit with the document, not in a chat thread nobody can find. Outstanding stips work the same way: a missing proof of ownership or an unsigned offer belongs on the deal with an owner, not in someone's memory. The aim is a clearer starting point for the person making the credit decision.
This matters most on borderline calls. If the time in business rule flagged a deal and someone decided the exception was acceptable, the decision and its reasoning belong in the book, attached to the flagged result. When the next action is written down, momentum survives handoffs, vacations, and busy weeks.
How this looks in Lendquo
Lendquo builds every deal around a single book. With document intake and bank statement analysis, each statement, credit report, tax return, and application lands in one place, parsed and organized, so you can see what has arrived and what needs attention before review begins. Incomplete files and unclear results surface as needs-attention items rather than silent gaps. From there you can track every deal in your pipeline, with open items and document status attached to the book rather than buried in an inbox.
When intake runs this way, review starts from a complete picture instead of a scavenger hunt, and the path from documents to decision gets shorter without anyone working faster.