The fee export changed and the finance import stopped matching

Preserve the input before repairing the sheet

Keep the original failing CSV, its export settings and the last working sheet version. If an earlier real export is available, preserve that too. Record the account or organization scope, date range, date basis and export format. Without those details, a difference caused by selecting different data can be mistaken for a column change.

List the actual dependencies on the old fields: header lookups, column positions, category filters, joins, grouped totals and descriptions used in a handoff. Trace the failing result to a particular dependency and an actual source row. Do not edit the only copy of the input or remove an unfamiliar charge to make the sheet balance.

Map the deprecated fields by purpose

Stripe's Fees report documentation marks fee_category as deprecated and directs categorization toward product and suite. Treat that as a change requiring a grouping decision, not proof that every previous category has a single interchangeable new label. Determine which replacement field or combination preserves the question your existing sheet answers, using the actual values in the export.

The documented replacement for balance_transaction_description is fee_description. Update references to the intended fee description only after checking the current header and how the downstream sheet uses that text. A description displayed for readers and a value used as a join key have different dependencies. A familiar-looking phrase is not evidence that it uniquely identifies a fee row.

Record any old category that cannot yet be mapped in an explicit unresolved group. Preserve its original label and amount. Ask the report owner about the precise missing mapping rather than assigning the charge to the nearest familiar category. Deprecation identifies fields to migrate; it does not establish a change in the merchant's contractual prices.

Keep the fee rows and amount fields intact

Stripe documents incurred_by for tracing fees to the transaction that incurred them, and more than one fee row can relate to that transaction. A repair that collapses rows merely because their transaction reference repeats can discard real fees. Preserve the source row detail and use the reference to relate records, not as an assumed unique fee-row identifier.

Keep amount, tax and currency distinct, and keep product and feature classifications distinct. Compare source and imported row counts, retained references and numeric field totals within each currency. Record unmapped rows alongside mapped rows so that a categorization gap cannot silently reduce the imported total. A passing total alone does not show that the categories or individual rows are correct.

If the mapped rows survive but totals still differ, check the report scope before making another schema change. Stripe distinguishes incurred-at from balance-transaction dates; those bases answer different questions. Fees data may take up to 96 hours after its balance effect to appear. The report also excludes specified charges, including Terminal devices, Capital, Atlas and after-use invoiced fees. A schema repair cannot make those exclusions disappear.

Release a documented mapping, with exceptions visible

Apply the proposed changes to a working copy of the established sheet using the preserved real export. The finance owner should be able to follow each used old column to its replacement, see that all input rows remain accounted for, and locate every unresolved classification. Record the mapping version and when it becomes the agreed import rule. Keep the old file readable as historical evidence rather than relabeling its headers and calling it an original.

For a Prism processing consultation, summarize the report, changed field and reconciliation question without sending the raw financial export through the public form. Confirm any reporting or reconciliation assistance in the scope, responsibilities, fees and terms before work. Prism's published help includes processing preparation and website questions; the provider explains its fields and account terms. Email follow-up to an inquiry does not purchase analysis or submit a processing application.

Fee export field migration map

Complete this from the preserved real CSV and the sheet that consumes it. Repeat the dependency rows for every used column. Keep unresolved mappings visible with their retained source-row references; do not enter zero for an unclassified charge. Use non-sensitive local references rather than pasting financial records.

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.