Ecommerce to Xero Accounting Handover

The best ecommerce-to-Xero setup is the one finance can reconcile and operations can support. It must preserve the commercial facts behind a bank deposit: gross sales, discounts, delivery, tax, refunds, fees, chargebacks and the transactions included in the payout. Installing a connector is only one implementation step.

Start with the platform-neutral ecommerce accounting handover guide if ownership and control totals are not yet agreed. Use the Xero handover service when chart-of-accounts, tax and settlement mappings need joint finance and systems design.

1. Write the Xero outcome

Ask finance which reports and reconciliations must remain possible. Some businesses need one Xero invoice per ecommerce order because customer balances, tax invoices or item-level reporting matter. Others keep detailed orders in the commerce platform and post controlled daily or payout summaries. A hybrid can be valid when B2B credit customers require invoices while paid consumer orders are summarised.

2. Build the mapping register

Document every transformation before connecting production. The register should name the source field or condition, Xero destination, tax treatment, effective date, owner and test evidence. Avoid a single generic sales account when finance needs to distinguish products, delivery, discounts or channels, but do not create hundreds of accounts simply to mirror every SKU.

• Sales revenue by the reporting dimensions finance actually uses.
• Shipping or delivery income and any related tax treatment.
• Discount handling, including whether the connector posts gross sale and a separate discount.
• Refund and credit-note treatment, including partial line and shipping refunds.
• Payment-method clearing account for each materially different settlement stream.
• Merchant fee, chargeback, rounding and foreign-exchange accounts.
• Customer and item creation rules, including duplicate prevention and archive behaviour.

3. Use clearing accounts deliberately

Xero’s online-sales guidance describes clearing accounts for bulk payments. Customer or summary payments are applied to the relevant clearing account. When the gateway payout arrives in the bank feed, the gross receipt is allocated to that clearing account and deducted fees are recorded separately. Refunds and credits also move through the same explainable bridge.

4. Control order-status triggers

Define which WooCommerce status creates an invoice or summary entry, which event marks payment, and what cancellation or refund does afterward. Do not post a failed or test order as revenue. Do not delete a paid accounting entry when an order changes; create the appropriate credit or reversal with a reference to the original event. Make retries idempotent so the same webhook cannot create two Xero documents.

5. Decide how customers and items are represented

Creating a Xero contact for every guest can produce duplicates and unnecessary personal data. A summary-customer model may be better for paid consumer sales, while account customers and B2B credit sales may need distinct contacts. Item-level posting is useful only when Xero is expected to report or value those items accurately. If an external inventory system owns quantities and cost, keep that boundary explicit.

6. Test tax, refunds and fees

1. Normal taxed sale with product, delivery and discount.
2. Zero-rated, exempt or different-tax item only when the business genuinely sells one.
3. Partial product refund with and without returned stock.
4. Delivery refund and goodwill credit that should not change quantity.
5. Gateway fee deducted before payout and a separate chargeback.
6. Order edited after posting, then corrected through an approved adjustment.
7. Duplicate webhook, timeout and replay with no duplicate Xero document.

Worked Xero payout example

A WooCommerce store takes card payments that the gateway settles in batches. The integration creates a daily sales summary split into taxable product revenue, delivery income, discount and output tax. The payment is posted to a card clearing account. The gateway statement shows the included orders, one refund and a processing fee. The refund creates a sales credit and clearing movement; the fee posts to payment-processing costs.

When the net payout appears in the bank feed, finance allocates the gross settlement to the card clearing account and records the fee adjustment. The resulting clearing balance consists only of transactions not yet paid out. Finance can select any residual item and trace it to an order, refund or settlement timing difference. That trace is the acceptance evidence.

7. Release in controlled stages

Connect one store, currency and payment method first. Run current transactions rather than importing years of history before the mapping is proved. Reconcile at least one complete payout and close period, then review the exception rate with finance. Add channels only after the same control can be repeated without manual reconstruction.

Ownership after launch

Assign owners for mapping changes, failed syncs, clearing-account review and finance close. Review the WooCommerce payment gateway reconciliation guide when payout differences originate upstream. Re-test the Xero handover after changing payment methods, tax rules, currencies, order statuses or inventory ownership.

Sources checked

• Xero ZA: Accounting for ecommerce
• Xero Central: Reconcile bulk payments received from online sales
• Xero App Store: Integrate Xero with WooCommerce

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.