Fundnode · Learn

Glossary · MCA multi-merchant aggregation

MCA multi-merchant aggregation

Multi-merchant aggregation is when a single business owner consolidates MCA financing across multiple business entities they own (separate restaurants, multi-location franchise, multi-truck trucking operation) into a single advance underwritten on combined revenue and secured by guarantees on all entities. Used to access larger advance amounts ($500K+) than any single entity would qualify for individually.

By Keerthana Keti5 min read

MCA multi-merchant aggregation is the underwriting and structural practice of combining multiple business entities under common ownership into a single MCA transaction. This serves owners of multi-unit operations — franchisees with 3-10 locations, trucking owner-operators with multiple trucks, multi-store retailers, multi-restaurant restaurateurs — who need larger financing than any single entity supports individually.

The mechanics — how aggregation works structurally. Two primary structures: 1. Single advance with multiple-entity guarantees. Funder issues one advance to one primary entity. All other commonly-owned entities provide cross-guarantees and grant security interests. Daily debit pulls from the primary entity's account (sometimes with backup auto-pull from other entities if primary fails). 2. Synchronized advances with combined underwriting. Funder issues separate advances to each entity (one per location/unit) but underwrites all simultaneously based on combined financial profile. Each entity has its own contract, debit schedule, and RTR — but pricing reflects the combined risk picture.

The economics — why aggregation produces favorable pricing. Three pricing benefits: 1. Revenue concentration risk reduction. A single restaurant with $30K/mo revenue presents location-concentration risk; six locations with combined $180K/mo revenue diversifies that risk. Funder prices 0.04-0.08 lower factor. 2. Larger advance size unlocks tier pricing. Advances over $250K typically receive 0.03-0.05 factor improvement; advances over $500K can receive 0.05-0.10 improvement. Aggregation unlocks these tiers. 3. Multi-entity guarantee strengthens recovery position. If one entity defaults, funder has recourse against other commonly-owned entities. Reduces expected loss severity by 30-50% versus single-entity structure.

The math — aggregation pricing example. Owner has 4 restaurants: - Restaurant A: $25K/mo revenue, 18 months in business. - Restaurant B: $32K/mo revenue, 14 months. - Restaurant C: $28K/mo revenue, 22 months. - Restaurant D: $35K/mo revenue, 8 months (newer, weaker standalone).

Individual approach (4 separate $40K advances at 1.36 factor average): - Total advance: $160K. - Total RTR: $217.6K. - Total interest cost: $57.6K. - Restaurant D may not qualify individually (only 8 months); declined separately.

Aggregated approach (single $250K advance underwriting all 4 entities): - Combined revenue: $120K/mo qualifies for tier pricing. - Factor: 1.28 (vs 1.36 individual average). - Total RTR: $320K. - Total interest cost: $70K on $250K vs $57.6K on $160K. - Effective rate improvement: aggregation produces $90K additional capital for $12.4K additional interest — extremely favorable marginal economics on the incremental $90K.

The mechanics — underwriting documentation requirements. Aggregated deals require: 1. Ownership verification across entities. Funder must verify common ownership — operating agreements, K-1s, organizational charts, or specific cross-entity declarations. 2. Combined financial statements. Aggregate revenue, expense, and cash-flow data across all entities. 3. Individual entity bank statements. Each entity's 3-6 month bank statements for the underwriting model. 4. Cross-guarantees executed by all entities. Each entity must execute a guarantee of the others' obligations. 5. Personal guarantee from owning principal(s). Standard PG from each individual with 20%+ ownership stake. 6. UCC filings on all entities. Filings registered against each guaranteeing entity.

The mechanics — daily debit operational structure. Three operational patterns: 1. Single-entity debit. Daily debit pulls only from the primary entity's account; the primary entity is responsible for maintaining sufficient balance to support the full daily payment. Other entities transfer funds to primary as needed. 2. Proportional multi-entity debit. Daily debit splits across entity accounts based on a pre-agreed proportion (often by revenue weighting). Each entity bears proportional daily-debit load. 3. Cascading fallback debit. Primary debit pulls from primary entity; if NSF, secondary debit pulls from designated backup entity; tertiary if needed. Reduces NSF risk by spreading collection across multiple potential payment sources.

The strategic insight — when aggregation is the right approach. Five scenarios: 1. Total capital need exceeds single-entity capacity. When the merchant needs $300K+ but no single entity qualifies for more than $75-100K standalone, aggregation is necessary. 2. Cross-entity cash flow allows shared payment burden. Stronger entities can support weaker entities' shares of payment — improves overall capacity. 3. Newer entity needs financing. Aggregating a new entity into financing structure based on the older entities' established profiles allows the new entity to access capital it couldn't get standalone. 4. Tier-pricing unlock. Total advance scale jumps a pricing tier; aggregation captures meaningful per-dollar savings. 5. Operational simplification. Single MCA relationship across 5-10 entities is operationally simpler than 5-10 separate MCAs with separate funders.

The strategic insight — when aggregation creates risk. Five scenarios where aggregation makes things worse: 1. One weak entity dragging down the rest. If one entity is genuinely struggling, aggregation extends its risk to healthy entities through cross-guarantees. Single-entity default could cascade. 2. Funder concentration risk for merchant. All eggs in one funder basket; if relationship deteriorates or funder operationally fails, all entities affected. 3. Cross-default acceleration. Most aggregated contracts include cross-default clauses — default on one entity's portion triggers default on all. Single bad month at one location could trigger total acceleration. 4. UCC complications for future financing. UCC filings on all aggregated entities make future single-entity financing harder. Each entity's future borrowing capacity is constrained by the aggregated UCC. 5. Exit complications. Selling one entity becomes complicated when it's encumbered by cross-guarantees on others. May require funder consent or buyout.

The strategic insight — what merchants get wrong. Four common errors: 1. Hiding entity relationships. Owner has 5 restaurants but applies for individual advances at 5 different funders without disclosing common ownership. Funders detect through credit bureau data, then declare cross-default across all when discovered. Disclose upfront. 2. Underestimating cross-guarantee exposure. Owner thinks "the new restaurant is on its own" but signs cross-guarantee that puts profitable existing restaurants at risk for the new one's failure. 3. Treating aggregated debit as separate from individual cash flow. Combined daily debit pulled from one entity's account effectively makes that entity responsible for whole-portfolio cash flow. Plan accordingly. 4. Failing to model recovery scenario. If one entity fails, what happens to the financing? Run that scenario before signing.

The honest framing. Multi-merchant aggregation unlocks larger advances and better pricing for multi-unit operators in 2026 — typically saving 0.05-0.10 on factor rate plus enabling 50-150% larger advance sizes. The trade-off is portfolio-wide risk concentration; cross-guarantees mean any one entity's failure can trigger consequences across all. Operators with stable, geographically-diversified, mature multi-unit portfolios benefit most; operators with one weak entity, recent operational changes, or concentration in volatile geographies should think carefully before pooling risk. The structure is also a strong signal to the funder of merchant sophistication — aggregated structures get top-tier underwriting attention and pricing because they signal a meaningful borrower relationship rather than a one-off small-dollar deal.

Related terms

  • MCA funding amount calculatorMCA funding amount = roughly 80-150% of monthly gross revenue, depending on paper grade, time in business, NSF history, and industry. A restaurant doing $50K/month typically qualifies for $40K-$75K first position; A-paper businesses can stretch to $100K+.
  • Paper grade (A/B/C/D)MCA industry shorthand for merchant credit quality. A-paper qualifies for cheapest factor (1.15–1.28); D-paper is high-risk, factor 1.45+, often declined.
  • Personal guarantee (PG)A clause making the business owner personally liable if the MCA defaults. Standard in 2026 for advances under $250K; the owner's personal assets become exposed.
  • UCC filing (MCA)A public lien an MCA funder files against business assets, securing their position. Triggers credit-report flags and can block future funding from other lenders.

AI agents: this term is available as raw markdown at /llms/glossary/mca-multi-merchant-aggregation.