What Is an ISO Submission?
An ISO submission usually includes an application, recent bank statements, identification documents, and other required materials packaged together.
In MCA and small business lending, this is one of the most common sources of deal flow, as brokers work with ISOs that generate large volumes of applications.
ISO submission typically appears when ISOs forward packets via email or upload them into portals. Operators use it to make sure they receive complete, consistent packets that can be scrubbed and moved to underwriting quickly.
Some teams may call it “broker submission” or “deal packet,” but ISO submission is the term most widely used in MCA workflows.
How Does an ISO Submission Work?
At a general level, ISO submissions move through a predictable cycle.
- Input: An ISO sends a submission packet containing applications, bank statements, IDs, and other supporting documents.
- Core action: The receiving team checks completeness and organizes files for review.
- Output: A deal packet is assembled and prepared for underwriting.
- Follow-on: If complete, the deal is reviewed. If incomplete, the broker or ISO is asked to resubmit missing materials.
Within Heron’s workflow, ISO submissions are normalized and structured automatically.
- Intake: ISO packets arrive in shared inboxes or portals and flow directly into Heron.
- Scrub/Checks: Heron checks for completeness, flags duplicates, and scrubs statements for risk signals.
- Write-Back: Clean data, such as applicant information, broker details, and timestamps, is written directly to the CRM.
- Next Action: Complete submissions route to underwriting, while incomplete ones trigger missing-info requests.
This makes sure ISO submissions are standardized and processed consistently without heavy manual oversight.
Why Is an ISO Submission Important?
ISO submissions are vital because they are the main source of deal flow for MCA brokers and funders. Speed matters: if packets sit in inboxes or are missing documents, deals stall and competitors win opportunities.
Accuracy is also key. Inconsistent or messy submissions can create rework, errors, and wasted underwriting time. By automating ISO submission intake, Heron helps teams scale, reduce touches, and keep deal flow moving.
Common Use Cases
ISO submissions play a role in every broker and funder operation.
- Receiving ISO packets by email and routing them into Heron automatically.
- Normalizing packets from different ISOs into a consistent format for underwriting.
- Detecting missing bank statement pages and sending auto-requests back to the ISO.
- Attaching applicant details directly to CRM records.
- Reducing duplicate submissions when the same packet is sent multiple times.
FAQs About ISO Submission
How does ISO submission reduce manual work for brokers and funders?
Heron automates the intake process by normalizing packets, checking completeness, and writing clean data into the CRM. This removes the need for staff to manually review every ISO email or document.
What inputs does an ISO submission rely on?
ISO submissions usually include applications, bank statements, identification documents, and supporting materials. Heron makes sure these are captured, checked for completeness, and routed to the right workflow.
What happens when an ISO submission is incomplete?
Heron flags missing documents, creates an exception, and can send an automated missing-info request back to the ISO. This keeps deals moving without underwriters wasting time on partial packets.