The debit that looks like one thing but is two
Open a stacked merchant cash advance account's bank statement, and nothing on the page says "stacked." There's no label, no summary line, no warning. What you see instead is a string of daily withdrawals — sometimes two, three or four a day — that, scanned quickly, look like one aggressive but singular repayment schedule rather than several independent ones layered on top of each other.
This article looks at why that layering is so easy to miss, what a real separation actually requires, and how to build the habit of catching it before it becomes a crisis instead of after.
It's written for anyone who might be the one staring at that statement — a business owner, a bookkeeper, an advisor meeting a new client — since the underlying pattern that hides stacking is the same regardless of who's doing the reading.
Why stacking is a recurring problem, not a rare one
Merchant cash advances exist precisely because they're fast — a business under cash pressure can often get funded within days, with far less underwriting friction than a traditional loan. That same speed is what makes stacking common: a business that takes a second advance to cover a gap left by the first one's daily debits rarely pauses to formally reconcile what it already owes before signing the next agreement.
It's also rarely a single reckless decision. More often it's a series of individually reasonable ones — a first advance to cover an equipment purchase, a second months later to smooth out a slow season, a third to bridge a gap while waiting on a large invoice to clear. Each decision makes sense in isolation; it's only the cumulative daily debit load, viewed together, that looks concerning.
Why the visual signature hides so well
A human scanning a printed or PDF statement naturally looks for obvious repetition — the same number, appearing often. Two overlapping recurring series rarely present that way. Instead they blend into a range of similar-but-not-identical numbers that reads, at a glance, as one somewhat variable daily fee rather than two distinct, independently-varying series.
When positions debit a percentage, not a fixed amount
Many MCA agreements debit a fixed percentage of that day's card sales rather than a flat dollar figure — which means a single position's own debits already vary day to day before a second position is even considered. That built-in variability is exactly what makes amount-based pattern matching unreliable and is a major reason stacking is harder to spot than it sounds.
It also means the natural instinct to look for "the" recurring amount — a single number that appears most often — actively works against finding a percentage-based position. There often isn't one dominant number to anchor on; there's a band of numbers that tracks the business's own daily sales, rising on a strong day and falling on a slow one, which is a fundamentally different thing to look for than a fixed figure.
Weekly debits mixed in with daily ones
Not every position debits daily — some funders debit weekly, at a proportionally larger amount. A weekly debit landing on the same day as several smaller daily debits from other positions can look, at a glance, like an unusually large single-day charge rather than its own separate, less-frequent series.
When two funders size an advance the same way
Funders often size a daily debit as a percentage of the business's average monthly revenue. Two different funders, both estimating from similar revenue figures, can independently arrive at daily debit amounts that land within a few dollars of each other — producing exactly the kind of close-amount overlap that makes two positions look like one noisy pattern.
This isn't a coincidence specific to any one funder — it's closer to a structural feature of how the industry prices risk. Sizing based on a percentage of recent revenue is a common, reasonable underwriting practice across many funders, which means two independently-underwritten positions on the same business are, if anything, more likely to land in a similar range than not.
The one tell that usually gives it away
The most reliable signal isn't the amount at all — it's the weekday cadence. Two positions rarely share the exact same set of active days: one might debit Monday through Friday, the other Monday through Saturday, or one might skip a specific day the other doesn't. Isolate the transactions on the day one position skips, and the other position's pattern becomes immediately clear on its own.
It works because weekday cadence is largely a function of each funder's own operational schedule — whether they debit on federal holidays, whether they run weekend batches, whether they skip a specific day for internal processing reasons — and those operational choices are essentially independent across funders. Two positions from different funders converging on the exact same active-day pattern by coincidence is possible but genuinely uncommon, which is what makes this signal hold up as reliably as it does in practice.
The documentation a real check actually needs
| Document | Used to confirm |
|---|---|
| Two to three months of bank statements | Enough history to confirm each position's recurring pattern |
| A rough list of known funders (if any) | A starting point to match against confirmed patterns |
| Prior bookkeeping notes on MCA debt | A baseline to compare against the newly separated schedule |
The most common findings
A smaller position absorbed into 'miscellaneous fees'
Its debits were never separated because they were assumed to be bank charges rather than a distinct advance.
Two close-amount positions read as one noisy pattern
The daily amount range was assumed to be one variable-rate position's normal fluctuation.
A weekly position mistaken for a large daily debit
The interval between occurrences was never checked against the other, genuinely daily positions.
A position that already paid off, still counted as active
The schedule wasn't updated after the position's debits stopped appearing.
What ties these four findings together is that none of them require an unusual or exotic error — each is a perfectly understandable read of the statement by someone scanning it quickly without a structured process behind them. That's exactly why they show up so often: they're not signs of carelessness, they're the predictable result of applying an intuitive read to data that specifically resists intuitive reading.
An example of what a finding looks like
A service business believed it had one MCA position outstanding, based on a bookkeeper's spreadsheet tracking a $340 daily debit. A closer read of three months of statements revealed a second, smaller Saturday-only debit series that had been quietly categorized as a "weekend processing fee."
| Item | Detail |
|---|---|
| Known position | $340/day, Mon–Fri |
| Missed position | $180/week, Saturdays only |
| Root cause | Weekly debit mistaken for a bank fee, never flagged as recurring |
What happens when stacking goes unnoticed
An incomplete debt picture makes every downstream decision worse — a refinancing conversation built on an understated debt figure can fall apart once the lender does its own due diligence, and a business planning cash flow around a partial picture of its obligations can be blindsided when a "miscellaneous" debit turns out to be a real, ongoing repayment.
There's a compounding version of this risk too: a business that doesn't know its true daily debit load is at real risk of taking on yet another position it genuinely can't sustain, simply because nobody had a clear, current total to check the new offer against. Discovering a third or fourth position after the fact is a materially harder position to negotiate from than catching the pattern before it grows further.
Why the cost compounds faster than the count suggests
Each individual MCA position is priced with its own factor rate, applied to its own advance amount — there's no volume discount for holding several at once, and no single blended rate that makes the combined cost easier to reason about. Two positions each carrying a 1.35x factor rate cost exactly what two positions cost; nothing about stacking them together reduces the total.
What does change is the daily cash flow impact, and that's where the real damage tends to show up. A single position debiting 12% of daily sales is manageable for many businesses. Three positions each debiting a similar percentage, all active on the same days, can quietly consume a share of daily revenue that leaves too little to cover payroll, rent or inventory — a math problem that's invisible until someone actually adds the separated positions back together.
How a lender reads a stacked account differently
A lender evaluating a refinance or consolidation request isn't just checking whether stacking exists — they're checking whether the business's own understanding of its position matches what the statements actually show. A business that arrives with a schedule that undercounts its positions, even unintentionally, reads as a bigger risk than one whose schedule is simply incomplete but honestly labeled as a work in progress.
That's part of why a self-prepared, source-documented schedule tends to land better than no schedule at all, even an imperfect one — it signals that the business has actually done the work of understanding its own obligations, rather than waiting for the lender's own diligence to surface the full picture.
Preparing before a lender or advisor asks
The most effective preparation isn't waiting for a refinancing conversation to force the question — it's having a current, separated debt schedule ready before anyone asks for it. A business that can hand over a complete, sourced schedule immediately makes a far better impression in a lending or advisory conversation than one that has to scramble to reconstruct it.
The value of a periodic internal check
A quarterly review of the bank statement's recurring debit patterns — even a quick one — is the simplest way to catch a new or previously-missed position early, before it compounds into a larger surprise. It doesn't need to be exhaustive; confirming that the known positions still match their expected pattern, and that nothing new has appeared, is often enough.
The habit is worth more than the individual check. A business that reviews its statement every quarter builds a running, current picture over time, where each check only has to confirm what changed since the last one. A business that never checks until forced to has to reconstruct the entire history from scratch under whatever deadline forced the question — a materially harder and more error-prone task than the routine version ever was.
Myths worth retiring
"If a position were missing, the bookkeeper would have caught it"
A bookkeeper working from a summary total, not the individual transaction pattern, can easily miss a position absorbed into a catch-all category.
"A high total daily debit means one very expensive position"
It's just as likely to mean two or three ordinary-sized positions stacked together.
"Stacking only happens to businesses in obvious financial distress"
It often happens to businesses managing perfectly ordinary cash flow gaps, one advance at a time, without any single decision looking reckless.
"Once the positions are found, the hard part is over"
Finding and separating the positions is the diagnostic step. Deciding what to actually do about a confirmed stacked position — negotiate, consolidate, refinance — is usually the harder and more consequential part.
The advisor's role once stacking is confirmed
Once a schedule is confirmed, an advisor's value shifts from finding the positions to interpreting what the pattern means for the business's options — whether consolidation, refinancing or a direct negotiation with a specific funder makes the most sense given the confirmed total obligation and each position's terms.
That handoff works best when the schedule the advisor receives is genuinely sourced, not just a summary — an advisor who can trace each position back to specific statement lines can move straight into strategy, while one handed only a set of totals often has to spend part of the engagement re-verifying the underlying numbers before trusting them enough to act on.
One position vs. several
A business with a single MCA position rarely needs this kind of separation exercise at all — one recurring debit is easy to identify on sight. The moment a second position joins, though, the separation task changes shape entirely, and the risk of a manual review missing or merging a position rises sharply with each additional position stacked on top.
The relationship isn't linear, either. Going from one position to two roughly doubles the number of possible pairwise overlaps a reviewer has to check for. Going from three to four more than doubles it again, since every new position has to be checked against every existing one. A business several positions deep is dealing with a meaningfully harder sorting problem than the position count alone suggests.
How long statements should be kept
Keeping at least six to twelve months of statements accessible gives enough history to confirm a position's full lifecycle — from its start date through to a payoff, if it has one — rather than only a partial snapshot that might miss when a position actually began or ended.
This is easy to underestimate the value of until the moment it's needed — a business asked to document a position's full history two years after it started has to either request reissued statements from the bank, which can take time and sometimes carry a fee, or reconstruct the history from incomplete records. Neither is necessary if the statements were simply kept accessible from the start.
A checklist before a debt conversation
At least two to three months of statements gathered
Every recurring debit grouped by weekday cadence and amount range
Leftover transactions confirmed genuinely irregular
Each position's start date and current status confirmed
A documented, sourced schedule ready to share
Any recent payoffs or new advances reflected
How a review typically unfolds
A typical review starts with a rough scan for repeating amounts, followed by grouping by weekday cadence to separate what a rough scan blended together, then a check that everything left over is genuinely irregular. If the leftover transactions still show a pattern, the grouping step is revisited until nothing recurring remains unaccounted for.
The order matters more than it might seem. Starting with amounts before weekday cadence tends to produce more false merges, since amount ranges are the signal most likely to overlap between two genuinely distinct positions. Leading with cadence and using amount as a secondary check, the order described throughout this piece, is the sequence that most consistently avoids that specific failure mode.
Which businesses see this most
Retail, restaurants and other card-sales-heavy businesses see this most often, both because they're common MCA borrowers and because their transaction volume is high enough that a stacked pattern has more room to hide among ordinary daily activity. But any business with more than one MCA position outstanding faces the same underlying separation challenge, regardless of industry.
Service-based businesses with lower transaction counts aren't immune, either — a professional practice or a contractor with fewer, larger daily deposits can still stack two or three positions, and in some ways a low-volume account makes the recurring debits stand out more clearly once someone actually looks, since there's less ordinary transaction noise around them.
Life after a stacking discovery
After confirming a stacked position, the natural next step is deciding what to do with the complete picture — whether that's negotiating directly with a funder, exploring consolidation, or simply building the confirmed schedule into ongoing cash flow planning going forward. Many businesses use the discovery as the moment to establish the periodic review habit they didn't have before.
What might change going forward
MCA underwriting practices continue to evolve, and some funders now check for existing advances before extending a new one, which may reduce how often stacking happens going forward. That doesn't remove the value of being able to independently confirm what's actually outstanding on an account — a documentation habit built around separating recurring patterns remains useful regardless of how underwriting practices shift.
Cross-funder underwriting checks also aren't universal, and even where they exist they typically rely on the applicant disclosing existing advances honestly or on a shared reporting database that not every funder participates in — neither is a guarantee against a determined business taking on a position the underwriting process didn't catch. Reading the bank statement directly remains the one source that can't be worked around by an incomplete disclosure.
In short
MCA stacking is easy to miss because it hides inside ordinary-looking variation on an otherwise unremarkable bank statement, not because anyone is trying to conceal it. Weekday cadence, amount range and consistency — read carefully, together — are what separate a genuinely stacked account from one with a single, somewhat variable position, and the businesses that catch it earliest are consistently the ones that check for it deliberately before a crisis forces the question, rather than only after one already has.
None of the individual signals is exotic — a date, an amount, a day of the week are the same three things any bank statement already prints. What separates a reliable finding from a missed position is simply whether those three signals get read carefully and together, rather than skimmed individually the way a quick glance at a statement naturally does.