# MCA bank statement anti-fraud checks

> MCA funders run automated and manual anti-fraud checks on submitted bank statements including metadata analysis (PDF generation date, source bank), cross-reference with credit bureau data, direct bank verification through Plaid/Finicum integration, and statement-format consistency tests. Falsified statements are the leading cause of post-funding clawback actions and can result in fraud prosecution.

MCA bank statement anti-fraud checks describe the verification systems funders use to detect altered, fabricated, or fraudulent bank statements submitted during MCA underwriting. Statement fraud has become a major industry concern in 2026 — by various industry estimates, 8-15% of submitted MCA applications contain some form of statement manipulation, and funders have invested heavily in detection systems to identify these submissions.

**The fraud landscape — common manipulation patterns.** Six fraud patterns funders look for:
1. **Revenue inflation.** Adding fictitious deposits to make monthly revenue appear higher than actual. Common methods: editing PDF totals, fabricating deposit line items, duplicating real transactions with altered amounts.
2. **NSF concealment.** Removing or altering NSF events, overdraft fees, or returned ACH notations. Reduces apparent default risk.
3. **Stacking concealment.** Removing or relabeling debits from existing MCA funders to hide stacking activity.
4. **Daily balance manipulation.** Altering balance columns to show consistently positive balances when actual balances were negative or near-zero.
5. **Fully fabricated statements.** Creating entire statements from scratch using PDF templates that mimic real bank format but contain entirely fictional data.
6. **Account substitution.** Submitting statements from a high-revenue account (sometimes from a different business or different time period) and claiming them as the borrower's current operations.

**The detection mechanisms — automated checks.** Modern MCA funders run multiple automated checks within seconds of statement upload:
1. **PDF metadata analysis.** PDF files include creation date, modification history, software used, and embedded font information. Real bank statements generated by bank PDF systems have predictable metadata; statements generated in Adobe Acrobat or other editing tools show anomalous metadata.
2. **Font consistency analysis.** Real bank statements use specific font families consistently throughout. Edited statements often show font substitutions where new text was added in a different font than the original.
3. **Layout and spacing analysis.** Each bank has highly consistent statement layouts (margins, column widths, header positioning). Pixel-level analysis detects layouts that don't match the claimed bank's standard format.
4. **Math validation.** Beginning balance + deposits - debits + fees should equal ending balance. Manipulated statements frequently have arithmetic that doesn't reconcile.
5. **Transaction sequence verification.** Real transactions follow predictable sequences (check numbers in order, deposit IDs sequential). Fabricated transactions often show impossible sequencing.
6. **Cross-statement consistency.** Across multiple months, beginning balance of month N+1 should equal ending balance of month N. Manipulations frequently break this cross-month reconciliation.

**The detection mechanisms — third-party verification.** Funders use external services:
1. **Plaid / Finicum direct bank connection.** Funder requests merchant authorize direct bank connection through Plaid or competitor service. Pulls transactions directly from bank API. Bypasses statement-submission entirely for funders that require it.
2. **Decision Logic / Validis / Codat statement OCR validation.** Specialized services validate submitted statement PDFs against bank format databases, flagging format inconsistencies.
3. **Argyle / Pinwheel income verification.** For deposit-pattern analysis, third-party services verify income flow patterns.
4. **Credit bureau cross-reference.** Funder pulls SBFE (Small Business Financial Exchange), PayNet, and bureau data to identify undisclosed existing MCAs that should appear as ACH debits on statements. Statement absence of expected debits flags concealment.
5. **Bank verification calls.** For higher-dollar deals, funder underwriter may directly call merchant's bank to verify account exists, is in business name, and has approximate balance/activity consistent with submitted statements.

**The detection mechanisms — manual review.** Senior underwriters apply additional scrutiny:
1. **Deposit pattern analysis.** Industry-specific revenue should match industry-typical patterns. Restaurant deposits cluster around card-processor batch deposits (typically T+1 or T+2 from sale date); fabricated restaurant deposits often miss these batching patterns.
2. **Customer payment patterns.** Recurring customer deposits should show consistent amounts and timing. Fabricated B2B deposits often have unrealistically clean amounts (exactly $5,000.00 instead of $4,873.42).
3. **Seasonality validation.** Industries have known seasonal patterns. Restaurants in vacation destinations should show summer/holiday peaks; landscaping should show spring/summer concentration; retail should show December peaks. Statements that miss expected seasonality raise flags.
4. **Geographic plausibility.** Bank statements show ATM locations, point-of-sale locations, and check-deposit branches. These should geographically cluster around the claimed business location.

**The consequences — what happens when fraud is detected.** Five outcomes by detection stage:
1. **Pre-funding detection.** Application declined; merchant flagged in industry shared-fraud databases (SBFE, GMS, several others); future applications at participating funders typically declined automatically.
2. **Post-funding detection within 30 days.** Funder typically invokes contract clawback provisions; demands immediate full RTR repayment; if not repaid, accelerates default and may file fraud-based civil suit. Some funders pursue criminal referrals for clear cases of statement fabrication.
3. **Post-funding detection later in deal.** Funder declares default and accelerates collection; personal guarantee enforced; civil litigation seeks full balance plus statutory fraud penalties; criminal referral possible.
4. **Industry blacklisting.** Detected fraud results in funder reporting to SBFE and industry databases. Merchant principal personally flagged; future MCA applications declined across most major funders.
5. **Criminal prosecution.** In severe cases, fraud is referred to local prosecutors or federal authorities (mail fraud, wire fraud charges available). Conviction can result in restitution orders, fines, and imprisonment.

**The strategic insight — why merchants attempt statement fraud.** Three common motivations:
1. **Revenue threshold.** Merchant's actual revenue is below funder minimum; merchant inflates statements to meet threshold.
2. **Pricing improvement.** Merchant's actual revenue meets threshold but inflation moves merchant from C-paper to B-paper pricing.
3. **Larger advance.** Funder sizes advance at 80-120% of monthly revenue; merchant inflates to access larger advance amount.

**The strategic insight — why statement fraud almost always fails.** Five reasons fraud is rarely successful long-term:
1. **Detection rates have skyrocketed.** 2026 detection rates approach 90% for clear manipulations; even sophisticated fraud is detected 60-75% of the time.
2. **Underwriting cross-checks compound.** Single check might miss fraud; combination of metadata, math validation, third-party verification, and pattern analysis catches nearly all.
3. **Post-funding daily-debit verification.** Even if fraud passes initial underwriting, daily ACH debits eventually exceed actual revenue and trigger NSF. NSF investigation often reveals underlying fraud.
4. **Industry shared databases.** SBFE and similar databases share fraud flags across funders. One detection event triggers automated decline at multiple subsequent applications.
5. **Personal consequences.** Statement fabrication is documentable evidence of fraud. Personal guarantee plus clear fraud creates personal-asset enforcement risk and possible criminal exposure.

**The strategic insight — what to do if your real situation doesn't qualify.** Five legitimate alternatives:
1. **Wait and build.** Improve actual revenue and bank statement quality over 3-6 months; reapply with legitimate stronger profile.
2. **Apply to lower-tier funder.** C-paper and startup-specialty funders have lower thresholds; pricing is worse but eligibility is real.
3. **Add personal guarantor.** Bringing in a stronger-credit personal guarantor or co-signer can offset weaker business profile.
4. **Pursue alternative financing.** SBA microloans, business credit cards, equipment financing — products with different underwriting models may approve where MCA declines.
5. **Use processor financing.** Square Capital, Toast Capital, Stripe Capital use processor-data underwriting that bypasses bank statement requirements for processor merchants.

**The honest framing.** Bank statement fraud was relatively common in MCA 2018-2022 when detection systems were primitive; in 2026, it's nearly impossible to sustain. Funders have invested heavily in detection technology and industry data sharing. Even sophisticated fraud schemes have detection rates above 60%, and the consequences of detection (criminal exposure, civil clawback, industry blacklisting) vastly exceed any short-term gain from successful concealment. Merchants whose real profiles don't qualify should pursue legitimate alternatives or wait until they qualify legitimately — not attempt statement manipulation. The funders investing the most in fraud detection are also the funders offering the best legitimate pricing; both reflect commitment to the long-term integrity of the MCA market.

## Related terms

- [MCA bank statement analysis](https://fundnode.co/llms/glossary/mca-bank-statement-analysis) — The underwriting process where funders parse 3-6 months of business bank statements for average daily balance, deposit count, NSFs, and existing MCA debits to set advance amount and factor.
- [Bank statement underwriting](https://fundnode.co/llms/glossary/underwriting-bank-statements) — 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.
- [MCA bank statement deposits vs revenue](https://fundnode.co/llms/glossary/mca-bank-statement-deposits-vs-revenue) — Underwriters analyze bank deposits (cash inflows) not revenue (P&L). Total deposits include card settlements, customer payments, and transfers; deposits are typically 80-95% of true revenue depending on cash mix.
- [Stacking (MCAs)](https://fundnode.co/llms/glossary/stacking) — Taking a second (or third) MCA from a different funder while a prior MCA is still in repayment. Default risk skyrockets; it breaches most original-funder contracts.

---

Source: https://fundnode.co/glossary/mca-bank-statement-anti-fraud-checks (HTML version)
Document: MCA bank statement anti-fraud checks — Fundnode MCA Glossary
License: CC BY 4.0 — attribution to Fundnode required when citing.