Ecommerce to Accounting Handover Guide

An ecommerce accounting handover is complete when finance can move from a bank deposit back to the payment settlement and the underlying orders without guessing. Orders alone are insufficient because gateways commonly settle several transactions together and may deduct fees, refunds or chargebacks before cash reaches the bank.

Use the Xero handover service when mappings, clearing accounts or exception ownership are unclear. The next guide, Ecommerce to Xero Accounting Handover, applies this control model specifically to Xero.

1. Agree the accounting boundary

List the systems that create commercial facts: ecommerce platform, payment gateway, marketplace, point of sale, inventory system, bank and accounting ledger. For each fact, name one authoritative source. The ecommerce platform may own order lines and customer-facing tax; the gateway owns settlement details and fees; the bank owns cash received; the ledger owns the final accounting classification.

2. Define the transaction contract

Write the fields required for every accounting event: source order, transaction ID, timestamp, currency, gross sale, discount, shipping, tax, refund, fee, net amount, payment method and settlement reference. Add stable SKU and tax mappings where line-level entries are required. Version the mapping so a historical transaction can be interpreted after the configuration changes.

• Use source IDs as references; do not rely on customer names or rounded amounts as unique keys.
• Preserve original currency and conversion evidence where more than one currency is involved.
• Separate discounts from refunds because they occur at different stages of the sale.
• Separate payment-processor fees from net sales rather than posting the bank deposit as revenue.
• Record cancelled, failed and test orders so they can be excluded consistently.

3. Choose the posting level

Choose the lowest level of detail finance needs for tax, customer accounts, inventory valuation and audit. Sending every click or order note into the ledger adds noise. Sending only net bank receipts hides sales, tax, fees and refunds. The right model preserves traceability without turning accounting software into the operational order database.

4. Use clearing accounts to bridge timing

Xero documents the use of a clearing account for bulk online payments: order payments are applied to the clearing account, the bank deposit is allocated to the same account, and merchant fees or refunds are recorded separately. The clearing balance should then explain transactions not yet settled, timing differences or errors rather than becoming a permanent unexplained amount.

5. Build daily and period-end controls

6. Design the exception queue

• Duplicate source reference or attempted reposting.
• Unknown product, customer, tax, currency or account mapping.
• Payout with no matching settlement detail.
• Refund recorded in one system but missing from another.
• Manual order edit after the accounting event was posted.
• Difference outside the approved rounding or timing rule.

Each exception needs the source IDs, detected time, financial impact, owner, action and resolution evidence. Do not silently create a suspense mapping for every unknown item. A visible queue protects the books and exposes upstream data problems that should be fixed at source.

Worked settlement example

A gateway settles several paid orders in one bank deposit. The settlement includes product sales, shipping and tax, subtracts one refund and deducts processing fees. The order data posts gross activity to the agreed sales, shipping and tax accounts, with customer payments going to a gateway clearing account. The refund produces a credit and clearing movement; the fee is recorded as an expense; the net bank receipt clears the remaining balance.

Finance reconciles the gateway settlement total to the included transaction IDs, then matches the net payout to the bank line. One order edited after settlement becomes an exception instead of being overwritten. The control passes when the clearing account reaches the expected residual and every residual item has a named cause.

Release and ownership

Run at least one full settlement cycle in a test or controlled pilot, including refund and failure paths. Obtain sign-off from ecommerce operations, finance and the integration owner. Keep the mapping register, exception procedure and close checklist with named owners. Re-test after changes to gateways, tax, order statuses, currencies or accounting apps.

Sources checked

• Xero Central: Reconcile bulk payments received from online sales
• WooCommerce: Orders Report
• Xero ZA: Accounting for ecommerce

This resource provides general implementation guidance. Verify platform settings, tax, legal, payment and operational requirements against the current business context before making a live change.