Reliability Update
· August 2026LatestPurchase orders now save for everyone on your team, not just administrators — and a purchase order raised in QuickBooks finally reaches Salesforce on its own. Vendor sync covers your whole vendor list, customer deactivation flows both ways, and the saves that used to fail quietly now say exactly what QuickBooks told us.
Purchase orders save for everyone, not just administrators
Saving a purchase order wrote its Salesforce copy in a way that quietly demanded administrator-level access to the whole org. Anyone without it — a purchasing manager on a standard profile, or the background job that mirrors purchase orders from QuickBooks — ended up with the order created in QuickBooks, no record in Salesforce, and a message that said only that it could not be saved. Tally no longer needs that elevated access. If you widened someone’s permissions to work around this, you can safely take it back.
Learn morePurchase orders created in QuickBooks now sync to Salesforce
A purchase order raised on the QuickBooks side used to stay there — Tally listened for changes to existing orders but skipped brand-new ones, so they never appeared in Salesforce. New purchase orders now come across automatically with their line items, and re-processing the same one can’t create a duplicate.
Learn moreEvery vendor syncs, not the first 100
QuickBooks returns 100 records per request unless you ask for more, and vendor sync wasn’t asking. If your company has more than 100 vendors, the rest were never created or updated in Salesforce — which also meant purchase orders for those vendors couldn’t link correctly. Vendor sync now pages through the full list, and the same fix went into the purchase order sync, so a catch-up run reaches your most recent orders instead of only your oldest.
Deactivating a customer works, and so does turning them back on
Marking a customer inactive in QuickBooks looked like it did nothing on the Salesforce side, and un-ticking then re-ticking Active in Salesforce deactivated the customer but would never reactivate them. Two causes: QuickBooks leaves inactive customers out of the search Tally was using, so a deactivated customer simply couldn’t be found any more; and Tally wasn’t recording the version stamp QuickBooks returns after each write, so the next edit was rejected as out of date — silently. Tally now reads the customer directly by its QuickBooks id, keeps the version stamp, and surfaces a rejection instead of swallowing it. Any automation you have watching the active flag fires as expected.
Failed saves say what actually went wrong
When QuickBooks accepted a purchase order but Salesforce couldn’t save its copy, the message stopped at “could not be saved” and the diagnostic detail was thrown away before anyone could read it. The reason now travels with the message and is written to the integration log, so support can see the cause on the first report instead of asking you to reproduce it. The customer editor also no longer reports success it didn’t get — it shows what QuickBooks actually replied.
Connecting and disconnecting QuickBooks
Your QuickBooks connection lives in the Tally Hub under QuickBooks Connector. Connect once and Tally handles the rest: it keeps the connection alive on its own in the background, so you are not signed out mid-day or asked to reauthorize every hour. The page tells you whether the org is currently connected rather than leaving you to guess.
Learn moreDisconnecting actually disconnects
Disconnect does the full job rather than just forgetting the connection locally. Tally revokes the access with Intuit, removes the stored credentials from your org, and stops the background job that keeps the connection refreshed. Nothing is left running against your QuickBooks company, and you can reconnect whenever you are ready.
Upgrading from an earlier version
This is a patch, so installing it over your current version keeps your settings, mappings, and history exactly as they are. There is nothing to reconfigure and no need to reconnect QuickBooks.
