The State Disclosure Map: Why MCA Compliance Depends on Where the Merchant Is
MCA compliance depends on merchant location and offer mechanics. This expanded guide explains how to build a state disclosure map, trigger disclosures at the right time, manage broker transmission, and maintain proof.
For multi-state MCA shops, the compliance map starts with where the merchant is principally directed or managed, where the broker operates, what product is offered, and whether the offer has become specific enough to trigger a disclosure. A static list of states is not enough. The map has to live inside the offer workflow. Official disclosure sources: California DFPI commercial financing disclosure page ; New York DFS commercial finance disclosure regulation announcement ; Virginia sales-based financing disclosure form rule . Build the state map as a decision tree Decision point Question to answer System field Recipient location Where is the business principally directed or managed? Is the owner a natural person resident in a covered state? principal_business_state, legal_address_state, owner_residence_state Product type Is this sales-based financing, closed-end financing, open-end credit, factoring, leasing, or asset-based lending? product_type, repayment_basis, purchased_percentage Amount threshold Is the financing amount inside the state threshold? Does the threshold use amount provided, principal amount, or another measure? funding_amount, purchased_amount, threshold_rule_version Provider or broker role Who extends the specific offer? Who transmits it? Is compensation paid to a broker? provider_id, broker_id, broker_compensation, exclusive_relationship Offer timing Has the merchant received a specific offer, selected an option, or accepted terms? offer_status, offer_presented_at, accepted_at Signature and retention Is a signed disclosure required? How long must evidence be retained? disclosure_signed_at, disclosure_storage_url, retention_until Operational steps for a compliant offer Step 1, intake: collect merchant state, business address, DBA, owner address where relevant, requested amount, product type, broker ID, and existing financing positions. Step 2, eligibility: run the state matrix before quote generation. If the merchant is in a covered state, lock the required fields and template. Step 3, quote building: calculate amount funded, total dollar cost, payment amount or percentage, estimated term, prepayment policy, fees, broker compensation where required, and collateral/security interest description where applicable. Step 4, disclosure delivery: deliver the correct disclosure at the same time the specific offer is extended. If the broker delivers it, require timestamped proof and the signed copy. Step 5, acceptance gate: do not allow closing until the signed disclosure, agreement, ACH authorization, and required stipulations are in the file. Step 6, retention: store the disclosure version, calculation inputs, signed PDF, delivery proof, broker transmission proof, and any payoff/refinance updated disclosure. What to track by state State rule category Why it matters Control Disclosure content States can require different rows, labels, annualized rate presentation, fee descriptions, and payment explanations. Versioned templates by state and product type. Broker duty A state may impose duties on the provider, broker, financer, or some combination. Broker agreement requires transmission evidence and prohibits off-template offer summaries. Registration or authority Some states include registration or authority-to-transact requirements for providers or brokers. Entity calendar with owner, due date, renewal proof, and stop-funding trigger if lapsed. Payoff/refinance disclosure Renewals can trigger updated disclosure obligations and merchant confusion. Renewal workflow calculates net funding, payoff, remaining purchased amount, fees, and discount treatment. Record retention Disclosure proof is only useful if retained with the calculation inputs. Document storage tied to article/file ID, template version, and retention date. Broker transmission is the weak link Many shops can generate the right form. Fewer can prove the merchant received it at the right time through the channel that actually sold the deal. If a broker sends a screenshot, edits the economics in a text message, or pressures the merchant before the disclosure is delivered, the provider may still own the risk. Require broker IDs on every offer. No broker ID, no commission, no funding. Send disclosures from the system when possible. If the broker must transmit, require timestamped proof, exact PDF copy, and signed return before closing. Ban side-by-side “cost summaries” unless approved. Unapproved summaries create mismatch risk against formal disclosure. Audit broker files monthly. Pull by state, broker, exception, complaint, and renewal. A sample state-matrix record Field Example value state California trigger_location Business principally directed or managed from state covered_products Sales-based financing and other commercial financing categories, subject to rule details offer_trigger Specific offer extended to recipient required_evidence Generated disclosure, calculation inputs, delivery proof, signed acceptance, broker transmission proof if broker delivered owner Compliance operations last_reviewed Quarterly or upon legal update Opinion The disclosure map should stop deals, not just document them If the state matrix only lives in a spreadsheet, it is a reference. If it blocks closing until the right disclosure evidence is present, it is a control. The second version is what operators need.