What's newin Tally for QuickBooks

When someone creates an estimate directly in QuickBooks, Tally now adds it to Salesforce automatically — with its number, dates, status, totals, addresses and line items — under the customer’s Account. If the QuickBooks customer isn’t in Salesforce yet, Tally brings the customer over first. Estimates that were only ever updated in QuickBooks are picked up too, and quantities like 1.5 are handled correctly.

Deleting an estimate or invoice in QuickBooks now removes the Salesforce copy instead of leaving an orphan behind. Before anything is removed, Tally confirms with QuickBooks that the record is really deleted, and removed records go to the Salesforce Recycle Bin. An invoice with payment history in Salesforce is kept and marked “Deleted” — excluded from balances and filters — so no payment records are lost.

Add a vendor without switching to QuickBooks. Click “+ New vendor” in the purchase order builder or on the Tally Hub vendors page, enter the company, contact and address, and Tally creates the vendor in QuickBooks first, then adds it to Salesforce. If QuickBooks rejects the name — display names must be unique across vendors, customers and employees — you see exactly why, and your entries stay put.

A vendor created from the purchase order builder is selected for you, with its email and address already filled in, so you can carry straight on with the order.

Invoice, estimate, sales receipt and purchase order views were rebuilt with clear status pills, a prominent balance or total, and tidy sections for details, line items, payments and totals. The Receive Payment window, the Tally Hub, the settings pages and the sync pages now share the same look, with helpful empty states instead of blank space. Invoice rows keep their buttons on one line in narrow page layouts.

Saving no longer waits on artificial pauses of several seconds — you see the result as soon as QuickBooks responds, with progress shown right on the button. Error messages now explain what went wrong instead of “Something went wrong”. Voiding an invoice reports QuickBooks’ real answer, and the Void, Send Reminder and PDF actions confirm success or explain a failure instead of closing silently.

Adding a new bank account during Receive Payment now charges the new account instead of the saved one. Voiding a sales receipt from its menu works again, purchase order ship-to addresses show every address line, card numbers are visible while typing in the payment method form, and invoice views refresh correctly after saving.

No setup is required for estimate and delete syncing — they use your existing QuickBooks webhook. To let non-admin users create vendors, make sure they have the updated QB Tally Permissions permission set.

Use the new QuickBooks Settings action on a Salesforce Product to select its Income Account from your synced chart of accounts. Inventory products also support an Inventory Asset Account. Your selections are used when creating a QuickBooks item or updating an existing one, following your product sync settings.

Check “I purchase this from a vendor” to enter purchase cost, purchase description, Expense Account, and Preferred Vendor. Search vendors by their display or company name. Tally checks account types and inactive references before saving; inventory products require the appropriate cost-of-goods-sold and asset accounts.

Updating unrelated product information preserves existing QuickBooks accounting details. Accounting-only edits preserve current QuickBooks stock quantities, and account changes do not request recategorization of historical transactions. Pending accounting edits remain available after a failed sync and are protected from incoming updates while waiting to be sent.

Invoice saves keep QuickBooks’ rejection details and your draft, and bring the error into view. When a rejection reports an inactive reference, Tally checks the referenced items and customer and names those it can confirm are inactive. If a timeout leaves the result uncertain, the message asks you to check QuickBooks before retrying. Flow invoice creation also returns the rejection details.

Saving mapping edits now checks for changes made since you loaded the page, prevents duplicate product creation within a batch, and preserves deliberately shared mappings. Conflict resolution includes the products already linked to an item. Successful rows are recognized even if another request fails, while failed changes remain available to correct and retry. Inactive items and searches containing apostrophes are handled correctly.

Filters and buttons wrap cleanly inside narrow Salesforce panels, including pages with an Activity sidebar. Invoice lists and product lines become labeled cards when space is tight. Invoice fields, totals, attachments, and creation buttons reflow to stay readable as you resize the window.

Invoices created from Salesforce Flow now resolve the current QuickBooks mapping from the selected Salesforce product, even when the Flow supplies only the product record ID. Unmapped lines without an explicit QuickBooks item ID are rejected with an explanation instead of letting QuickBooks substitute its default service item.

Recurring billing checks the start date, end date, and occurrence limit before creating the next invoice. New recurring invoices also start with their own transaction identity and payment state instead of inheriting those details from the previous invoice.

Payment sync totals the amounts actually allocated to an invoice and keeps unapplied money separate. Removing a payment recalculates linked Salesforce invoice copies. Voiding reads the current QuickBooks invoice version first, and incoming notifications for a different QuickBooks company are ignored.

Percentage discounts now calculate correctly in invoice, estimate, and sales-receipt requests. Estimate requests include the entered billing and shipping addresses, and address fields retain their correct city, state, and country values in the affected Flow and document paths. Sales-receipt forms retain rejected drafts and prevent repeat saves while a request is running. Generating invoice, estimate, or sales-receipt PDFs preserves other Salesforce files with the same title, including when a download fails.

On existing installations, your Salesforce administrator should add the QuickBooks Settings action or the new accounting fields to your Product page layout and ensure users have the updated QB Tally Permissions permission set. Refresh or verify the synced accounts and vendors for your connected QuickBooks company before selecting them. Automatic product updates require Salesforce-to-QuickBooks product sync to be enabled; installing this release does not turn it on for you.

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.

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.

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.

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.

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.

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.

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.

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.

The Sync Products hub now includes a live, side-by-side view: every QuickBooks item on the left, the Salesforce product it's linked to on the right. Color-coded tiles total up what's mapped, suggested, unmapped, and conflicting, and one filter jumps straight to the rows that need attention — no more exporting both catalogs to a spreadsheet to compare them.

A new choice at the top of Sync Settings. “Map products myself” is built for established Salesforce orgs that already have a product catalog: your QuickBooks items load side by side with automatic suggestions, and sync never creates or re-links a product on its own. “Auto-match & create” is for brand-new orgs with no products yet (or far fewer than QuickBooks) — Tally builds and maintains the Salesforce catalog automatically using your matching strategy. Switch anytime; the settings page reshapes itself around your choice.

When a QuickBooks item and an unlinked Salesforce product share a name or SKU, Tally pre-fills the match in amber and waits for you. One click on Accept links them. Nothing is ever linked behind your back, so a coincidental name can never quietly merge the wrong products.

Open any row and search your Salesforce catalog by name or SKU. Every result shows its link status before you pick, and products already linked to another QuickBooks item appear disabled with the reason — you always know why an option is off the table. And when sharing is the point, a deliberate override toggle unlocks those options and spells out exactly what will happen — for example, that two Salesforce products will now sell the same QuickBooks item — before anything saves.

QuickBooks has an item Salesforce doesn't? No pre-sync required — your QuickBooks catalog is already loaded on screen, so Create in SF stages the product from those details (name, SKU, type, price) and builds it when you save, with the QuickBooks link stamped from the very first moment. No half-created products, no cleanup pass later.

If two Salesforce products ever ended up linked to the same QuickBooks item, the row turns red and shows every claimant. Pick the one that should win and Tally unlinks the rest — dirty data you may not have known you had, resolved in seconds.

Edits stage on screen with a running count on the Save button, then write in one batch. Every row reports back individually — successes turn green in place, failures show the reason in plain English right on the row. And if a sync job changed a mapping while you worked, Tally rejects just that row instead of silently overwriting it.

Sync Products is now organized into three tabs — Sync Settings up front, with Product Mapping and Sync Health one click away — so setup, mapping, and monitoring each get a full page instead of sharing one long scroll.

The Receive Payment modal gained a Cash / Check / Other option: pick a payment method straight from your QuickBooks company, stamp the date and check number, and the invoice flips to Paid in both systems — nothing is charged.

Automate full or partial payments with the method and reference stamped in both systems. Bulk-safe by design — one Flow run can record payments across hundreds of invoices — and overpayments are rejected instead of stranding credits in QuickBooks.

The Tally Hub now shows your catalog's health at a glance — linked, pending, and failed counts with last-sync time. Every failed product carries the reason in plain English and what to do about it.

Full pagination for catalogs beyond 1,000 items, fractional quantities, automatic deactivation when items retire in QuickBooks, and bulk-safe exports that don't trip platform limits.

The builder catches a missing vendor, empty lines, or a missing vendor email before anything leaves Salesforce — and Save and Send now emails the vendor every time, attachments or not.

When QuickBooks rejects something — an inactive customer, an expired connection, a duplicate document number, closed books — Tally now shows the real reason and the fix, everywhere: invoices, payments, purchase orders, and product sync.