Virginia MCA Compliance Requirements
Virginia MCA Compliance Requirements (2026)
Virginia’s Sales-Based Financing Providers (SBFP) framework is live. If you offer sales-based financing (including many MCA-like structures) to Virginia recipients, you need (1) proper SBFP disclosures delivered with the offer and (2) active registration for covered providers and brokers through the Virginia State Corporation Commission (SCC) / Bureau of Financial Institutions.
Looking for the full U.S. view? See the MCA Compliance Requirements (2026) hub.
At a Glance
Effective baseline: Virginia’s SBFP chapter applies to sales-based financing agreements entered into on/after July 1, 2022, and required covered providers/brokers to register with the Commission (including a statutory “register by November 1, 2022” requirement for those operating at the time). Disclosures must be provided with a specific offer, and the recipient’s signature (including e-signature) is required at acceptance.
What Virginia requires (high level)
- Registration for covered sales-based financing providers and sales-based financing brokers.
- Offer-stage disclosures using the required form/format prescribed by the Commission.
- Signature capture (paper or e-signature) when the recipient accepts the specific offer.
Not legal advice. This page is an operational overview for marketing/sales and workflow planning. Counsel should confirm applicability for your specific product and channels.
1 | Who’s Covered in Virginia
Virginia’s SBFP framework is focused on sales-based financing transactions and defines both providers and brokers. In practice, your workflow should first decide: “Are we the provider, are we brokering, or both?”—then ensure the right registration and the right disclosure flow.
Providers
- Entities extending a specific sales-based financing offer to a Virginia recipient (subject to definitions/exemptions in the chapter).
- Providers must deliver the required disclosures and obtain signature at acceptance.
Brokers / ISO channels
- Virginia requires registration for sales-based financing brokers (and providers).
- Operationally: keep broker activities aligned with a centralized disclosure + signature capture workflow.
Practical takeaway: Virginia is where “channel ops” matters. If ISOs touch the deal, keep disclosure delivery and signature capture inside a controlled system.
2 | Virginia Disclosure Requirements (Plain English)
Virginia requires providers to deliver specific disclosures at the time of extending a specific offer, using the formatting prescribed by the Commission. When the recipient accepts the offer, the provider must obtain the recipient’s signature (including electronic signature) on the required disclosures.
What your team should be ready to disclose
- Total amount of sales-based financing and disbursement amount (if different)
- Finance charge and other required cost terms (per the statute/form)
- Payment mechanics (especially for variable remittance structures)
- Any required additional items included in the Commission’s prescribed formatting
Exact fields are defined in the chapter + Commission formatting; implement via a controlled template.
Operational best practices
- Use a version-controlled disclosure tied to the “specific offer”
- Require signature capture before finalizing (no sign → no fund)
- Store disclosure + signature + timestamps in an audit log
Tip: Virginia explicitly cares about signature capture on disclosures at acceptance—build that step into your pipeline, not as a “later” admin task.
3 | Registration (Virginia SCC / Bureau of Financial Institutions)
Virginia requires registration for covered SBFP providers and SBFP brokers. The SCC/BFI publishes the registration form and also publishes registrant lists that are useful for vendor diligence and “are we listed?” checks.
What to track internally
- Registration status for provider and (if applicable) broker entities
- Legal entity names used in Virginia (match registrations to contracts)
- Renewal/maintenance cadence and compliance ownership (who is responsible)
- Disclosure signature capture compliance (audit evidence)
Where to confirm details
Practical takeaway: Make “Virginia registration verified” a deal prerequisite for in-scope originations. It’s a simple checkbox that prevents expensive mistakes.
4 | How LendSaaS Helps Teams Stay Virginia-Ready
Offer-Stage Disclosure Engine
Generate a “specific offer” disclosure packet in seconds, tied to the deal record and protected by version control.
E-Sign + Signature Capture
Capture recipient signatures (including e-sign) at acceptance and store proof automatically—so your file matches Virginia’s signature expectations.
Registration-Aware Deal Ops
Track whether your provider/broker entities are registered and make registration status a visible gating checkpoint in your pipeline.
Audit Log (Export-Ready)
Time-stamped storage of disclosures, signatures, and key deal metadata—easy to export for internal reviews, partners, and compliance checks.
5 | FAQs (Virginia)
Does Virginia “apply to MCAs,” specifically? +
Is Virginia disclosure-only, like Georgia/Kansas? +
When do disclosures get delivered in Virginia? +
How do we confirm our registration status? +
Want the macro view? See the MCA Compliance Requirements (2026) page and compare Virginia with other enacted states.
Ready to make compliance easier?
LendSaaS helps MCA and sales-based financing teams automate disclosures, capture signatures, keep audit trails clean, and stay ahead of state-by-state requirements.