Onyx IQ Blog | Insights on Lending Operations & Automation

How to Stay Compliant While Scaling Your Lending Operation

Written by Onyx IQ | Nov 2, 2026, 7:45:00 PM

Updated November 2026

Compliance gets harder faster than loan volume grows. The manual checks that hold up at fifty deals a month break at five hundred, and in a regulated business every missed disclosure, unverified registration, undocumented decision, or collection slip can turn into a penalty, a regulatory inquiry, a merchant dispute, or a lost capital partner.

The good part: compliance does not have to slow growth. With the right operating model, technology, and a few outside specialists, you can add volume, products, brokers, and states without adding a proportional compliance team. This guide is written for commercial and alternative lenders, merchant cash advance funders included. It covers how compliance attaches across the lending lifecycle, which rules may apply, what breaks as you scale, how to measure it, and a 90-day plan to put it in place.

This is general information for funders, not legal advice. What applies to you depends on your products, your states, your counterparties, and the facts of each deal. Confirm current obligations with qualified counsel.

Start here

How do commercial lending workflows impact compliance requirements?

Every stage of a commercial lending workflow creates a compliance obligation, so your workflow and your compliance program are the same system seen from two angles. When volume is low, a person can carry each obligation by hand from step to step. As you scale, the handoffs become the weak point: a disclosure goes out too late, a registration never gets verified, an exception gets approved with no documentation, or a complaint never gets categorized. A scalable program treats each stage as a control point, like this:

Lifecycle stage Compliance objective Example controls
Marketing and lead gen Accurate claims, appropriate targeting Approved marketing library, broker and ISO rules, complaint monitoring
Intake and application Complete, accurate, protected data Identity and business verification, data minimization, access controls, document checklists
Underwriting and decisioning Consistent, explainable decisions Credit policy, exception approvals, model documentation, override monitoring
Offer and disclosure Correct disclosure at the required time State rules engine, disclosure templates, APR or estimated-APR calculation, acknowledgment capture
Funding Authorized, documented funding Registration and licensing verification, funding checklist, approval evidence, audit trail
Servicing Accurate account administration Reconciliation, statements, notices, payment handling, record retention
Collections and default Lawful, consistent conduct Collection scripts, complaint escalation, UCC and guarantee procedures, vendor oversight
Enterprise-wide Demonstrable governance Risk assessment, policies, training, KRIs, audit trail, corrective actions

The practical takeaway: compliance works best as a set of controls embedded in the workflow, so each obligation is met and the evidence captured as the deal moves. That reframing is what lets compliance scale, and it starts with knowing which rules actually reach your business.

The rulebook

Know which rules may apply to you

Commercial and alternative lenders do not all carry the same load. The first move is to classify the product, identify the states involved, and work out which federal, state, and contractual requirements actually apply. The core consumer-credit laws, the Truth in Lending Act, RESPA, and HMDA, are built around consumer and residential mortgage lending, and most commercial loans and merchant cash advances fall outside them.

Federal

  • ECOA and fair lending: ECOA reaches extensions of credit to businesses, so keep consistent criteria, document decisions and exceptions, and apply Regulation B adverse-action rules where they fit.
  • UDAP and the FTC Act: unfair or deceptive practices standards can reach advertising, disclosures, servicing, and collections, even where no statute names your specific product.
  • GLBA and privacy or security laws: determine whether GLBA, the FTC Safeguards Rule, or state laws like CCPA apply, then put appropriate administrative, technical, and physical safeguards on the data you hold.
  • AML and KYC: determine whether Bank Secrecy Act obligations apply directly. Even where they do not, bank partners, processors, and capital providers often require identity verification, sanctions screening, and beneficial-ownership review.
  • Section 1071: the CFPB's revised small-business data rule excludes merchant cash advances, with a January 1, 2028 compliance date for covered institutions. For most funders, state law is the more immediate surface.

State

State commercial-financing, sales-based-financing, and revenue-based-financing laws are now the central compliance issue for MCA funders. At least eleven states have disclosure laws that can reach MCA-style deals (California, Connecticut, Florida, Georgia, Kansas, Louisiana, Missouri, New York, Texas, Utah, and Virginia), and Vermont has enacted a licensing-and-disclosure framework that takes effect July 1, 2027. Our state-by-state regulation guide breaks down each one. Do not assume one national workflow works everywhere: coverage can turn on the merchant's location, where the deal was solicited, where the offer was extended, the product structure, and the amount.

The scaling trap

What breaks as you grow

Growth exposes weak controls. These five failure points create the most compliance risk, and each has a control that contains it.

  • Fragmented data. When application, decision, disclosure, funding, servicing, and complaint data live in separate systems, producing evidence becomes a manual scramble, and missing timestamps are hard to explain under audit. Control: keep one deal record that links the application, decision, disclosure, contract, funding approval, servicing activity, and complaint history.
  • Manual handoffs. Spreadsheets and email approvals work at low volume and create errors at scale. A missed disclosure trigger is usually a workflow problem, not a knowledge problem. Control: convert recurring checks into system-enforced steps, with required fields, approval gates, and document-generation rules.
  • Multi-state expansion. Each new state can add disclosure, registration, licensing, broker, usury, or collection requirements, and entering one without updating templates and training creates exposure on the first deal. Control: use a state-entry checklist, and do not enable funding in a state until legal review, disclosure logic, registration, and training are done.
  • Broker and vendor risk. Brokers, ISOs, servicers, processors, and capital partners can all introduce risk, and a broker's misleading marketing can land on you even though it was outsourced. Control: use vendor due diligence, written compliance requirements, audit rights, approved-marketing controls, and complaint escalation.
  • Model and pricing risk. AI-driven underwriting and automated pricing can create fair-lending risk if no one monitors inputs, outcomes, and overrides. Control: keep a model inventory, test outcomes periodically, monitor overrides, and require human review for material exceptions.

The framework

Build a compliance program that scales

A durable program has five components that work together:

  • Risk assessment. Map every product, state, channel, broker, vendor, and data flow to the laws that apply, rate the risk, and assign an owner to each one. Refresh it whenever you enter a state, launch a product, add a broker, change pricing, or adopt a new model.
  • Written policies and procedures. A policy says what must happen; a procedure says who does it, when, in which system, and what evidence to keep. Version-control every policy, template, and state rule so you can show what was in effect on any given date.
  • Embedded controls. Build the checks into origination and servicing so issues surface before a deal closes: the required state disclosure before its trigger, registration verified before funding, APR calculated from deal terms, exceptions approved and documented, and a timestamped audit trail on every material action.
  • Complaint and incident management. Treat complaints as an early-warning system, categorized by product, state, channel, broker, and root cause, and run a separate incident process for security events and material disclosure failures.
  • Training and reporting. Give role-based training to sales, underwriting, funding, servicing, collections, and leadership, train brokers on the rules that apply to them, and report key risk indicators on a regular cadence.

Measure it

Track compliance with a KRI dashboard

A dashboard makes compliance measurable instead of a gut feel. Start with a small set of high-value indicators rather than tracking everything at once. The thresholds below are suggested starting points, so tune them to your risk tolerance. Treat the middle band as a trigger for documented management review and the top band as immediate escalation.

Key risk indicator How to measure it Frequency Healthy Watch Escalate
Disclosure delivered before trigger On-time disclosures / deals requiring one Weekly 100% 98-99.9% Below 98%
Disclosure exception rate by state Exceptions / covered deals Weekly Below 1% 1-3% Above 3%
APR or estimated-APR outlier rate Outliers / calculated deals Weekly Below 1% 1-2% Above 2%
Registration verified before funding Verified / deals requiring it Weekly 100% 98-99.9% Below 98%
Broker registration verified Verified / brokered deals requiring it Weekly 100% 98-99.9% Below 98%
Underwriting exception rate Exceptions / approved deals Monthly Below 5% 5-10% Above 10%
Model override rate Overrides / decisions Monthly Below 5% 5-10% Above 10%
Payment reconciliation break rate Unresolved breaks / items Weekly Below 1% 1-3% Above 3%
Overdue corrective actions Overdue / total actions Monthly 0% 1-10% Above 10%
Regulatory-change lag Avg days from effective date to live Monthly 30 days or less 31-60 days Over 60 days

For MCA funders

Add the MCA-specific controls

MCA funders need controls that generic commercial-lending compliance misses, because the product and its collection mechanics are specific.

  • Product classification. Work out whether the deal is a true purchase of receivables, revenue-based financing, a loan, factoring, or a hybrid. The classification drives disclosure, registration, usury, and UCC analysis. Our lending glossary defines the terms.
  • UCC and collateral. Review UCC-1 filings, collateral descriptions, jurisdictions, continuations, and terminations, because stale or inaccurate filings create perfection and priority problems at enforcement.
  • Guarantees and confessions of judgment. Personal guarantees and confession-of-judgment provisions affect collection rights, and their enforceability varies by state, so they need legal review and consistent handling.
  • Reconciliation and default. MCA disputes often turn on how payments were applied, how holdbacks were calculated, and how default was declared, so keep clear records of each.
  • Collections conduct. Aggressive tactics create legal, reputational, and capital-partner risk, so apply documented scripts, escalation rules, complaint handling, and vendor oversight.

Technology

Let technology carry the load

Technology turns recurring manual checks into repeatable controls, which is how you handle ten times the volume without ten times the headcount. Look for a platform that can:

  • Run compliance checks inside origination and servicing, not after the fact
  • Generate jurisdiction-specific disclosures from deal data
  • Calculate APR or estimated APR consistently
  • Verify and document registration or licensing status
  • Keep a timestamped audit trail showing user, action, deal, document version, and time
  • Configure rules by state, product, broker, and deal type
  • Capture merchant acknowledgments and signed disclosures
  • Produce exception reports and KRI dashboards, and intake and escalate complaints

How Onyx IQ helps

Onyx IQ builds compliance into the funding workflow, so the work happens as the deal moves and the evidence is there the moment someone asks for it. For a growing funder, the gains are the point: you expand into new states without a legal project for each one, you stop risking per-violation fines over a missed disclosure, and you walk into an exam or a capital-partner review with the file already built. Subject to your own legal review, here is what that looks like in practice:

  • Expand into new states without the overhead. Onyx IQ detects the merchant's state and generates the right disclosure at the funding event, and when a new state law takes effect the template is added for you. When Mississippi's law took effect, its disclosure was live in the platform that day, so funders did not have to build it under a deadline.
  • Stop missing disclosures and APRs. The platform generates the state disclosure and calculates the APR to spec before the contract, then captures the merchant's signature and a timestamp and attaches the signed copy to the deal record.
  • Walk into any exam audit-ready. Every approval, modification, and decision is logged automatically across underwriting, servicing, and collections, so the audit file is built continuously instead of assembled the week before an exam.
  • Give capital partners the reports they ask for. Static pool reports by vintage, collection curves, and GAAP-formatted outputs come out of the box, which is exactly what a bank sponsor or syndicator wants before extending a facility.
  • Clear security diligence once. SOC 2 Type II covers the platform end-to-end, from origination through reporting, under one attestation.

As Nick Lavoie of Lavoie Capital put it, Onyx IQ “gave us the structure and compliance framework we needed from day one.” One honest caveat on that last point: SOC 2 Type II is strong evidence of security controls, but it does not by itself satisfy GLBA, state privacy laws, or every contractual requirement, so treat it as one input into a broader data-security review. For the mechanics of how the disclosures run, see our guide to automated disclosures for MCA compliance, and the servicing and audit trail behind it.

Partners

Use outside specialists strategically

You do not have to build every capability in-house. Compliance counsel can interpret state laws, review disclosures, and track legal changes. An independent consultant can design policies, run gap assessments, and prepare you for audits. A specialized servicer can handle payment processing, escrow, reconciliation, and collections under strong oversight. An independent auditor or model-validation provider can test controls and fair-lending outcomes. The rule of thumb: outsource work that is operationally heavy and far from how you win deals, and keep accountability for the compliance outcomes, the vendor performance, and the regulatory change.

Put it in place

A 90-day implementation plan

Days 1 to 30: baseline

  • Inventory products, states, channels, brokers, vendors, and data systems
  • Map the deal lifecycle from lead to payoff or default
  • Pull a sample of recent deals and test disclosure, registration, documentation, and exception controls
  • Identify the missing owners, policies, and evidence

Days 31 to 60: build controls

  • Update policies and procedures, and configure state rules, disclosure templates, and approval gates
  • Create a state-entry checklist and a pre-funding checklist
  • Stand up complaint categorization and corrective-action tracking
  • Assign an owner to every material control

Days 61 to 90: operate and prove

  • Launch the KRI dashboard and run a targeted self-audit
  • Train origination, underwriting, funding, servicing, and collections teams
  • Set quarterly regulatory-change, vendor, and model-review cycles
  • Report results to leadership with owners and deadlines
 

Scale without the compliance drag

See compliance built into the workflow

See how Onyx IQ runs disclosures, the APR calculation, and the audit trail as part of funding, so you add volume and states without adding a compliance team.

FAQ

Compliance and scaling FAQ

How do commercial lending workflows impact compliance requirements?

Every stage carries an obligation: intake involves data protection and verification, underwriting involves consistent and documented decisioning, funding involves disclosure and registration, servicing involves accurate administration, and collections involves lawful conduct and records. The handoffs between stages are where obligations get missed, so the fix is to build the checks into each step rather than review deals after they close.

Which regulations apply to commercial and MCA lenders?

It depends on the product and jurisdiction. The consumer-credit laws (TILA, RESPA, HMDA) mostly do not reach commercial loans or MCAs. What can apply: ECOA and fair lending, UDAP and the FTC Act, state commercial-financing and sales-based-financing laws, privacy and security laws like GLBA and CCPA, AML and KYC expectations, UCC rules, and contractual requirements from bank or capital partners.

Does the Truth in Lending Act apply to merchant cash advances?

Generally no. TILA is a consumer-credit law, and a typical MCA is structured as a purchase of future receivables rather than a loan, so it falls outside TILA. State commercial financing disclosure laws, not TILA, are usually the primary disclosure source for MCA funders.

Does the CFPB regulate MCA funders?

The CFPB's revised Section 1071 rule excludes merchant cash advances from covered transactions, with a January 1, 2028 compliance date for institutions still covered. That does not remove all federal conduct risk, since the FTC Act's ban on unfair or deceptive practices can still apply, but the day-to-day surface for funders is state law.

What should compliance technology do?

Run controls inside origination and servicing, generate jurisdiction-specific disclosures, calculate APR or estimated APR, verify registrations, keep a timestamped audit trail, configure rules by state and product, capture signed acknowledgments, and surface exceptions and KRIs before they become systemic failures.

How do I keep compliance from slowing growth?

Build the controls into the deal workflow, assign clear owners, automate recurring checks, monitor with exception reports and a KRI dashboard, train your teams, and use outside specialists for heavy or specialized work. Compliance slows growth when it is a manual review after the fact; it keeps pace when it is embedded in origination and servicing.

When should a lender outsource compliance or servicing?

Outsource work that is operationally heavy and far from how you win deals, and keep accountability for the outcomes. Compliance counsel can track regulatory change, and a specialized servicer can run payment processing, escrow, and collections under oversight. Many MCA funders keep servicing in-house and use outside counsel for state-law work.

Sources

Sources and references