Check whether the fee export is mature enough to reconcile
For Stripe’s Fees report, fee data may take up to 96 hours after the fee affects the balance. Start that check from the fee’s balance-effect date, not the customer’s order date or the time you downloaded the CSV. Also confirm that the fee belongs to the selected account, date basis and period, and is within the report’s coverage. A recent in-scope fee may need a later export; an excluded fee needs a different record. A still-unexplained omission after those checks is a focused provider question, not proof that the fee was waived or charged incorrectly.
For: A research-only merchant or finance operator investigating recent fees that do not appear in a Stripe Fees report export.
Find the actual record showing when the fee affected the Stripe balance. Keep that timestamp and time zone alongside the export’s generation or download time, distinguishing the two if both are available. The documented delay concerns availability of fee data after balance effect. It does not run from the order’s creation, fulfillment, payout or the date someone first noticed the fee.
Compare the export’s timing with that balance event. If the export was obtained inside the documented 96-hour window, preserve it as the version used for the initial comparison and schedule a later export after that window. If you only know when an old file was downloaded, you have not established when its data was generated. Record that uncertainty instead of claiming the report was current.
The phrase up to 96 hours describes Stripe’s report-data timing. It is not a fee reversal deadline, an arrival date for funds or a reporting rule for every provider. If the balance-effect timestamp is missing, obtaining that record is the next step; adding 96 hours to a convenient order date would not answer the question.
A mature export can still use the wrong coverage
Stripe’s Fees report covers most fees paid from the balance. Its documented exclusions include Terminal devices, Capital, Atlas and fees invoiced after use. An excluded invoice will not become an included row merely because you wait longer. Identify how the charge was collected and use the relevant invoice or product record when the Fees report does not cover it.
Next check the selected account and period. Stripe distinguishes incurred-at dates from balance-transaction dates; those bases answer different questions. A fee can fall inside a period under one basis and outside it under the other. Record which basis the export actually uses before searching for the row. A report that includes the payment’s date does not necessarily include the fee’s balance date.
For an organization export, confirm that the account which paid the fee is included and remains identifiable in the chosen output. Keep currency, amount and tax fields distinct. A mismatch between a dashboard total and your CSV calculation may need a separate field or date-basis reconciliation, even when the data is old enough to be available.
Recheck the same question with a later file
When the fee is recent and otherwise in scope, record a specific recheck time after the documented window measured from its balance effect. Obtain a new export using the same intended account, period and date basis, and retain both files with their timestamps. Reopening the original CSV cannot show data that arrived later. If you correct a filter as well, record that change so you do not attribute every difference to data maturity.
Search the itemized data using the available fee and underlying transaction references. Stripe documents incurred_by for transaction reconciliation and notes that a transaction can have multiple fee rows. Compare the relevant rows and their amounts rather than assume one customer payment must produce exactly one fee entry.
Classify the result as now included, outside the selected range, outside documented report coverage, or still unexplained. If the row appears only in the later file with otherwise matching settings, record that observed change; do not invent a technical reason for the lag. If the fee is excluded, record the document that accounts for it instead of continuing the same export retry.
Escalate an omission that remains after the scope checks
For a fee still absent after the maturity window, assemble the balance-event reference, fee amount and currency, chosen date basis, reporting period, export timestamps and the coverage checks you completed. Ask Stripe where that specific fee should appear and whether the selected report is expected to include it. Use its authorized support route for account-specific evidence; avoid circulating entire financial exports when a limited reference answers the question.
Until the discrepancy is explained, keep the relevant reconciliation open. Absence from a report does not make the fee zero, waived or improper. The CSV is also not a PDF tax invoice. A conclusion about pricing, tax or the reason for the discrepancy would need evidence beyond the report’s data-availability rule.
For a Prism processing consultation, summarize the website, research-only products and the report-completeness question without uploading statements or customer records to the public form. Confirm any requested reconciliation assistance, responsibilities, fees and terms before work. Prism’s published support includes processing preparation and provider website questions; the provider decides account terms. The form receives an inquiry followed up by email, not an appointment, purchase or processing application.
Fee-report maturity check
Use one table for a real missing fee or a precisely defined group of fees with the same coverage. Keep original records in your authorized finance system. Work through timing, coverage and selection before choosing a later export or a provider question; a blank date means maturity is not yet established.
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.
Fee-report maturity check. The last column is for temporary notes.
Completeness check
Record to use
What the result changes
Your finding
Fee balance-effect date
Record to useThe actual balance record with time and time zone.
What the result changesProvides the start of Stripe’s up-to-96-hour report-data window; do not substitute the order date.
Export timestamp
Record to useGeneration time where available, download time and the retained file reference.
What the result changesShows which export version was checked and whether its age is actually known.
Included period
Record to useSelected start and end, time zone and incurred-at or balance-transaction basis.
What the result changesDetermines whether the event belongs in this export even after its data is available.
Account selection
Record to useThe account that paid the fee and the export’s account selection or account-preserving records.
What the result changesExcludes a wrong-account search before treating the missing row as a reporting defect.
Known coverage exclusion
Record to useFee product and collection method compared with the documented exclusions.
What the result changesTerminal devices, Capital, Atlas and after-use invoiced fees require their relevant records rather than waiting for this report.
Fee matching reference
Record to useAvailable fee reference and incurred_by association, with separate amount, currency and tax fields.
What the result changesAllows multiple fee rows for the same underlying transaction to be examined without assuming one-to-one correspondence.
Recheck or provider question
Record to useA later export time after the window, or the precise question for an in-scope unresolved omission.
What the result changesChooses a finite next action rather than repeatedly downloading the same immature or unsuitable report.
Later result
Record to useNew file reference, matching filters and whether the fee appears or remains absent.
What the result changesRecords what changed and keeps an unexplained difference open without inventing its cause.
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.
Limits
The timing and coverage described here are for Stripe’s Fees report. Other reports and providers can use different availability rules.
A missing row does not establish fee waiver, a billing error, a tax position or entitlement to a credit.
Use internal references only; do not put card data, credentials, private payment links, full bank details or customer records in this worksheet or the consultation form.
Stripe Fees report — checked 2026-09-29. Data may take up to 96 hours after balance effect. The report covers most balance-paid fees and excludes Terminal devices, Capital, Atlas and after-use invoiced fees. Date bases differ; incurred_by supports transaction reconciliation with multiple fee rows. Organization formats, amount/tax/currency fields and the distinction from a PDF tax invoice matter to scope.
Prism solutions — checked 2026-09-21. Published support includes processing preparation and help with provider website questions. Scope, fees and terms are discussed before work; providers decide eligibility and account terms.
Prism contact — checked 2026-09-21. The form requests the website, products and question and excludes payment card details, passwords and customer records. Follow-up is by email; the request is not an appointment, purchase or processing application.
Discuss my processing options
Want to talk through your own processing situation?