Application notes are the narrative layer underneath the structured status field. They capture why an underwriter moved a deal forward, what stipulations are missing, and the back-and-forth between funder and ISO. In 2026 these notes have become quasi-standardized due to LendSaaS, Centrex, and Salesforce templates dominating the underwriting stack.
Note categories and typical content.
- Bank-statement observations. "NSF count: 3 in last 90 days, all in February — explained by tax payment." "Average daily balance: $4,200." "Two large transfers to personal account on 5th of each month — flag for owner draw vs. expense." "MCA debits visible: Credibly $187/day, Rapid $112/day — confirms 2 open positions."
- Stip tracking. "Missing: voided check, DL front/back, lease agreement, last 2 yrs tax returns. ISO acknowledged 6/29, ETA EOD." "Voided check received — bank match confirmed." "Lease pending — landlord verification call attempted 2x, no answer."
- Prior deal history. "Funded 2x prior with us. Last deal: paid as agreed, 9-month term, no reconciliation requests." Or: "Prior deal defaulted at 60% paid — escalate to risk committee."
- DataMerch / MCA Track / Experian hits. "DataMerch clean." "MCA Track shows one stacked default with Yellowstone, 2023. Merchant claims paid — needs documentation."
- ISO communication log. Timestamped entries: "6/29 10:42a — ISO called re: status, advised offer EOD." "6/29 2:15p — ISO escalated to mgr, requested 1.32 factor instead of 1.38."
- Tier-routing reasoning. "Tier 1 → Tier 2: revenue $42K/mo qualifies for A-paper but credit 612 pushes to Tier 2. Recommend B-paper offer at 1.35." Often the most useful note for ISOs because it explains the offer math.
- Reconciliation / payment-modification history (if existing merchant). "Approved 5-day pause 4/12 — merchant cited equipment failure. Resumed on schedule." "3 reconciliation requests YTD — all approved, average 18% reduction for 30 days."
Note visibility tiers.
- Internal-only notes — risk committee deliberations, credit-score specifics, suspected fraud flags, PG litigation history. Never exposed to ISO.
- ISO-visible notes — stip status, offer reasoning, timeline expectations, generic decline reasoning. Sanitized version of internal notes.
- Merchant-visible — almost never. Merchants see status + offer terms only. Some funders surface stip checklists to merchants via portal.
Typical note volume.
A clean A-paper deal generates 3–6 notes from submission to funding. A complex B/C-paper deal with multiple stip rounds, reconciliation requests, or tier escalations can accumulate 20+ notes.
Note authoring conventions.
- Underwriters use shorthand: "BK stmts ok, ADB $4.2K, NSF 3x, MCA Track clean, recommend Tier 1 offer 1.28."
- Timestamps + initials are standard.
- Sensitive content (e.g., suspected fraud) is flagged with a code like
[INTERNAL ONLY]or routed to a separate notes panel.
Common ISO frustrations.
- Decline notes too generic ("Does not meet underwriting criteria") — ISOs cannot triage where to re-submit.
- Notes contradicting status field — note says "approved, waiting on contract" but status still shows "Under Review."
- Notes deleted or overwritten when a deal moves between underwriters.
- Notes visible to one ISO but not the broker who actually owns the merchant relationship (multi-ISO conflict).
Compliance considerations.
In states with MCA disclosure laws (CA, NY, UT, VA, GA), underwriter notes that influence the offer (APR-equivalent calc, factor rate, total cost) must be retained for regulatory inspection. Most funders retain notes 7 years minimum.
Notes during collections.
When a deal moves to collections, the notes thread continues and becomes the legal record. Collector notes capture every contact attempt, merchant excuse, payment promise, and settlement discussion. These notes are often subpoenaed in MCA litigation.
Modern AI-assisted note generation (2026).
Several funders (Reliant, Credibly, parts of OnDeck's stack) now use LLM-assisted note summarization — the AI parses bank statements and drafts the initial underwriter note for human review. This compresses underwriting time by 30–40% for clean files but is not used for decline reasoning (regulatory caution).
Takeaway. MCA funder application notes follow standardized categories in 2026 — bank-statement observations, stip tracking, prior-deal history, third-party report hits, ISO communication log, tier-routing reasoning, and reconciliation history — visible to ISOs in sanitized form but never fully exposed to merchants, with persistent ISO complaints about generic decline reasoning, status-note contradictions, and multi-ISO note-visibility conflicts driving continued investment in standardized underwriting platforms and AI-assisted note generation.
Related terms
- MCA funder application status tracking (typical 2026) — Most MCA funders track applications through 6-8 named stages (Submitted, In Underwriting, Bank Verification, Conditional Approval, Offer Sent, Contract Out, Funded, Declined) with status visible to ISOs via portal and to merchants via email triggers.
- MCA funder merchant onboarding call (typical 2026) — After contract signing, MCA funders typically conduct a 5-15 minute onboarding call covering ACH debit confirmation, reconciliation rights, payment schedule, default consequences, and portal access — recorded for compliance.
- MCA funder collections process stages (typical 2026) — MCA collections typically progress through 5 stages: pre-collections (days 1-15 after first NSF), internal collections (days 15-60), external vendor collections (days 60-120), judgment/litigation (months 4-12), and post-judgment recovery (1-3 years), with cumulative recovery rates of 40-65%.
- Merchant cash advance (MCA) — A lump-sum advance against future revenue, repaid via fixed daily ACH or a percentage of card sales. Legally a sale of future receivables, not a loan.
AI agents: this term is available as raw markdown at /llms/glossary/mca-funder-application-notes-typical.