Stripe Smart Disputes and QuickBooks: What a Win Costs

Every bookkeeper who has handled a Stripe chargeback learns the same arithmetic. A dispute arrives, Stripe pulls the money and a $15 fee out of your balance, and you decide whether to fight it. Fighting costs another $15, and you get that second $15 back if you win. So contesting is close to free, and a win makes you whole.

Stripe's Smart Disputes fee breaks the second half of that sentence. Under Smart Disputes, winning is the outcome that costs you money, and the cost is a percentage of the sale rather than a flat fee. That changes which disputes are worth fighting, and it changes what a recovered dispute is actually worth once it reaches your books.

If you are reconciling Stripe against QuickBooks by hand every month, start a free trial and let the sync handle the ledger while you handle the disputes.

The three fee lines, as Stripe writes them

Stripe's pricing page lists three separate dispute charges. They stack, and the order matters:

• Dispute received fee. "$15.00 for each dispute you receive."
• Dispute countered fee. "$15.00 for each dispute you respond to manually. You get this fee back for won disputes. You don't get this fee back for lost disputes."
• Smart Disputes fee. "30% of the disputed amount for each dispute you win. There's no Smart Dispute fee for lost disputes. The dispute received fee still applies."

Read the second line closely. The counter fee attaches to disputes you "respond to manually", which is the phrase that separates the two paths. And read the third line twice, because the two halves point in opposite directions from anything else on your Stripe bill: you pay it only when things go well, and it scales with the size of the sale.

The worked example, both ways

Take a $200 charge that gets disputed.

You respond manually and win. The dispute opens, and $215 leaves your balance: the $200 payment plus the $15 received fee. You submit evidence yourself, which adds the $15 countered fee. You win, so the $200 comes back and the countered fee comes back with it. The received fee does not. Net cost of the win: $15.

Smart Disputes responds and wins. The same $215 leaves your balance. You do not respond manually, so there is no countered fee. You win, the $200 comes back, and Stripe bills 30% of the disputed amount, which is $60. Net cost of the win: $75.

You lose, either way. $215 is gone, and there is no Smart Disputes fee, because it only applies to wins.

So Smart Disputes is not insurance against chargebacks. It is a contingency fee on recovery. Stripe is explicit that the outcome is not guaranteed: "We don't guarantee that disputes countered with Smart disputes will be resolved in your favor, because the final decision lies with the issuer. However, we only bill you a Smart Disputes fee if you win."

The only number that decides whether it is worth it

The comparison above makes Smart Disputes look expensive, and that comparison is the wrong one for most businesses. It assumes you would have contested the dispute yourself, assembled good evidence, and won, which also depends on the dispute being one of the categories you can actually win. Stripe's own framing tells you the case it built the product for: Smart Disputes "helps you recover revenue you might otherwise lose to timeouts or incomplete submissions".

That is the real counterfactual at a small company. Disputes arrive on a Tuesday, the person who could answer them is doing something else, the deadline passes, and the dispute is lost by default. Against a timeout, 30% is not a fee on a win you already had. It converts a certain 100% loss into a 70% recovery.

So the number to find before you decide anything is your timeout rate. Pull your last twelve months of disputes and sort them into three piles: contested and won, contested and lost, never answered. If the third pile is large, Smart Disputes is straightforwardly good for you. If the third pile is empty because someone genuinely works every dispute, you are paying 30% for work you already do well, and the flat $15 countered fee is the cheaper path.

Most companies do not know which pile is biggest, which is why the fee gets evaluated on its headline instead of on the business.

How Smart Disputes decides what it can fight

It does not fight everything. Stripe determines eligibility "using multiple factors, including the dispute reason code, payment method, evidence availability, evidence relevance, and cost", and it exposes that decision rather than hiding it.

Through the API, the dispute object carries a smart_disputes.status with three values:

Status	What it means
available	A packet is ready and can be submitted automatically.
requires_evidence	A packet becomes available if you supply the fields listed in recommended_evidence.
unavailable	The dispute is not eligible, and supplying more fields will not change that.

The middle status is the useful one. A dispute sitting at requires_evidence is telling you exactly which fields would make it fightable, in a smart_disputes.recommended_evidence array. Stripe's example is adding a tracking ID, which then lets it pull delivery history and proof of delivery from fulfillment providers on your behalf.

There is also a control over who submits. The intended_submission_method field takes prefer_manual, the default, where "Stripe submits your evidence if you've added any. If you haven't, Stripe submits a Smart Disputes packet (if available)." The alternative is prefer_smart_disputes, where "Stripe combines your evidence with Smart Disputes' generated evidence and submits the strongest possible packet."

Two things follow from that default that are easy to miss. If you add no evidence, a packet goes in on your behalf whether or not you thought about it, because "If you take no action, Smart Disputes submits the packet automatically to make sure you don't miss the opportunity to contest a dispute." And auto-submit is a setting you can turn off in the Dashboard, so this is a decision you can make deliberately rather than discover on an invoice.

One thing Stripe's documentation does not spell out is how a combined packet under prefer_smart_disputes is billed if it wins, given that you contributed evidence to it. If you plan to work disputes that way, confirm the billing treatment in your own Dashboard before you assume it follows either published line.

What the dispute already did to your QuickBooks records

Before the fee question matters, the dispute itself has already moved through your books, and it does not move the way people expect.

Stripe describes the opening sequence plainly: the issuer creates a formal dispute on the card network, "which immediately reverses the payment", and "After that, Stripe debits your balance for the payment amount and dispute fee."

On the QuickBooks side, that arrives as an adjustment balance transaction, and Acodei does not give it a record of its own. Acodei imports adjustments and reverses or adjusts the original entry rather than posting a standalone transaction. Which shape that takes depends on your sync mode. On daily summary accounts the deduction is folded into that day's summary, reducing the net deposit. On real-time accounts, the original sales receipt or payment is voided or removed.

The case that generates support tickets is an invoice. If the disputed charge paid a Stripe invoice, the linked payment in QuickBooks is deleted, and the invoice reopens as unpaid. That is expected behaviour after a chargeback, not a sync failure, and it is worth telling whoever watches your receivables before they see it for the first time.

The full journal-entry treatment of a chargeback covers which accounts to debit and how to reverse the entry when a dispute goes your way. What matters here is the step that comes after.

The manual step that Smart Disputes makes routine

Acodei does not automatically re-post a won dispute as a new payment. When Stripe returns the funds, you record the payment or mark the invoice paid yourself.

That has always been true, and at most companies it has always been rare, because most disputes that go unanswered are lost. Turn on a product whose entire purpose is winning disputes you would otherwise have lost, and a step that used to come up twice a year starts coming up monthly.

This is the operational consequence that gets missed. Smart Disputes does not just change a fee line. It increases the frequency of a manual reconciliation task that probably lives in one person's head rather than on a checklist. If you enable it, put "re-post recovered disputes" on the month-end close list at the same time.

Where the Smart Disputes fee lands, and what is documented

Here is the honest boundary, and it is worth stating rather than papering over.

Acodei's product documentation does not name Smart Disputes anywhere. There is no documented, Smart-Disputes-specific treatment, so this post will not invent one.

What is documented is the general handling that a fee of this shape falls under, and it is enough to tell you where to look. Stripe fees post in QuickBooks against a product called "Stripe Fees – Acodei", created during onboarding and mapped to an account you choose. That product covers all Stripe fees rather than just per-charge processing, including product fees for things like Billing and Radar. Fees are then split into two categories that route independently: transactional fees, meaning the fee on a charge or refund's own balance transaction, and non-transactional fees, meaning standalone fee balance transactions. Per-account settings send each category either onto daily balance summary line items or into a separate expense.

Non-transactional Stripe fees are the relevant half here, and they are captured when they occur and posted through the daily balance summary even on accounts that sync charges in real time.

So the practical instruction is a specific one rather than a guess: find the date Stripe billed the fee, open the daily balance summary for that date, and see which line it landed on given your own fee settings. If you want these separated from ordinary processing fees, the fee routing settings are where that happens, not a Smart Disputes toggle.

The reporting trap, and it is a real one

Once you are winning disputes through Smart Disputes, "amount recovered" and "cost of disputes" stop agreeing, in a way that a flat $15 fee never caused.

The $200 comes back to your balance on one date, through the reversal of a record Acodei already adjusted. The $60 arrives as a Stripe fee, on a different date, aggregated with every other fee Stripe charged you that day. Nothing connects them in QuickBooks unless you connect them.

Two consequences are worth planning for.

The fee scales with the sale. A $2,000 dispute that you win costs $600. At a flat $15, dispute costs were noise on the P&L and nobody tracked them per case. At 30%, a handful of large recovered disputes is a real number sitting inside your Stripe fee expense, unlabelled.

Resolutions straddle periods. Disputes take weeks. A dispute opened in one month is routinely resolved and billed in the next, so the debit and the recovery and the fee can land in three different places. If you close books monthly, the reversal you are looking for may not exist yet.

The fix is the same discipline the chargeback accounting post recommends for the countered fee: keep dispute-related fees on their own line or class rather than folding them into general processing fees, so you can report actual dispute economics instead of inferring them. That is a mapping decision on your side, and it is much easier to make before the fees start arriving.

What to do this week

1. Count your timeouts. Twelve months of disputes, three piles. This single number decides whether Smart Disputes is a discount or a tax for you.
2. Check your auto-submit setting. Know whether packets are going in on your behalf today. It is in your Dashboard dispute settings either way.
3. Fill in the data fields. Smart Disputes eligibility improves with data. Stripe recommends collecting cardholder name, phone, billing address, email and terms-of-service acceptance at checkout, sending email receipts, and passing shipping carrier and tracking numbers for physical goods. Disputes sitting at requires_evidence are the ones this unlocks.
4. Add the re-post step to your close. Recovered disputes do not restore themselves in QuickBooks.
5. Decide where dispute fees live in your chart of accounts before the first 30% fee arrives, not after.

Frequently asked questions

What is the Stripe Smart Disputes fee?

It is 30% of the disputed amount, charged for each dispute you win through Smart Disputes. Stripe's pricing page states it as "30% of the disputed amount for each dispute you win", and adds that there is no Smart Disputes fee for lost disputes and that the dispute received fee still applies.

Do I pay the Smart Disputes fee if I lose?

No. Stripe charges the Smart Disputes fee only on wins, and states directly that "You incur no Smart Dispute fee on lost disputes." You still lose the disputed amount and the $15 dispute received fee, which is charged regardless of outcome.

Does the $15 dispute fee still apply with Smart Disputes?

Yes. Stripe's pricing page says so explicitly: "The dispute received fee still applies." The fee that Smart Disputes replaces is the $15 countered fee, which attaches to disputes you respond to manually.

Is Smart Disputes cheaper than responding to disputes myself?

It depends entirely on what you would otherwise do. Responding manually costs $15, refunded if you win, so a manually won dispute is cheaper than a Smart Disputes win. But that comparison only holds if you would actually have responded, with good evidence, before the deadline. Against a dispute that would have timed out unanswered, Smart Disputes turns a total loss into a 70% recovery.

Where does the Smart Disputes fee appear in QuickBooks?

Acodei's product documentation does not name Smart Disputes, so there is no documented Smart-Disputes-specific record. What is documented is that Stripe fees post against the "Stripe Fees – Acodei" product mapped to an account you chose at onboarding, that this product covers Stripe product fees and not only per-charge processing fees, and that standalone fee balance transactions are captured through the daily balance summary for the date they occur. Check the daily balance summary for the billing date to see how it landed on your account.

Does winning a dispute restore my QuickBooks records automatically?

No. Acodei does not automatically re-post a won dispute as a new payment. When Stripe returns the funds, you record the payment or mark the invoice paid yourself. Because Smart Disputes is designed to win disputes you would otherwise have lost, this manual step comes up more often once it is enabled.

Why did my invoice reopen as unpaid after a chargeback?

Because that is the designed behaviour. A dispute arrives as an adjustment, and rather than posting a separate record, Acodei reverses the original entry. When the disputed charge paid an invoice, the linked payment is deleted and the invoice returns to unpaid. An open invoice after a chargeback is expected, not a sync error.

Can I turn Smart Disputes off?

Yes. Auto-submit can be disabled in your Dashboard dispute settings, and you can still respond to any dispute manually or accept it before the deadline. The intended_submission_method field gives the same control through the API.

The short version

Smart Disputes is a contingency fee, not insurance. It costs 30% of the disputed amount, only on wins, on top of a $15 received fee you pay either way. Whether that is a good deal is decided by one number you probably have not measured: how many disputes you currently lose by not answering them.

On the books, remember that the dispute already reversed your original record when it opened, that a win does not restore that record on its own, and that the fee arrives separately from the recovery, on a different date, inside your Stripe fee total. Decide where it should live before the first one lands.

If the reconciliation underneath all of this is still manual, start a free trial and let the Stripe to QuickBooks sync keep the ledger current while you work the disputes that matter.