Show the trading cycle behind a seasonal volume estimate
Show the requested historical period month by month, including verified inactive periods and missing records, then place the future trading calendar in a separate schedule. Label the busiest recorded month, the average over the full period and any active-month average with their exact bases. A peak is observed history for that month, not evidence that the same volume will recur all year. Support any future estimate with the assumptions and records that produced it, and explain the calendar alongside a required single-number field.
For: A research-only merchant whose actual trading cycle makes one monthly processing figure an incomplete description for a provider.
Use the dates, entity, account and payment scope in the provider’s request. For every period in that range, record the actual activity and the source that supports it. Keep inactive periods visible. A complete report showing no relevant activity can support zero for that measure; an inaccessible report cannot.
For a Stripe account, the balance summary report covers a selected period in settlement currency and separates gross, fees and net activity, with itemized transactions available. Use the components that match the requested measure. Total balance movement or net payout should not be relabeled as card-processing volume: other balance activity can have a different meaning, and the balance report does not associate payouts with individual payments.
Keep currencies and provider accounts distinguishable. State the date boundaries and report basis so someone else can reproduce the calendar. If records cover only part of a cycle, describe that coverage. An apparent quiet period in an incomplete export does not establish that the business stopped trading.
Use averages that reveal their denominator
If you calculate a calendar-month average, divide the sum of the same defined activity measure by the number of calendar months covered, including verified zero-activity months. If you also calculate an active-month average, state which months qualify as active and how many were included. These are descriptive calculations from your records, not provider acceptance formulas.
Identify the highest actual month separately, with its date and supporting report. Multiplying that peak by twelve is a hypothetical continuation of peak activity, not the actual annual total or evidence of the next year’s sales. An average across the full calendar can also hide the scale of a real peak, so retain the monthly schedule even if the form accepts only one figure.
Partial months require an explicit label. Do not compare a partial month with complete months as though their observation windows were equal, or describe an annualized partial period as completed history. If the provider asks for a specific average or expected volume definition, use it and attach the explanation of the nonuniform cycle.
Support the seasonal explanation without inventing a cause
A repeating pattern in retrieved reports supports a description of when activity occurred. The reason for that pattern needs its own record. Connect actual operating calendars, dated closure notices or documented purchasing cycles to the relevant periods only where those records exist. Do not call an unexplained spike seasonal simply because it makes a forecast easier to present.
Use separate labels for observed activity, a documented operational driver and a proposed explanation. A closure record can establish that the store planned not to trade on those dates; it does not, by itself, prove the precise sales effect. If the available history contains only one busy period, describe that limited observation instead of claiming a repeatable annual pattern.
Stripe’s restricted-business policy prohibits misleading descriptions of the business and processing for undisclosed products. That is a reason to keep the actual catalog and operating model visible in a Stripe inquiry, not a seasonal-volume approval rule. A forecast cannot establish eligibility, and Stripe’s policy should not be represented as another provider’s terms.
Keep future operating dates and future sales separate
Write the coming trading calendar from the business’s documented plans. Distinguish dates that are decided from dates still conditional. Beside each future period, record the forecast measure, the historical period used for comparison and any supported assumption that changes the estimate. A planned opening date can be known while the sales expected after opening remain uncertain.
If the application requires one monthly estimate, preserve the wording of that field and explain the calendar and calculation behind the submitted figure. Where its meaning is unclear, ask whether it wants a calendar average, an active-period expectation or another defined measure. Do not substitute a peak or enter an account limit as the forecast. Retain the version of the estimate and its preparation date so later changes can be explained.
For a Prism processing consultation, bring a summary of the provider’s question, the period your reports cover and the particular ambiguity the seasonal calendar exposes. Agree scope, responsibilities, fees and terms before work. The provider decides document sufficiency and account terms; this calendar makes the description traceable without predicting sales or acceptance.
Seasonal volume evidence calendar
Use the historical-period row for each actual month and the future-period row for each planned month in a private working copy. Keep the measured amount, currency and source beside each entry. Separate zero, missing and planned activity; do not fill unknown periods with an average.
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.
Seasonal volume evidence calendar. The last column is for temporary notes.
Calendar component
Records or calculation
Required distinction
Your period and evidence
Historical period
Records or calculationRequested dates, account, entity, currency and report coverage.
Required distinctionIdentify complete and partial months before comparing amounts.
Actual activity
Records or calculationProvider report or itemized payment records for each historical month.
Required distinctionUse the requested measure consistently; do not substitute net payout or undifferentiated balance movement.
Inactive or missing period
Records or calculationComplete records showing no relevant activity, or the exact unavailable report.
Required distinctionVerified zero and missing evidence remain different entries.
Seasonal driver evidence
Records or calculationDated operational records linked to the observed periods.
Required distinctionSeparate a documented business event from an unproven explanation for sales changes.
Historical summaries
Records or calculationFull-period total and denominator, active-month definition and denominator, and the highest recorded month.
Required distinctionLabel each measure; a peak and an active-month average do not describe every month.
Future trading dates
Records or calculationCurrent operating plan with definite and conditional dates identified.
Required distinctionPlanned availability is not completed sales or processing history.
Forecast assumption
Records or calculationHistorical comparison, supporting business records, calculation and preparation date for each future period.
Required distinctionState what is assumed and what remains uncertain without inventing future orders.
Application field mapping
Records or calculationExact field wording, requested definition and attachment or explanation supplied.
Required distinctionTie the single figure to its calendar basis; leave provider acceptance and limits to the provider.
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
This worksheet supplies no acceptance threshold, recommended account limit or prediction of future sales.
Stripe reports describe Stripe activity in their documented scope; use another provider’s records and definitions for that provider.
Keep raw customer records, full account or bank details and identity documents out of public consultation messages.
Stripe prohibited and restricted businesses — checked 2026-09-28. Stripe prohibits misleading information about the nature of the business and processing for undisclosed products. Approvals are service-specific and can be modified or revoked; the policy does not prescribe a seasonal forecast formula.
Stripe balance summary report — checked 2026-09-21. The report covers a selected period in settlement currency, separates gross, fee and net activity and allows itemized exports. It does not associate payouts with payment transactions.
Discuss my processing options
Want to talk through your own processing situation?