When to pause MCA debits (and how reconciliation actually works)

Pausing MCA debits is one of the most common things owners want to do and one of the most commonly mishandled. Done correctly, a pause buys you 2 to 4 weeks of breathing room to audit contracts and engage counsel without triggering default. Done incorrectly, the same pause accelerates the balance, files a confession of judgment, and freezes your accounts. The difference comes down to whether you use the reconciliation language already in your contract or you simply stop paying. This article walks the right and wrong ways to pause.

TL;DR

• Reconciliation is a contractual right in almost every MCA contract that allows you to request adjustment of the daily debit when actual revenue does not match the projection.
• A documented reconciliation request, with bank statements supporting it, pauses debits without triggering default.
• Bank blocks without a reconciliation request are typically default triggers.
• Lender response to a reconciliation request usually takes 5 to 10 business days.
• A proper pause buys 2 to 4 weeks to audit, engage counsel, and prepare the workout path.
• Pausing without legal cover is the single most expensive form of MCA self-help.

What reconciliation actually is

The reconciliation clause is the legal mechanism in most MCA contracts that allows the merchant to request adjustment of the daily debit when actual revenue does not match the lender's projection. The clause is almost always present because it is what makes the contract structurally a sale of receivables rather than a fixed loan. Without reconciliation language, the contract risks being recharacterized as a usurious loan in jurisdictions that police the distinction.

The clause is rarely used by merchants because it is buried in the contract and the salesperson at funding does not mention it. Most owners do not know they have the right to request adjustment until a relief firm points to the clause. That gap between the legal right and the awareness of the right is where most of the leverage in pre-default MCA work comes from.

How to formally request reconciliation

A reconciliation request is not a phone call. It is a documented written notice with substantive evidence. To do it properly, the request needs to include a few specific elements.

A clear written notice, ideally certified mail or a documented email thread. The notice should reference the specific contract by date and contract number, identify the requesting party clearly, and state explicitly that the merchant is invoking the reconciliation clause.

Supporting financial documentation. Bank statements for the operating account covering 60 to 90 days, ideally tied to processor or POS reports if available. The documentation should show the actual revenue trajectory and how it compares to the assumed revenue at funding. The gap is the substantive basis for the request.

A specific proposed adjustment. The request should not just ask for a pause to zero. It should propose a reasonable adjusted daily debit that fits actual revenue, calculated against the specified percentage in the contract. A request that asks for the adjustment the contract already entitles the merchant to, with documentation, is harder for the lender to refuse than a vague plea.

A clear timeline for lender response. Most contracts specify a response window, typically 5 to 10 business days. If the contract is silent, the request should specify a reasonable response window.

Lender response timelines

Lenders typically respond to a documented reconciliation request within 5 to 10 business days. Responses fall into a few categories.

Granted in full. The lender adjusts the daily debit to the proposed amount. This is rare on a first request but becomes more common when the request is well-documented and the lender sees a credible counterparty on the other side.

Granted in part. The lender adjusts the daily debit to a number between the requested amount and the original amount. This is the most common positive response and is workable for most relief programs.

Refused without substantive response. The lender ignores the request, refuses to acknowledge it, or sends a generic denial. This is the response that produces the most leverage downstream. A refused reconciliation request, properly documented, is a strong piece of evidence in any subsequent settlement negotiation or legal challenge. Lenders that refuse documented reconciliation expose themselves to claims that they are running the contract as a fixed loan rather than a true sale of receivables, which has real legal consequences in many jurisdictions.

Counter with retaliation. Some aggressive lenders respond to a reconciliation request by accelerating the balance, filing a COJ, or threatening UCC enforcement. This response is itself useful evidence of bad faith. It also means the relief path needs to shift from negotiation to legal defense quickly.

What the pause buys you

A documented pause via reconciliation buys 2 to 4 weeks. That window is enough to do a full audit of the contract stack, calculate effective APRs across all contracts, identify procedural defects, engage counsel where needed, and design the workout path. Without the pause, all of that work has to happen while daily debits continue draining the operating account, which makes everything harder and slower.

The pause is not free. Lenders sometimes respond aggressively even to a properly documented request. The expected outcome is some lenders cooperate, some do not, and the response pattern shapes the rest of the program. Knowing in advance which lenders will cooperate and which will not is itself useful information.

The risks

Reconciliation is the right tool but it has risks. Aggressive lenders can interpret a reconciliation request as a precursor to default and file a COJ preemptively. This is rare with well-documented requests but does happen. It is one reason credible relief firms run reconciliation requests in coordination with attorney availability rather than blindly.

Lenders can also reject the request and continue debiting. If the request was well-documented, the rejection is leverage. If the request was poorly documented, the rejection just confirms the lender's right to keep debiting. Documentation matters.

A third risk is timing. A reconciliation request filed mid-program with no follow-through plan is a wasted opportunity. The request should be the first move of a coordinated workout, not an isolated action. Filing it without a plan to act on the response is poor execution.

When bank blocks make sense

Bank blocks (instructing your bank to refuse ACH debits from a specific lender) are sometimes the right move, but the situations are narrower than the "I cannot afford it" framing suggests.

Bank blocks make sense when default is already in play and the merchant is preserving cash to fund a settlement or defense. They make sense when a lender has refused a documented reconciliation request and continued debiting at the original amount. They make sense as part of a coordinated workout where counsel is in place and the legal exposure has been assessed.

Bank blocks do not make sense as a first response. They do not make sense before reconciliation has been formally requested. They do not make sense without legal coverage in place. Used incorrectly, a bank block is a default trigger that accelerates the balance and exposes the merchant to COJ filing.

The right pause is technical and unglamorous

The right way to pause MCA debits is technical, documented, and coordinated. The wrong way is fast and loud and produces accelerations and freezes. Most credible relief firms can pause debits within 5 to 14 days using reconciliation, depending on the lender mix and the documentation available. The pause is not the goal, it is the first step in a sequence that ends with the contracts resolved.

What to do next

If you are considering pausing MCA debits, do not block the bank yet. Pull your contracts, document 60 to 90 days of bank statements, and have a credible firm draft the reconciliation requests with you. Run our free calculators to quantify your stack burden first. The first week of a properly designed pause sets up the entire program. Doing it correctly the first time is materially cheaper than fixing a self-induced default later.