WooCommerce QuickBooks integration review: records
Review a WooCommerce QuickBooks integration by its actual product edition, sales and refund mappings, then check a sample for duplicate or missing records.
- Published
- Last updated
Yes, WooCommerce connects to QuickBooks Online through Intuit’s connector. A useful WooCommerce QuickBooks integration review must identify the connector generation as well as the accounting edition. The newer connection imports individual orders, but WooCommerce payout reconciliation still needs a separate process.
Choose it for paid-order accounting when you can maintain that reconciliation. A requirement for unpaid-order imports or two-way stock updates changes the decision.
Identify the QuickBooks product and connector
Identify the Australian QuickBooks Online company and the actual connector before comparing features. QuickBooks Online is the cloud accounting destination considered here. A QuickBooks Desktop company file requires its own supported connection and access arrangement.
Intuit’s new e-commerce connector guidance includes WooCommerce among the connections replacing OneSaas. The new WooCommerce connector imports individual orders as sales receipts or invoices. It supports customer tracking, product matching and tax mapping.
The same guidance gives limits that affect this choice. The new connectors sync every few hours and can’t import orders as unpaid. They don’t provide two-way inventory sync. For WooCommerce, payout-level reconciliation is a future feature. Keep stock ownership and settlement accounting outside any promise of automatic two-way updates or complete payout matching.
The legacy OneSaas setup has different options, including hourly auto-sync and an optional stock workflow. Those options don’t establish what the newer connector does. Record the app name shown in your account and whether you’re migrating an existing connection.
For a Desktop proposal, record its product year, country edition and company-file host. Identify who can authorise access and which computer runs the connection. Intuit’s Web Connector instructions describe a Desktop connection mechanism. They don’t establish that an Online app supports your Desktop file.
Set the sync start boundary after identifying records already in the accounts. Intuit’s migration procedure requires a start date without overlap with previously imported data. Finish the old connection’s pending reviews before replacing it. A later start also needs an explicit plan for the unimported gap.
Verify the sales and refund records
Verify gross sales and each adjustment independently of the bank payout. Record the WooCommerce order number and its destination document ID, then trace the customer and product references. Product matching in the newer connector uses stock keeping units (SKUs) or product names.
Decide whether each imported sale is a sales receipt or an invoice with a separate payment. Record the selected payment account and which integration owns the payment entry. A bank feed deposit must match the money already recorded without creating the sale again.
The legacy setup has dedicated shipping and discount items, customer-record choices and payment-account mapping. Its refund option creates adjustment notes when the required refunded statuses are selected. Apply those instructions only to that legacy workflow. For the newer connector, use the destination refund record actually created before deciding whether a manual entry is needed.
Fictional two-order sample
Assume a fictional domestic store with tax-exclusive prices and 10% goods and services tax (GST). All amounts below are invented to show the reconciliation. They don’t establish how your own goods or processor fees are taxed.
Order A contains two items at $80 each. A $16 discount reduces product sales to $144. Shipping adds $6, so the subtotal is $150. GST is $15 and the customer pays $165.
Order B contains one $40 item with no shipping or discount. GST is $4 and the customer pays $44. The two original sales therefore total $209, including $19 GST.
One item from Order A is later returned. Its discounted value is $72, with $7.20 GST. Shipping remains charged. The partial refund is $79.20.
| Component | Amount excluding GST | GST | Customer amount |
|---|---|---|---|
| Order A after discount and shipping | $150 | $15 | $165 |
| Order B | $40 | $4 | $44 |
| Original sales combined | $190 | $19 | $209 |
| Partial refund of Order A | -$72 | -$7.20 | -$79.20 |
| Remaining sales combined | $118 | $11.80 | $129.80 |
Compare Order A’s actual shipping item and discounted product amounts with that expected result. Check the tax code as well as the total. An invoice can total $165 while assigning the wrong portion to tax or shipping.
For a manual adjustment, Intuit describes refund receipts for returned items. Its separate procedure for a refund of a paid invoice begins with an adjustment note. Choose the procedure that matches the original accounting record. Confirm the connector hasn’t already recorded the same refund before adding anything manually.
Reconcile and recover a bounded sample
Reconcile the two original sales and the partial refund against their destination records, then match the settlement. Keep the order date, refund event and bank settlement date as separate fields. Set the connection’s timezone consistently so an overnight event doesn’t appear missing from a daily comparison.
Suppose the processor deducts a fictional total fee of $5 and settles both orders and the refund together. The expected deposit is $209 minus $79.20 minus $5, or $124.80. The fee is an assumed deduction, not a quoted processing rate.
The gross customer receipts remain $209. After the refund, the customer amount retained is $129.80. The bank receives $124.80 because the processor retains $5. Intuit’s bank deposit procedure explains grouping payments and recording fees separately. Have the bookkeeper select the appropriate accounts and fee tax treatment.
A wrong reconciliation records only $124.80 as sales and leaves the original orders unexplained. The correct sample traces $209 of receipts, a $79.20 refund and the $5 fee to that deposit. The worksheet must include the original document references so it can expose equal-value duplicate entries.
These are the expected results for your isolated sample. Exercise these cases with disposable store and accounting records:
- Import Order A once, then process the same event again. Confirm one sale and the correct payment total remain. Intuit documents duplicate-prevention retries, but the destination records establish your sample’s result.
- Include an order that already has an invoice. Match the existing reference and inspect its payment before importing. Resolve the overlap instead of creating a replacement sale automatically.
- Interrupt one import and inspect both systems before retrying. Record whether the sale exists, whether payment exists and which operation failed. Retry only the missing operation through the supported workflow.
- Correct a deliberately wrong partial-refund mapping. Confirm the final refund total is $79.20 and retain the correction’s link to the original order. Check that recovery didn’t create another customer payment.
Classify differences before changing mappings. A transaction beyond the last sync boundary is a timing difference. An excluded order status is a selection difference. A record with the correct order reference but the wrong tax account is a mapping difference. Pause the affected flow until its cause is understood.
Review complete operating fit
Use the newer Intuit connection when its paid-order imports meet your needs and a named bookkeeper owns settlements and refunds. Keep a store administrator responsible for access, status filters and failed imports. Record who covers exceptions when either person is away.
Choose another supported approach if unpaid orders or automatic stock updates are requirements. A Desktop requirement needs an edition-specific assessment rather than approval based on Online documentation.
Include the accounting subscription, any connector charge and ongoing reconciliation work in the cost comparison. Intuit’s legacy connection screen uses the label “Connect free integration”. That label doesn’t price a Desktop connector, a different marketplace plugin or the retailer’s accounting subscription. Use the terms for the exact app you authorise.
Keep the permitted history boundary with the connection settings. The legacy sync-settings guide says moving its starting date later requires connector support. For migration, preserve the last reconciled reference and inspect the imported range before resuming.
Approve the connection only when the sample’s sales and refund are traceable, each payment has one owner and the deposit difference is explained. Taking customer payments on QuickBooks invoices remains a separate setup from transferring WooCommerce sales records.
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.