A statement bundle contains more than one merchant account

An account map comes before the application total

Write the legal entity and business activity named in the application beside the wording of the history request. Then list every account appearing in the bundle, using a private account index and a shortened reference in the worksheet. For each account, identify the entity on its records and the storefronts or activities it actually covered during the requested period. A present-day brand name cannot settle what an older account processed.

Stripe's multiple-account documentation associates each account with one business's legal entity and tax ID. It also allows the same legal entity to use its tax ID on more than one account when the public business information fits. Therefore, matching entity names do not prove that two statements are for the same account. Different account references do not necessarily mean different entities either. Those are separate checks.

Keep records for another entity visible in the index as outside the requested scope, with the reason recorded. If the provider asked about related entities as well, that request expands what must be supplied. Do not use a narrow interpretation to hide an account the application expressly asks about.

Identify whether an export has already combined accounts

Stripe's Fees report documentation describes organization exports that can aggregate, concatenate or separate account data, with account_id included in specified formats. Before using an organization export, inspect the chosen format and actual columns. Record whether the file preserves account attribution. Do not assume every export has an account_id column simply because one documented format does.

An aggregate with no usable account attribution cannot establish which component belongs to the requested activity. Retrieve account-level records or an appropriate account-identifying format where available. Keep the original aggregate and record the replacement export's scope; do not assign unexplained portions to accounts by guesswork.

This documentation concerns the Fees report. Its rows describe fees, and one underlying transaction can have multiple fee rows. It does not turn a fee export into a complete processing statement or sales-volume history. Confirm that the record type answers the application field before using any of its totals. Another provider's report needs its own documented interpretation.

Separate overlap from missing history

Compare the accounts, dates and report type in the combined export with the individual files. If the same account and period are represented in both, designate which file supplies the application figure and which is supporting detail. Adding both would count the same coverage twice. Keep a link in the private index so another reader can trace that choice without deleting original records.

For each included account, mark requested periods present, missing or not yet available. Keep a low-activity period, a period with refunds or a disputed period in the requested set. An exclusion should explain an entity, activity or reporting boundary, not select a more favorable performance story.

If one account mixes the requested activity with other activity, account separation alone will not solve the allocation. Use traceable underlying records if they establish the split, retain the reconciliation, and label any derived summary as your summary. If the split cannot be supported, disclose the mixed scope and ask how the provider wants it presented. Do not invent a percentage.

Deliver an index that explains every inclusion

The packet is ready for the provider's assessment when each included figure has an account, entity, activity, period and source file, and every exclusion or unresolved overlap has a reason. Keep currencies and reporting bases identified; a bundle total should not erase those differences. The provider decides whether the supplied history satisfies its request.

For a Prism processing consultation, describe the number of accounts, the business activities and the unresolved scope question in ordinary language. The existing processing service can help organize that discussion within an agreed scope. Send statements only through the provider's authorized document channel, not the public consultation form. Scope, fees and responsibilities are confirmed before work; an organized history is not an approval decision.

Multi-account history boundary table

Complete one copy per account in the real bundle, then compare copies for overlapping coverage. Use shortened references and document pointers, not full account identifiers or transaction details. An account is ready for inclusion only when its relationship to the request and any duplicate coverage are explained.

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.