← All articles

Ecommerce accounting

Clearing-account aging for ecommerce payouts

Build an aging schedule for pending payouts, reserves and disputes so each clearing-account balance has supporting records and a follow-up owner.

Published

2026-09-30

Last updated

October 6, 2026

4

Published on Beamarc: September 30, 2026.

A clearing account connects payment activity to the cash received in your bank. Its ending balance should be supported by specific items, such as pending payouts, documented reserves, disputes or transactions that need correction.

An aging report makes those items visible. It shows what remains open, how long it has been outstanding, what is expected to happen next and who will follow up.

What the balance represents

A positive processor balance is often an amount receivable. A negative balance can arise when refunds, fees or disputes exceed available funds, and may represent an amount payable. Investigate the cause and apply the appropriate presentation; a negative number is not automatically an error.

The account does not need to be zero at every month-end. It needs to reconcile to supported balances for the same date, with recoverability assessed where appropriate.

Match the schedule to your posting method

  • Order or transaction posting: retain order and payment references, and reconcile them through to payout IDs.
  • Settlement posting: retain settlement IDs, deductions, reserves and pending items. Make separate period-end adjustments where the settlement omits revenue or costs belonging in the reporting period.

Do not post the same sales through both an integration and a manual settlement journal. Decide which source records each part of the transaction.

Fields to include in the aging report

  • Processor and currency.
  • Transaction, settlement, payout or dispute reference.
  • Item type: pending payout, reserve, dispute, adjustment or unmatched transfer.
  • Date first recorded and original amount.
  • Remaining open amount after partial settlements.
  • Expected release or resolution event.
  • Days outstanding, status and last update.
  • Supporting report or case reference.
  • Assigned owner, next action and follow-up date.

Use separate clearing accounts or a schedule that reliably distinguishes each processor. Avoid netting unrelated processors, currencies or disputes together.

Build the schedule in five steps

  1. Choose a cutoff date. Export the general ledger and processor reports as of the same date, documenting time-zone or report-window differences.
  2. Identify open items. Match charges, deductions and transfers by reference rather than assuming equal amounts belong together.
  3. Reconcile to external support. Compare the open schedule with pending payouts, reserve reports and dispute records. Avoid counting the same held balance twice.
  4. Classify the difference. Distinguish timing, holds, disputes and posting errors. Keep unresolved items visible as investigations rather than forcing a classification without evidence.
  5. Assign follow-up. Record the expected action, the responsible person and the date for review.

Illustrative open-item schedule

Total open items are $9,710.32.

  • Shopify pending payout: $4,231.50; 2 days; match to the scheduled deposit.
  • Stripe pending payout: $1,892.00; 3 days; confirm the payout status.
  • PayPal hold: $650.00; 8 days; retain the hold notice and expected review date.
  • Stripe dispute: $189.00; 17 days; track the response deadline and assess recoverability.
  • Shopify reserve: $2,400.00; 35 days; reconcile to the reserve report and release terms.
  • Unmatched PayPal transfer: $347.82; 75 days; trace both sides of the transfer and review for duplication or missing entries.

An old item warrants investigation, but its age alone does not establish that it is an error or should be written off.

Set review rules around the actual payout cycle

For routine payouts, an internal policy might call for checking an item after one expected payout cycle, escalating after two, and documenting a resolution plan after three. Those are management review thresholds, not provider deadlines or automatic accounting rules.

Reserves and disputes need their own expected timelines. Use contract terms, case status and current evidence. Recognize a loss or reclassification when the accounting facts require it, rather than clearing an item simply because it reached a certain age.

Common causes of differences

  • Deposit differs from payout: check timing, adjustments, fees, foreign currency, split transfers and bank debits.
  • Duplicate entries: determine whether a connector and a manual journal recorded the same activity. Preserve an audit trail when correcting closed periods.
  • Refunds recorded twice: connect the original refund entry to the later settlement deduction.
  • Reserves mixed with normal payouts: separate their support and expected release dates.
  • Missing opening support: reconstruct the relevant historical transactions before relying on the current ending balance.

Month-end sign-off

The sum of the open-item schedule should equal the general-ledger clearing balance. Reconcile that schedule to processor evidence, explaining any report timing or classification differences. Retain the exports, deposit matches, reserve and dispute support, and review notes together.

A reviewer should be able to follow a balance from the financial statements to the schedule and then to the source record without reconstructing the process.

How Beamarc can help

Beamarc provides bookkeeping, monthly close, financial reporting and accounting advisory. We can discuss the records available, the questions you need answered and the support that fits your business. Scope, responsibilities, timing and fees are agreed before work begins.

Request a consultation.

Related reading

General information only. Accounting and tax treatment depend on your facts and reporting framework. This article does not provide assurance or establish a client relationship.

Your choice is stored in this browser for six months. Revisit it any time using Cookie settings in the footer. Read the cookie notice.