For most merchant cash advance funders, the underwriting process starts in an inbox. ISOs send submissions by email — an application, four to six months of bank statements, sometimes a driver's license, a voided check or processing statements — and each one waits until someone opens it, renames the files, checks what is missing and keys the basics into the CRM. In a busy week, deals that would have funded are lost simply because a faster funder answered first.

Submission intake is the most automatable part of MCA underwriting and also the easiest place to automate too much. This guide covers what intake should do, what to automate, and where automation should hand over to an underwriter.

Intake is the first stage: getting a complete, labelled file in front of the right reviewer before any analysis begins.

What intake has to accomplish

  1. Capture every submission, whatever the channel — email, portal, API or CRM — against one deal record.
  2. Classify each document: application, which months of which account's statements, IDs, processing statements, contracts.
  3. Check completeness — missing months, unsigned applications, statements for a different account or entity.
  4. Extract the basics — business name, owners, requested amount, the statement period and headline figures.
  5. Screen against the funder's hard knock-out criteria, such as restricted industries, time in business or states you do not fund.
  6. Route the deal to the right queue with a clear status, and tell the ISO what is missing.

What to automate at intake

Almost all of the list above is mechanical, and automating it is pure gain. Classification and completeness checks are where most manual time goes; a system that reads a submission and replies within minutes "we have March–July for account ending 2208, June is missing" does more for speed-to-offer than any downstream improvement. For the detail of reading mixed files, see our guide to document intelligence for lenders.

Hard knock-outs are also safe to automate, provided they really are hard. A funder that never funds a particular industry gains nothing from an analyst confirming that by hand. The key is that these rules are the funder's own, written down, versioned and visible — not a vendor's default.

What to keep for the underwriter

Trouble starts when intake automation begins to make soft credit calls. Scoring a file as "low quality" and sending it to the bottom of a queue, auto-declining on revenue that is just below a threshold, or treating an unusual deposit pattern as a red flag — each of these is a judgment that can be right for most files and wrong for the one that matters. Seasonal businesses, recent bank switches and legitimate transfers between the owner's accounts all look odd to a rule and normal to an experienced underwriter.

Intake metrics worth tracking

  • Time to first response — from submission received to the ISO hearing back, whether with an offer, a request or a decline.
  • Complete-on-arrival rate by ISO — which partners send full files, and which need coaching. Our guide for brokers and ISOs can help.
  • Touches per file before it reaches an underwriter.
  • Knock-out accuracy — how often a file screened out at intake would, on review, have met your criteria.

The last metric is the one most funders never measure, and it is the one that tells you whether intake automation is saving time or silently costing you deals.

From intake to underwriting: the handoff

Good intake does not just move a file faster; it hands the underwriter a better file. The documents are labelled, the statement period is confirmed complete, and the values extracted at intake keep a link to the page they came from, so the analysis that follows — cash flow, existing positions and stacking, verification and fraud signals — starts from evidence rather than from re-reading the submission.

From here, this article is about Cevrynt

How Cevrynt handles intake

Illustrative product view: a bank statement pack read once into a reusable cash-flow view, with deposits, balance health, debt rhythm and exceptions each linked to the source.
Illustrative view of Bank Statement Analysis · synthetic dataSee Bank Statement Analysis

Cevrynt treats intake as the first stage of one evidence-linked review rather than a separate tool. Whatever arrives lands against the same deal; each document is classified and read, gaps are surfaced, and extracted values stay linked to their source as the file moves into bank statement analysis, verification, fraud review and your policy. It flags and organizes; it does not auto-decline on soft signals, and the credit decision stays with your underwriters. Intake connections to your existing channels and CRM are scoped with you before a pilot — see Integrations.

To see intake and analysis run on one of your recent submissions, book a walkthrough.