Why do WooCommerce and Xero reconciliations go wrong?

They often go wrong because order data, payment settlement, VAT treatment and refund treatment are mixed together too early. ClearCommerce keeps source ecommerce data separate from Xero posting rules.

How do I stop WooCommerce flooding Xero with invoices?

Use daily paid-date summary posting for retail orders rather than individual invoice posting for every order. Individual invoice mode can still be used for trade customers.

What should I check first if WooCommerce VAT does not match Xero?

Check the source tax data, Xero tax-rate mappings, refund handling, shipping treatment and whether the report is based on order date or paid date.

WooCommerce, Shopify and BigCommerce to Xero accounting workflows. Book a demo

Troubleshooting guide

Seven WooCommerce-to-Xero problems that point to the wrong accounting workflow

When ecommerce reconciliation keeps breaking, the connector is not always the cause. The problem is often a posting rule that ignores payment timing, refunds, customer type or the difference between sales and settlements.

Show us the problem Main WooCommerce workflow

1. Xero contains one invoice for every consumer order

The integration may be technically working while creating an unusable ledger. Retail summarisation is the accounting design question to review.

2. The bank deposit is lower than recorded sales

Gross sales and net gateway settlements are being compared as if they were the same event. Clearing accounts and fee postings are needed to explain the difference.

3. Sunday orders appear in Sunday accounts even though payment was Monday

The workflow is grouping by created date rather than the chosen paid-date basis.

4. BACS orders appear paid before the transfer arrives

Payment method behaviour is being hardcoded instead of allowing BACS to remain an unpaid receivable.

Diagnosis

Trace each problem to one layer

Source data

Is the order, payment, tax or refund fact wrong or missing in WooCommerce?

Accounting treatment

Is the export profile or mapping choosing the wrong date, account, tax rate or payment behaviour?

Export execution

Did Xero reject the payload, or did a retry fail to recognise a record that was already exported?

Fix the cause

Do not solve a mapping problem by editing every Xero transaction manually

Correct the rule at the integration layer, test it on a small range, preview the output and then use the history to prove what changed.

Self-check

Signs a WooCommerce store has outgrown ad-hoc Xero posting

Xero contact list has grown past a thousand one-time customer names
Month-end VAT return needs manual adjustment most months
Nobody can explain a standing balance in the payment clearing account
Refunds show up as unexplained adjustments rather than linked entries

Bring one failed reconciliation example

We can identify whether the failure sits in source data, treatment or export execution.

Book a troubleshooting demo