What happens if you miss one MCA payment

What a missed payment actually is on an MCA

Start with the mechanics. A merchant cash advance is the purchase of a slice of your future receivables at a discount. It is not a loan, and its price is a factor rate, not an interest rate. You repay by remitting a fixed amount through an automatic ACH bank debit, usually every business day, about 21 debits in a typical month, or once a week. Our guide on how the daily payment works covers the plumbing. The part that matters today is simple: the funder pulls, and your bank either honors the debit or returns it.

A missed MCA payment is usually not a payment you forgot to send. It is a debit the funder presented on schedule that your bank sent back for insufficient funds, an NSF return in banking terms. Maybe a customer paid a day late, a deposit posted after the debit ran, or the weekend's card revenue had not settled. The funder does not see the reason. It sees a returned item.

Here is the calm center of this article. At many funders, one returned debit is treated as an exception to be managed, not a default to be declared. Returns happen across their portfolios every day. But two things are true at once: common practice is often forgiving, and the paper is often strict. Many agreements define an event of default broadly enough to technically include any missed remittance. What your funder typically does and what your agreement allows are different questions, and this article keeps them separate. One bounce usually starts a clock and a conversation, not a collapse.

The retry: what many funders do with a returned debit

The first thing that commonly happens is mechanical. Many funders re-present a returned debit, meaning they run the same pull again, sometimes within a business day or two, sometimes alongside the next scheduled debit. Others add the missed amount to a later debit so the schedule catches up. Some pause the pulls and call before retrying anything. There is no universal sequence: retry behavior varies funder to funder and is sometimes spelled out in the agreement, so ask directly how yours handles a return.

The retry is the first fork in the road. A covered retry reads, on the funder's screen, like a timing problem that fixed itself. A failed retry starts to read like a revenue problem. So the same-day move that matters most is making sure the account can absorb the re-presented pull, plus the other debits already scheduled around it. A second return teaches the funder more than the first one did, and none of it is good.

The fees: your bank's side and the funder's side

One bounce commonly costs money in two places. Your bank typically charges a returned-item or NSF fee for a debit it sends back, and a failed retry can mean another one. If the account has overdraft coverage, the debit may clear instead, with an overdraft charge in its place. Fee schedules differ, and some banks reverse a first fee if you call and ask, which costs nothing to try.

On the funder's side, many MCA agreements list a returned-payment or NSF fee of their own, usually in the fee schedule or an addendum. Some also carry default fees, which typically apply only once a default is actually declared, not on a single return. Amounts and triggers vary by contract, which is why this article prints no dollar figures for them: the only number that matters is the one in your agreement. Find the fee schedule, read the default section behind it, and ask the funder to point to the exact clause if anything is unclear.

The phone call, and why answering it is the cheap move

Expect to hear from the funder, commonly within a business day or two: a call, an email, or a text from the servicing team. The purpose at this stage is usually operational, not legal: they want to know whether this was a blip or the start of a pattern, and whether the retry will clear. Most funders would rather keep a remittance flowing than push a file toward collections.

Answer it, or better, call before they do. An owner who is reachable and plain about what happened reads as a business managing timing. A returned debit plus an unreachable owner reads like the start of a walk-away, and files tend to move toward escalation on silence, not on a single return. Practices vary, but reachability is the one variable entirely under your control today.

Keep the call simple. What happened, in one honest sentence. When the money will be there. What you are asking for: a specific retry date, a short adjustment, or a reconciliation review if revenue has genuinely dropped. Then confirm whatever was agreed by email, so the understanding exists somewhere other than two memories of a phone call.

Cure periods: the agreement decides, not custom

A cure period is a defined window to fix a missed remittance before it can be treated as an event of default. Some agreements grant one, often tied to written notice from the funder and a set number of days. Many are silent, which means no defined window exists. And some define default, on paper, at the first missed remittance, even where the funder in practice works with merchants well past that point.

No article, including this one, can tell you how long you have. There is no standard grace window across MCA agreements, and any specific number of days you read online describes someone else's contract. Two ways to answer it: read the default and remedies sections of your own agreement, or ask the funder in writing: does my agreement provide a cure period for a returned debit, and what does it require of me. Get the answer in writing too.

If a formal written notice of default arrives, the stage has changed, whatever the phone conversations felt like. Take the paper seriously, respond, and treat it as the moment to have a qualified attorney read your actual agreement. This article is general information, not legal advice.

When one miss becomes a pattern, and a pattern becomes a default

What commonly separates an exception from a declared default is repetition plus communication, not a single event. One return, covered on the retry, with a phone call behind it, tends to stay an exception. Returns that repeat across weeks, retries that keep failing, and an owner who has gone quiet: that is the fact pattern that commonly sits behind a declared default. The declaration is the funder's move under the agreement. Nobody can promise where the line sits, only that repetition moves you toward it and communication moves you away.

Draw one distinction sharply, because funders draw it too. A debit that bounced because revenue was thin is a return. Deliberately blocking the ACH, issuing a stop payment, or closing the account the funder draws from is an affirmative act, and many agreements name those acts directly as events of default. Do not do them while you sort this out. Stopping payments can trigger a declared default and acceleration, a confession of judgment where your agreement contains one and where it is enforceable, UCC lien consequences, and personal-guarantee claims. Legitimate restructuring keeps you in good standing. Our guide on stopping MCA debits legally covers the safe paths, and confession of judgment and MCA agreements explains that clause.

Two reassurances, both hedged because contracts vary. Most MCA personal guarantees are drafted as performance guaranties, meant to reach bad-faith conduct, diverting receivables to a hidden account, closing the business to dodge the agreement, not an honest slow month; read yours rather than assuming. And a single return is not, at most funders, the moment heavy machinery starts. If things escalate to a declared default, that stage has its own sequence and its own playbook, and we cover it in what actually happens in an MCA default.

Reconciliation is the front door; a bounce is the back door

If the debit bounced because revenue genuinely fell, there is a contractual tool built for exactly that, and it is the most useful thing on this page. Many MCA agreements include a reconciliation clause, sometimes called a true-up. The remittance was sized against an estimate of your revenue; reconciliation lets you ask the funder to adjust the debit to match actual revenue for the period, and, done right, to true up anything overcollected. It exists because the product is a purchase of receivables: when the receivables shrink, the remittance is supposed to be able to shrink with them.

Requesting reconciliation is not an admission of failure. It is using the agreement as written, and it differs from a miss in kind: a bounce is the payment failing by accident; reconciliation is the payment resizing by contract. If you read one clause of your agreement this week, make it this one: what the reconciliation section requires, usually a written request with bank statements or processing records, and what the funder is obligated to do in response.

Then follow the procedure exactly and keep the paper. Ask in writing, attach what the clause requires, keep remitting while the request processes, and save every reply. A recent New York appellate ruling made the stakes plain: a merchant who later claims a reconciliation clause was not real must show they actually tried to use it. The paper trail protects you in both directions: with the funder now, and in any dispute later.

The same-day list

Everything above compresses to a short list. The order matters less than doing all of it today:

• Call the funder before they call you. Say what happened in one plain sentence and when the money will be there.
• Ask four questions: was a fee charged on your side; will the debit be re-presented, and when; does my agreement provide a cure period, and what does it require; does my agreement include reconciliation, and how do I invoke it.
• Cover the retry. Move what you can into the account, and check every other debit scheduled this week, any other advance positions, payroll, rent, so the fix does not bounce something else.
• Call your bank. Confirm what was charged and whether the debit was returned or paid into overdraft, and ask whether a first fee can be reversed.
• Document why it happened, for yourself: the late deposit, the slow customer, the seasonal dip. If revenue dropped, that record becomes the backbone of a reconciliation request.
• Confirm everything by email: date, name, what was agreed.
• Do not let a second miss follow. The first is commonly read as an exception; the second begins a pattern. If next week looks like it might repeat, say so on today's call and ask for the adjustment now.

Getting ahead of the next one

One caution first. The tempting same-day fix is a fast new advance to cover the gap, and stacking a second position to protect one debit converts a one-day timing problem into months of a second daily pull. If the remittance itself is the problem, resize it or restructure it. Do not multiply it.

A first bounce is information: the debit and your deposits are not aligned, in timing or in size. Timing fixes are the gentlest. Where the agreement and the funder allow, ask whether the debit can land on a different day or later in the day, after card batches settle and deposits post, or whether the account can move from daily to weekly remittance so pulls land after revenue does. Funders vary, the agreement decides what is on the table, and none of it gets granted if it is never asked.

Size fixes come next. If the remittance is out of proportion to what the business actually clears in a month, run the numbers before the numbers run you. The advance affordability tool shows what share of monthly revenue the debits consume, and if the payments are already heavy, our guide on what to do when daily payments are too high maps the options in order. Reconciliation, again, is the contractual resize for a genuine revenue drop, and it is available before anything bounces, not only after.

If more than one position is pulling from the account, restructuring before the pattern compounds is usually the widest door. Traditional consolidation replaces several advances with one facility and one payment, typically in about 3 to 10 business days. Reverse consolidation deposits capital on a schedule that offsets the existing daily pulls, so the net outflow drops while the old positions pay down, typically in about 3 to 7 business days. Be clear-eyed about both: lower payment, more breathing room, not necessarily less total cost, because stretching a payoff can leave the total repaid the same or more.

If today's bounce has you staring at next week's calendar, get a second set of eyes on the numbers. A review starts with your positions and a few bank statements, no credit pull to start, and nothing about it is an offer of credit: estimates only, actual terms set by underwriting. Start at our MCA relief page or call or text 866-625-4413. The legal line stays bright: this is general information, not legal advice, and once a notice of default, litigation, a judgment, or a frozen account is involved, a qualified attorney reading your actual agreement is the right call.