MCA ACH pull mechanics

The daily ACH pull is the operational heart of every MCA. Understanding exactly how it works — entry classes, settlement timing, return windows, NSF mechanics, and the bank's role — is the difference between a merchant who manages their cash flow proactively and one who gets surprised by bounces, fees, and default escalation.

The mechanics — what type of ACH entry is used. MCA pulls are almost always:

1. CCD (Corporate Credit or Debit) entries — the standard business-to-business ACH classification. Allows the originator (the funder) to initiate a debit against the receiver's (merchant's) business account.
2. Authorized via written FRSA + bank authorization form — the merchant signs both the MCA contract and a NACHA-compliant authorization (often a "Voided Check ACH Form") at funding. The funder retains the authorization for the life of the deal and must be able to produce it on demand.
3. Variable amount or fixed amount. Most modern MCAs run fixed daily amounts (e.g., $620/day every business day). Some "true holdback" structures pull a percentage of daily card volume via the processor — different mechanic, covered separately.

The mechanics — the daily timeline. A typical pull on a Tuesday:

• Monday 4-6 PM ET. Funder's ACH operator (often a third-party processor like ACHWorks, Nuvei, or Repay) submits the day's batch to its ODFI (originating bank) for next-day settlement.
• Tuesday 6 AM ET. ODFI submits to the Federal Reserve ACH network.
• Tuesday 8-11 AM ET. Merchant's RDFI (receiving bank) processes the debit against the merchant's account. Most banks post by 11 AM ET; some delay until end-of-day.
• Tuesday end of day. Funds settle to the funder's account.
• Wednesday-Thursday. Return window. If the merchant's bank returns the entry (NSF, account closed, stop payment, unauthorized), the funder is notified within 2 business days.

The mechanics — what happens on a failed pull. If the Tuesday debit returns NSF on Wednesday:

1. Funder's portal flags the bounce automatically. Servicing team receives an alert by Wednesday afternoon.
2. Re-pull policy. Most funders re-attempt the debit Wednesday night for Thursday settlement. Some attempt up to three retries within a week.
3. NSF fee charged to the merchant. Typically $25-100 per bounce, applied to the next successful pull or accumulated as an end-of-deal fee.
4. Bank-side NSF fee. The merchant's own bank typically charges $30-40 per returned ACH. So a single bounce often costs $65-140 between the two sides.
5. Default trigger threshold. Most FRSAs define default as 3-5 consecutive bounced pulls within a rolling 14-30 day window — at which point acceleration, COJ filing, and collections begin.

The mechanics — return codes that matter. NACHA return codes the funder watches for:

• R01 (Insufficient Funds). Standard NSF. Default risk grows with frequency.
• R02 (Account Closed). Major red flag — often indicates the merchant has switched banks to evade pulls. Acceleration almost always follows.
• R08 (Payment Stopped). Stop-payment from merchant. Considered an intentional default; almost always triggers acceleration and litigation.
• R10 (Unauthorized Debit). Merchant has disputed the authorization with their bank. Funder must produce the signed authorization within 60 days or the chargeback stands. Repeated R10s prompt UCC and judgment enforcement.
• R29 (Corporate Customer Advises Not Authorized). Same effect as R10 on commercial accounts.

The strategic insight — what merchants control. Three operational levers:

1. Maintain a buffer account. Keep 5-10 business days of debits ($3-15K depending on deal size) as a floor in the operating account. Eliminates accidental NSFs from timing mismatches.
2. Match pull timing to deposit patterns. Most funders will move the pull from morning to afternoon (or vice versa) on request — useful if customer card-batch deposits land midday.
3. Request a same-day reversal if a legitimate NSF was timing-only. If the bounce was because a deposit landed an hour late, the funder can usually re-initiate same-day rather than waiting 2 days. This avoids the bounce hitting the default counter.

The strategic insight — what merchants must NOT do. Three actions that escalate from "bumpy" to "litigation" almost overnight:

1. Stop payment on the ACH (R08). Treated as intentional breach. Almost always triggers immediate acceleration and COJ.
2. Close the account (R02). Same — treated as evasive intent.
3. Switch banks without disclosing. The funder will eventually find the new account via UCC searches or processor data and serve a writ; meanwhile the missed pulls are racking up default counts.

The honest framing. ACH pull mechanics are the most boring and most consequential part of an MCA. Funders run their portfolios on bounce-rate signal — a clean, predictable pull pattern earns goodwill on renewals, reconciliations, and prepayment discounts. A choppy pull pattern marks the merchant as a workout file and changes every subsequent conversation. The merchant who treats the daily pull as a fixed operating expense — buffered, monitored, never blocked — preserves every form of leverage they have on the deal.

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.
• Daily debit MCA — Daily debit MCA repayment pulls a fixed dollar amount from the merchant's business bank account every business day via ACH until the total factor amount is collected. Most common repayment structure in 2026, replacing card-split funding.
• MCA bounce fee (NSF fee, returned ACH fee) — Fee the funder charges when a daily ACH debit fails for insufficient funds — typically $25-$50 per bounce, on top of the merchant's bank NSF fee. Often triggers default review at 3+ bounces.
• MCA ACH bounce fee — Fee charged by the funder when a scheduled daily ACH debit fails (R01 NSF / R09 uncollected) — typically $25-$50 per event, stacked on top of the merchant's bank NSF fee of $30-$45.
• ACH pull stop payment MCA — When a merchant instructs their bank to block the funder's daily ACH debit — almost always an immediate breach triggering acceleration, COJ filing, and asset enforcement; legally permitted under Reg E but operationally catastrophic for the merchant.
• 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.

AI agents: this term is available as raw markdown at /llms/glossary/mca-ach-pull-mechanics.