MCA Stacking: How to Account for Multiple Advances on One Merchant

When One Merchant Has Five Advances

"Stacking" is when a merchant takes a new merchant cash advance while one or more existing advances are still outstanding — often from different funders, sometimes several deep. It's one of the most consequential realities in MCA, and one of the hardest things to keep straight on the books. Each advance has its own funder, its own factor rate, its own daily pull, and its own claim on the same shrinking pool of the merchant's daily revenue.

For a funder, stacking is both a risk to underwrite and an accounting problem to solve. Here's how to keep the books honest when a merchant is stacked.

General guidance for funders, not legal or accounting advice. Positions, priority, and enforceability vary by contract and state — confirm specifics.

Why Stacking Raises the Stakes

When a merchant carries multiple advances, every funder is pulling from the same daily deposits. If the total daily remittances exceed what the business can sustain, something gives — usually the merchant starts bouncing pulls (see chargebacks & NSFs), and the funders furthest down the stack are the most exposed. Position matters: earlier advances generally have first claim on cash flow; later ones absorb the risk.

Each Advance Is Its Own Set of Books

The cardinal rule: never commingle stacked advances. If your shop funds a merchant who already has two other advances, your advance still gets its own:

• Liability / receivable carried at its own RTR,
• Factor income recognized on its own schedule,
• Collection ledger tracking your pulls specifically — not the merchant's total outflow.

You account for your position. What the other funders are owed isn't on your books — but their existence is a risk factor you track, because it directly affects whether you get paid.

Roll Up Exposure by Merchant

When your shop funds the same merchant more than once (stacking your own paper), each advance is still separate — but you also need a merchant-level view: total RTR outstanding across all your advances to that merchant, total daily pull, and combined exposure. This is where a per-deal ledger that rolls up by merchant earns its keep — it's the only way to see that you have $180K of RTR riding on one struggling business across four deals.

Renewals vs. Stacking

Don't confuse the two. A renewal pays off the old advance and replaces it — one position becomes another. Stacking adds a position on top of the existing one — now there are two live advances. Booking a stack as if it were a renewal (netting them) understates your total exposure and hides risk. Book gross: each advance stands on its own.

What Stacking Means for Collections and Defaults

A stacked merchant's cash flow is stretched thin, so:

• Watch the NSF rate closely — stacked merchants bounce first.
• Model defaults conservatively — a stacked position is higher-risk paper, and your reserves should reflect it.
• In a syndication, disclose the stack — participants are sharing that elevated risk.

The Bottom Line

Stacking isn't inherently a problem to account for — it's a discipline. Keep every advance on its own books, roll up exposure by merchant so you can see concentration, never net a stack into a renewal, and price the risk into your reserves. Funders who track stacked positions cleanly see trouble coming; those who blur them find out at default. That's exactly the deal-level tracking our MCA practice — and our software — were built for.