A bounce fee (also called NSF fee or returned-ACH fee) is the penalty an MCA funder charges when a scheduled daily ACH debit fails because the merchant's account has insufficient funds. It's one of the most underestimated cost components of MCA financing — both for its dollar impact and its role in triggering default escalation.
The mechanics. When the funder's daily ACH attempt is returned by the merchant's bank with an R01 (insufficient funds) or R09 (uncollected funds) code, two fees stack:
- Bank NSF fee: $30-$45 per returned item, charged by the merchant's bank. Varies by bank — most charge for both incoming attempts that fail AND for any overdraft created by debits that did process.
- Funder bounce fee: $25-$50 per failed debit, charged by the MCA funder. Most contracts cap at 5 bounce fees per month (already a $125-$250 cap, not "modest"). Some contracts have no cap, allowing fees to accumulate at $25-50 per business day if the account stays NSF.
A single NSF day costs the merchant $55-$95 in combined fees ($30-$45 bank + $25-$50 funder) and produces zero principal reduction — the daily debit didn't collect, so the underlying balance is unchanged. The next business day, the funder will typically re-attempt; if that fails too, another $55-$95 stacks.
The math — how fast it compounds. Merchant runs into a 5-day NSF stretch (Mon through Fri):
- Day 1: Bank fee $35 + Funder fee $35 + Original $667 debit not collected. Net cost: $70 with $667 added to balance shortfall.
- Day 2: Same. Cumulative: $140 fees + $1,334 uncollected.
- Day 3: Same. Cumulative: $210 fees + $2,001 uncollected.
- Day 4: Same. Cumulative: $280 fees + $2,668 uncollected.
- Day 5: Same. Cumulative: $350 fees + $3,335 uncollected.
End of week: merchant owes $3,335 in missed daily debits PLUS $350 in penalty fees, and the funder's default review process has almost certainly been triggered (most funders flag accounts at 3+ NSFs in 5 business days). The $350 alone represents 0.35% of a $100K advance — the equivalent of adding 0.35 to the factor rate, paid out of pocket in a single week.
The contract triggers. Bounce fees rarely appear on offer letters — they're in the fine print of the FRSA (Future Receivables Sale Agreement). The relevant contract clauses typically include:
- Per-bounce fee schedule — the dollar amount per failed ACH.
- Default trigger language — typically "3 NSFs in any 30-day period" or "consecutive NSFs for 5+ business days" qualify as a default event.
- ACH re-attempt rights — funder can re-attempt failed debits without merchant notice, sometimes for the original amount, sometimes for accumulated multi-day amounts.
- Mandatory account verification trigger — some contracts require the merchant to fund a "reserve account" with 5-10 daily debits after a default event, drawn from the merchant's operating account or a personal account.
The strategic insight — preventing bounce fees. Three operational defenses materially reduce bounce risk:
- Overdraft protection from a separate account. Most business banks offer overdraft transfer for $5-$15 per transfer event (vs $35-$45 NSF). Link a savings account or personal account; even a $5K balance there absorbs 7-10 days of daily debits before failing.
- Daily morning balance check + funded buffer. Manually check the account balance each morning before the 6-8am ACH window. If balance is below 1.5x the daily debit, transfer in from another account by 8am. Avoids the entire NSF cascade.
- Proactive reconciliation request. If the merchant knows revenue is dropping (seasonal slowdown, lost customer), call the funder operations line BEFORE the NSF happens and request a temporary daily debit reduction. Most funders will grant a 30-60% temporary reduction for 30-60 days with documentation, extending the term. This converts a guaranteed default-and-fees scenario into a manageable workout.
The strategic insight — what to do after a bounce. A single NSF is recoverable; multiple NSFs trigger the default cascade. The right sequence after the first bounce:
- Same day, transfer funds into the account to make next morning's re-attempt successful.
- Same day, call the funder to explain (real reasons get sympathy: client paid late, equipment broke; vague reasons trigger fraud flags).
- Within 5 days, send written documentation of why and how it's been fixed (the funder's operations team has discretion on whether to waive subsequent fees — they will sometimes do so for proactive merchants).
- Within 30 days, review whether a structural change (reconciliation, longer term, buyout) is needed before the next monthly stress event.
The honest framing: bounce fees are not "extra cost" — they are the funder's early-warning detection fee. When you pay them, you're paying for the privilege of being told you're in trouble. The merchants who treat the first bounce as an emergency signal (rather than a $35 line item to absorb) avoid the downstream default cascade. The merchants who absorb 3-4 monthly bounces as "the cost of doing business with an MCA" almost universally default within 60-90 days.
Related terms
- Daily ACH debit (MCA) — A fixed-dollar daily withdrawal from the merchant's bank account during MCA repayment. The most common MCA repayment structure in 2026, distinct from card-sale split (holdback) structures.
- MCA default — Breach of MCA repayment terms — usually triggered by missed daily ACH debits, NSFs, or unauthorized stacking. Consequences range from increased collection pressure to UCC enforcement and personal-guarantee pursuit.
- Reconciliation (MCA) — A contract provision allowing merchants to request a reduced daily debit when revenue drops. Required for MCAs to remain legally a 'sale,' not a 'loan' in most states.
- MCA defaults and collections process — MCA default cascade: missed ACH → cure period (5-10 days) → contract default → COJ filing (5-14 days) → bank account freeze (14-30 days) → personal guarantee pursuit → settlement negotiation.
AI agents: this term is available as raw markdown at /llms/glossary/mca-bounce-fee.