Georgia MCA Compliance Requirements
Georgia MCA Compliance Requirements (2026)
Georgia’s SB 90 disclosure framework is live. If you provide MCA-like products (often structured as receivables purchases) or other covered commercial financing to Georgia businesses, you need compliant, pre-consummation disclosures—and clean, consistent documentation that matches your actual payment mechanics.
Looking for the full U.S. view? See the MCA Compliance Requirements (2026) hub.
At a Glance
Effective baseline: Georgia requires specified disclosures before consummation for covered commercial financing transactions consummated on/after January 1, 2024, generally for amounts ≤ $500,000. The statute also includes broker restrictions and Attorney General enforcement.
What Georgia requires (high level)
- One-time, pre-consummation disclosure for each covered transaction.
- Core economics: funds provided, funds disbursed, total of payments, total dollar cost, payment cadence.
- Variable payment methodology described in the agreement (important for sales-based financing).
- Broker rules (e.g., limits on advance fees, misleading representations).
Applicability depends on definitions, thresholds, and exemptions—confirm with counsel.
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 Georgia
Georgia’s statute defines covered commercial financing transactions as business-purpose transactions involving (a) commercial loans, (b) commercial open-end credit plans, or (c) accounts receivable purchase transactions. Coverage is generally capped at $500,000 and subject to exemptions.
Providers
- Generally: a person who consummates more than five covered transactions in Georgia in a calendar year.
- Includes certain platform/marketplace participants depending on structure.
- Multiple exemptions exist (e.g., federally insured depository institutions and other statutory carve-outs).
Brokers / ISO channels
- Georgia includes broker-related restrictions (and enforcement) within the disclosure framework.
- Operationally: keep broker practices aligned with disclosure timing and approved marketing language.
Practical takeaway: Georgia is a “process state.” Your edge is a repeatable workflow: GA recipient → confirm ≤ $500k → generate disclosure → capture acknowledgement → store the exact version delivered.
2 | Georgia Disclosure Requirements (Plain English)
Before consummating a covered transaction, the provider must disclose key terms. The statute is also explicit that only one disclosure is required per transaction (and generally not again for modifications/forbearances after consummation). For variable payments, the agreement should describe the methodology and circumstances that cause payments to vary.
Common disclosure elements (operational view)
- Total funds provided
- Total funds disbursed (if different)
- Total amount to be paid to the provider
- Total dollar cost
- Payment manner / frequency / amount (or estimated initial payment if variable)
- Prepayment costs/discounts (and where to find them in the agreement)
Best practices for MCA / sales-based financing
- Standardize “variable payment” language and ensure it matches actual remittance mechanics
- Use a disclosure gate: no docs signed / no funding until acknowledgement is captured
- Keep “funds provided vs funds disbursed” clean (fees, payoffs, third-party payments)
Tip: Most GA issues come from misalignment: sales promises one thing, the agreement says another, and the disclosure doesn’t match either. Make all three consistent.
3 | Broker Restrictions + Enforcement (Georgia)
Georgia’s framework includes broker conduct limits (e.g., restrictions on collecting certain advance fees and prohibitions on misleading practices), and enforcement authority sits with the Georgia Attorney General. The statute also specifies civil penalties and clarifies there is no private right of action.
What teams should track
- Approved sales/ISO scripts and marketing claims (avoid misleading representations)
- Disclosure version control + proof of delivery
- Deal size gating (≤ $500k) and exemptions (where applicable)
- Document consistency: disclosure ↔ agreement ↔ actual payment behavior
Where to confirm details
Practical takeaway: If you run ISO channels, Georgia is where “compliance ops” meets “go-to-market.” Build controls so disclosures and documentation stay consistent at scale.
4 | How LendSaaS Helps Teams Stay Georgia-Ready
Disclosure Workflow + Version Control
Generate the correct Georgia disclosure packet, lock versions, and keep the team using the approved template—every time.
Acknowledgement Capture
Capture acceptance timestamps and keep proof of delivery tied to the deal record to reduce “he said/she said” risk.
Deal Gating (≤ $500k) + Consistency Checks
Standardize funds provided vs funds disbursed logic and keep disclosures aligned with the agreement and payment mechanics.
Audit Log (Export-Ready)
Time-stamped storage of disclosures, acknowledgements, and key deal metadata—easy to export for internal review.
5 | FAQs (Georgia)
Does Georgia “apply to MCAs,” specifically? +
What’s the dollar threshold in Georgia? +
When must the disclosure be delivered? +
Does Georgia require provider/broker registration like Connecticut or Missouri? +
Want the macro view? See the MCA Compliance Requirements (2026) page and compare Georgia with other enacted states.
Ready to make compliance easier?
LendSaaS helps MCA and sales-based financing teams automate disclosures, keep audit trails clean, and stay ahead of state-by-state requirements.