Connect QuickBooks

Common issues

• "Vendor unresolved." Open the document and pick or create the QuickBooks vendor. After this, Tally remembers — same vendor name in future documents auto-matches.
• "GL mapping missing." Tally has a category for the document but no QuickBooks account assigned to it. Open GL Mappings, pick the right account for that category, save.
• "Push failed: account is inactive." The QBO account is set to inactive. Either reactivate it in QuickBooks or pick a different account in your GL mapping.
• "Push failed: token expired" or "reauthorize required." Open Settings → Connections and reconnect QuickBooks. The token refresh sometimes needs to be re-confirmed (Intuit's policy, not Tally's).
• "I pushed a document but it's not in QuickBooks." Refresh QuickBooks — sometimes there's a delay. If still missing after a minute, check the push history in Tally for the QBO Bill ID and search QuickBooks for that ID directly.
• "My plan doesn't show the Push button." QuickBooks push is available on Starter and above. See Plans and billing.

If you're a bookkeeper

You can guide your client through the connection in two ways:

1. Client-initiated — the client signs in to their Tally portal and connects QuickBooks themselves. This is the default path; the client owns the credentials and the audit trail of the connection event.
2. You walking the client through it on a call — share-screen, watch them click Connect, and verify the connection lands.

Once connected, you (with the right access level) can use the connection on the client's behalf — push, preview, resolve vendors, fix mappings. The connection itself stays anchored to the client's workspace.

If you're a bookkeeper helping a client

• The client connected QBO but I can't push for them. Make sure your access level for that client is "review" or "full" — view-only access doesn't include push permission.
• The client's QBO has different accounts than I expected. GL mappings are per-client. Pull up that client's GL Mappings page (not your firm's) and set the mapping there.
• A client's books look right in Tally but the QBO Bill is wrong. Compare the push preview to the actual QBO Bill in case a manual edit happened in QBO afterwards. Tally never changes QBO records after the initial push.

If you're a small business owner

1. Open Settings → Connections → QuickBooks.
2. Click Connect QuickBooks.
3. You'll be redirected to Intuit to sign in and authorize Tally for the right QuickBooks company.
4. After authorization, you're back in Tally with the connection active.

The connection covers a single QuickBooks company per Tally workspace. Tally never sees your Intuit password; the authorization gives Tally a scoped token she renews automatically.

Mapping categories to QuickBooks accounts

When you connect QuickBooks, Tally pulls in your Chart of Accounts. You then tell her which Tally category maps to which QBO account:

• "Office Supplies" → "6201 Office Supplies"
• "Software Subscriptions" → "6510 Software & Subscriptions"
• "Meals & Entertainment" → "6310 Meals 50%"

You can do this in two ways:

• Bulk — open the GL Mappings page and set everything in one sitting before your first push.
• Per-document — leave mappings open and resolve them when a document needs one. Tally remembers your choice; you only do each mapping once.

For firms: GL mappings live per-client. Each client's QBO has its own Chart of Accounts, so each client gets its own mapping — they don't bleed across.

Pushing — preview, then commit

Before any document hits QuickBooks, you see a preview:

• The Tally fields (vendor, amount, date, category, line items).
• The QuickBooks Bill that would be created (vendor record, account, amount, line items, memo).
• Anything Tally flagged as a problem (missing GL mapping, vendor not resolved).

You commit the push. Tally:

1. Creates the Bill in QuickBooks.
2. Stamps the document with the QBO Bill ID and a timestamp so the same document can never be pushed twice (idempotency).
3. Adds an entry to the push history page so you can see what's gone through.

If something fails (QBO is down, the company is locked, a field is rejected), Tally shows you the QBO error message verbatim so you know what to fix. The document stays in the "ready to push" state.

Resolving vendors

QuickBooks tracks vendors as their own records. Tally tries to match every document to a QBO vendor automatically (by exact name, then by close match). When she can't:

• Open the document.
• In the QuickBooks panel, pick the right QBO vendor from the dropdown — or click Create new vendor in QuickBooks to add it directly.
• Tally remembers the match. The next document from that vendor goes through automatically.

If you're a bookkeeper resolving a vendor on a client's behalf, the new QBO vendor is created inside the client's QuickBooks (using the connection they authorized). You don't get prompted in your own QBO.

What gets pushed

• Bills for reviewed expense documents (invoices and receipts).
• Line items preserved when extracted cleanly.
• Vendor + account + amount + date + memo populated from the document.
• A PrivateNote stamp identifying that Tally created the Bill (so it never gets re-pushed even if you retry).

What doesn't push:

• Documents that aren't approved yet — push is downstream of review.
• Documents missing a resolved vendor or category.
• Anything that would create a duplicate Bill (Tally checks the PrivateNote stamp before creating).

What's next

• Documents — review and approve
• Bank feed — bring transactions in automatically alongside QBO
• Bookkeeper workspace — push activity rolls up to your Command Center
• Troubleshooting — when QBO push goes sideways

What you'll do

• Connect a QuickBooks Online company to Tally.
• Map the categories Tally uses to your QuickBooks accounts.
• Resolve vendors so each document lines up with the right QBO vendor record.
• Preview a push and commit it.
• Spot and fix common blockers (missing vendor, missing GL mapping, plan availability).