A payout is already scheduled when we plan to close the account

A scheduled transfer can outlast account access

Stripe’s scheduled-payout closure guidance describes two events that can happen at different times: a payout continues, while the access needed to investigate it may end. Closing the account is therefore not a documented way to cancel a scheduled payout. A planned closure date should not be recorded as the date the transfer stops or the money arrives.

Before closure, identify which entries actually have a scheduled payout reference. Copy the status and expected arrival date exactly as shown, with the time you checked them. Keep an expected date distinct from a bank receipt. If a transfer has not yet been matched to an actual bank credit, leave its receipt unresolved even if the account is otherwise ready to close.

Check the balance without losing sight of transfers

Stripe’s separate owner-close balance guidance says an account cannot close while it holds a balance. A negative balance must be brought to zero; a positive balance must be paid out to the bank account on file. For manual payouts, that guidance calls for a payout of the full balance. These are conditions of Stripe’s owner-close flow, not evidence that an already-scheduled transfer reached the bank.

Record the balance and the scheduled-payout list as separate checks. If the balance condition is unmet, resolve that through Stripe’s account process. If the balance permits closure but a listed transfer is still awaiting receipt, retain that transfer on the exit record. Do not infer that no money remains in transit solely from a balance figure.

Preserve evidence someone can retrieve after closure

Export the reports you need while access remains, as Stripe recommends. For each transfer, record the file location, covered period and payout reference so a later investigator can find the relevant entry without the old Dashboard. Confirm that the authorized person responsible for reconciliation can open the saved file. A report saved only behind access scheduled to end leaves the same retrieval problem unresolved.

Use a bank destination label that the business recognizes without copying full account details into the worksheet. Keep the underlying bank and provider records in the business’s protected record system. Add the expected arrival date from the provider record, not a date calculated from a generic payout promise. If a date or destination is missing, record that gap before the owner makes the closure decision.

Assign a person to compare the transfer with the eventual bank record. Their task is to preserve the link between the scheduled reference and the actual outcome. A later bank credit can establish receipt; an export of a scheduled entry only establishes what was scheduled at the time of export.

Make failure follow-up possible before it is needed

Identify the official support route available to the account owner after closure and preserve any existing case reference. If that route or the authority to request a retry is unclear, ask about that specific transfer before closing. Stripe warns that retrying a failed payout can be difficult after Dashboard access is revoked; the guidance does not guarantee a retry route, a recovery date or a successful transfer.

Where the timing is under the owner’s control, an unresolved transfer is a reason to reconsider whether closure should happen yet. The practical decision is whether the remaining uncertainty can be managed with records and an available follow-up route. Completing a worksheet does not resolve the transfer itself.

For a scoped Prism processing consultation, describe the research-only website, the planned owner closure and the record-access question. Any assistance with the old account needs an agreed scope and authorized access; Stripe controls its account process. Scope, responsibilities, fees and terms are discussed before work. The public inquiry receives email follow-up and does not book an appointment, buy a service or submit a processing application.

Scheduled payout exit record

Complete one copy for each genuinely scheduled payout. An expected date remains expected until matched to a bank record. An unreadable export or an unknown follow-up route is an unresolved closure dependency, not a completed check. Use references and storage locations rather than sensitive records.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.