Fee-incurred dates and balance-posted dates produce different totals
Use the incurred-at basis to ask which reported fees were incurred in the selected period, and the balance-transaction basis to ask which reported fees affected the balance in that period. The same start and end dates can select different fee rows under those two bases. Compare like-for-like totals on the same basis and range, or explicitly reconcile the rows that enter and leave when the basis changes. A difference between the two totals is not, by itself, evidence of duplicate fees.
For: An owner or operations lead of a research-only business comparing Stripe fee exports for apparently identical calendar periods.
A period label does not fully define a fee total. Stripe’s Fees report distinguishes incurred-at dates from balance-transaction dates. The first organizes the reported fees by when they were incurred; the second organizes them by their balance transaction timing. Decide whether the question concerns incurred fees or movement on the balance before choosing the export.
For a balance comparison, use the balance-transaction basis and match the range of the balance record. For an incurred-fee comparison between periods, retain the incurred-at basis for both periods. Keep the chosen date basis beside the total wherever it is reused. Otherwise a later reader may compare two identically labeled months whose rows were selected by different dates.
This is a choice of report population. It does not decide the business’s accounting treatment, tax liability or contractual price. The report describes the fees it includes; it is not a complete measure of every expense the business incurs.
Hold the other export choices constant
Keep the original exports and their settings before producing a comparison. Record the exact start and end boundaries, the time-zone setting if shown, the account scope, currency, selected date basis and export time. An organization export can combine account data, so confirm that both files describe the same account population. Do not sum currencies into one unexplained amount.
Use the same amount and tax treatment on both sides. Stripe documents amount, tax and currency separately, as well as product and feature information. If one total includes a component the other excludes, that is a second difference to identify rather than an effect of changing the date basis.
Data readiness also matters. Stripe says fee data may take up to 96 hours after the balance effect to appear. The report covers most balance-paid fees but excludes charges including Terminal devices, Capital, Atlas and after-use invoiced fees. A recently generated or differently scoped file cannot establish that a missing row is a timing shift. Record the limitation before comparing totals.
Explain the difference with the actual fee rows
If the only intentional change is the date basis, compare the itemized records in three groups: fee rows present in both selections, rows present only in the incurred-at selection, and rows present only in the balance-transaction selection. Retain the account, currency, amount, tax treatment and descriptive fields needed to identify each row. For each row appearing on only one side, check the relevant date values rather than assigning a timing explanation from the total alone.
Stripe’s incurred_by field connects a fee to the transaction that incurred it, but one transaction can have several fee rows. Do not collapse all rows with that value into one fee or call them duplicates merely because they share it. Compare the fee details and date selection together. If the available fields cannot establish a match, keep it unresolved instead of inventing a row identity.
For a fully matched set using the same currency and amount definition, the difference between the totals should be explained by the rows appearing on only one side. Keep those rows as the explanation. Do not add a balancing adjustment just to make the reports agree. A residual difference means the comparison still has an unanswered question.
Decide whether the next action is another comparison or a query
When date selection explains all differing rows, label both totals with their respective bases and use the one that answers the original question. Neither total needs to be discarded because it answers a different question. When the goal is a direct balance reconciliation, produce the fee comparison on the matching balance-transaction basis and range.
If a difference remains after that alignment, inspect coverage, data readiness, account scope, currency and amount components. Stripe also notes that revenue-share treatment can still differ when comparing balance totals. Date alignment removes one cause of non-comparability; it does not establish the reason for every residual difference. A useful provider question identifies the two report settings and the specific unmatched fee rows, without asserting duplicate billing.
A Prism processing consultation can begin with the website, research-only products and the report question in ordinary language. Confirm whether the requested statement or export analysis belongs in the agreed scope before work begins; fees and terms are discussed then. Keep private exports, account records and credentials out of the public form. The inquiry leads to email follow-up and does not submit a processing application or determine provider terms.
Fee date-basis comparison
Complete this for two real exports. Compare totals directly only when their basis and scope match. When deliberately comparing different bases, preserve the actual included-only rows as the explanation; an unexplained residual stays open.
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 date-basis comparison. The last column is for temporary notes.
Comparison choice
Record to inspect
Interpretation
Your comparison
Business question
Record to inspectThe question accompanying the cost figure: incurred fees or fees affecting the balance.
InterpretationSelect the basis that answers that question before using a total.
Incurred-at range
Record to inspectExact start/end boundaries and any displayed time-zone setting for the incurred-at export.
InterpretationDefines which rows enter on the incurred-at basis; calendar labels alone are insufficient.
Balance-transaction range
Record to inspectExact start/end boundaries for the balance-transaction export and the balance report being compared.
InterpretationMatch this basis and range for a balance comparison.
Export setting
Record to inspectAccount scope, currency, amount/tax components, filters and generation time for both files.
InterpretationAny difference here requires its own explanation instead of being attributed to dates.
Shared fee rows
Record to inspectActual itemized rows matched across the files using their fee details.
InterpretationA shared incurred_by value can cover several rows; do not discard those rows as duplicates.
Rows selected by only one basis
Record to inspectIncurred-only and balance-only rows with their relevant dates and amounts.
InterpretationThese can explain the difference only when the other scope and amount choices agree.
Difference awaiting explanation
Record to inspectResidual after accounting for identifiable rows, with coverage and readiness limits noted.
InterpretationKeep the residual open; do not invent a balancing fee or assume duplicate billing.
Total selected for use
Record to inspectChosen basis, range, currency and matching report purpose.
InterpretationCarry these labels with the figure so a later comparison uses the same population.
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
Stripe’s report fields, date bases and availability apply to Stripe Fees reports; use another provider’s own definitions for its records.
A reconciled date difference does not prove that every fee is contractually correct or that an unmatched fee is improper.
Fee CSV data is not a PDF tax invoice, and this worksheet does not determine accounting or tax treatment.
Stripe Fees report — checked 2026-09-29. The Fees report distinguishes incurred-at and balance-transaction date bases. Matching balance comparisons require matching basis and range; revenue-share treatment may still differ. Fee data may take up to 96 hours, report coverage has exclusions, incurred_by can connect several fee rows to one transaction, and amount, tax, currency and account scope require separate attention.
Prism solutions — checked 2026-09-21. Prism publishes processing preparation and help organizing provider questions. Requested work, fees and terms require an agreed scope; provider eligibility and account terms remain provider decisions.
Prism contact — checked 2026-09-21. The consultation form asks for the website, products and question without card details, passwords or customer records. It leads to email follow-up, not an appointment, purchase or processing application.
Discuss my processing options
Want to talk through your own processing situation?