Resolving an order exception

An order exception means TruSync found something on the order it couldn’t map automatically. Here’s how to clear one.

Find out what’s unmapped

Open Order Exceptions and open the specific exception — it tells you whether the issue is a payment method, a tax jurisdiction, or a product.

Resolve by type

• Unmapped payment method — go to Settings → Payments for that store and map the payment method to a QuickBooks payment method.
• Unmapped tax jurisdiction — go to Settings → Tax for that store and map the jurisdiction to a QuickBooks tax rate.
• Unmapped product — go to Settings → Products for that store and map the product to a QuickBooks item.

Once the mapping exists, TruSync syncs the order — you don’t need to do anything to the exception itself.

If an exception won’t clear

• Double check you mapped the exact payment method, jurisdiction, or product name shown on the exception — a similarly-named mapping won’t match.
• Confirm your store and QuickBooks connections are both active; a lapsed connection can leave exceptions unresolved even after mapping.

FAQ

Why doesn’t TruSync just pick the closest existing mapping? Auto-mapping to a default causes rework later when an order lands in the wrong QuickBooks account — TruSync would rather wait for an explicit mapping than guess.

Will new orders with the same payment method also become exceptions? No — once you’ve mapped it, future orders using that payment method sync normally.

Can more than one exception share the same fix? Yes — mapping one payment method, jurisdiction, or product often clears every exception caused by it at once.