WooCommerce Xero integration: sales and payment records

Connect WooCommerce and Xero using verified sales, tax, fee and refund mappings, then reconcile a bounded sample without duplicating invoices or payments.

Yes, a WooCommerce Xero integration can send store orders to Xero as individual invoices through the Xero extension sold on WooCommerce Marketplace. It can also record payments. Set one owner for each accounting record before switching on automatic exports, then reconcile sales separately from the processor’s bank deposit.

Choose the supported connection and record owners

Choose the Xero extension for WooCommerce when you need order-level invoices. This is an installed connector, not a daily summary or a bank feed. Keep its licence, the store’s hosting and the Xero subscription in your operating budget.

Use a Xero user authorised to connect apps to the intended organisation. Xero’s connected-app guidance requires a standard or administrator role with permission to edit connected apps. Record the organisation’s name and base currency before authorising access.

Follow the extension’s connection and mapping instructions. Create an OAuth 2.0 app, copy the store’s redirect address and connect the intended organisation. Keep credentials private. Start with manual exports.

Write down who creates each record before importing anything:

  • WooCommerce owns the order and its line amounts. The connector creates the Xero invoice.
  • Choose either the connector or an existing payment integration to record receipts. When another integration owns receipts, set Send Payments to Manual.
  • The bookkeeper owns processor fee entries and payout reconciliation.
  • WooCommerce remains the stock owner for this procedure. Send Inventory Items matches stock keeping units (SKUs) to Xero item codes. It isn’t a two-way stock sync.

Keep a separate test store and accounting organisation for fictional orders. A test export into the live accounts creates a real accounting record.

Map sales and adjustments

Map the store’s actual order lines to the intended Xero accounts before comparing the invoice total. Select account codes from your own chart of accounts, with the bookkeeper approving tax treatment. Include shipping and order fees in that review.

The connector allocates discounts to invoice lines, without the coupon code. It matches contacts by billing email. Check each sample’s customer and any SKU/item-code match. Foreign order currencies need multi-currency in Xero and that currency enabled.

Fictional sale and partial refund

Assume a fictional taxable domestic sale with tax-exclusive prices and 10% goods and services tax (GST). These assumptions illustrate the calculation. They don’t establish the tax treatment of your products.

A customer buys two identical items at $100 each. A $20 discount reduces product sales to $180. Shipping is $10, so the taxable subtotal is $190. GST is $19 and the customer pays $209.

Later, one item is returned. Its discounted value is $90 and its GST is $9. The partial refund is $99, with shipping retained. Record the refund against the original order and its accounting reference.

RecordBefore GSTGSTTotal
Products before discount$200$20$220
Discount-$20-$2-$22
Shipping$10$1$11
Sale after discount$190$19$209
Partial refund-$90-$9-$99
Sale remaining$100$10$110

Keep the original order date separate from the refund date and the eventual settlement date. The extension normally uses the order date for the invoice, as described in its invoice customisation guide. A later payout doesn’t move the sale to the payout date.

Processor deductions need their own comparison. The extension sends order fee lines. Processor charges are recorded separately.

Suppose the processor retains a fictional $4 fee and includes the refund in the same settlement. The bank deposit is $209 minus $99 minus $4, or $106. That $4 is an assumed total deduction, not a quoted rate or a tax calculation.

Reconcile the actual store-record sample

Reconcile a small, named sample by order reference and accounting document ID before enabling automatic exports. Use the fictional sale above as an expected result, then compare it with the records your isolated setup actually creates.

For each sample, retain the order’s line amounts, currency and status alongside its Xero invoice reference. Add the receipt reference and the processor settlement reference separately. Match the customer identity as well as the amount: two customers can place equal-value orders.

For the $209 example, expect an original invoice of $209 and one receipt of $209 if the connector owns payments. A partial refund requires its own accounting adjustment. Paid invoices require manual adjustment in Xero. Don’t assume a store refund created a credit note.

Xero’s online-sales reconciliation procedure uses a clearing account for bulk online payments. It also describes credit notes referencing the original invoice and refund payments through the clearing account. Have the bookkeeper apply that procedure to the $99 refund.

The reconciliation worksheet must explain the $106 deposit through the $209 receipt, $99 refund and $4 deduction. Recording $106 as the original sale would hide the refund and fee. Recording both the $209 receipt and the payout as new sales would count the same customer money twice.

Check duplicate and failed events

Use these cases in the isolated sample before expanding the import:

  1. Export one order, then send that same order again. Confirm the invoice count and receipt total remain correct. Compare document IDs, not just a success message.
  2. Include an order whose invoice already exists. Match its number and status before retrying. Resolve a paid or restricted invoice in Xero instead of creating another one.
  3. Include an invoice whose payment failed. Correct the failed payment’s cause and confirm only one receipt exists after recovery. Keep the successful invoice reference.
  4. Correct an incorrectly recorded partial refund with the bookkeeper. Link the correction to the original refund and confirm the final credit is $99, without another sale or customer payment.

Order notes contain invoice identifiers and export errors. Read the returned error before resending. A failed response alone doesn’t prove that the destination lacks a record.

Maintain access and recovery

Assign a named bookkeeper to resolve exceptions and a store administrator to maintain the connection. Keep a shared list of failed order references, their destination records and the action still needed. Close an exception only after the accounting result matches the store and settlement evidence.

The connector’s triggers control invoice and payment timing. Existing orders can be sent manually, so set an agreed starting boundary before a history import. Exclude orders already represented in Xero and begin with a small batch. Don’t treat reconnecting as permission to replay all history.

After 60 days without token use, reconnecting can be necessary. For retirement or replacement, pause exports and use Xero’s Connected Apps screen to revoke the connection. Preserve the final reconciled boundary so a replacement starts after the records already accounted for.

Resume automatic exports only when the sample has one invoice per intended order, the correct receipts and a traceable refund. Keep accepting customer invoice payments as a separate setup task from importing store sales.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup