How Virginia's 229 Registered MCA Providers Reshape Bank Verification Compliance

Virginia's Growing Registry Puts MCA Compliance in Focus

Almost four years after Virginia's sales-based financing provider law took effect, the state's registry has quietly grown to 229 registered parties. The increase of 27 companies since last year may seem modest, but the trend line tells a larger story. Both funders and brokers operating with Virginia-based merchants must register, and the compliance infrastructure that registration demands is reshaping how the industry approaches bank verification. For MCA professionals evaluating bank verification software for funders, this regulatory momentum is impossible to ignore.

What makes Virginia's framework significant is not the number itself. It is the precedent. Registration requires companies to maintain records, follow disclosure rules, and demonstrate that their underwriting processes meet a baseline of accountability. When a regulator audits a registered provider, the question shifts from "did you fund this deal?" to "can you prove how you verified it?" That distinction changes everything about how bank verification must work in practice.

This article breaks down what Virginia's registry growth means for MCA funders, why state-level regulation is accelerating demand for verifiable audit trails, and how asynchronous bank verification creates the compliance documentation that registered providers need.

Why State Registration Demands Better Audit Trails

Registration Changes the Documentation Burden

Before Virginia's law, most MCA funders operated without formal state oversight. Verification was a matter of internal policy. Some funders relied on live phone calls where an underwriter walked a merchant through their banking portal. Others accepted static PDF bank statements with little provenance checking. Neither approach produced the kind of documentation that holds up under regulatory scrutiny.

Registration changes the calculus. When a funder is listed on a state registry, they are implicitly agreeing to operate within a framework that can be audited. Virginia's statute requires registered providers to maintain records related to each transaction. While the law does not prescribe a specific bank verification method, the practical implication is clear: funders need to show their work. A verbal confirmation on a phone call that nobody recorded does not constitute showing your work.

The 229 companies on Virginia's registry in 2026 represent a cross-section of the industry. Some are large, well-capitalized funders with established compliance departments. Others are smaller ISOs and brokers who registered to maintain market access. For all of them, the question is whether their current verification process can withstand an audit request. For many, the honest answer is no.

Multi-State Compliance Adds Layers of Complexity

Virginia is not operating in isolation. California's disclosure requirements, New York's pending legislation, and Utah's registration framework are all creating a patchwork of state-level obligations. A funder originating deals across multiple states now faces overlapping compliance requirements, each with its own nuances around documentation, disclosure, and recordkeeping.

This multi-state reality makes informal verification methods increasingly untenable. A live call might satisfy one state's expectations while falling short in another. PDF bank statements might pass muster in a jurisdiction with loose oversight but create liability in one that demands provenance verification. The only sustainable approach is a verification method that produces consistent, high-quality documentation regardless of which state's rules apply.

As we explored in our analysis of how MCA litigation risk reshapes bank verification compliance for brokers, the legal exposure from inadequate verification is not theoretical. It is showing up in courtrooms and regulatory actions. State registration accelerates this exposure because it gives regulators a clear list of companies to audit.

What Audit-Ready Verification Evidence Looks Like

Regulators examining a registered MCA provider's verification practices want to see several things. They want a clear record of what was requested from the applicant. They want evidence that the applicant provided live, authentic banking data, not manipulated documents. They want timestamps showing when each step occurred. They want the ability to review the verification independently, without relying on the funder's summary or interpretation.

Screen recordings of live banking sessions satisfy all of these requirements in a way that no other verification method can match. When a merchant logs into their actual banking portal and navigates through account summaries, transaction histories, and balance information while a recording captures the entire session, the result is a piece of evidence that speaks for itself. The recording shows the bank's own interface, populated with live data, at a specific moment in time.

Exact Balance was designed around this principle. Every verification request generates a secure link sent to the applicant, who records their banking session directly in their browser. The recording is encrypted, timestamped, and stored in Google Cloud. An activity log tracks when the link was opened, when the recording started, and when it was submitted. This is the kind of audit trail that satisfies a regulator's inquiry without requiring the funder to reconstruct what happened from memory or fragmented notes.

How Asynchronous Verification Creates a Compliance Advantage

The shift from live verification calls to asynchronous workflows is often framed as a convenience upgrade. Funders save time. Applicants avoid scheduling hassles. Deals close faster. All of that is true, but the compliance dimension is equally significant and often overlooked.

Live verification calls are inherently difficult to document. Even when a funder records the call, the recording captures audio of someone describing what they see on screen. It does not capture the screen itself. The funder is left with secondhand evidence: a voice saying "I see a deposit of $14,000 on March 15th" rather than video proof of that deposit appearing in the bank's own interface. If a dispute arises later, or if a regulator questions the verification, that audio recording carries far less weight than a screen capture of the actual banking portal.

Asynchronous screen recording flips this dynamic. The applicant records their own screen, showing their own banking data, at their own convenience. The funder reviews the recording on demand. Every frame of the video is a visual record of what the bank's portal displayed at the time of recording. This is not a summary or an interpretation. It is primary evidence.

For funders registered in Virginia and other regulated states, this distinction matters enormously. Consider a scenario where a funded merchant defaults and alleges that the funder should have detected irregularities during verification. With a live call, the funder's defense rests on the underwriter's recollection and possibly a low-quality audio recording. With an async screen recording from Exact Balance, the funder can produce a timestamped video showing exactly what the underwriter reviewed, along with an activity log proving the verification was completed before funding.

The Consumer Financial Protection Bureau has signaled increasing interest in how alternative lenders conduct due diligence, and state regulators are watching closely. Funders who invest in verifiable, auditable processes now are building a compliance moat that will pay dividends as regulation tightens.

Practical Implementation for Registered Funders

Adopting async bank verification is not just about purchasing software. It requires rethinking the verification workflow to maximize both compliance value and operational efficiency. Here is how registered funders are approaching the transition.

First, standardize what gets verified. Exact Balance allows funders to define custom instructions for each verification request. Instead of leaving it to an underwriter's judgment on a live call, funders specify exactly what the applicant needs to show: account summaries for the last 90 days, transaction details for specific date ranges, or evidence of recurring revenue deposits. This standardization ensures consistency across verifications, which is exactly what auditors want to see.

Second, build verification into the deal timeline, not around it. Because async verification eliminates scheduling, it can happen in parallel with other underwriting steps. The applicant receives their verification link within minutes of submitting an application. By the time the underwriter is ready to review the deal, the recording is already waiting. This is the speed-to-lead advantage we discussed in our coverage of how speed to lead depends on bank verification software for MCA brokers, but it doubles as a compliance advantage because verification is completed and documented before any funding decision is made.

Third, retain everything. Every recording, activity log, and request detail should be stored and accessible for the duration required by applicable state law. Exact Balance's underwriter dashboard centralizes all of this. Funders can filter by status, review recordings, and pull up the complete history of any verification request. When an auditor calls, the response time is minutes, not days.

The 27 new companies that joined Virginia's registry in the past year are each facing these same decisions about how to build compliant verification workflows. Those who treat verification as a checkbox will find themselves scrambling when an audit arrives. Those who treat it as core infrastructure will find that the same system that protects them from regulators also helps them close deals faster and detect fraud earlier.

Frequently Asked Questions

What does Virginia's sales-based financing registration require for bank verification?

Virginia's registration law requires providers to maintain records related to each sales-based financing transaction. While it does not mandate a specific bank verification method, the recordkeeping obligation means funders need documentation that can withstand regulatory review. Screen recordings of live banking sessions, combined with timestamped activity logs, provide the most comprehensive evidence of verification. Funders relying on undocumented live calls or unverified PDF statements face significant risk during audits.

How does asynchronous bank verification help with MCA compliance?

Asynchronous bank verification produces a complete, tamper-evident record of every verification step. The applicant's screen recording captures their banking portal in real time, and the platform logs when links are opened, recordings started, and submissions completed. This creates an audit trail that satisfies state-level recordkeeping requirements without requiring manual documentation from the underwriter. The recorded evidence is visual and timestamped, making it far more defensible than notes from a phone call.

Which states require MCA providers to register or obtain licenses?

As of 2026, Virginia, California, Utah, and several other states have enacted or proposed registration and disclosure requirements for sales-based financing providers. New York continues to develop its own framework. Each state's requirements differ in scope and specificity, but the common thread is increased documentation and transparency obligations. Funders operating across multiple states should adopt verification processes that meet the strictest applicable standard to avoid compliance gaps.

Can screen recordings replace bank statements in MCA underwriting?

Screen recordings do not replace bank statements entirely, but they add a critical layer of authenticity verification. A PDF bank statement can be edited with basic software, making it unreliable as standalone evidence. A screen recording of the merchant logging into their banking portal and navigating to the same transactions shown on a statement is nearly impossible to fabricate. Many funders now use screen recordings as the primary verification method and treat bank statements as supplementary documentation. Exact Balance's AI-guided recording workflow ensures applicants capture the specific data underwriters need, reducing back-and-forth and strengthening the evidentiary value of each verification.

Conclusion

Virginia's registry of 229 sales-based financing providers is a clear signal that MCA regulation is not retreating. It is expanding, state by state, with each new registration requirement raising the bar for documentation and accountability. Funders who continue to rely on informal verification methods are building on a foundation that regulators are actively undermining.

The solution is not more paperwork. It is a verification process that generates its own compliance documentation as a natural byproduct of doing business. Async screen recordings, timestamped activity logs, and centralized dashboards turn every verification into an audit-ready event.

Visit exactbalance.ca to see how asynchronous bank verification fits into your compliance workflow. Replace the scheduling, the phone calls, and the documentation gaps with a process that protects your business every time a regulator asks to see your records.