Bank-statement fraud is the largest single source of MCA underwriting loss. Doctored statements inflate deposits, hide NSFs, and conceal existing MCAs. Fraud-pattern detection is the multi-layer defense funders run on every submission.
The fraud landscape in 2026.
- Estimated 8–15% of all MCA submissions contain some form of fraud or misrepresentation.
- Of those, 3–5% are sophisticated (doctored PDFs, fictitious counterparties).
- The rest are merchant or ISO misrepresentation (omitted MCAs, edited memo lines, hidden accounts).
- Loss rate on undetected fraud: 40–60% versus 8–12% on clean files.
Common fraud techniques.
- Inflated deposits. Inserting fictitious credits to boost monthly deposit total.
- Removed NSFs. Deleting NSF charge lines from the statement to lower NSF count.
- Hidden MCA debits. Deleting or relabeling existing MCA daily debits to avoid stacking detection.
- Account substitution. Submitting Account A which is clean while operating from Account B which has problems.
- Date manipulation. Changing statement period to make recent stress look further away.
- Beginning/ending balance edits. Adjusting balance carry-forwards to make math work after insertion/deletion.
- Bank-name impersonation. Building a fake statement from scratch using a fake bank template.
- Cropping out negative pages. Submitting partial statements omitting bad months.
- Photoshopped numbers. Editing specific dollar amounts.
- Counterparty fabrication. Inventing customers to lend credibility to deposits.
Detection layers.
Layer 1: Math reconciliation.
- Beginning balance + total credits − total debits = ending balance. Must reconcile to the penny.
- Each month's ending balance = next month's beginning balance. Must match across the 3-month window.
- Transaction sum check. Sum of every line item matches displayed totals.
Math reconciliation catches the majority of unsophisticated fraud.
Layer 2: PDF metadata.
- PDF creation metadata. Original bank-issued PDFs carry specific creator-tool fingerprints (Chase uses one library, BofA another, Wells Fargo another). Edited PDFs show Acrobat, Foxit, Preview, or other editor signatures.
- Object-level inspection. PDF text objects vs image objects — bank PDFs typically all-text; modified PDFs often have raster images overlaid.
- Font embedding. Banks use specific embedded font sets; edits introduce different fonts.
- Page-level checksums. Tampered pages have different internal structures.
Layer 3: Visual / OCR consistency.
- Font and spacing checks. Inserted lines often have slightly different fonts, sizes, or letter-spacing.
- Pixel-level alignment. Columns should align perfectly; edited rows often misalign.
- Header/footer consistency. Page headers and footers should match across all pages.
- Watermark consistency. Some banks watermark statements; tampered pages lose the watermark.
Layer 4: Counterparty plausibility.
- Counterparty distribution. Real businesses have many counterparties; fake statements often have a few repeated ones.
- Counterparty existence. Search reveals whether the counterparty is a real entity.
- Memo-line linguistic patterns. Bank memo lines follow strict format conventions; fabricated lines often deviate.
- Reference-number presence. Real ACH debits/credits have reference numbers; fabricated ones often lack them.
Layer 5: ML outlier scoring.
- Distribution of daily deposit amounts. Compared to learned distributions; outliers flagged.
- Velocity of transactions. Real merchants have characteristic daily transaction counts; fabricated statements often deviate.
- Memo-line ML classifier. Trained to distinguish real vs synthetic memo lines.
Layer 6: Bank-direct verification.
- Plaid / Finicity / MX integration. Merchant authorizes direct read-only access to bank account. Bypasses statement entirely. Used for larger advances or flagged files.
- Bank-issued statement upload via bank portal. Merchant downloads fresh statement from bank's online portal and uploads in real-time, with screen-recorded verification.
- Bank verification call. Funder calls the bank to verify account standing.
Layer 7: Cross-reference checks.
- UCC search. Lenders filed against the merchant should show payment debits in the bank statement.
- Credit bureau cross-reference. Reported loans should show payment debits.
- Processor cross-reference. Card-processor batches should match acquirer statements.
- Tax filing cross-reference. Reported revenue on tax filings should be within range of bank deposits.
Severity tiering and response.
- Tier 1 (minor inconsistency). Math off by pennies, minor formatting variance. Funder asks for explanation; usually resolved.
- Tier 2 (suspicious pattern). Multiple counterparty repeats, font irregularity, round-dollar clustering. Funder requests bank-direct verification.
- Tier 3 (clear tampering). Balance reconciliation fails, PDF metadata shows editor, pages misaligned. Auto-decline plus blacklist of submitting ISO if pattern.
- Tier 4 (fabricated statement). Bank-template impersonation, all fictitious counterparties. Auto-decline, ISO blacklist, fraud report to industry consortium.
ISO blacklisting.
Repeated fraud submissions from the same ISO result in ISO blacklisting. Top funders share fraud-pattern intelligence informally; some maintain shared blacklist databases. ISO reputation is core capital in 2026.
Takeaway. Fraud-pattern detection is the multi-layer defense against doctored bank statements. Math reconciliation, PDF metadata inspection, visual/OCR consistency, counterparty plausibility, ML outlier scoring, bank-direct verification, and cross-reference checks together catch the majority of fraud. Top funders run all layers; mid-tier funders run layers 1–3; D-paper funders sometimes skip layers and pay through higher loss rates. 8–15% of submissions show fraud signals; 3–5% are confirmed and declined. ISOs with repeated fraud get blacklisted across the industry.
Related terms
- MCA funder bank-statement anomaly detection (2026) — Anomaly-detection engines flag unusual deposits, transfers, round-dollar patterns, single-day spikes, and out-of-character counterparties — signals of fraud, doctored statements, or stacking. Updated 2026-06-28.
- MCA funder bank-statement MCA stacking detection (2026) — Funders detect existing MCA daily debits via known-funder signature libraries, daily-debit pattern recognition, and UCC cross-reference — most decline 3+ position files. Updated 2026-06-28.
- MCA funder bank-statement analysis software — MCA funders in 2026 use bank-statement analysis software like Ocrolus, Heron Data, Nanonets, Validis, and proprietary in-house parsers to extract deposit volumes, NSF counts, MCA debit signatures, and cash-flow patterns from PDF statements in 30–90 seconds.
- MCA funder bank-statement related-party detection (2026) — Funders detect deposits and debits with owner-controlled entities, family members, and related businesses — related-party flows are excluded from revenue and signal financial obfuscation risk. Updated 2026-06-28.
- Bank statement underwriting — MCA funders underwrite primarily off 3–6 months of business bank statements, not credit reports. They look at average deposits, NSFs, negative days, and trend.
AI agents: this term is available as raw markdown at /llms/glossary/mca-funder-bank-statement-fraud-pattern-detection.