Keep account identity in an organization fee export

Choose the layout from the reconciliation question

An organization total can answer how much the selected group incurred under the report's definitions. It cannot identify which account bore a particular fee if the relevant account distinction is absent from the output. Start by writing whether you need a group total, an account subtotal, or a fee line traceable to an account and transaction. These require different levels of detail.

Stripe's Fees report documents three organization export arrangements. Aggregate output combines reporting across accounts; concatenated output brings account output together; separate output keeps accounts apart. The format name alone is not enough to approve the file. Inspect the actual header and row detail, because account_id is documented for specified formats rather than every possible report layout.

Make the account origin survive the spreadsheet

For a concatenated file, confirm that the account identifier is present, populated and retained in the working sheet. Group by that identifier before calculating account subtotals. Keep a separate mapping from each identifier to the business's own account label. A familiar brand name is useful for reading the result, but it should not replace the provider identifier used to trace it.

For separate-account files, keep an index connecting each original file to the selected account and report settings. If you later combine those files, carry their verified account origin into the combined working copy. A manually added origin column is your annotation; retain the originals so another person can check it. If a file cannot be tied to one account, its origin remains unresolved.

An aggregate can still be useful as a control total. Compare it with the detailed files only after confirming the same included accounts and reporting scope. Do not use a proportion of group sales to manufacture the account attribution that the fee evidence lacks. That would be an internal allocation assumption, not a record of which account paid.

Match scope before investigating a difference

Keep the included account list, currency, selected period and date basis with the export. Stripe distinguishes when a fee was incurred from the date it affected the balance. Comparing those two bases can produce different totals even when the account identifiers are intact. Match the basis and range before treating a difference as an omitted account; revenue-share treatment can still require separate explanation.

The Fees report covers most fees paid from the balance, not every business cost. Its stated exclusions include Terminal devices, Capital, Atlas and fees invoiced after use. Those exclusions do not become account-level fees merely because you need a complete cost picture. Keep any separate supporting records outside the total until you have defined what the comparison includes.

Finish with traceable account totals or a named missing export

The result is usable when each account subtotal can be traced to original rows or a clearly identified account file, and every included account agrees with the scope you intended. If identity is missing, the next action is to request or generate the appropriate detailed export. If identity survives but totals differ, preserve the unmatched references and investigate scope rather than assigning the remainder to an account.

For a Prism processing consultation, describe the research-only storefronts, the report layout and the reconciliation question. Any requested reconciliation assistance needs an agreed scope, responsibilities, fees and terms. The provider decides account terms. Use the public form for the website, products and question; keep the exports, bank records, customer records and credentials out of that message. The request receives email follow-up and does not submit a processing application.

Organization export scope check

Complete one copy for the actual export under review. Keep it with the unmodified files in your authorized records. Accept a layout for account reconciliation only when both account origin and the required detail survive; otherwise name the replacement export needed.

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.