Position Requests and Stacking: What ISOs Should Know Before Submitting a File to a Direct Funder
An ISO in Long Island called us on a Tuesday morning with a file he'd already struck out on twice. His client, a contractor in Nassau County, was sitting in 2nd position on a $38,000 advance from six months back and needed $25,000 more to cover materials on a job that paid net-60. Two funders had already passed on the file without much explanation beyond "too many positions." He wanted to know if we'd even look at it before he burned another day shopping it around.
We pulled the bank statements that afternoon. The contractor's daily payment load was manageable relative to deposits, revenue had grown quarter over quarter, and there was nothing in the file that made the deal fundable — it just needed an underwriter willing to actually read it instead of auto-declining on position count alone. We funded $22,000 in 3rd position the next day.
That's the story behind most stacking conversations: not "will a direct funder do 3rd position," but "will someone actually look at the file instead of pattern-matching on the number." This post walks through how we evaluate position requests, what tends to get approved and what doesn't, and how to package a stacked file so it gets a real read instead of a form rejection.
What "position" actually means, and why it matters to underwriting
Position refers to where a given merchant cash advance — or revenue-based advance, if you're working the softer term with a merchant — sits in the repayment queue relative to other active advances against the same business's revenue. A business with one active advance is in "1st position." Take a second advance while the first is still being repaid, and that new advance is in "2nd position." A third makes it "3rd position," and so on.
Every additional position adds a daily or weekly payment obligation on top of the ones already running. That's the whole risk question in a nutshell: does the business generate enough revenue to cover all the payments stacked on top of each other, with enough left over to actually run the business? A file with 4 positions and a payment load eating 35% of daily deposits is a different animal than a file with 2 positions eating 12%.
This is also where we want to be direct with ISOs: we evaluate position requests case by case, not as a standing menu. We're not going to tell you upfront "we do 1st, 2nd, and 3rd as a matter of policy" — what we'll actually fund depends on the specific file: the revenue trend, the existing payment coverage, the industry, and the reason the business needs the money. Some 2nd position files are easy yeses. Some are hard no's. The position number alone doesn't decide it; the underwriter reading the actual bank statements does.
What gets a stacked file approved
Here's what our underwriters are actually looking at when a file comes in with existing positions already on it.
Payment coverage relative to deposits. We look at total daily or weekly payment obligations — existing plus the new request — as a percentage of average daily bank deposits. Once combined payments start running past roughly 15–20% of daily revenue, approval gets harder and the amount we can offer shrinks. Past 25%, most files get declined outright regardless of position number.
Revenue trend, not just revenue level. A business doing $60,000/month that's flat or growing is a very different file than one doing $60,000/month that's down 20% from three months ago. Declining revenue with existing positions already stacked is the single fastest way to a decline.
Time since the last advance. A business that took an advance 30 days ago and is already asking for more, with no clear reason, reads differently than a business that's six months into repayment and needs incremental capital for a specific job or season.
Negative days and NSFs. A handful of negative balance days is common and not automatically disqualifying. A pattern of NSFs clustered around existing payment dates tells us the current stack is already too heavy — adding another position on top of that rarely ends well for the merchant, and we'll say so.
The reason for the request. "We need materials for a signed job" or "payroll gap while we wait on a receivable" underwrites very differently than "general working capital" with no specific use. Specificity helps on every file, but it matters more the deeper into the stack you go.
What disqualifies a stacked file
A few things make a stacked file close to unfundable no matter how it's packaged:
4+ active positions with payment coverage already above 25% of deposits. The business is functioning as a cash-flow pass-through to existing lenders, and a new advance just accelerates the problem.
Revenue that's declined for three or more consecutive months while positions have been added, not paid down.
Under 6 months in business, or under $20,000/month in revenue — this disqualifies a file regardless of position count.
A pattern of daily payment defaults or reversed ACH attempts on an existing position within the last 60 days.
If a file has any of these, a quick call to one of our underwriters before building out the full package will usually tell you in minutes whether it's worth pursuing.
How to package a stacked file so it actually gets read
The single biggest thing that slows down a stacking decision is missing payoff or balance information on the existing positions. Here's what makes a stacked file move fast through underwriting:
3 months of business bank statements, complete — not excerpts, not statements with balances redacted.
A current payoff statement or balance summary for every active position — the remaining balance, the daily or weekly payment amount, and the payment frequency.
A one-line reason for the request — what the money is for and, ideally, the timeline (a job that pays in 45 days, a seasonal inventory buy, a piece of equipment that's down).
Merchant contact information and consent to talk directly, if the file needs a quick clarifying conversation. Files that require three rounds of email back-and-forth through an intermediary take longer than files where we can get a five-minute answer straight from the business owner.
Send that complete package upfront and most stacked files get a same-day answer. Send a partial file and expect a day or two of follow-up requests before underwriting even starts.
Why submitting a stacked file to a direct funder beats shopping it
When a heavily stacked file gets shopped to five or six funders at once, each one runs its own version of the payment-coverage math independently, working from whatever payoff information got passed along — often incomplete or stale by the time it reaches the third or fourth funder in the chain. That's how a fundable file ends up with four declines: not because the numbers don't work, but because nobody in the chain had the full picture.
We underwrite in-house and fund from our own balance sheet, which means the person deciding on your stacked file is the same person you can call to walk through the specifics before you submit. On a borderline stacking decision, that direct access is often the difference between a decline and an approved offer at a lower amount than requested. You can submit a file directly through 501advance.com and get a same-business-day read from an actual underwriter, not a queue.
For ISOs building a pipeline of stacked and tough-to-place files, that direct underwriter relationship compounds. We pay competitive commissions on funded deals, and when a merchant comes back for a renewal, we pay renewal commissions on that business too — you're not starting from zero every time a client needs more capital.
Position: 1st — Typical payment coverage ceiling: Evaluated case by case on the merits of the file — What we need to see: Standard 3 months of statements, use of funds
Position: 2nd — Typical payment coverage ceiling: Up to ~15–20% combined coverage on a healthy, growing file — What we need to see: Statements + payoff/balance on the 1st
Position: 3rd — Typical payment coverage ceiling: Case by case; requires strong revenue trend and specific use of funds — What we need to see: Statements + payoff/balance on all active positions
Position: 4th+ — Typical payment coverage ceiling: Rarely approved; requires an exceptional file — What we need to see: Full payoff history; typically a smaller, targeted amount
Get a stacked file in front of an underwriter today
If you've got a file sitting in 2nd or 3rd position that another funder passed on without much explanation, send us the bank statements and the current payoff balances. We'll give you a straight answer — approved, approved at a lower amount, or declined with the actual reason — usually the same business day. Call (888) 860-6970 or submit through 501advance.com.
Frequently asked questions
Will you always do 1st position on a new client?
We evaluate every position request case by case based on the file — there's no standing policy that guarantees 1st position or any other position as a default. Revenue, industry, and the specific numbers on the bank statements drive the decision.
What's the maximum position you'll fund?
There's no fixed cap we advertise, because it depends entirely on payment coverage and revenue trend. In practice, most approvals we make are in 2nd or 3rd position; 4th and beyond is rare and requires an unusually strong file.
Do you require payoff letters on every existing position?
Yes, or at minimum a current balance and payment schedule for each active advance. Without that, we can't calculate real payment coverage, and the file will sit until we get it.
How fast can a stacked file get funded once it's approved?
Once terms are signed, funding typically happens within 24 hours, the same as a non-stacked file. The extra time in a stacking scenario is almost always in underwriting review, not in wiring the money.
Does a merchant cash advance in 3rd position cost more than one in 1st?
Generally yes — factor rates tend to move up as position and overall payment coverage increase, because the risk profile is different. We'll always give you the specific factor rate on the actual file rather than a general rule.
What if the merchant has an open position with a funder who won't provide a payoff statement?
This happens more than you'd think. A recent bank statement showing the daily debit amount for that position is a workable substitute — it won't have the exact remaining balance, but it's usually enough for us to model payment coverage and give you a preliminary answer while the payoff request is still pending.
Can ISOs submit a stacking file directly, or does it need to go through a portal process first?
Send the bank statements and existing balance information straight to our underwriting team by phone or through 501advance.com. There's no multi-step portal queue slowing down a first look at the file.
Have a stacked file sitting in someone else's decline pile? Send us the bank statements and current payoff balances. Direct underwriter access, same-business-day answer.
Submit a file at 501advance.com → or call (888) 860-6970.
Comments