Key Takeaways
- A New York bankruptcy court reclassified 19 MCAs totaling $10.8 million as loans, applying a detailed 36-page analysis of how the advances functioned in practice.
- Courts increasingly look at how repayment was actually collected, not just what the contract says, making bank verification documentation a critical compliance asset.
- Funders who rely on verbal verification calls without recordings or audit trails face heightened reclassification exposure.
- Asynchronous bank verification with timestamped recordings creates a defensible record showing that underwriters evaluated real merchant cash flow before funding.
- The ruling signals that MCA funders in 2026 need bank verification software that produces compliance-grade documentation, not just underwriting convenience.
A 36-Page Ruling That Changes the Compliance Calculus for MCA Funders
When a bankruptcy court devotes 36 pages to analyzing whether merchant cash advances are really loans, every funder should pay attention. That is exactly what happened this week in a New York case where the Chapter 7 Trustee of the Estate of Kossoff PLLC challenged an MCA funder's agreements, and the court sided with the trustee. Nineteen MCAs worth $10.8 million were reclassified as loans, a decision that exposes how courts evaluate MCA structures when they reach the litigation stage. For funders relying on bank verification software for funders to underwrite deals, this ruling raises a direct question: does your verification process produce documentation strong enough to survive judicial scrutiny?
The court did not focus solely on the language in the MCA contracts. It examined how repayment was actually collected, whether the funder bore genuine risk tied to the merchant's revenue, and whether the relationship functioned more like a fixed-obligation loan than a true purchase of future receivables. This analytical framework means that the evidence trail behind every funded deal, including how a funder verified the merchant's banking activity, is now part of the compliance equation.
Why Reclassification Risk Demands Better Bank Verification Documentation
Courts Look at Behavior, Not Just Contracts
The critical insight from this ruling is that judges evaluate what actually happened during the life of the MCA, not merely what the contract promised. If a funder's repayment collection resembled fixed daily debits regardless of revenue fluctuation, the court treats it as a loan. If the funder never adjusted remittance percentages based on actual sales volume, the court treats it as a loan. The contract can say "purchase of future receivables" in bold type on every page, and it will not matter if the funder's behavior tells a different story.
This is where bank verification becomes a compliance function, not just an underwriting step. When a funder reviews a merchant's live banking portal before funding, that review serves two purposes. First, it confirms the merchant's actual cash flow to support the underwriting decision. Second, it creates evidence that the funder genuinely evaluated whether the merchant's revenue could support the proposed remittance structure. If the deal is later challenged, that evidence shows the funder was pricing risk against real revenue, which is the hallmark of a true receivables purchase.
Verbal Verification Calls Leave No Defensible Trail
Most MCA funders still verify bank activity through live phone calls where an underwriter walks the merchant through their online banking portal. The underwriter asks the merchant to scroll through transactions, reads numbers off the screen, and types notes into a CRM. When that call ends, the only record is whatever the underwriter chose to write down.
In a reclassification dispute, those handwritten notes carry almost no evidentiary weight. There is no way to prove what the underwriter actually saw. There is no timestamp showing which accounts were reviewed. There is no visual record confirming that the merchant's transaction history matched the bank statements submitted with the application. A plaintiff's attorney can argue that the funder never performed meaningful due diligence, and the funder has nothing concrete to rebut that claim.
As we explored in our analysis of when a merchant cash advance is really a loan, the legal distinction between MCA and loan often comes down to how well the funder can demonstrate that the deal was structured around genuine revenue risk. Bank verification recordings are one of the strongest pieces of evidence a funder can produce.
Asynchronous Recordings as a Compliance Asset
Exact Balance replaces live verification calls with browser-based screen recordings that merchants complete on their own time. Each recording is timestamped, securely stored on Google Cloud, and linked to a full activity log showing when the verification link was opened, when the recording started, and when the submission was completed. The underwriter reviews the recording on demand, verifies transaction authenticity, and marks the request as verified with a single click.
From a compliance standpoint, this creates exactly the kind of audit trail that matters in reclassification litigation. The recording shows the merchant's actual bank portal, their real transaction history, and their live account balances at a specific point in time. It is not a summary written from memory. It is not a screenshot that could have been edited. It is a continuous video of the merchant navigating their own banking interface, guided by AI-powered step detection that ensures every required element is captured.
When a court asks whether the funder conducted genuine due diligence before purchasing future receivables, a timestamped screen recording of the merchant's banking session is a far more compelling answer than a line in a CRM that reads "bank verified by phone."
Building Portfolio-Level Defense Against Reclassification Claims
The Kossoff ruling did not involve a single MCA. It involved 19 deals over a four-year period, all of which were analyzed under the same framework. This signals that reclassification challenges can target entire portfolios, not just individual transactions. A trustee or regulatory body can pull every MCA a funder has executed and apply the same behavioral analysis to each one.
For funders operating at scale, this means that verification consistency matters as much as verification quality. If some deals have recordings and others do not, if some verification notes are detailed and others are blank, the inconsistency itself becomes evidence of weak underwriting controls. A funder that uses standardized async verification for every deal creates a uniform compliance record across the entire portfolio.
This is particularly relevant for funders who are raising capital through securitization or institutional credit facilities. As we covered in our analysis of how investment-grade notes reshape bank verification requirements, institutional investors increasingly expect funders to demonstrate rigorous, documented underwriting processes. A portfolio where every deal includes a timestamped bank verification recording is far more attractive to investors than one where verification quality varies from deal to deal.
The timing of this ruling also coincides with broader capital markets activity in the MCA space. Fundworks just extended and upsized its investment-grade corporate notes to $40 million, and Credibly has opened its warehouse line to outside investors through blockchain rails. As more capital flows into MCA portfolios from sophisticated investors, the bar for documentation and compliance will only rise.
Funders who treat bank verification as a checkbox exercise are building portfolios on a foundation that may not survive legal challenge. Funders who treat it as a compliance function, with standardized recordings, full audit trails, and AI-guided quality assurance, are building portfolios that can withstand scrutiny from courts, regulators, and institutional investors alike.
What Funders Should Document in Every Verification
Based on the analytical framework the court applied in the Kossoff ruling, funders should ensure their bank verification process captures several specific data points for every deal. The merchant's account summary showing current balances. Transaction history covering the date range specified in the underwriting criteria. Evidence of deposit patterns that correlate with reported revenue. Any existing MCA repayment obligations visible in the transaction history, which also serves as a stacking fraud detection mechanism.
With Exact Balance, funders define these requirements as custom instructions when creating each verification request. The merchant receives clear, specific guidance on what to record, and the AI-guided recording coach walks them through each step. The result is a recording that captures exactly what the underwriter needs to see, every time, without the variability that comes from phone-based verification.
Frequently Asked Questions
What does it mean when a court reclassifies an MCA as a loan?
Reclassification means the court determines that a merchant cash advance functioned as a loan in practice, regardless of how the contract was structured. This subjects the transaction to usury laws, licensing requirements, and other lending regulations that MCAs are typically exempt from. The New York bankruptcy court's 2026 ruling reclassified 19 MCAs worth $10.8 million by analyzing how repayment was actually collected rather than relying on contract language alone.
How does bank verification protect MCA funders against reclassification risk?
Bank verification creates documented evidence that the funder evaluated the merchant's actual revenue before funding, which supports the argument that the deal was a genuine purchase of future receivables rather than a disguised loan. Timestamped screen recordings of live banking sessions show that the funder's underwriting was tied to real cash flow data. This type of documentation is far more defensible in court than handwritten notes from a phone call.
What is async bank verification for MCA lending?
Async bank verification eliminates the need to schedule live phone calls with merchants. Instead, merchants receive a secure link, record their banking portal through a browser-based screen capture tool, and submit the recording for underwriter review. Platforms like Exact Balance add AI-guided step detection to ensure every required element is captured, creating a standardized, compliance-grade verification record for every deal.
Why do MCA funders need audit trails for bank verification?
Audit trails protect funders in three scenarios: litigation, regulatory examination, and investor due diligence. The Kossoff ruling demonstrates that courts will examine how funders actually conducted underwriting, not just what the contract says. A complete audit trail showing when verification was requested, when the recording was submitted, and what the recording contained gives funders a defensible record. In 2026, as institutional capital flows into MCA portfolios at increasing scale, investors are also demanding this level of documentation.
Conclusion
The New York bankruptcy court's reclassification of $10.8 million in MCAs as loans is not an isolated event. It is the latest signal that courts, regulators, and investors are scrutinizing how MCA funders actually conduct underwriting. Funders who rely on undocumented phone calls for bank verification are building portfolios with a compliance gap that grows more dangerous with every deal.
Exact Balance gives funders the tools to close that gap: asynchronous screen recordings of live banking sessions, AI-guided step detection, timestamped audit trails, and secure cloud storage. Every verification produces a compliance-grade record that can stand up to judicial scrutiny, investor due diligence, or regulatory examination. Visit exactbalance.ca to see how async bank verification fits into your workflow.