Mapping settings

Mapping settings tell TruSync how to translate your store’s data into QuickBooks terms. There are three kinds.

Customer mapping

TruSync maps every order from a store to a single QuickBooks customer, chosen when you set up the store — it doesn’t create a separate QuickBooks customer per shopper.

Payment method mapping

Each payment method your store offers needs a matching QuickBooks payment method. Orders using an unmapped payment method become an order exception rather than posting with a guessed mapping — TruSync never auto-maps a payment method to a default. This step only applies to stores where payment methods matter; marketplace stores like Amazon and eBay skip it, since Invoices don’t carry a payment method.

Tax jurisdiction mapping

Sales tax works differently than the other two: TruSync controls the tax amount on each order (using your store’s own tax calculation), but the destination account the tax lands in is determined by which QuickBooks tax rate you map a jurisdiction to. Each QuickBooks tax rate is tied to a tax agency, and that agency owns the liability account — TruSync doesn’t set a liability account directly. Mapping a jurisdiction to the right tax rate is what routes the money correctly.

This step only appears for stores where you handle sales tax yourself. Marketplace stores skip it, since the marketplace already collects and remits tax as a facilitator.

FAQ

Can I map more than one payment method to the same QuickBooks payment method? Yes, if that’s how you want them grouped in QuickBooks.

What happens if I don’t map a tax jurisdiction? Orders from that jurisdiction become an order exception until you map it.

Should I turn on QuickBooks’ automated sales tax calculation? No — TruSync already calculates tax using your store’s own tax engine and tells QuickBooks not to recalculate it. Turning on QuickBooks’ automated calculation on top of that would double up the tax logic.