When an MCA Becomes a Loan: The Recharacterization Risk Every Funder Should Understand
MCA recharacterization risk turns on economics and conduct, not labels. This expanded guide explains true-sale evidence, reconciliation design, default triggers, recourse, servicing behavior, and file proof.
Courts and regulators look beyond labels. An agreement can say “purchase of receivables” while the economics, payment schedule, reconciliation process, default triggers, and recourse rights make it look like a loan. The operator question is simple: who actually bears the risk that receivables come in slower than expected? Legal context: Hudson Cook discussion of bankruptcy recourse in MCA agreements ; California DFPI commercial financing disclosure page . The true-sale evidence stack Evidence category Stronger true-sale signal Weaker signal Payment variability Remittance adjusts with actual receipts or sales, and the merchant can realistically request reconciliation. Fixed daily payment continues regardless of revenue, with reconciliation unavailable or ignored. Term Estimated duration changes with business performance. Hard repayment schedule resembles amortization. Recourse Default rights focus on merchant interference, fraud, diversion, or breach of covenants. Funder can demand payment in full when sales slow, business closes, or bankruptcy occurs. Servicing behavior Staff explains and processes reconciliation requests consistently. Servicing pressures merchant to keep paying the same amount after documented revenue decline. Collections conduct Remedies match contract breaches and documented impairments. Automatic acceleration, aggressive account seizures, or threats make the transaction look absolutely repayable. Design reconciliation as a real process Merchant instructions: the agreement and welcome email should explain how to request reconciliation, what documents are needed, and expected timing. Intake queue: every request should get a ticket ID, timestamp, merchant contact, claimed revenue change, requested payment adjustment, and supporting documents. Evidence review: compare bank deposits, processor statements, seasonality, closures, returns, and known disruptions. Do not require impossible proof. Decision record: approve, deny, or request more information with a reason code and reviewer identity. Payment update: apply the adjusted remittance prospectively or as policy requires, then confirm the new amount to the merchant. Audit sample: review reconciliations monthly, especially denials, repeat requests, and accounts that later default. Default triggers that deserve review Trigger Risk question Cleaner drafting/operation Business slowdown Does ordinary revenue decline trigger default? Treat slowdown as reconciliation/servicing issue, not automatic default. Bankruptcy Does filing alone create immediate full recourse? Review carefully with counsel. Bankruptcy-as-default can weigh against true-sale treatment. Account change Is the merchant diverting receivables or simply changing banks? Require notice and verification, then distinguish impairment from administrative change. Missed ACH Was the debit unauthorized, returned, or tied to lower sales? Investigate return reason before acceleration. Stacking Does another position actually impair purchased receivables? Document the impairment and agreement breach rather than treating every new advance the same. File proof for recharacterization defense Contract version: current receivables purchase agreement and state-specific addenda. Offer math: purchased amount, purchased percentage, expected remittance, estimated term, and disclosure values. Merchant communications: onboarding email explaining purchased receivables, reconciliation, and servicing contact path. Payment history: remittance pattern, adjustments, missed payments, reasons, and communications. Reconciliation records: all requests, supporting documents, decisions, and payment changes. Collections notes: remedy used, contract basis, approvals, and merchant contact record. Red flags before funding The deal only works if daily debits never change. That is a credit-underwriting signal and a product-structure warning. The merchant is already stacked beyond cash-flow capacity. Additional positions can turn servicing into collection immediately. The broker sold the term as fixed. Merchant expectations will conflict with true-sale language. The agreement has reconciliation, but the platform cannot process it. Paper rights without operational support are weak evidence. Opinion The best protection is operational consistency Recharacterization risk is not solved by a magic clause. It is reduced when the economics, communications, servicing, and collections behavior all show the funder accepted receivables risk rather than demanding absolute repayment.