Displayed fee totals differ from the exported components
First establish that the display and export describe the same fee activity. Keep amount, tax and currency as separate fields, confirm what the displayed total includes, and use the units defined for that specific record. Preserve the export’s original precision before comparing it with the display. Calculate a remainder only after those definitions match. An unexplained difference stays unresolved; it is not evidence of a universal rounding rule or duplicate billing.
For: A research-only merchant comparing a provider’s displayed fee total with the exported components for the same fee activity.
Match the fee activity before comparing its presentation
Record the display’s exact label, account, currency and selected activity alongside the export filename and its filters. This page concerns two presentations of the same fee activity. If the records describe different accounts, periods or date bases, they are not ready for a component comparison. Retain those mismatches as separate questions instead of treating them as rounding.
Stripe’s Fees report provides separate amount, tax and currency fields. It can also contain several fee rows associated with the same transaction through incurred_by. A shared transaction reference therefore does not establish that two rows are duplicates. Preserve the rows and their product or feature descriptions while identifying which ones belong to the displayed total.
The report covers most fees paid from the balance, with documented exclusions, and data may take up to 96 hours after the balance effect to appear. If the export is incomplete for the activity being compared, record that limitation. A missing component is not a zero-valued component.
Establish whether tax is already included
Copy the raw amount and tax fields without combining them. Then locate the definition of the displayed fee: does that particular view describe a fee before tax, a total including tax, or some other grouping? The fact that an export has both columns does not, by itself, justify adding them for every comparison. Check the field definitions and the display’s own explanation before selecting the arithmetic.
Where the records establish that a displayed total includes a separately stated tax component, include that component once using the documented definitions. Where a tax-inclusive amount already includes it, adding tax again would compare a different quantity. If neither the view nor its documentation establishes inclusion, leave the reconstructed total unresolved and ask for that definition.
Keep the tax attached to this provider fee record. It is not automatically the tax the store collected from buyers, and a CSV fee export is not a PDF tax invoice. This comparison identifies a presentation difference; it does not determine tax liability or the correctness of a tax assessment.
Check units and precision at the source
Write the currency code for each value. Do not combine different currencies into one difference or assume that matching currency symbols prove the codes match. Next, establish whether each field is expressed in major units, minor units or another format documented for that export or display. Retain the unmodified source values beside any converted working values.
Stripe documents minor-unit amounts for its API, including zero-decimal currencies and currency-specific exceptions. That API convention is not sufficient evidence that a downloaded fee CSV needs the same conversion. Applying a divide-by-100 rule to every value can create a discrepancy rather than explain one. Use the definition for the actual field and record any conversion explicitly.
Copy the number of decimal places actually shown in the interface and preserve all precision present in the export. If a spreadsheet displays fewer decimals, inspect the underlying imported value as well as its formatting. A sum of displayed, rounded-looking components and a displayed aggregate of original components are different calculations. Do not select one and call it the provider’s rule without documentation.
Keep the remainder visible and ask one precise question
Once component inclusion, units, currency and row scope agree, subtract the reconstructed comparable total from the displayed total and record that sign convention. Keep the calculation traceable to the original fields. A zero difference establishes that this comparison reconciles under those documented definitions; it does not prove the fee matches the contract. A nonzero difference remains the amount requiring explanation.
If precision appears relevant, record the raw values, visible precision and the exact calculation that differs. Ask the provider which aggregation and rounding rules apply to that named display and export. Do not create an adjustment called rounding solely to make the remainder disappear. Duplicate billing requires evidence about the fee records themselves, not merely two numbers that fail to match.
For a Prism processing consultation, summarize the website, research-only products, provider and disputed presentation in ordinary language. Ask whether the requested fee-comparison assistance fits the engagement. Prism’s published work includes processing preparation; scope, fees and terms are discussed before work. Keep full statements and private account records out of the public form. The inquiry receives email follow-up and does not purchase an analysis or submit a processing application.
Fee component comparison
Complete one comparison per currency and defined fee group. Preserve the original export and enter only non-sensitive field values or private-record references. If a definition is missing, leave the calculated total blank and name the missing definition; never force a balancing amount.
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 component comparison. The last column is for temporary notes.
Comparison item
What to copy or establish
Interpretation
Your value or finding
Same fee activity
What to copy or establishDisplay label, report name, account reference, filters and fee-row association.
InterpretationA different row scope must be resolved before arithmetic can reconcile the views.
Export amount field
What to copy or establishExact header, original value, sign and documented inclusion basis.
InterpretationThe label alone does not establish whether another component should be added.
Export tax field
What to copy or establishOriginal tax value and the definition linking it to the amount and displayed total.
InterpretationInclude tax once only when the definitions support that treatment.
Currency and units
What to copy or establishCurrency code and field-specific unit definition for both records.
InterpretationAPI minor-unit rules do not automatically define CSV formatting.
Displayed total and precision
What to copy or establishExact total, decimal places shown and any available description of aggregation.
InterpretationVisible precision is an observation, not a documented rounding algorithm.
Comparable component total
What to copy or establishIncluded row references, unchanged source values and each documented conversion or inclusion step.
InterpretationLeave blank if any prerequisite definition remains unknown.
Unexplained difference
What to copy or establishDisplayed total minus the comparable component total, in one currency and unit.
InterpretationPreserve a nonzero remainder; do not label it rounding or duplicate billing without evidence.
Question that closes the gap
What to copy or establishThe missing inclusion, unit, aggregation or rounding definition for the named view.
InterpretationA precise question lets the provider explain this comparison without inventing a 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
Stripe’s report and API conventions apply to the Stripe records described. Another provider’s export needs its own field definitions.
This comparison supplies no fee formula, universal rounding rule, duplicate-billing finding or tax conclusion.
Do not enter full bank details, card data, passwords, customer records or private account documents into the public consultation form.
Stripe Fees report — checked 2026-09-29. The export separates amount, tax and currency and may contain multiple fee rows associated through incurred_by. Report scope, date basis and availability matter; CSV fee data is not a PDF tax invoice. These facts do not establish the cause of a particular difference.
Stripe supported currencies — checked 2026-09-29. Stripe API amounts use currency minor units with zero-decimal currencies and documented currency-specific exceptions. This does not establish a universal rounding algorithm or the formatting of a particular fee-export field.
Prism solutions — checked 2026-09-21. Public support includes processing preparation, storefront review and help with provider website questions. Requested scope, fees and terms are discussed before work; providers decide account terms.
Prism contact — checked 2026-09-21. The inquiry requests the website, products and question, excludes sensitive payment and customer records, and receives email follow-up. It does not purchase a service or submit a processing application.
Discuss my processing options
Want to talk through your own processing situation?