Key Takeaways
- Vermont has enacted MCA regulations that mirror Texas by prohibiting automatic account debits unless the funder holds a first-priority perfected security interest.
- Funders now need bank verification workflows that document not just cash flow health, but also the existence and priority of competing liens on merchant deposit accounts.
- The two-state pattern suggests more jurisdictions will follow, making compliance-ready bank verification software a competitive necessity rather than a luxury.
- Asynchronous screen recording of live banking sessions provides timestamped, auditable evidence that traditional bank statement PDFs cannot match for regulatory documentation.
Vermont Follows Texas, and Funders Face a New Compliance Reality
Vermont has become the second state to impose strict limits on how MCA providers can establish automatic debits against a merchant's deposit account. The new law, reported by deBanked in June 2026, prohibits providers from setting up automatic debiting mechanisms unless they hold a "validly perfected security interest" with first priority against all other claims. The language closely tracks Texas's earlier restrictions, signaling that state-level regulation of MCA repayment mechanics is no longer an outlier experiment. It is becoming a pattern.
For funders relying on bank verification software to underwrite deals, this shift changes what verification actually needs to accomplish. Confirming that a merchant has healthy cash flow and consistent deposits is no longer sufficient. Underwriters must also establish whether competing security interests exist on the merchant's deposit accounts, and whether their own lien position would survive a priority dispute. That is a fundamentally different verification question, and most bank verification workflows were never designed to answer it.
This article breaks down what the Vermont law requires, why it creates new documentation burdens for funders, and how async bank verification workflows can close the compliance gap before more states follow suit.
What Vermont's Auto-Debit Law Actually Requires
The Perfected Security Interest Standard
The core of Vermont's new regulation is deceptively simple: a provider cannot establish a mechanism for automatically debiting a recipient's deposit account unless the provider holds a validly perfected security interest in that account under Title 9A, with first priority against all other claims. In practice, this creates several requirements that ripple through the entire underwriting and verification process.
First, the funder must actually file a UCC-1 financing statement against the merchant's deposit account before setting up ACH debits. That filing must be properly perfected under Vermont's version of the Uniform Commercial Code. Second, the funder's security interest must hold first priority, meaning no other creditor can have a prior perfected interest in the same account. If another MCA funder, a term lender, or even a bank with a right of offset has a prior claim, the automatic debit mechanism is prohibited under the new law.
This is where bank verification enters the picture. To confirm first-priority status, funders need visibility into the merchant's existing obligations and account encumbrances. A standard bank statement PDF, even a genuine one, does not disclose whether another party has filed a UCC lien against the account. The verification must go deeper.
The Two-State Pattern and What It Signals
Texas enacted similar auto-debit restrictions earlier, and Vermont's decision to adopt nearly identical language suggests coordinated legislative momentum. When two states independently arrive at the same regulatory framework, compliance teams should treat it as a leading indicator rather than a coincidence. States like Connecticut, which has already imposed commercial financing disclosure requirements, could be next to layer auto-debit restrictions on top of existing transparency mandates.
The practical implication for funders is that building compliance workflows state by state is unsustainable. A funder originating deals across multiple jurisdictions needs a bank verification process that captures enough information to satisfy the strictest regulatory regime in its portfolio, not just the minimum required in any single state.
Why Traditional Bank Verification Falls Short for Auto-Debit Compliance
Statement PDFs Cannot Prove Lien Position
The standard MCA underwriting workflow involves collecting 90 days of bank statements, reviewing average daily balances, counting NSF transactions, and estimating monthly revenue. None of that analysis addresses the question Vermont's law now asks: does this funder hold a first-priority perfected security interest in this specific deposit account?
Bank statement PDFs are snapshots of transaction activity. They do not disclose whether a UCC-1 has been filed against the account, whether the bank itself holds a security interest through a deposit account control agreement, or whether another funder has already perfected a lien. A verification process built entirely around statement analysis leaves funders blind to the very information they need for compliance.
Live Verification Calls Are Not Auditable Enough
Some funders attempt to gather lien and obligation information during live verification calls, asking the merchant to navigate their banking portal and confirm whether other funders are debiting the account. The problem is that live calls produce no durable record. If a regulator or auditor later asks the funder to prove that it verified its priority position before establishing automatic debits, a phone call provides no evidence.
Even when funders take notes during verification calls, those notes reflect the underwriter's interpretation rather than what the merchant actually showed. In a compliance dispute, the distinction matters. Regulators want to see the primary source, not a summary of it. As we explored in our analysis of how audit season exposes bank verification documentation gaps, the difference between "we asked" and "we can prove what we saw" is the difference between passing and failing a compliance review.
How Async Screen Recording Closes the Gap
Asynchronous bank verification through recorded screen sessions solves both the depth and the documentation problem simultaneously. When a merchant records their live banking session, the funder's review team can see exactly what accounts exist, what recurring debits are active, and whether other funders are already pulling from the account. The recording is timestamped, stored securely, and available for audit at any time.
With Exact Balance, funders can include custom instructions that direct the merchant to show specific screens: account summaries, scheduled payments, authorized debits, and any security or lien notices visible in their banking portal. The AI-guided recording coach walks the merchant through each step, confirming completion in real time. The result is a visual, verifiable record that goes far beyond what any PDF statement or phone call can provide.
For Vermont compliance specifically, this means a funder can document that it reviewed the merchant's account for competing debits before establishing its own ACH mechanism. Combined with a UCC search, the recording creates a layered compliance file that addresses both the transaction-level and lien-level requirements of the new law.
Building a Bank Verification Workflow That Scales Across Regulatory Regimes
The Vermont law does not exist in isolation. Funders operating in 2026 face a patchwork of state-level requirements that range from disclosure mandates in Connecticut and California to auto-debit restrictions in Texas and now Vermont. New York's proposed MCA criminalization bill would add yet another layer of compliance risk. Each jurisdiction imposes slightly different documentation standards, but the underlying need is the same: provable, auditable evidence of what the funder knew about the merchant's financial position before funding.
A compliance-ready bank verification workflow should address three distinct layers. The first is transaction verification, confirming that the merchant's cash flow matches what they represented on their application. The second is obligation verification, identifying existing debits, competing funders, and potential stacking. The third is lien verification, establishing whether the funder's security interest holds priority over other claims. Traditional verification processes handle only the first layer. Vermont's law demands all three.
Async screen recording naturally accommodates this expanded scope because the instructions sent to the merchant can be customized for each deal. A funder originating in Vermont can instruct the merchant to show authorized debit schedules and account agreements. A funder originating in Connecticut can request the specific transaction history needed for disclosure calculations. The recording captures whatever the instructions require, and the audit trail documents exactly what was shown and when.
This flexibility is what separates purpose-built bank verification software from generic document collection tools. Open banking APIs and automated statement parsers excel at extracting structured data from known fields, but they cannot show a regulator what a merchant's banking portal looked like at the moment of verification. For compliance purposes, the visual record is irreplaceable.
Frequently Asked Questions
What does Vermont's MCA auto-debit law require from funders?
Vermont's law prohibits MCA providers from establishing automatic debiting mechanisms on a merchant's deposit account unless the provider holds a validly perfected security interest with first priority over all other claims. In practice, this means funders must file a UCC-1 financing statement, confirm their priority position, and document their compliance before setting up ACH debits. The law mirrors Texas's earlier auto-debit restrictions and signals growing state-level regulation of MCA repayment mechanics.
How does bank verification help with MCA auto-debit compliance?
Bank verification helps funders document what they knew about a merchant's account before establishing automatic debits. By reviewing a recorded screen session of the merchant's live banking portal, underwriters can identify competing debits, existing obligations, and other funders already pulling from the account. This visual, timestamped evidence satisfies regulatory requirements for auditable documentation that PDF statements and phone calls cannot provide.
Will more states follow Vermont and Texas on MCA auto-debit regulations?
The two-state pattern strongly suggests additional states will adopt similar restrictions. Connecticut and California have already enacted commercial financing disclosure laws, and layering auto-debit restrictions on top of those existing frameworks is a natural legislative progression. Funders should build compliance workflows designed for the strictest regulatory standard in their origination footprint rather than reacting to each new state individually. The Consumer Financial Protection Bureau has also signaled interest in small business lending oversight, which could accelerate state-level activity.
What is async bank verification and how does it work for MCA lenders?
Async bank verification replaces live phone-based verification calls with browser-based screen recordings. The funder sends the merchant a secure link with custom instructions specifying what to show in their banking portal. The merchant records their session at their convenience, and the funder's team reviews the recording on demand. Exact Balance adds AI-guided coaching that walks the merchant through each step and verifies completion in real time. Every recording is timestamped, encrypted, and stored with a full activity log for compliance purposes.
Conclusion
Vermont's auto-debit restrictions represent more than a single state's policy choice. They mark the expansion of a regulatory pattern that will reshape how MCA funders document their right to collect. Bank verification workflows built solely around cash flow analysis are no longer sufficient. Funders need verification processes that capture obligation data, identify competing interests, and produce durable audit trails that satisfy regulators across multiple jurisdictions.
Exact Balance was built for exactly this kind of compliance challenge. Custom instructions, AI-guided recording, and secure cloud storage give funders the documentation they need without the scheduling overhead of live calls. Visit exactbalance.ca to see how async verification fits into your compliance workflow before the next state follows Vermont's lead.