Currency balances were added as if they were one amount

Define the unit of each balance

Stripe’s balance summary report covers a selected period in settlement currency and separates gross, fee and net amounts. Read the currency code and the report’s account and balance scope before copying an amount. Do not assume that a currency shown on a storefront, original payment or buyer payment method is the unit of the balance report you are reconciling. Use the report’s own currency field.

Separate the records by currency, then use the same period and time-zone basis for each comparison. Preserve whether the amount came from a formatted report or a raw API field. Stripe’s currency documentation says API amounts use currency-specific minor-unit rules, including zero-decimal currencies and exceptions. It is therefore unsafe to apply a universal division by 100 to every imported amount. This does not mean a formatted report needs rescaling; identify the format first.

Close each currency against its own movements

For each currency, take the opening amount from the chosen report, add all signed balance movements within that same report scope, and compare the result with its closing amount. Keep credits and debits in the direction the source defines. If you use net movements, do not deduct their already-included fees a second time. If you reconstruct net from components, document which fields you used and compare with the report’s own net figure.

A remaining difference belongs to that currency’s reconciliation. Trace missing rows, incompatible periods, duplicated entries, amount units and balance scopes before drawing a conclusion. Do not offset a discrepancy in one currency with an unrelated amount in another. Keep any unexplained remainder with its supporting references instead of creating a balancing entry.

Stripe’s balance report does not associate payouts with individual payment transactions. Use it here to reconcile the balance period. A question about which sales were in one automatic payout needs the payout-specific records, even if the currency and total look similar.

Identify conversion as recorded activity

Stripe’s balance-transaction definitions identify currency_conversion as a balance movement and stripe_fx_fee as a conversion-fee type. For a conversion shown in the actual ledger, retain its transaction reference, date, signed amount and currency, together with the originating record where available. Use the provider’s references to associate the relevant movements; matching dates or similar amounts alone do not establish a connection.

Keep any documented source-currency decrease and destination-currency increase in their respective currency reconciliations. They describe movement between units, not two new sales. A separately recorded conversion fee is another component to identify, subject to the report’s amount definitions. Do not add a fee again if it is already included in the net amount you used.

A conversion type tells you that the balance movement is classified as conversion. It does not supply a rate, prove a fee formula or explain an unseen merchant’s discrepancy. Record the actual conversion details when they exist. If an expected counterpart or fee cannot be found, retain the missing reference as a question rather than deriving a transaction from a public exchange rate. Do not create a separate balance conversion entry merely because an original charge and its settlement record use different currencies.

Keep consolidation traceable to the native reconciliations

Once each native balance is reconciled or has a clearly stated unresolved difference, preserve those original totals. If the business needs a common-currency presentation, record the presentation currency, conversion basis, date and responsible preparer separately. Link each presented figure back to the native amount and the basis actually used. Do not overwrite the native closing balances with translated values.

A reporting translation and a provider conversion answer different questions. The first expresses a figure in another unit for a stated purpose; the second is an actual recorded funds movement. This worksheet does not choose an accounting policy or establish tax or revenue treatment. Where a presentation basis has not been agreed for the intended report, keep that consolidated figure unfinished while retaining the usable native-currency work.

For a Prism processing consultation, summarize the website, research-only products and the report mismatch. Confirm any reconciliation assistance, responsibilities, fees and terms before work begins. Provider account terms and eligibility remain provider decisions. Send a description of the currency and report problem through the public form, not bank statements, full account details, customer exports or payment credentials. The inquiry leads to email follow-up; it is not a processing application.

Currency-specific balance table

Repeat this worksheet for each native currency using the same defined reporting scope. Complete the native reconciliation before adding a separate consolidation record. Leave absent movements and conversion evidence unresolved; enter safe record references, not private payment data.

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.