Skip ahead to the main page
Partner Huddle
Pages

Stripe Smart Retry windows: 5 options for client fees

Partner Huddle Editorial Team · Published · 11 min read

Choose a Stripe Smart Retry window based on client response time, then set the retry count and plan follow-up before it ends.

Key takeaways

  • Match the retry window to how quickly the client can act.
  • Assign someone to follow up on each unpaid invoice.
  • Plan the next action before automatic retries end.

Someone at your firm has to decide how long to wait, how hard to push, and when to stop. For small accounting firms that bill through Stripe, the most useful place to start is the retry policy, because it decides what happens automatically before anyone has to pick up the phone.

If your firm sends monthly bookkeeping invoices, quarterly tax preparation fees, or payroll service charges, a failed payment means money you planned for is late. Your team wants to collect it without damaging the relationship. The retry setting works quietly in the background, so it is worth understanding before you decide anything else.

Stripe's Smart Retry policy lets you set a limit on retries. You choose how many times Stripe tries again, and you choose the period those tries must fit into. The official documentation says you can set the Smart Retry policy "to retry payment a specific number of times within a time period: 1 week, 2 weeks, 3 weeks, 1 month, or 2 months." The automatic collection guide lays out those options.

Those five periods are the subject of this post. Each section below covers one window: what it suits, where it can go wrong, and how a small firm might think about it. You know your clients better than any default does, so use these notes as starting points rather than rules.

One point before we start. The window is only half of the setup. The number of tries inside the window matters too, because more tries spread over the same period means more chances to catch a payment that has been fixed. Stripe's default is a useful reference point, and we will come back to it.

Window 1: 1 week

A one-week window is the shortest of the five. It fits failures you expect to fix quickly. A common example is a client who has just received a new card from their bank and will update it within a few days. If the retries succeed in that span, your invoice closes fast, your records stay clean, and your team does not have to spend time on it.

The trade-off is time. A week is not much when the fix involves a bank call, a card that has to be reissued, or a finance manager who is out of the office. If the retries end before the client has acted, the invoice comes back to your team with no progress made. You then need your own follow-up, and you have lost the head start the automation gave you.

For a small firm, this window makes the most sense for recurring, low-dollar fees from clients who pay on time most months. When a payment fails for such a client, it is often a one-off, and a short window handles that case neatly. It is a poor match for a client whose payments fail in patterns, or for any balance large enough that a missed payment would strain your cash flow.

Keep one habit regardless of the window: check the invoice status on the day the retries finish, not a week later. A short window makes this easy to forget, because the automation seems to finish so quickly.

Window 2: 2 weeks

Two weeks is the setting Stripe itself recommends. The documentation describes the "recommended default setting" as "8 tries within 2 weeks." That makes it a sensible starting point for most firms, because you are not guessing at a number that the platform has not already considered. The automatic collection guide gives the figure.

Two weeks is long enough for several attempts to spread across the period, and short enough that a failed invoice does not sit open for a month while nobody acts. For many clients, that balance is right. A client who sees a failure notice on a Monday has time to update a card or call the bank before the window ends.

Where two weeks falls short is with slow responders. If your client is slow to read email, or if the decision to pay goes through a manager who meets only twice a month, the window may close before anyone at the client's office has seen the notice. In that case, pair the default with a reminder from your own team on day three or four, so the client has a clear prompt to act while the retries are still running.

The default is a good place to begin, but you can change it. If your review of the first few months shows that most failed invoices close inside a week, you might shorten the window for those clients. If many fail and then succeed late, a longer window may serve you better.

Window 3: 3 weeks

Three weeks sits between the default and the one-month option. It gives a client a little more room to respond than two weeks does, without the long open period that comes with a month or more. It suits clients whose payments run on a predictable internal cycle, such as those who pay bills in batches, rather than those who pay as soon as they see an invoice.

The main risk is the same as with the other windows, but it is more subtle: a longer window keeps the invoice open for longer, and that is easy to forget. Three weeks can feel like a long time to someone busy with client work during tax season or a month-end close. Set a reminder in your calendar for the day the window ends, and write down what you will do if the invoice is still unpaid.

Three weeks is also worth considering when a failure has causes outside the client's control. When the cause is a bank review or a reissued card, the fix can take longer than a few days, and a window that is too short can end the retries before the fix arrives.

For a client who has paid late before but has not been a serious problem, three weeks is a reasonable choice. Keep the rest of your process the same, and watch how it performs.

Window 4: 1 month

A one-month window lines up with how many firms already think about billing. If you invoice monthly, the window covers one full billing cycle. A payment that fails early in the month has the rest of that cycle to be retried. That is a clear, easy-to-explain rule for both your staff and your clients. Review your monthly billing dates alongside the retry window.

The window does create a planning challenge. The next month's invoice can go out while last month's is still open. Clients who see two open invoices may pay the wrong one, or assume one has been paid when it has not. Use invoice descriptions that name the service and the period, such as "March bookkeeping," rather than a generic label.

One month also suits fees that follow a steady calendar, such as quarterly reviews or monthly payroll support for clients with predictable finances. Choose it when the client's cash flow is steady enough that a failure looks like a timing problem rather than a sign of trouble.

Do not let a monthly window become a monthly gap in attention. Some firms set the retry window to a month and then do nothing until the invoice is three months old. Build a small weekly check into the team's routine, so open invoices get looked at before they age.

Window 5: 2 months

Two months is the longest window on the list. It gives a client the most time to fix a problem. It is most useful for larger balances, for clients whose finances move in cycles, and for situations where a quick decision would cause more harm than a slow one.

The cost is that an invoice can stay open for up to two months without a clear outcome. For an accounting firm, that means more reconciliation, a longer list of open receivables, and a higher chance that the client forgets the fee entirely. You will need your own check-in dates during that period, and a clear note about who owns the follow-up.

A longer window is not the same as a safer one. More time does not replace contact with the client. A two-month window with no outreach is just a slow failure. If you use it, pair it with a schedule: an email at the start, a call at the midpoint, and a final decision at the end.

How Smart Retries chooses the timing

Within the window you pick, Stripe decides when to try. The documentation explains that "Using AI, Smart Retries chooses the best times to retry failed payment attempts to increase the chance of successfully paying an invoice." You do not pick the exact times, and that is the point of the feature. The automatic collection guide describes it in full.

Stripe also describes a broader set of help around failed payments: "These include automatically updating your users' saved cards, sending emails when a failed payment occurs, and retrying cards at strategic times." Each of these does a different job. An updated card can fix the cause of a failure. An email tells the client that something went wrong. A well-timed retry is what actually collects the money.

The same guide notes that timing can matter in small ways. It says that "payments made for debit cards in certain countries might be slightly more successful at 12:01 AM in local time zones." That is a detail about timing, not a promise, and it applies only in certain countries. Do not build a schedule around it. Use the window and your own reminders instead.

For a small firm, the practical lesson is that Smart Retries reduces the manual work your team must do on failed payments, but it does not remove the need to contact the client. Automation handles timing. People handle the relationship.

What to do when the retries run out

Once the window closes without payment, the invoice needs a decision. Stripe gives you a status option for past-due invoices: you can mark an invoice as uncollectible when it is past due by 30, 60, or 90 days. Marking an invoice uncollectible is a status change in Stripe. It is not a settlement with the client, and it does not end the conversation about the fee. Read the guide for the exact options.

Before any window closes, decide what your firm will do next. The options usually include a final call, a last notice with a clear deadline, a move of the balance onto the next invoice, or a write-off under your firm's own policy. Write these down, so the team does not have to make the choice from scratch every time.

Be careful with legal and tax details. Whether a fee can be written off, and how that affects your books, depends on your location, your engagement terms, and your accounting method. Ask your firm's accountant or advisor before you adopt a write-off rule. This post does not give that advice.

What to tell your clients

Clients rarely enjoy hearing that a payment failed, so the message matters. Keep it short and specific. Name the invoice, the amount, and the due date. Say what you need them to do, such as update the card on file or contact your office. Avoid wording that sounds like an accusation. Many failures have ordinary causes: a card has expired, a bank flagged a charge, or a monthly spending limit was reached. Use your invoice checks before sending a client bill to review the details you will reference.

Tell clients up front how your firm handles failed payments. A short line in your engagement letter or invoice footer lets them know what to expect, so a reminder does not feel like a surprise. Keep the tone the same from client to client, so your team sounds consistent no matter who sends the message.

Decide who owns each open invoice. One person should follow up on each one, so two team members do not send conflicting reminders on the same day. A shared list with a name and a next-action date next to each open invoice is enough for most small firms.

Illustrative example: planning follow-up

An illustrative balance of 60 dollars remains unpaid after a card failure. The client expects to update the card soon. Your team records who will contact the client, asks for the update while retries continue, and checks the invoice when the window closes. If it remains unpaid, the owner follows the firm's agreed next step. The balance alone does not determine the window; the client's response time and your follow-up plan matter too.

A checklist for your team

Use this list when you set up or review your Stripe retry policy:

  1. Pull a list of clients who pay through Stripe, sorted by how often their payments have failed.
  2. Record the selected retry count alongside the window.
  3. Move clients with repeated failures or slow replies to a longer window, one group at a time.
  4. Add a calendar reminder for the day each window closes.
  5. Send your own reminder before the window ends, not after.
  6. Decide the next step for each open invoice before the window closes.
  7. Review the results every quarter and adjust the groups.

Keep the list short. Your team will follow a simple process more reliably than a detailed one.

What to do today

Open your current retry policy and record its window and retry count. Choose an unpaid invoice, assign its owner, and add the window's closing date to your calendar.

What firms ask about retry windows

Can I choose the exact retry times?

Stripe chooses the retry times within your selected window. Review the policy's retry count and time period together when checking your setup.

Does a longer window guarantee payment?

A longer window does not guarantee payment. Keep a follow-up plan for invoices that remain unpaid when retries end.

Sources