MCA Chargebacks & NSFs: Accounting for Bounced and Reversed Payments

The Payment That Comes Back

In merchant cash advance, collections are the whole game — daily or weekly ACH pulls against a merchant's account. But not every pull clears. Some bounce (NSF — non-sufficient funds), some get returned by the bank, and some get reversed when a merchant disputes them. On a general ledger built for a normal business, these reversals quietly corrupt the numbers: collections look higher than they were, the receivable looks smaller than it is, and a merchant who's actually failing looks current.

Here's how to account for MCA chargebacks and NSFs so the books stay honest — and so you can tell the difference between a one-off bounce and a merchant heading for default.

General guidance for funders, not tax or accounting advice for your situation. Confirm treatment with your accountant.

First: What "Chargeback" Means in MCA

The word gets used loosely. In practice there are three flavors, and they're accounted for the same way:

• NSF (non-sufficient funds): the pull fails because the merchant's account can't cover it.
• ACH return: the bank returns the debit — wrong account, closed account, or a stop-payment.
• Dispute / reversal (a true chargeback): the merchant tells their bank the debit was unauthorized and it's clawed back.

In every case, cash you thought you collected didn't stay collected. The accounting job is to reverse it cleanly.

Recording a Reversed Pull

Say you drafted $500 and it bounces two days later. If you already booked the $500 as a collection — reducing the receivable and recognizing a slice of factor income — you now have to unwind it:

• Reverse the cash — the $500 never really landed.
• Restore the receivable — the RTR you reduced comes back.
• Reverse the factor income you recognized on that pull.

The clean way to handle high volume: book collections net of same-period reversals, and for reversals that cross periods, record a specific reversing entry. What you must not do is leave the original collection standing — that overstates both your cash and your recognized income.

The Metric That Matters: NSF Rate

One bounce is noise. A rising NSF rate on a deal is the earliest signal a merchant is in trouble — usually weeks before a formal default. Track reversals as a percentage of scheduled pulls, by deal. A merchant whose pulls start bouncing repeatedly isn't a collections hiccup; they're a default forming.

Chargebacks in a Syndication

When a deal is syndicated, a reversed pull has to flow back to the participants too. If you already split and remitted the collection, a later reversal means their share was overstated — it has to be clawed back or netted against the next remittance. This is exactly why participant statements must tie to the ledger: a reversal that isn't reflected in the split leaves every downstream statement wrong.

Chargeback vs. Default

The distinction that trips funders up: a chargeback is a failed collection, not automatically a loss. A merchant can NSF once and catch up — don't write off the deal on a bounce. But when the reversals stack up and the merchant stops paying, that's when you move to a bad-debt write-off: clear unearned income first, then write off the cash actually at risk. Confusing the two — writing off on a single NSF, or ignoring a pattern of them — is how a portfolio's real health gets hidden.

The Bottom Line

Reversed pulls are a fact of MCA life; the question is whether your books reflect them. Reverse the cash, restore the RTR, unwind the factor income, flow it through the syndication, and watch the NSF rate as an early-warning gauge. Do that and your collections numbers mean something. Skip it and every metric downstream — yield, defaults, participant returns — is quietly wrong. That's the kind of deal-level rigor we built our practice around.