Back to blog
Article

Shopify Payments Has a New Activity Report. It Doesn't Close the Books

The new Shopify Payments activity report explains balance movement, fees, holds, and payouts. Finance teams still need an order-to-bank-to-ERP close.

AorBorC field note / Last reviewed August 23, 2026

10m
Read time
Aug
Published
Shopify Payments Has a New Activity Report. It Doesn't Close the Books

A report that explains a payment balance does not close the books.

Category: Shopify, E-commerce & Finance Operations
Author: AorBorC Technologies
Published: August 23, 2026

Shopify announced a new Shopify Payments activity report on August 22, combining a period's opening and closing balances, activity, fees, payouts, net movement, and PDF export.

It clarifies movement inside Shopify Payments before funds reach the bank. Shopify is equally clear about the boundary: the report reflects payment-balance activity, not revenue for accounting purposes.

The AorBorC view is simple: use the report as one piece of month-end evidence, not as the close itself. A reliable close still has to connect orders and returns, Shopify Payments activity, payout deposits, the bank statement, and the ERP or accounting ledger.

What changed

The Shopify Payments activity report is available from Finance > Documents and the Payouts area. For a date range and payout currency, it summarizes the starting balance, gross activity, fees, payouts, net movement, and ending balance. It can group charges, refunds, disputes, adjustments, duties and taxes, reserves and holds, shipping, and payouts.

The report is organized around balance activity and transaction dates, unlike reviewing one deposit at a time. Its PDF preserves that view for period review or accountant handoff.

Several limits belong beside the announcement, not in fine print. The report is for Shopify Payments. It excludes Shopify billing fees, third-party processors, and third-party payment methods. Each payout currency has a separate report, and Shopify documents a three-day data delay. The store owner or a staff member with permission to view payouts must access it.

Who should check this

The report matters most to Shopify Payments merchants explaining a period-end balance, fee difference, payout gap, refund, dispute, or reserve. It is especially useful when finance jumps between order reports, payout exports, bank deposits, and ERP entries without one named reconciliation owner.

Each payout currency has a separate activity report. When multi-currency payouts are enabled, Shopify also documents separate payout groupings by currency. Stores using third-party processors or payment methods outside Shopify Payments need a separate evidence lane.

If a store does not use Shopify Payments, this release is not its reconciliation answer. The better task is to map the actual payment providers, exports, settlement references, and accounting handoffs in use.

Why operational leaders should care

A payment provider balance and accounting revenue answer different questions. The provider balance explains funds moving through a payment account. Shopify's sales reports use order-based sales, discounts, reversals, shipping, and tax data; its Payments reports address captured payments. Their timing and totals can differ from Shopify Payments balance activity.

Payouts add another boundary. Shopify's Payouts page shows previous and scheduled payouts. Opening a payout provides transaction detail and fees, while its Overview provides a transfer reference where available. A payout marked Deposited means Shopify sent it to the bank; Shopify notes that the bank may still need time to process and deposit the funds.

That is why an activity report whose opening-to-closing movement ties can still coexist with an unmatched bank deposit or an open ERP clearing balance. A clearing account is simply the temporary ledger account used to hold payment activity until the corresponding bank settlement and fees are matched. If nobody owns the bridge, unexplained amounts accumulate even when every individual system looks internally consistent.

The four-clock close

Treat month-end as four connected evidence clocks:

  • Order and revenue clock: Orders, captures, discounts, returns, shipping, and taxes establish what was sold or reversed and when.
  • Shopify Payments activity clock: Charges, refunds, disputes, fees, holds, adjustments, and payouts explain movement inside the Shopify Payments balance for one currency and date range.
  • Payout and bank clock: Payout detail connects balance transactions to a transfer. The bank statement confirms when the deposit actually settled and which reference arrived.
  • ERP close clock: The finance system records revenue, tax, gateway clearing, fees, refunds, disputes, holds, and cash in the accounting period approved by the finance owner.

The clocks will not always show the same total on the same day. That is not automatically an error. It becomes an operational problem when the team cannot explain the difference, identify the source record, or name the person who will clear it.

Commerce owns the order and refund facts. Finance owns accounting policy, posting, and period close. The integration owner preserves identifiers and monitors failed handoffs. One person may fill more than one role in a smaller business, but the decisions should still be explicit.

A ten-step implementation checklist

  1. Choose one closed period and currency. Start with a completed month and one Shopify Payments payout currency. Wait through the documented three-day delay before using the report for the exercise.

  2. Name the owner and reviewer. Give one person responsibility for preparing the reconciliation and another qualified person responsibility for reviewing exceptions and approving the close.

  3. Export and test the activity evidence. Save the Shopify Payments activity report for the same date range and currency. Verify that its starting balance, Balance change from activity, and ending balance reconcile. Use the expanded Gross activity, Fees, Payouts, and Net amount breakdown to explain the movement; do not subtract payouts a second time. Log any unexplained difference before comparing Shopify with the bank or ERP.

  4. Collect the order-based view. Run the relevant Shopify finance and payment reports for the same period and time-zone basis. Keep sales, returns, tax, shipping, and captured-payment timing distinct from provider-balance movement.

  5. Collect payout and bank evidence. Export payout transactions and retain the payout date and status. From each payout's Overview, retain the transfer reference when Shopify provides one. Match every payout in scope to the bank statement rather than relying only on its Shopify status. Put unmatched or still-processing payouts in the exception log.

  6. List every excluded payment method or provider. Record every third-party processor or payment method outside Shopify Payments, plus Shopify billing fees. Give each one its own evidence source and owner.

  7. Build the reference map. Preserve the order number, payment transaction, payout date and status, the payout Overview's transfer reference where available, currency, refund or dispute reference, bank entry, and ERP document or clearing entry. Do not use an amount and date as the only match key.

  8. Test exceptions across periods. Trace one ordinary sale, one refund that crosses the month boundary, and one applicable fee, dispute, reserve, or hold. Confirm how each appears in the report, payout date and status, the payout Overview's transfer reference where available, bank, and ERP.

  9. Reconcile the ERP clearing balance. Match provider activity, fees, payouts, and bank settlements to the configured ledger accounts. Let the qualified finance owner decide accounting and tax treatment; do not have an integration silently invent entries.

  10. Close with an exception log. Record unmatched amounts, cause, owner, next action, and review date. Re-run the evidence after delayed activity appears and retain the approved report, payout detail, bank proof, and ledger trail.

Operational impact for e-commerce and ERP

This release is about finance visibility; Shopify's announcement does not describe changes to catalog, checkout, inventory, fulfillment, or support workflows. A duties adjustment may point to a cross-border order, a refund to a return decision, and a fee or hold to the gap between expected cash and the order-based payment total.

In an Odoo or other ERP implementation, the useful design is not “import the PDF.” It is a controlled mapping between orders, payment transactions, refunds, payouts, bank entries, and ledger records. That mapping needs stable identifiers, currency rules, exception states, and a recovery path. AorBorC's Odoo implementation work covers the wider order-to-cash and finance-control layer.

For Shopify operations, product catalogs, checkout readiness, inventory and order handoffs, returns, finance workflows, integrations, and reporting should be tested as one long-lived system. Our e-commerce store development practice treats checkout completion as the start of the operating trail, not the end.

Risks, limits, and where the hype is not useful

Shopify explicitly says the report is not a statement of revenue. Its documentation presents balance activity, not a profit report, tax-liability calculation, or accounting-policy decision. A store with several gateways can have an activity report whose opening-to-closing movement ties while its overall payment reconciliation remains incomplete.

Date ranges and time zones can also create legitimate differences. Payout schedules follow their own timing, bank processing adds another date, and the activity report itself has a three-day delay. Multi-currency stores must work currency by currency rather than netting unlike balances into one unexplained total.

The PDF is useful evidence, but evidence still needs a control. Define who generated it, which period and currency it covers, which excluded systems were reviewed, and how exceptions reached the ledger. Do not describe the release as the first time reconciliation became possible or as an automatic ERP integration.

Human-reviewed AI can help group unmatched records, summarize exception notes, or prepare a reviewer queue. It should not decide whether a variance is revenue, a liability, a tax adjustment, a write-off, or an approved posting. Those decisions belong to the named finance owner.

The AorBorC view

Shopify has made one provider-side balance easier to explain. The implementation opportunity is to connect that evidence to the rest of the operating system without pretending one report owns every truth.

AorBorC is a founder-led Zoho, AI, Odoo, Shopify, and business-systems partner. We map the workflow first, then build or repair the permissions, integrations, ERP modules, finance handoffs, reporting, test evidence, and human review path around it. Our founder-led delivery and rescue approach is outlined in the company profile.

For a rescue or audit, the useful output is bounded: one period, one currency, the source exports, the reference map, observed variances, owners, and a remediation decision. That is more durable than a dashboard screenshot and more honest than calling the close automated.

Business takeaway

Use the Shopify Payments activity report to explain the provider balance. Close the books only after orders, excluded payment methods and providers, payout details, bank settlement, and ERP entries can be traced by period and currency with named human review.

Your next move

Take one completed month and one payout currency. Run the activity report after its delay, then trace one sale, one refund, one fee or hold, and one payout through the order record, bank, and ERP. If the identifiers or owners disappear between systems, plan the Shopify-to-ERP reconciliation workflow with AorBorC.

Next step

Need help mapping this workflow?

Start with the workflow, roles, decisions, and system handoffs. AorBorC can map the operating problem, identify the right build path, and define a practical first phase before your team commits to implementation.

Related Articles

August 16, 2026

Odoo 19 Self-Billing: Test the Journal Before You Trust the Sequence

An upstream Odoo 19 change lets incoming self-billed invoices prefer a dedicated sales journal. Test routing, sequences, posting, and reconciliation.

Read article

August 15, 2026

Odoo 19's Dropship-Kit Cost Fix: Margin Needs a Component Trail

An upstream Odoo 19 fix covers a narrow path where a dropshipped kit's Sales Order Cost could become zero while component PO lines retained supplier prices.

Read article