Four withdrawals a day, one unlabeled account
Ask a bookkeeper what actually makes a stacked merchant cash advance account hard to work with, and the honest answer is rarely the math — a daily debit at a fixed amount is not a complicated pattern on its own. What actually costs time is that a business with three or four simultaneous positions sees all of those debits land in the same account, on the same days, at similar-looking amounts, with nothing on the statement itself saying which withdrawal belongs to which advance.
"MCA stacking" — taking a second, third or fourth advance while earlier ones are still being repaid — is common enough among small businesses under cash pressure that most bookkeepers and accountants who work with retail, restaurant or service-business clients have seen it. What makes it hard isn't the concept; it's that no funder's platform shows you the other funders' debits, and the borrower's own bank statement is the only document that actually contains all of them together.
This page describes how that statement — the borrower's own, not any funder's portal export — is read and separated into individual position ledgers, so the actual debt schedule becomes visible instead of staying buried inside one blended cash-outflow line.
Where an MCA debt schedule actually breaks
A wrong debt schedule is almost never caused by a math error — the daily debit amount is printed right there on the statement. It's caused by misattribution: a debit assigned to the wrong position, or a position missed entirely because its debits looked similar enough to another position's to be merged by mistake. A handful of patterns show up again and again.
Two positions with nearly identical daily amounts
A $412 debit for Position A and a $415 debit for Position B, both landing most weekdays, get manually lumped into one pattern because the difference is easy to miss when scanning a statement by eye.
A new position added mid-statement
A fourth advance starts partway through the period, and its early debits get folded into an existing position's total instead of recognized as a distinct new pattern.
A position that pays off and stops
When a position's debits end, the remaining debits from other positions can look like a changed pattern for the same position, rather than being correctly read as one position closing out.
Weekly debits mixed with daily ones
Some funders debit daily, others weekly on a fixed day — a weekly debit at a larger amount can get mistaken for an unusually large daily debit instead of its own separate cadence.
An ordinary recurring expense read as a position
A weekly payroll processor fee or a recurring vendor payment that happens to fall on similar days gets swept into the MCA total, inflating the apparent debt load.
None of these need a dramatic explanation — they're the ordinary cost of eyeballing a statement with hundreds of lines and trying to sort recurring debits into buckets by hand. Reading every transaction the same way, grouped by its actual recurring pattern rather than a rough visual scan, closes most of this gap simply by removing the manual sorting step where mistakes creep in.
Why this isn't a simple recurring-transaction filter
A basic recurring-transaction filter — the kind that flags a subscription charge — looks for one signal: same amount, roughly the same interval. A stacked MCA account defeats that signal on both counts. The amount for a single position can vary slightly day to day (some MCA agreements debit a percentage of that day's card sales, not a fixed dollar figure), and multiple positions can share almost the same interval, since most MCA debits land on business days only.
Separating positions correctly means looking at the whole recurring shape of each debit series — its typical amount range, which weekdays it actually lands on, and how consistently it repeats — not just matching one number against another. That's a genuinely different, harder problem than flagging a $9.99 subscription that repeats monthly.
What separating positions actually proves
A correctly separated debt schedule shows, for each position: its debit pattern (amount range and weekday cadence), the date range it's been active, and the running total actually paid so far within the statement period. When every debit on the account is accounted for across the separated positions — with only genuinely non-MCA transactions left over — the schedule is proven complete, not because every debit was individually verified against a funding agreement, but because nothing was left unexplained.
That completeness check is what turns a rough guess ("we think we have three advances outstanding") into an evidence-based answer ("here are the three recurring debit patterns on the account, and here is what's left after they're accounted for").
The one document this starts from
Unlike most reconciliation problems, this one has a genuine advantage: everything needed to separate positions is already sitting in a single document the business already has — its own bank statement. There's no need to log into three or four different funder portals, no need to request a payoff letter from each funder just to see the pattern, and no dependency on whether the business still has active login credentials for a funder it's trying to get out from under.
That's also precisely why this is a distinct problem from anything a funder's own platform solves — a funder's servicing portal shows that funder's own debits and nothing else. The bank statement is the only place all of them appear together.
What gets read
Every transaction on the statement — date, amount, description, running balance — is extracted exactly as printed, then grouped into candidate recurring series based on amount range, weekday pattern and consistency. A debit that doesn't clearly belong to a recurring pattern is left in the general transaction list rather than forced into a position it may not belong to.
How it works
Upload the business bank statement
For the period you want reconciled — a single month or several months at once.
Every transaction is read on its own
Date, amount, description and running balance extracted from the statement's own layout.
Recurring debits grouped into candidate positions
Debits sharing an amount range and weekday cadence are clustered into their own series.
Ambiguous debits flagged, not guessed
A debit that could plausibly belong to more than one position is marked for a quick confirmation.
Exported
Excel, CSV or JSON, with every debit tagged to its separated position and its source line.
A stacked account, separated
A small retail business uploads three months of its business checking statement, suspecting it has more MCA debt outstanding than its bookkeeper's spreadsheet shows.
| Result | Detail |
|---|---|
| Statement lines processed | 612 |
| Recurring debit positions found | 3 |
| Total debited across all positions (3 months) | $41,280 |
| Transactions flagged for confirmation | 6 |
The bookkeeper's spreadsheet had tracked two positions. The third — a smaller, weekly-debit advance that started mid-period — had never been entered, because its debits had been quietly absorbed into "miscellaneous fees" on the existing tracking sheet.
What a stacked MCA actually looks like on a statement
A single MCA position typically shows as a debit on most business days — Monday through Friday, sometimes Saturday — at a consistent amount or a consistent percentage of that day's deposits. When a business has stacked two or more positions, the signature is multiple such series running in parallel: two, three or four debits on the same day, each with its own amount range and its own start date, easy to mistake for one noisy pattern if read as a single series.
The clearest tell that stacking is present, rather than one position with an unusually large daily debit, is a consistent gap between two amount clusters — for instance, debits reliably falling either near $300 or near $550, with almost nothing in between — which is what a second, independent recurring series looks like laid on top of the first.
Manual vs. automatic
| Manual | Automatic |
|---|---|
| Statement scanned by eye for repeating amounts | Every transaction read and grouped by pattern automatically |
| A close-amount position pair gets merged by mistake | Distinct weekday cadence and amount range keep positions separate |
| A new mid-period position is missed entirely | A new recurring series is detected as soon as it establishes a pattern |
| Reconciliation effort grows with every added position | Same method applies regardless of how many positions are stacked |
From two positions to five
A business with a single MCA position can usually track it by eye — one debit amount, one weekday pattern, easy to spot on a statement. A business with four or five stacked positions turns the same task into a genuinely hard sorting problem, where the number of ways debits can be plausibly grouped grows quickly and a manual read becomes error-prone exactly when getting it right matters most.
Reading and grouping every transaction the same way, regardless of how many positions are actually present, keeps the effort per statement flat — what changes is only how many candidate groupings need a human confirmation, which stays a small fraction of the total transaction count.
Who uses this
Bookkeepers for small retail and restaurant clients
A stacked account's actual debt schedule, ready before a client meeting.
Turnaround and restructuring advisors
Bank statements read and organized without needing access to every funder's portal.
CPAs preparing a business for refinancing
A clean, sourced debt schedule to hand to a prospective lender or consolidator.
Business owners trying to understand their own debt
The same document-level clarity a professional would produce, without the professional's hourly rate.
Edge cases worth knowing
A position that switches from a fixed daily amount to a percentage-of-sales debit partway through — some funders offer this adjustment on request during a slow season — needs its two phases matched back to the same position rather than read as an ended position and a new, unrelated one starting.
A returned or bounced debit, where an attempted withdrawal fails and shows as a reversal a day or two later, needs to be netted against the position it belongs to rather than counted as a separate, smaller debit that throws off the pattern.
Why a per-position ledger beats a single cash-flow view
A cash-flow summary that only shows total daily outflow is easy to trust until someone asks how many positions are actually outstanding and what each one still owes. Reconstructing that answer later means going back through months of statements and re-sorting every debit by hand under deadline pressure — often exactly when a refinancing conversation is time-sensitive.
Keeping every debit tagged to its separated position, with the source statement line attached, turns that reconstruction from a scramble into a detail that's already sitting in the data, ready the moment someone needs the actual debt schedule.
What this doesn't do
Doesn't tell you the exact remaining balance or factor rate
It shows the debit pattern and totals paid; the original advance amount and factor rate come from each funding agreement, not the bank statement.
Doesn't recommend refinancing, consolidation or any specific action
It surfaces the actual debt schedule clearly — deciding what to do about it is a financial decision that stays with you or your advisor.
Doesn't replace a funder's own payoff statement
For an exact, legally binding payoff figure, you still need to request that directly from the funder — this gives you the pattern to know which funders to ask.
Doesn't give legal or financial advice
Any question about your specific obligations under a merchant cash advance agreement belongs with a financial advisor or attorney, not this tool.
What it does fits in one sentence: turn a bank statement full of similar-looking daily debits into a clear, position-by-position ledger, so the actual debt schedule doesn't have to be reconstructed from memory or guesswork every time someone needs to see it.
Feeding into a refinance or consolidation conversation
A lender or consolidator considering a refinance for a stacked MCA business typically wants to see exactly what's currently outstanding across every position — not a rough estimate. Every document that conversation draws on starts from the same underlying source material this tool reads.
Building the actual refinance proposal — negotiating terms, structuring a payoff sequence — stays a step your advisor or the consolidating lender typically owns. What this tool changes is how much of the underlying legwork, pulling and organizing the current debt picture from bank statements, is already done by the time that conversation starts. See the step-by-step tracking guide for how that process fits together.
Security and privacy
Uploads are encrypted with TLS from end to end.
Processing runs on infrastructure with SOC 2-aligned controls.
Original documents are deleted shortly after processing.
Nothing you upload is ever used to train AI models.
For a bank statement carrying a business's full financial picture, that matters — details are on the security page.