Stripe Dispute Window and Closed Months

Almost every dispute policy starts from the same number. Card networks give the cardholder 120 days, so a payment older than four months is safe, and a month you closed half a year ago cannot move.

The number is real. Stripe states that card networks typically allow cardholders to initiate disputes within 120 days of the original payment. What gets dropped is the sentence right after it, and the one after that, which together undo the conclusion for an entire class of business.

If you take money now for something that happens later, your dispute window has not started yet.

That is not a technicality. It is the difference between four months of exposure and more than a year of it, on revenue you have already recognised, reported, and in some cases paid tax on. This post works through what Stripe actually documents about dispute timing, and then answers the question that timing raises for anyone who closes months tightly: when a reversal finally lands, which month does it change?

If you would rather Stripe disputes, refunds and payouts arrived in QuickBooks already tied to the records they belong to, start a free trial.

The 120 days is a baseline, not a limit

Stripe's framing is more careful than the policies built on top of it. The complete statement is that card networks typically allow cardholders to initiate disputes within 120 days of the original payment, "but their rules allow more time in some situations."

Then Stripe names the situations: "Certain industries, such as travel or event ticketing, are prone to longer intervals between the original purchase and a dispute."

Two hedges in one paragraph, and both are load-bearing. Typically is not always. Some situations is not none. A policy that reads the first clause and stops has quietly converted a default into a guarantee.

The event-date rule, and who it applies to

Here is the sentence that settles the question, quoted from Stripe's dispute documentation:

Generally, when a customer pays for a future event or service (like a vacation reservation, professional services appointment, or event ticket), the dispute window starts on the event date, not the payment date.

Read it again with your own revenue in mind. The clock does not start when the money arrives. It starts when you deliver.

That covers far more businesses than the three examples suggest. If any of this describes your revenue, your dispute window is not measured from the sale:

Conferences, workshops and ticketed events
Weddings, catering and venue bookings
Courses, camps, cohorts and anything with a start date
Professional services booked in advance or on a retainer beginning later
Travel, tours, retreats and seasonal rentals
Memberships and subscriptions that begin on a future date
Any deposit at all against work you have not done yet

For a business selling a physical product today and shipping it this week, payment date and event date are close enough that the distinction never surfaces. For everyone above, they can be six or nine months apart, and the gap is pure added exposure.

What that looks like with real dates

Take a wedding photographer. On 15 January a client pays a 4,000 dollar deposit against a 20 September wedding.

You do the ordinary thing. The payment syncs, the revenue lands in January, you close January in mid February, and by April the quarter is filed and nobody is looking at that sale any more.

Now apply Stripe's rule. The dispute window starts on 20 September, not 15 January. The typical 120 days runs from there, to roughly 18 January of the following year.

So a payment you booked, closed, reported and moved on from is disputable a full twelve months after it landed in your account. Nothing about that is a Stripe quirk or a failure of your bookkeeping. It is the documented rule, and a policy built on "120 days from the charge" would have written this sale off as safe nine months too early.

The rest of the clock, which stacks on top

Everything above is the window for the cardholder to start a dispute. Once one exists, three further intervals apply, all of them documented by Stripe:

Stage	How long Stripe says it takes
Your window to respond to the issuer	Usually 7 to 21 days, depending on the card network
The issuer evaluating the evidence you sent	Usually 60 to 75 days, depending on the card network
Full lifecycle, initiation to final decision	2 to 3 months

Stripe is explicit that this is not negotiable: you "can't reliably accelerate this timeline, except by accepting the dispute in the Dashboard or API." Accepting is the only fast exit available to you, and it is the one where you lose the money on purpose.

Your own deadline is not a general rule but a per-case date. The Dispute object carries an evidence deadline that Stripe defines as the "date by which evidence must be submitted in order to successfully challenge dispute." Stripe adds a detail worth knowing before you plan around it: that value "will be 0 if the customer's bank or credit card company doesn't allow a response for this particular dispute." Some disputes cannot be contested at all. For those, Stripe says it "immediately closes them as lost as soon as we notify you about them," and you never get to present anything.

Stack the intervals and the totals come out like this. For an ordinary card sale delivered immediately, up to 120 days to initiate plus up to three months to resolve puts a final decision close to seven months after the payment. For the wedding deposit above, the window does not even open for eight months, and a final decision can land more than a year after you recognised the revenue.

Wallets and pay-later methods run a different clock again

Cards are not the only thing in your Stripe balance. Stripe documents local payment methods separately and the numbers are not the same: these "typically allow customers up to 180 days to file a dispute, compared to the 120-day window common for card payments."

Stripe also notes that for these methods the provider decides the dispute rather than a card issuer, that deadlines and evidence requirements vary by provider, and that some of them include an inquiry phase where the issue can be resolved before it becomes a formal dispute.

So "how far back can a chargeback reach" has no single answer. It has at least three:

Roughly 120 days from payment, for an ordinary card sale delivered at once
Roughly 180 days from payment, for many wallet and pay-later methods
120 days from the event date, for anything you sold ahead of delivery

The third one is the one that reaches into closed months, and it is the one nobody has a number for.

Which month actually changes

This is where general dispute advice stops being useful. Everyone knows a chargeback reduces revenue. The question a closed month raises is narrower and much more practical: when the reversal lands, does it change the month of the original sale, or the month you found out?

The answer depends on how your sync is configured, and the two common modes move in opposite directions.

Stripe reports a dispute to your balance as an adjustment, which is its general type for corrections made outside the normal payment flow. Acodei imports adjustments, but it does not post a standalone QuickBooks transaction for them. It reverses or adjusts the original associated entry instead. What that means in practice splits cleanly by mode:

In real-time sync, the original sales receipt or payment is voided or corrected. The record that changes is the January record, so January changes.
In daily summary mode, the adjustment is folded into that day's deposit, where a negative adjustment reduces that day's net deposit. The record that changes is today's, so the current month changes.

Side by side:

	Real-time sync	Daily summary
What gets touched	The original sales receipt or payment	That day's summary deposit
Which period moves	The period the original sale sits in	The current period
Reaches into a prior period	Yes	No
What the books show	The bad sale, undone at source	A net reduction on the day it happened

Neither column is the wrong answer, and it is worth being clear about the trade rather than treating one as a defect. Real-time tells the truth about which sale went bad and keeps the sale and its reversal attached to each other, at the cost of reaching back into a period you had finished with. Daily summary keeps closed months closed and puts the hit in the period you learned about it, at the cost of a deposit line that no longer corresponds to that day's actual sales.

If the disputed charge had paid a synced invoice, the mechanics are different again: the linked payment is deleted and the invoice reopens as unpaid. From the QuickBooks side that looks like an old invoice spontaneously going unpaid, which is exactly what it is.

One thing this post will not tell you is how any of that interacts with a QuickBooks closing date. Acodei's documentation does not cover closing dates or period locks, so if you set one, find out what your own configuration does before you rely on it rather than assuming either outcome.

Winning does not put the money back by itself

There is a tempting way to think about the timing problem, which is that a dispute you expect to win is a temporary blip and therefore not really an accounting event. It is worth removing that idea now.

Acodei does not automatically re-post a won dispute as a new payment. When Stripe returns the funds, you record the recovery yourself by re-collecting the payment or marking the invoice paid. On the invoice path, that reopened invoice stays open until you close it, however the dispute went.

Stripe's own economics point the same way. Winning returns the disputed amount and the dispute countered fee, but Stripe states that unless your contract says otherwise it never returns the dispute received fee. A won dispute is a smaller loss, not a cancelled one. For the full journal-entry treatment of the withdrawal, the fees and the reversal, see Stripe chargeback accounting in QuickBooks.

What to actually hold against this

None of the above argues for a reserve against every sale. It argues for knowing which of your revenue carries a long tail, which for most businesses is a minority of it.

Separate future-dated revenue from delivered revenue. Deposits, prepaid bookings and anything with a service date ahead of the payment date are your exposed set. Everything shipped or delivered at the point of sale runs on the ordinary clock.
Date the exposure from delivery, not the sale. For the exposed set, a sale is not out of range until roughly four months after the event, not four months after the money arrived.
Know which way your own sync moves. If you are on daily summary, a year-old dispute hits the current month and your closed periods are undisturbed. If you are on real-time, the original month is the one that moves, and a closed month can change. That is a question worth answering before it happens rather than during a reconciliation.
Keep the evidence retrievable for as long as the window runs. Shipping records, service documentation, signed agreements and customer correspondence all become useless the moment they are unfindable, and for a future-dated sale that can be eighteen months after the transaction. The fields Stripe actually accepts are worth knowing in advance, and they are covered in Stripe dispute evidence.
Treat the early signals as the real deadline. An inquiry is the stage where a case can still be closed without a dispute fee, and it behaves nothing like a formal chargeback. That distinction is worth reading once, in Stripe dispute inquiries.
Do the monthly close so a late reversal is visible when it lands. A reversal that changes a closed month is only a problem if you find it in an annual review. The Stripe to QuickBooks month end close checklist covers the reconciliation that surfaces it in the month it happens.

Frequently asked questions

How far back can a Stripe chargeback go?

For an ordinary card payment, Stripe states card networks typically allow 120 days from the original payment, though network rules allow longer in some situations. For local payment methods such as wallets and pay-later providers, Stripe puts the typical window at up to 180 days. And when a customer pays for a future event or service, Stripe says the window starts on the event date rather than the payment date, which can push it well past a year from the payment.

Does the Stripe dispute window start at payment or at delivery?

Both, depending on what you sold. Stripe's general rule is 120 days from the original payment. Its stated exception is that when a customer pays for a future event or service, such as a vacation reservation, a professional services appointment or an event ticket, the dispute window starts on the event date. If you take deposits or sell anything scheduled, the second rule is the one that applies to you.

How long does a Stripe dispute take to resolve?

Stripe documents the full lifecycle, from initiation to final decision, as 2 to 3 months. Inside that, you usually have 7 to 21 days to respond depending on the card network, and if you submit evidence the issuer usually takes 60 to 75 days to evaluate it. Stripe states you cannot reliably accelerate the timeline except by accepting the dispute.

Can a Stripe chargeback change a month I have already closed?

It depends on your sync mode. A dispute reaches Acodei as a balance adjustment, and Acodei reverses or adjusts the original record rather than posting a standalone transaction. In real-time sync that means the original sales receipt or payment is voided or corrected, so the original month is what changes. In daily summary mode the adjustment reduces that day's net deposit instead, so the effect lands in the current period and closed months are untouched.

Why is there no chargeback transaction in my QuickBooks?

Because a dispute does not create one. Acodei imports the adjustment but does not post a separate entry for it, so a chargeback appears as the original sale being undone rather than as a new record. If the charge had paid a synced invoice, the linked payment is deleted and the invoice reopens as unpaid. Nothing is missing.

Is the dispute window different for Klarna, PayPal or other wallets?

Yes. Stripe documents local payment methods separately and says they typically allow customers up to 180 days to file a dispute, against the 120-day window common for cards. The provider rather than a card issuer decides the outcome, and Stripe notes that deadlines and evidence requirements vary by provider, with some offering an inquiry phase first.

Can I speed up a Stripe dispute?

Not meaningfully. Stripe states the timeline cannot reliably be accelerated except by accepting the dispute in the Dashboard or API, which resolves it immediately by conceding the money. There is also a category of dispute you cannot respond to at all: where the cardholder's bank does not permit a response, the evidence deadline is returned as 0 and Stripe closes the dispute as lost as soon as it notifies you.

The number worth writing down

The useful output of all this is not a policy. It is one date per exposed sale.

For anything you delivered at the point of payment, the ordinary card clock runs about 120 days and the practical end of the story is roughly seven months out. For anything you sold ahead of delivery, the clock does not start until you deliver, and a January deposit against a September event stays disputable into the following January, with a final decision possible months after that.

Which month absorbs the hit is then a configuration question rather than a mystery. Real-time sync reaches back and changes the original month. Daily summary puts it in the month you found out. Knowing which of those your books do is most of what separates a dispute that is an annoyance from one that reopens a period you had signed off.

Sources for everything above: Stripe's how disputes work documentation for the timing rules and the event-date exception, and the Dispute object reference for the evidence deadline. For the object itself, its statuses and what Stripe debits and when, see Stripe dispute.

If you would rather not find out which month a reversal changed by discovering it during a reconciliation, Acodei syncs Stripe disputes, refunds, fees and payouts into QuickBooks tied to the records they belong to. Start a free trial.

How Far Back the Stripe Dispute Window Reaches