An automatic payout includes transactions from earlier periods

Select the payout before selecting sales dates

Start with the actual payout reference, account, currency and payout type. Stripe’s payout reconciliation report associates automatic payouts with their settlement batches. The date range used to select a report is not permission to remove older transactions from the batches it reports. If you first filter the transaction list to a sales week, you may discard part of the very payout you want to explain.

Preserve an unchanged private copy of the relevant export and work from a copy for the comparison. Retain the provider’s transaction references and reported membership. A separate store sales report can help locate an original order, but its creation-date filter does not define which transactions Stripe placed in this payout. This page concerns an automatic payout; Stripe says instant payouts require business reconciliation because it cannot identify their constituent transactions.

Separate the event, availability and arrival dates

For each earlier-dated line, record the original event date as the source labels it and the availability date if the provider record supplies one. Keep time zones and date-field names attached to the entries. Then keep the payout date and its expected bank arrival in separate fields. These dates answer different questions: when activity occurred, when funds were available, which payout included the activity, and when a bank credit was expected.

Stripe sends payouts from available funds. Its payout schedule does not shorten settlement. That distinction explains why a sales-created window is an unreliable substitute for batch membership. It does not identify the particular delay on an unseen transaction. If the record lacks an availability date or does not explain an interval, leave that interval unresolved rather than inventing a country rule, reserve or account restriction.

Expected bank arrival is another reported date, not proof of receipt. Bank posting can take additional time. Whether the bank has received this payout is a separate comparison with the bank record; an earlier sale date alone cannot establish that the payout is late.

Keep the complete batch while isolating the question

Use the report’s amount definitions and currency consistently when comparing its itemized batch with the payout total. Do not compare a gross sales column with a net payout and call the difference an omitted transaction. Keep non-sale lines the batch actually contains, with their original labels, instead of retaining only the entries that resemble store orders.

Mark each questioned older line by its provider reference. Establish whether it is assigned to this payout, whether you have its original event and availability records, and whether its amount was already included in another total you prepared. Being visible in a prior sales report and in this payout report does not establish a duplicate payment: those reports answer different questions. A duplicate needs evidence of duplicate records or movements, not merely two appearances in different reports.

If the batch total still does not match, retain the specific unmatched references and the report settings used. Do not delete an older line or add a balancing figure to force agreement. An unexplained membership or amount is the question to take back to the provider with the payout reference.

Close a date-filter error or escalate a named gap

When the full reported batch explains the payout and the earlier lines have a documented relationship to it, correct the comparison’s date basis and keep the original sales-period view separately. The useful conclusion is that this payout contains those earlier events, not that the sales dates should be rewritten. If membership is clear but availability evidence is missing, record those two findings separately.

For a Prism processing consultation, describe the website, research-only catalog and the payout-report question using a concise summary. Reconciliation assistance requires a confirmed scope, responsibilities, fees and terms. Provider account decisions and payout explanations remain with the provider; an inquiry does not change payout timing or establish processing eligibility. Keep customer exports and full bank details out of the public form. Follow-up is by email.

Automatic payout cohort record

Use one sheet per automatic payout. Repeat the transaction rows in your private records for every questioned older line. Retain the full batch; do not limit it to the sale dates you expected. Record only safe references here.

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.