What tracking multiple positions actually requires
The math behind an MCA debt schedule — summing debits per position — is a few lines in a spreadsheet. What actually requires work is getting to the point where you know, with confidence, which debits belong to which position in the first place, when no funder's statement tells you that directly.
This guide walks through that process step by step, from the raw bank statement to a documented, source-backed schedule — whether you do it by hand or with a tool that reads the statement for you.
Nothing here assumes a specific bank, a specific number of positions, or a specific level of prior experience — the nine steps that follow work the same way whether you're separating a single second position from a first one you already understand well, or untangling four or five positions on an account you're seeing for the first time.
Why the process matters more than the arithmetic
Two people can total the exact same set of debits and still arrive at different, wrong schedules — because one merged two close-amount positions into one, and the other missed a smaller position entirely by absorbing its debits into a catch-all category. The arithmetic is never the risk. The process that determines which debits get summed together is what decides whether the answer holds up.
That's the reason this guide is organized as nine sequential steps rather than a single grouping instruction — each step exists specifically to catch one of the failure modes that turn a straightforward sum into a wrong one, and skipping a step tends to reintroduce exactly the error that step was there to prevent.
Pull every statement for the full period
Gather the bank statements covering the period you want reconciled — at least two to three months gives enough history to establish a reliable recurring pattern for each position.
If the business has switched banks recently, pull statements from both the old and new account for any month that spans the switch — a position that started before the switch will otherwise look like it began mid-air on the new account, with no visible history behind it.
List every recurring debit you can see by eye first
Do a rough first pass, noting any debit amount that appears more than a few times. This isn't the final grouping — it's a starting list of candidates to refine in the steps that follow.
Resist the urge to sort or group anything yet at this stage — the goal is only to build a complete candidate list. Skipping ahead to grouping before the full list exists is a common way to lock in an early, wrong assumption about how many positions are actually present.
Group debits by weekday cadence
Sort your candidates by which specific days of the week they land on. A position debiting Monday through Friday is a different series from one debiting Monday through Saturday, even if their amounts overlap.
This is usually the single most reliable separating signal in the whole process — two independent positions very rarely share the exact same active weekdays, even when their amounts land close together. If a candidate list feels stuck, re-sorting by weekday first, before touching amounts at all, is often what breaks it open.
Narrow each group by amount range
Within each weekday-cadence group, check whether the amounts form one tight cluster or two separate ones. Two clusters within the same cadence group usually means two positions sharing a similar debit schedule.
Look at the spread, not just the average — a genuinely single position debiting a percentage of sales will still cluster within a coherent band that widens and narrows gradually with revenue, while two blended positions tend to show a visible gap in the middle of the range, with few or no debits landing between the two clusters.
Confirm each group's start date
Find the first debit in each confirmed group. This date matters for two reasons: it lets you order positions by age, and a start date that falls mid-statement is a hint the position may have been taken out more recently than the others.
Note the date precisely rather than approximately — "sometime last quarter" isn't enough detail to later confirm whether a specific position matches a specific funding agreement, and the exact start date is often the single fact a business owner can independently verify against their own records.
Check for a mid-period pattern change
Look for a group whose amount or cadence shifts partway through the statement period — a common sign of a position that switched from a fixed daily debit to a percentage-of-sales structure, not a new, unrelated series starting.
The distinguishing detail is continuity: a genuine mid-period change keeps the same weekday cadence and description text across the shift, just with different amounts on either side of it. A truly new position, by contrast, usually starts with its own distinct weekday pattern from day one, even if its amounts happen to be close to an existing group's.
Set aside what's left over
Once every recurring group is confirmed, the transactions that don't fit any of them should look genuinely irregular — ordinary business expenses, one-off purchases, payroll. If what's left over still shows a pattern, a position has likely been missed.
This step is worth doing deliberately rather than skipping — it's the closest thing to a completeness check the whole process has. A leftover pile that's genuinely irregular is reassuring; a leftover pile with its own visible rhythm to it means step three or four needs another pass before the schedule can be trusted.
Total each position separately
Sum the debits within each confirmed group on its own — never combine two positions' totals into a single figure, even for a summary view, since that's exactly the kind of blending that hides a stacked account's real shape.
If a summary total is genuinely needed for a quick reference, keep the per-position breakdown right next to it rather than replacing it — a single combined figure with no supporting breakdown is exactly the kind of number nobody downstream can independently check.
Document the schedule and its sources
Record each position's date range, amount pattern and total, with a reference back to the statement and page it came from — not just the final numbers, so the schedule can be verified later without redoing the whole process.
Include the date the schedule itself was prepared, and the statement period it covers, directly on the document — a schedule with no as-of date attached ages quietly and can end up being relied on months after it stopped reflecting reality, with nobody noticing until it's pointed out.
Signs a position has been misgrouped
A group's amount range is unusually wide
A single position's natural variation rarely spans more than a modest band — a group ranging from $150 to $400 is more likely two positions blended than one noisy one.
A group has debits on every single weekday with no exceptions, ever
Real-world debiting almost always skips at least an occasional day — a bank holiday, a low-balance skip. A group with zero exceptions across months is worth a second look for whether two similar series got merged.
The leftover pile has a recognizable rhythm
As covered in step seven, this is the clearest sign a position is still hiding in what's supposedly irregular activity.
A position's total doesn't roughly match what the business owner remembers
Not proof of an error on its own, but worth reconciling — a large gap between the documented total and the owner's own recollection deserves a conversation before the schedule is finalized.
When the business uses more than one bank account
Some businesses split operating funds across two accounts — sometimes deliberately, to separate a reserve from day-to-day cash, sometimes as a leftover habit from switching banks without fully consolidating. When that's the case, run the full nine-step process on each account independently first, rather than trying to merge the raw transaction lists together before grouping.
Merging first tends to introduce false pattern matches — a debit in one account and an unrelated one in the other can coincidentally share an amount and weekday, and if you've already combined the transaction lists you lose the account-level context that would otherwise make the mismatch obvious. Grouping each account separately, then comparing the two finished position lists at the end, keeps that context intact.
What columns the working spreadsheet actually needs
| Column | Why it's there |
|---|---|
| Transaction date | Builds the weekday cadence used in step three |
| Amount | Feeds the amount-range narrowing in step four |
| Description as printed | A secondary check when a funder name is legible |
| Candidate group / position label | Your working assignment, revised as grouping firms up |
| Statement source and page | The reference that makes step nine's documentation possible |
Keeping the group label as its own editable column, rather than immediately sorting transactions into separate tabs per position, makes it much easier to revise an early grouping guess as steps five and six surface new evidence — moving a row between tabs is more friction than editing a label, and that friction quietly discourages the corrections that keep the schedule accurate.
Double-checking the finished schedule
Before treating a schedule as final, add every position's debits back together and compare the total against the account's actual total debit activity for the period, net of ordinary business expenses. A schedule that accounts for an implausibly small share of total debits usually means a position was missed in step seven; one that accounts for an implausibly large share usually means ordinary expenses got swept into a position group by mistake.
It's also worth re-running step seven's leftover check one final time after the schedule feels complete — a fresh look with the confirmed positions already in mind sometimes catches a small, low-frequency position that a first pass reasonably treated as noise.
An example, start to finish
A four-month statement for a small restaurant is reviewed. An initial scan suggests one large, noisy daily debit — but grouping by weekday cadence, following the nine steps above in the order described, reveals two distinct series hiding inside what first looked like a single variable position.
| Step | Result |
|---|---|
| Weekday cadence | One series Mon–Fri, one series Mon–Sat |
| Amount range | $220–$260 vs. $180–$310 |
| Start dates | 5 months ago vs. 7 weeks ago |
| Leftover after grouping | Ordinary, irregular business expenses only |
Both figures — the two separated schedules and their supporting statement pages — are handed to the business owner together, confirming for the first time that a second position had been taken out without the bookkeeper being told, and giving both of them a genuinely complete, sourced picture to plan the business's finances from going forward.
A printable checklist
Full statement period gathered
Recurring debit candidates listed
Debits grouped by weekday cadence
Each group narrowed by amount range
Start date confirmed for each position
Mid-period pattern changes checked
Leftover transactions confirmed genuinely irregular
Each position totaled separately and documented
How long each step takes
For someone with a steady routine, most steps move quickly once the statement is in hand — the grouping steps, not the final documentation, typically take the most time. Reading the statement into a structured form once shifts most of that time to a one-minute upload instead of an hour of manual sorting.
Steps three and four together tend to be where most of the manual time actually goes, since they're the steps requiring genuine judgment about ambiguous cases rather than mechanical sorting. Steps one, two, eight and nine are comparatively fast once a routine is established — gathering, listing, summing and recording are all mechanical once the harder grouping decisions have already been made.
Common mistakes worth avoiding
Grouping by amount alone
Two positions with close daily amounts get merged into one, hiding a position entirely.
Missing a weekly-cadence position among daily ones
A weekly debit gets read as an unusually large daily debit instead of its own separate series.
Assuming a mid-period change means a new position
A position that shifted from fixed to percentage-based debiting gets split into two incorrectly.
Not documenting the source for each total
The final schedule can't be verified later without redoing the entire grouping process from scratch.
Working from a single month when more history is available
A single month can genuinely be ambiguous in ways that several consecutive months, viewed together, usually resolve.
How often this actually needs doing
Ideally whenever a new statement period closes, so a new position or a payoff is caught quickly — not only when a refinancing conversation makes it urgent. The later a change is caught, the harder it is to reconstruct exactly when it happened.
A monthly cadence also keeps each individual review small. Letting several months accumulate before the next check means more transactions to sort through at once and a longer stretch of time during which an unnoticed new position could have been taken on, both of which make the eventual catch-up review meaningfully harder than a series of smaller, regular ones would have been.
With tooling vs. by hand
By hand, this process is fully workable — many bookkeepers do exactly this for their clients. What a document-reading tool changes is the grouping step itself: instead of manually sorting hundreds of transactions, the recurring patterns are identified automatically, with anything genuinely ambiguous flagged for a human decision.
The nine steps themselves don't change either way — what changes is how much of each step is mechanical versus manual. Steps one and two stay essentially the same regardless; steps three through six are where automation does the most work, since sorting hundreds of transactions by weekday and amount is exactly the kind of repetitive pattern-matching a document-reading tool handles quickly, leaving the genuinely ambiguous cases for a human to decide.
If this is your first stacked account
Start with the most recent full month, where the patterns are freshest and easiest to confirm, rather than attempting to reconstruct a full year's history at once. One completed month gives you a working pattern to extend backward.
It's also worth accepting, on a first attempt, that the initial grouping may need revision once a second and third month are added — a pattern that looked ambiguous in isolation often resolves cleanly once more history is visible, so treat the first pass as a working draft rather than a final answer.
Who this guide is for
Bookkeepers preparing a client's books, restructuring advisors assessing a business's actual debt load, and business owners trying to understand their own stacked position will all recognize this process — the steps are the same regardless of who performs them.
It's also written to work for someone doing this for the very first time, not just for someone with existing experience separating MCA debt — the nine steps assume no prior familiarity with the account beyond the statements themselves, which is deliberate, since a new bookkeeper or a business owner facing their first stacked account is exactly the audience most likely to need a structured process rather than intuition built from repetition.
Doing this across many months of statements
Each month goes through the same nine steps, and the confirmed patterns from earlier months make later months faster to check — once a position's cadence and range are established, later statements mostly confirm the existing pattern rather than requiring fresh discovery.
Treat each month's pass as a confirmation exercise rather than starting from zero — check that the known positions' debits still fall within their established weekday cadence and amount range, then apply step seven's leftover check to that month specifically, watching for anything new that doesn't match an already-confirmed pattern. That's usually enough to catch a change without re-running the full discovery process every single month.
A short glossary
| Term | Meaning |
|---|---|
| Position | A single merchant cash advance being repaid via recurring debits |
| Stacking | Having two or more positions outstanding at the same time |
| Holdback | The percentage of daily sales debited under a variable-rate advance |
| Factor rate | The multiplier applied to the advance amount to set total payback |
These four terms cover most of what comes up while working through the nine steps — position and stacking describe what's being separated, while holdback and factor rate explain why the daily debits behave the way they do once separated. Knowing the difference between a fixed-amount position and a holdback-based one, in particular, is what makes step four's amount-range narrowing make sense rather than feel arbitrary.
Handing this off to an advisor
A schedule that lives only in one person's spreadsheet, without the underlying reasoning documented, is hard for anyone else to trust or extend. Handing a lender, consolidator or new bookkeeper the schedule alongside the source statements and the grouping logic behind it means they can verify it themselves instead of taking your word for it. See the full overview for how this fits into the rest of the reconciliation.
A good handoff also anticipates the question that comes next, not just the schedule itself — an advisor receiving a stacked account's schedule will almost always ask why a specific debit was grouped where it was, and having that reasoning already documented, rather than having to reconstruct it from memory on a call, is what turns the handoff into a genuinely useful starting point instead of just a set of numbers to re-verify.
