Which report should anchor the month-end close package for Shopify, PayPal, Stripe, and Amazon?

For a month-end close package, the top report should be the one that presents the period in balance terms: beginning balance, movement during the period, and ending balance. That gives the package a single reference point for reconciling payouts, fees, refunds, and other activity before you add supporting detail.

The practical question is not which report has the most rows, but which one already frames the period the way a bookkeeper or finance lead needs to review it. On the evidence provided, Shopify and PayPal both document reports that serve that role directly. Stripe and Amazon are different: Stripe’s balance transaction list is the movement layer underneath the balance, and Amazon’s reporting tools and transaction records require more attention to posting-date logic and report changes.

Source documentation is provider reporting behavior, not a legal rule. The goal is to build a repeatable handoff package, not to treat any one provider’s terminology as universal.

Shopify says the Shopify Payments activity report is meant for period-level review, month-end reconciliation, PDF record keeping, and accountant handoff. It includes starting balance, store earnings, fees, payouts, net movement, and ending balance. That combination makes it the clearest anchor report for a Shopify close package.

If your package needs a second layer, Shopify’s Finance overview helps you separate accumulated payouts pending transfer to the bank account from available Shopify Balance cash, including holds. That is useful when the close package needs to distinguish between money that has accumulated for transfer and money that is already available in Shopify Balance.

A sensible Shopify package therefore starts with the activity report and then adds the Finance overview when you need a cash-position view around the payout timing. The activity report tells the story of the month; the Finance overview helps explain where the cash sits at the end of that period.

PayPal says the Balance report is used to reconcile payment activities such as sales, refunds, disputes, fees, and withdrawals with end-of-day balances and to understand payouts to bank accounts. That makes it the best anchor report when the close package needs a balance-based summary tied to payment activity.

PayPal also says the Settlement report provides detailed information about each transaction affecting settlement and summarizes debits, credits, and beginning and ending balances for each currency. If the balance report is the main schedule, the settlement report is the detailed backup that explains what changed and in which currency.

Monthly and custom statements add another summary layer: they present beginning and ending balances, total debits and credits, and balance-affecting transaction activity for the selected reporting period. In practice, that makes them useful when you want a period statement beside the balance report, especially if the package needs a cleaner summary for review. The reporting hierarchy is therefore balance report first, then settlement report or monthly statement depending on how much transaction detail the reviewer needs.

The evidence for Stripe points to the balance transaction list as the underlying movement layer for balance-impacting events. That means the report set should be organized from the movement layer upward: first the transaction list, then whatever summary schedule you use to reconcile the balance position.

For a month-end package, that is a different structure from Shopify or PayPal. Those providers document a ready-made summary report that already combines period movement and balance framing. Stripe’s balance transaction list is the source layer, so the close package needs a separate reconciliation view built on top of it rather than treating the list itself as a finished summary.

The useful decision here is not to look for a one-to-one equivalent of the Shopify or PayPal summary report. Instead, keep the balance transaction list as the evidence for the balance-impacting events and place the month-end reconciliation schedule above it as the anchor for review.

Amazon says the Reports API is used to retrieve and manage reports for a selling business, and it warns that Amazon regularly adds new fields and field values, so report handling must account for updates. That means the first step in a repeatable close package is to choose a report structure that remains traceable when fields change.

Amazon transaction records can include a PostedDate, which supports grouping activity by posting date rather than only by payout date. For month-end close work, that distinction matters because the package needs a way to organize activity by when it posts, not just by when cash is paid out.

So the anchor for an Amazon close package should be the report or extract that lets you group by posted activity, with the remaining supporting reports arranged underneath it. The evidence does not point to a single named summary report in the way Shopify and PayPal do, so the practical hierarchy is built around posted-date tracing and report maintenance rather than around a specific preset summary.

A good internal rule is to keep the posted-date view at the top of the package and use any payout or detail reports as support beneath it. That keeps the month-end handoff tied to the activity that actually posts in the period, while still recognizing that Amazon report fields can change over time. This article provides general information and is not tax or legal advice.