Tax mapping is the #1 cause of post-launch QBO sync errors. It's one dropdown — set it once, before turning on real sync, and you won't think about it again.
How it works
Run a Call calculates the tax on every invoice from your account's tax rate. When the invoice syncs, QuickBooks needs to know which QBO sales-tax code that tax belongs to — that's the mapping.
Set it up
- Settings → QuickBooks (or Settings → Integrations → QuickBooks).
- Find Sales Tax Code.
- Pick the QBO tax code that matches your jurisdiction (the dropdown lists the codes from your QBO file — e.g. California, State sales tax).
- Save.
The invoice posts to QBO with Run a Call's calculated tax amount attached to that code — the QBO total matches your total to the cent, including on milestone invoices where tax is split across the payments.
What happens if you skip it
If your account charges tax and no Sales Tax Code is selected, Run a Call refuses to sync taxed invoices rather than write wrong numbers into your books:
- Taxed invoices wait with the message "No sales-tax code selected in QuickBooks settings." Nothing incorrect reaches QBO.
- The initial bulk sync won't start until a code is picked (same as the Income Account requirement).
- The moment you pick a code and save, the waiting invoices sync automatically.
Untaxed invoices are unaffected either way.
Without this guard, a taxed invoice would land in QBO without its tax — the QBO total would silently understate, and a full payment would then overpay the QBO invoice. If you connected QBO before setting a tax code, go pick one now.
Tax-exempt customers
Invoices with no tax sync with no tax — nothing to map. If you keep tax-exempt customers, make sure their line items aren't marked taxable in Run a Call.
Verify before going live
There's no sandbox toggle — verify with a real, small invoice:
- Create a small taxable invoice and send it.
- Open the synced invoice in QBO.
- Confirm the tax line shows and the total matches Run a Call exactly.