Kansas MCA Compliance Requirements
Kansas MCA Compliance Requirements (2026)
Kansas’s Commercial Financing Disclosure Act (SB 345) is live. If you provide MCA-like products (often structured as receivables purchases) or other covered commercial financing to Kansas businesses, you need compliant disclosures delivered before (or at) consummation—plus clean, audit-ready proof of what was delivered and when.
Looking for the full U.S. view? See the MCA Compliance Requirements (2026) hub.
At a Glance
Effective baseline: Kansas SB 345 took effect July 1, 2024 and generally excludes commercial financing transactions over $500,000. Disclosures must be delivered before or at consummation, and the statute states that only one disclosure is required per transaction (no new disclosure required for later modifications/forbearance).
What Kansas requires (high level)
- Written disclosures for covered commercial financing transactions.
- Timing: before or at the time of consummation.
- Provider threshold: “provider” generally means a person who consummates more than five covered transactions to a Kansas business in a calendar year.
- Deal-size scope gate: transactions > $500,000 are excluded.
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 Kansas
Kansas defines “commercial financing transaction” broadly and includes categories that can overlap with MCA / sales-based financing and receivables purchase structures. Coverage often turns on (1) whether your transaction fits the definition, (2) whether the recipient is a Kansas business, (3) whether the deal is within scope (notably the $500,000 cap), and (4) whether you meet the “provider” threshold.
Providers
- Generally, a person who consummates more than five commercial financing transactions to a Kansas business in a calendar year.
- Also includes certain online platform arrangers working with a depository institution (per definition).
Brokers / ISO channels
- Kansas defines “broker” and includes broker-related rules in the Act.
- Operationally: keep broker/ISO activities aligned with disclosure timing and approved marketing language.
Practical takeaway: Kansas is a “scope + process” state. If you systemize deal gating (≤ $500k) and disclosure delivery, you’ll avoid most issues.
2 | Kansas Disclosure Requirements (Plain English)
Kansas requires providers to disclose required terms before, or at the time of, consummating a covered commercial financing transaction. The statute also states that only one disclosure is required per transaction and a new disclosure is not required for modifications/forbearance/changes to an already consummated transaction.
What your team should be ready to disclose
- Total funds provided and total funds disbursed (if different)
- Total of payments / total amount to be paid
- Total dollar cost of financing
- Payment schedule/cadence and amounts (or estimates if variable)
- Key fees and material terms
Operational best practices
- Deal gate: confirm ≤ $500,000 and not otherwise excluded
- “No disclosure, no consummation” workflow step
- Store disclosure + timestamps + acknowledgement in an audit log
Tip: Variable payment structures need especially clear disclosures. If payments can change, keep your disclosure logic and agreement language consistent.
3 | Enforcement + Penalties (Kansas)
Kansas provides for civil penalties for violations, with increased penalties for violations that continue after written notice from the Attorney General. Commentary sources also note the Attorney General’s enforcement authority and that the Act creates no private right of action.
What to track internally
- Disclosure version delivered (exact PDF/HTML) + timestamp
- Acknowledgement timestamp (who accepted, when)
- Deal amount (≤ $500k gate) and product type classification
- Broker/ISO involvement and approved marketing language
Penalty framework (high level)
- $500 per violation, capped at $20,000 aggregated
- After written notice of a prior violation: $1,000 per violation, capped at $50,000 aggregated
- External commentary: AG enforcement; no private right of action
Practical takeaway: Kansas rewards “boring consistency.” Build a repeatable disclosure workflow and keep proof attached to every deal record.
4 | How LendSaaS Helps Teams Stay Kansas-Ready
Disclosure Workflow + Version Control
Generate the correct Kansas disclosure packet, lock versions, and keep teams using the approved template—every time.
Automated Delivery + Acknowledgement
Deliver disclosures at the right moment and capture acceptance timestamps—so your compliance file is defensible.
Deal Gating (≤ $500k)
Flag Kansas transactions over $500k as out-of-scope and keep your disclosure workflow triggered only when it should be.
Audit Log (Export-Ready)
Time-stamped storage of disclosures, acknowledgements, and key deal metadata—easy to export for internal reviews and partner diligence.
5 | FAQs (Kansas)
Does Kansas “apply to MCAs,” specifically? +
What’s the Kansas deal-size cap? +
When must disclosures be delivered in Kansas? +
Does Kansas require a new disclosure if a deal is modified later? +
Want the macro view? See the MCA Compliance Requirements (2026) page and compare Kansas 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.