Why a failed payout can look like a normal deposit
A Stripe payout can initially show as paid, then change to failed within 5 business days; bank-return timing can add further delay. A payout appears in the Stripe Dashboard with a status that suggests the money is on its way or already sent. Days go by, and the deposit never shows up on the bank statement you are working from. Later, the record changes and the payout is marked failed. The gap between the first status and the final one is where most of the confusion lives.
Key takeaways
- Treat a paid payout with no bank line as open until you match it or record a confirmed failure.
- Count business days from the date your written rule specifies.
- Record the payout ID, status, date seen and expected deposit date at each check.
This post explains why that gap exists, how to plan your checks, and how to write your reconciliation notes so the next person does not start the search from zero. The advice is written for bookkeepers and operations leads at small accounting firms, but the logic applies to any team that reconciles payouts by hand.
Nothing here replaces your client's own records or your firm's policies. Use it as a working method, and check the current Stripe documentation for any detail that matters to a specific account.
Two records that were never meant to match on the same day
Bank reconciliation exists because two records of the same money rarely agree at every moment. Sage describes the problem this way: "But because of timing differences, processing delays, and occasional errors, these two records don’t always align." ( Sage's guide to bank reconciliation)
For payouts, the two records are the Stripe payout record and the bank statement line. Stripe records when it sent the payout. When funds become available depends on settlement timing, and the client's bank may take additional time after receiving the payout. Those events happen on different clocks. A payout can be real in Stripe's system and still be missing from the bank statement for a while, which is normal, not a sign of a broken process.
This is why a single day's comparison can mislead. If you compare on the day a payout is expected, you may see a gap that closes a few days later. If you compare too late, you may miss a real failure. Set your comparison window in advance, and write it down. For the wider review, see the bank reconciliation checks.
What a payout status is telling you
A payout moves money from Stripe to the bank account connected to the client's Stripe account. The Dashboard shows its status, and that status can change after it first appears. Stripe's payout documentation says so directly: "When a payout fails, the status might initially show as paid, but then change to failed within 5 business days." ( Stripe, Receive payouts)
Read that sentence carefully. The word "paid" is not a final answer. A bookkeeper who marks a payout as settled the moment it shows paid may have to unwind that entry later.
The same page also explains why the failure notice can be slow to arrive: "It can take up to 5 additional business days for your bank to return the payout and inform us that it failed." ( Stripe, Receive payouts) In plain terms, the bank's reply is part of the timing. The delay sits with the bank's processing, not with your firm's records.
So the practical rule is simple. A paid payout with no bank line needs checking before you call it settled or failed. It is open. Keep it open until you can match it or record a confirmed failure.
How the business-day windows stack
Stripe's payout page describes status changes and bank returns separately. These are two different clocks, and Stripe describes the bank-return time as additional, so the two may stack without a fixed combined total.
Do not assume a fixed total. Your count depends on when the payout was sent, which days fall in the window, and when your bank statement period ends. Track the dates you actually see, not a number you guessed.
Counting business days without guessing
Counting is where many teams go wrong. People count calendar days out of habit, or they count from the day they first noticed the payout instead of the day it was sent. Both habits make the window look shorter or longer than it is.
Stripe's payout page includes a sentence about counting business days that is worth reading in full. It says, "If you use business days, the next Monday is day 0." ( Stripe, Receive payouts) Use that sentence as a reminder that the starting day matters. Before you apply it to a specific payout, read the surrounding text on the page, because the rule depends on the context around it.
For your own working notes, record three dates for each payout: the date Stripe shows it, the expected deposit date from the Dashboard, and the date you check the status. Then count business days from the date that fits the rule you are using, and write that rule in the note. A reviewer should be able to repeat your count without asking you.
Setting a comparison window before you start
Most reconciliation problems start with an unspoken assumption about timing. Settle that assumption at the start of each period, and write it at the top of your working file. Decide how many business days you will wait before an unmatched payout moves from open to a closer look. Pick a number that matches the Stripe text you read, not one that matches your firm's convenience. The Stripe page gives its windows in business days, so your window should be counted the same way.
Apply the relevant window consistently for each client's payout timing. If one client's payouts get a longer wait because they are easier to chase, the period will look inconsistent to a reviewer and will be hard to defend. A written rule with documented reasons for exceptions is easier to review than unexplained differences.
Revisit the window when the relevant timing or documentation changes. If Stripe updates its payout documentation, check the new wording and adjust your file. Do not change the window because one payout is inconvenient. That is the kind of change a reviewer will question.
When the money is available is a separate question
Sending a payout and making funds available in the bank are not always the same event. Stripe's page is direct about this: "The time when funds become available depends on your settlement timing, and your bank might take additional time to make the funds available after receiving them." ( Stripe, Receive payouts)
For a bookkeeper, this means the bank statement can lag the payout even when nothing has failed. The bank may have received the payout but not yet made it available, and the line may show up in a later statement period. If you close the month on the statement date alone, you can end up with a client payout that seems missing but is simply in transit.
Build that into your close checklist. Ask whether any payouts from the last few days lack a bank line, and check their timing before deciding how to record them.
Use the Dashboard as your first source
Before you call a payout missing, look at the record that Stripe keeps. Stripe's documentation gives you a direct place to start: "Track a payout: View your payouts and their expected deposit dates in the Dashboard." ( Stripe, Receive payouts)
Make a habit of pulling the payout list for the period you are reconciling. Note the payout ID, amount, status, and expected deposit date. The expected date is useful as a comparison point, but it does not automatically start every timing window. Without it, you are estimating, and estimates are hard to defend when a client asks why an entry changed.
Keep access in mind too. Your firm may not have Dashboard access for every client. If you do not, ask the client to share the payout list or a report you can review. Do not ask for their login details; a read-only report or an export from their own account is enough for matching.
A workflow with 6 reconciliation steps
A written workflow lets a second person pick up your work without guessing. Here is one that works for small firms matching a handful of clients each month.
- Export or list every payout in the period, with its ID, amount, status, and expected deposit date.
- Match each payout to a bank line by amount and date window. Mark matches as closed and note the bank line reference.
- For any payout with no bank line, mark it open, not missing. Write the date you checked and the status you saw.
- Count business days from the date your rule specifies. Use that window to schedule a recheck of open items.
- Recheck the Dashboard status when the window ends. If it has changed to failed, record it as failed and follow your firm's process for reversing or adjusting the earlier entry.
- If the status is still paid and the bank line is still absent after the window, escalate. Check the client's bank details on file, confirm the statement period, and write the findings in the file before you contact anyone.
The steps are short on purpose. The discipline is in the notes. A status you saw on a given day, with a date next to it, is more useful than a conclusion you reached later.
Illustrative example: one open payout
A client payout of 100 shows as paid on a Friday, and no bank line has appeared by the following week. You mark it open and note the payout ID, the status and the date you checked. Your written rule allows 5 business days, so you schedule a recheck for the last day of that window. If the Dashboard now shows failed, record it as failed and adjust the earlier entry rather than deleting it.
Tracking open items across months
Open items need the most care, because they are easy to forget. A payout that is open this month may still be open next month, and a reviewer should be able to see that history without rebuilding it.
Keep a running list of open payouts at the firm level, separate from the monthly reconciliation file. For each item, record the client, payout ID, amount, first date it appeared as open, and the date of each recheck. When an item closes, move it to a closed list with the date and the reason, rather than deleting it. Deleting an open item removes the evidence that you looked for it.
Review the running list at a fixed point in each cycle, such as before the monthly close. Items that are past the comparison window and still unresolved deserve a direct question to whoever owns the client relationship. Items that are still inside the window can wait, but they should be listed so nobody assumes they were overlooked.
What to write in the reconciliation notes
Notes do three jobs: they show what you checked, they show when you checked it, and they show what you decided. For each open payout, write the payout ID, the status and date you saw, the expected deposit date, and the rule you used to count days. If you later changed the entry, write why in one sentence.
Avoid vague notes such as "still pending" or "will check later." They tell the next reader nothing about the window or the date. Instead write something like "Paid as of the check date, no bank line yet, window still open." That is specific enough for anyone to act on.
Also keep a copy of any screenshot or export you relied on, filed with the client's reconciliation. Store it where your firm stores other client records, and keep the file name consistent so it is easy to find during a review.
When a payout really does fail
Sometimes the status does change to failed, and the work shifts from waiting to recording. For a related deposit case, see Failed client deposit: 2 five-business-day windows. Start by confirming the status in the Dashboard on the day you record it, and save a copy of what you saw. The failure is a fact about the payout, and your entry should reflect it.
Next, reverse or adjust the earlier entry according to your firm's process. Do not simply delete the original line. The original entry showed what was recorded at the time, and the adjustment shows what changed and why. A reviewer should be able to follow both.
Finally, check whether the client needs to act. A failed payout may require a conversation about the bank details on file or the account that received it. Keep that conversation factual. Describe the status, the date you saw it, and the next step. Leave the cause to the client's bank or to Stripe if they have stated one.
Common mistakes to avoid
Several errors come up again and again in reconciliation work.
One mistake is netting silently. If a failed payout is offset against a later payout without a note, the next reviewer will not see what happened. Keep each payout as its own line, even when the amounts happen to look like they cancel.
Another is delaying the check. If you wait until the end of a quarter to look at open items, the Dashboard may have changed and you will have less context to explain it. Check open items on a schedule, and record what you saw each time.
How to explain the delay to a client
Clients often ask why their money is not in the bank yet, or why a payout they saw in Stripe changed. Give them a short, accurate answer. Explain the payout's current status, its expected deposit date, and which timing window you are checking.
Send the payout ID and the dates you checked. Clients can use that information to find the payout in their own Dashboard, and it shows you did the work. Avoid promising a specific arrival date beyond what the Dashboard shows as expected. If the expected date has passed and the status is still paid with no bank line, say so plainly and tell them what you will check next.
Closing thoughts
Stripe payouts are easy to match when everything lands on time. The work is in the cases that do not. The bank statement is one record, the Dashboard is another, and your notes are the link that lets a reviewer follow the story.
Start with the habit that costs the least: write down the expected deposit date and the status you see, every time you check. It also makes every later question easier to answer, because the answer is already in the file.
Frequently asked questions
Why does a payout show as paid and then failed?
A Stripe payout can initially show as paid and then change to failed within 5 business days.
How should I count the days?
Count business days from the date your written rule specifies, and write that rule in the note.
What if there is still no bank line after the window?
Keep it open, record the status and date you saw, and escalate as step 6 describes.