WooCommerce BACS orders in Xero

BACS orders often need different treatment from card or wallet orders because payment may not have arrived when the WooCommerce order is created.

Book a demo BACS invoice page

Why BACS orders are different

A BACS order can be a promise to pay rather than a completed payment. Marking it paid in Xero too early can make debtor and bank reconciliation reports misleading.

Recommended treatment

Many WooCommerce stores treat BACS and account-term orders as individual unpaid invoices in Xero, with a named customer contact and due date.

How ClearCommerce supports this

ClearCommerce has export profile settings for invoice status, payment handling, invoice number strategy, contact matching and due dates.

How this fits with retail summaries

BACS orders can use individual invoice mode while card-paid retail orders use daily summary mode.

Questions people ask

FAQs

Should BACS orders be included in daily summaries?

Not always. BACS orders are often better as individual unpaid invoices where the customer and due date matter.

Can BACS invoices be created as draft or approved?

ClearCommerce supports invoice status rules such as draft, submitted or approved depending on the export profile.

Can BACS be mixed with daily retail summaries?

Yes. The architecture is designed to support different treatment by store and payment method rules.

Ready for cleaner WooCommerce accounting in Xero?

Book a demo and tell us your order volume, payment gateways, VAT setup and current Xero workflow.

Request a demo View pricing