Revenue-share treatment changes a fee-report comparison
Matching dates does not make two reports measure the same fee components. Stripe's Fees report documentation identifies revenue-share treatment as a reason totals can still differ after the date basis and range are aligned. Check how each report includes, excludes or otherwise accounts for revenue share before calling the difference an unexplained charge. Attribute only the amount your records support; leave any residual or unknown treatment unresolved.
For: A research-only merchant comparing actual fee totals from Stripe reports after checking their date ranges.
Preserve the two original exports and write down their report names, account coverage, currency, selected date range and date basis. Stripe distinguishes when a fee was incurred from when it affected the balance. Identical calendar dates selected against different date fields do not establish an aligned comparison.
If that date check is already complete, keep its result with the files and move to report composition. There is no need to keep shifting the period merely to force a match. The question now is whether the totals count the same things. This is narrower than comparing processing costs across months or deciding whether an invoice line matches an agreed price.
Also record when each export was generated. Stripe says Fees report data may take up to 96 hours after a fee affects the balance. A recent export with incomplete data should remain provisional; that possibility must not be silently folded into a revenue-share adjustment.
Find the documented revenue-share treatment
Stripe expressly identifies revenue-share treatment as a potential remaining difference when comparing fee and balance totals, even with matching date basis and range. That establishes a legitimate reporting question. It does not establish that this merchant has revenue share, which report is larger or how much of a particular difference it explains.
For each report, locate its definition of the total being compared and any entry, accompanying explanation or provider response describing revenue share. Record the treatment in the report's own terms. If one report includes a component that the other handles elsewhere, identify the corresponding real entry and its amount. If the documentation or export does not let you identify that treatment, write unknown rather than inserting the difference as an assumed revenue-share amount.
Do not use a pricing percentage or a remembered commercial arrangement to manufacture a balancing entry. A contract can help frame the question, but the comparison needs evidence connecting the report's treatment to the actual period and amount. An unexplained difference is not itself evidence that revenue share exists.
Build a comparison bridge without altering the exports
Keep the original totals intact and create a separate comparison note. Choose and label the direction of the comparison, such as first report total minus second report total, retaining the reports' sign conventions. List each documented difference in scope beside its supporting entry and state whether it increases or decreases that difference. Count each supported amount once.
Use that note to show the original difference, the portion supported by the revenue-share records and the remaining unexplained amount. This is a reconciliation aid, not a new charge or an accounting adjustment to post. If the sign or treatment cannot be established, stop short of calculating an adjusted total. A missing input is not zero.
If the documented revenue-share treatment accounts for the full difference, the records support an explanation of why those report totals differ. They do not establish that every fee matches the agreement. If a residual remains, keep it visible. Stripe's Fees report covers most balance-paid fees and has stated exclusions, including after-use invoiced fees; two differently scoped reports need not become identical after one adjustment.
Ask about the residual, not a presumed extra charge
Prepare a question that names both reports, their aligned basis and range, the relevant currency and account scope, the documented revenue-share treatment and the remaining amount. Ask which report definition or entry explains that residual. If treatment itself is unknown, ask that narrower question first instead of alleging that the provider charged the difference.
For a Prism processing consultation, describe the business, the two report types and the question you cannot resolve. Prism's published role includes processing preparation, storefront review and help with a provider's website questions. Confirm any report-analysis work, responsibilities, fees and terms before it begins. The provider explains its records and account terms. Keep the full exports in an appropriate private channel; the public inquiry asks for the website, products and question and follows up by email without booking work or submitting an application.
Revenue-share comparison record
Use one sheet for two real report totals in one currency and a defined account scope. Preserve the original exports. Document treatment before calculating an adjustment, and leave the residual unknown if the required amount or sign is not 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.
Revenue-share comparison record. The last column is for temporary notes.
Comparison input
Evidence to record
Decision it supports
Your finding
First report basis
Evidence to recordReport name, original total, column definition, currency, account scope and export date.
Decision it supportsDefines the first figure without changing its meaning to match the other report.
Second report basis
Evidence to recordThe same identifying details for the other report, including what its fee total covers.
Decision it supportsShows whether the compared totals have the same scope.
Date alignment
Evidence to recordStart and end dates plus the actual date field used in each export.
Decision it supportsMatching ranges are insufficient if one uses incurred dates and the other balance-effect dates.
Revenue-share treatment
Evidence to recordDefinition or written provider explanation for each report and any identifiable supporting entry.
Decision it supportsDistinguishes a documented treatment difference from an assumed balancing amount.
Supported comparison amount
Evidence to recordActual amount, currency and sign linked to the revenue-share evidence; label the comparison direction.
Decision it supportsShows how much of the original difference the records explain, without assuming a universal formula.
Data completeness
Evidence to recordExport generation dates and any fee activity still within the documented reporting delay.
Decision it supportsKeeps a provisional total separate from a confirmed difference in treatment.
Remaining unexplained amount
Evidence to recordOriginal difference less only documented differences in the chosen comparison direction, or unknown if inputs are missing.
Decision it supportsDefines the remaining report question; it is not automatically an additional fee or an improper charge.
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 revenue-share comparison described here is a documented Stripe reporting issue, not a rule for every provider's statements.
This worksheet does not determine contractual entitlement, tax liability, a fee rate or a credit owed. A Fees report CSV is not a tax invoice.
Do not put full account details, bank details, customer records or payment-card data in the public inquiry or worksheet.
Stripe Fees report — checked 2026-09-29. Fee-incurred and balance-transaction dates differ. Revenue-share treatment can leave different totals even after matching date basis and range. The report has scope exclusions and data may take up to 96 hours after balance effect; these facts do not identify an unseen merchant's discrepancy or tax liability.
Prism solutions — checked 2026-09-21. Public support covers processing preparation, storefront review and provider website questions; scope, fees and terms are discussed before work. Provider eligibility and account terms remain provider decisions.
Prism contact — checked 2026-09-21. The public form requests the website, products and question, excludes payment-card details, passwords and customer records, and receives email follow-up without purchasing work, booking an appointment or submitting an application.
Discuss my processing options
Want to talk through your own processing situation?