We're rolling out a change that accountants have requested for many years: adding the Payee field to the options in Reclassify Transactions.

Now in addition to being able to mass-reclassify fields like category/account, class, and location, you'll be able to bulk edit payee as well.

Payee edits will be available on most transactions, but there are a few exceptions. US customers with automated sales tax turned on won't be able to edit payees on sales receipts, since that could trigger unexpected tax implications. Invoices and Bills will be restricted as well, to avoid unexpected problems with A/R and A/P.

This feature is rolling out across Reclassify Transactions worldwide. If you don't see it yet, you will soon.

Pro tip: there is also a bulk reclassify feature for payee in the Posted tab of the bank feed. That feature allows you to bulk-select posted bank transactions and adjust the payee there. But that was limited to transactions that came from a bank feed, whereas the Reclassify feature we're announcing today will work for all transactions regardless of source.

Thank you to the many of you who have requested this feature over the years. Please continue to leave feedback, and let us know what you think of this latest addition!

If Intuit moved your firm from to (free plan), here’s what you need to navigate the new experience that’s built for you with feedback from accountant firms.

Your client data and settings are retained. What’s changed most is .

Use this short guide to get oriented.

In QBOA, your landing page was the Client List. In IAS, your landing page is now Home — a new, customizable dashboard.

Home gives you a centralized, high-level view of your firm. Customize it with widgets for the information you use most, and check its alerts for disconnected bank feeds, data connection issues, product updates, books close status, and more. You can also use the global search bar at the top of IAS to quickly jump to clients, tools, or pages.

Helpful: Getting started in Intuit Accountant Suite

Open Clients and make sure you can find the clients you worked with in QBOA.

To open a client’s books, use the dropdown next to your firm name at the top of IAS. Once you enter a client, you can continue working in their QuickBooks Online company as usual.

If you use Accountant tools in QBOA, look for My Menu.

My Menu is the new customizable home for the accountant tools, actions, and pages you use most often. Add your frequently used tools and bookmark important pages so you don’t have to learn the entire new navigation at once.

Helpful: Use accountant tools and features

Go to Work to see and manage work across your client portfolio.

This is where IAS brings together service-delivery tools such as Client Insights, Books Close, Tax, and Projects.

You don’t need to configure everything on day one. Just learn where Work lives and how it relates to the client work your firm already performs.

Helpful: Work related resources for the transition

Go to Firm hub for things related to your accounting practice rather than an individual client, including Manage users, ProAdvisor resources, and Integrations.

If you want guided training specifically for the transition, start with the “From QBOA to Intuit Accountant Suite” courses in ProAdvisor Academy. There are separate paths for admin/all-access users and non-admin users.

Helpful: ProAdvisor Trainings for the transition

If you’re not sure what to do after signing in, do just these five things:

Once you can do those five things, you have the basics you need to continue working.

Use Intuit’s full transition guide when you’re ready to explore more features, including Intuit Intelligence, workflows, client management, Books Close, and additional firm tools.

Read: Getting Started in Intuit Accountant Suite

Yes. If the time isn’t right, your firm can switch back to QuickBooks Online Accountant and rejoin Intuit Accountant Suite at any time. All of your data and settings are retained. Both Primary Admins and Company Admins can make this switch.

To switch back: go to (gear icon) > > > .

You know the drill: a customer payment lands in your bank feed, but it doesn't line up to the penny with the invoice. Maybe the wire came in $18 short because of a bank service charge. Maybe the customer made a partial payment, took a discount, or paid two invoices with one deposit. QuickBooks couldn't cleanly match the amounts, so you were left recording the payment manually, forcing a workaround in Advanced Match, or worse, categorizing the deposit as new income and overstating both revenue and receivables.

This update handles it right in the match flow. When a bank transaction matches one or more invoices or bills but the amounts don't agree, QuickBooks now surfaces the difference and asks one simple question: how do you want to handle it?

If the customer simply hasn't paid in full yet, choose . QuickBooks allocates the deposit across the matched invoices and leaves the remainder as an open balance on the invoice, so the receivable stays open for the customer's next payment. Nothing gets written off or miscategorized just to make a match work.

. If the gap is a merchant processing fee, bank charge, discount, or write-off, choose . Enter the adjustment amount, payee, and category (for example Merchant service fees, Bank charges, Discounts given, or Bad debt expense), and add a memo like "spoke to customer, agreed to waive $18 fee" so there's a clean audit trail. QuickBooks records the adjustment as its own transaction, closes out the invoice, and matches the bank line, all in one step.

If a customer pays more than the open balance, matching the deposit automatically creates a customer credit you can apply to a future invoice or refund. No manual credit memo needed for an overpayment.

When QuickBooks suggests a match with a difference, it explains the suggested allocation in plain language (which invoices, how much to each, and what the leftover amount appears to be), and the running totals at the bottom always show the bank amount, matched payments, resolved adjustments, and remaining difference. Nothing is pre-decided for you; you review and pick the option that fits.

This is rolling out to everyone now. Take it for a spin the next time a payment comes in a little short (or a little over) and drop your feedback in the comments!

Undo Reconciliation was limited to accountant users — so a Primary Admin on QuickBooks who made a mistake reconciling their own books was stuck waiting on their accountant, or resorting to creating a QuickBooks Online Accountant account just to work around it.

This update opens Undo Reconciliation to Primary Admins, with guardrails that match the weight of the action.

— a mistaken reconciliation no longer means waiting on outside help or spinning up a QBOA account as a workaround. The undo is right there in the reconciliation history, for the person who did the reconciling.

— undoing a reconciliation affects the beginning balance and every reconciled transaction in the period, so every user confirms an explicit acknowledgment of the consequences before anything is unwound.

— when a business has an accountant attached, the flow prompts them to check in with you before undoing.

This is now generally available.

When a reconciled account's beginning balance breaks, the Discrepancy Report is supposed to tell you why. In practice, it often didn't — the old report was vague about what actually changed, missed whole categories of changes, and left you digging through the audit log to reconstruct what happened before you could even start fixing it.

This update rebuilds the report so every discrepancy tells you who changed what, when — and gives you a suggested fix you can act on without leaving the report.

— each modified or deleted transaction now shows who made the change, what the change was, and when it happened, so you're diagnosing from facts instead of reverse-engineering the audit log.

— including cases the old report missed entirely, like voided transactions, unposted bank feed transactions, account moves in the chart of accounts, and changes to splits. If it can knock a beginning balance out, it now shows up with an explanation.

— every discrepancy comes with a clear, prescriptive suggested resolution for that specific error case, right in the Review tray. You stay in control of the books; if the change was a mistake, the right next step is already laid out.

a Review tray lets you correct the transaction in place, so resolving a discrepancy no longer means bouncing between the report, the register, and the audit log.

This is rolling out now and will reach everyone over the coming days. Give it a try the next time a beginning balance doesn't match, and let us know what you think through your comments.

If you track departments, locations, or jobs, you already know the gap: QuickBooks could predict the category on a bank transaction, but Class and Location still came in blank. That left you filling those fields by hand — transaction after transaction — whenever your reports depended on them.

This update predicts Class and Location from your own coding history — the same way we already recall categories from similar transactions — and only recommends when that history is consistent enough to trust.

— we look across up to 24 months of similar historical transactions and suggest the Class and Location you use on those patterns, so recommendations arrive closer to post-ready instead of half-filled. Class only shows as a strong suggestion when past coding is highly consistent; Location is held to an even tighter bar and a vendor-identity check. A wrong Class on a P&L-by-class report is worse than an empty field, so we leave it blank when the signal isn't there. — categorization no longer stops at the account. When the pattern is clear, Class and Location can come along too.

This is now generally available. Give it a try in the QuickBooks bank feed and let us know what you think through your comments.

Transfers should be the easy ones — money left one account and landed in another. In practice, matching often broke when more than one same-amount transfer sat in the feed. The old logic worked when exactly one pair existed; multiple cash moves, operating sweeps, or credit-card payments at the same amount meant missed matches… or a bank transfer paired to the wrong bill just because the dollars lined up.

This update shows every viable transfer pair in a ±7-day window — across bank-to-bank and credit card — and lets you pick the right one.

Surfaces all candidate pairs, not just one — when several same-amount transfers sit close together in date, you see the options and choose the correct account-to-account pair instead of getting no suggestion or a single forced guess. Covers the transfer types that break recon — bank-to-bank and credit-card transfers in that short window are included, so cash moves between accounts, operating sweeps, and card payments can reconcile cleanly. Closes a loud source of misses and wrong matches — same-amount transfers were a top matching pain point: a clear "Online Transfer to CHK…" getting matched to an unrelated bill for the same amount. Multiple suggestions cut both the miss and the mis-pair.

This is now generally available. Give it a try in the QuickBooks bank feed and let us know what you think through your comments.

Not every suggested match deserves the same click. Until now, a sure-thing bill payment and an ambiguous same-amount guess looked identical in the bank feed — no signal for which ones you could trust at a glance, so every suggestion felt like the same level of risk.

This update scores every suggested match and shows that confidence as a badge you already know from categorization: green when the evidence is strong, blue when you should take a closer look. Weaker suggestions stay out of the inline feed so your review list focuses on what actually needs judgment.

— exact amount, payee alignment, whether there's a single clear candidate, how close the dates are, how often you've accepted this pattern before, and whether the money-in or money-out type fits. The score is clear and explainable — green means strong evidence on the books, not a black-box guess. — green is high confidence (you can accept with less second-guessing); blue is medium confidence, where something is still ambiguous — a new payee, multiple candidates, or thinner history. Low-confidence noise drops out of the inline experience so it doesn't compete with the work that matters.

— the highest-confidence band is what can graduate to auto-post over time when those matches are consistently accepted, with every auto-post one-click reversible. Newer books stay conservative on purpose: without history, even a clean match rarely shows green until the pattern is proven.

This is now generally available. Give it a try in the QuickBooks bank feed and let us know what you think through your comments.

As part of the new bank feed, we released improved AI-powered categorization that is significantly more accurate than the categorization in the old version. We also released AI-powered explanations that tell you why the AI suggested what it did.

However, we've heard feedback from some of you that you'd rather not have that explanation taking up space when you click into a bank transaction to categorize and post it. So we've added a new toggle that allows you to hide the explanations. Hiding the explanations won't stop QuickBooks from continuing to make category suggestions on transactions when it is confident, but you'll no longer see the explanation taking up space.

Hiding the explanation once will hide it for all transactions, but of course you can turn the explanation on and off whenever you'd like.

Give it a try and let us know if you have any feedback!

Until now, QuickBooks only predicted the From/To field on money-out transactions. Every deposit, customer payment, and refund came into the bank feed with a blank payee — so you had to fill it in by hand, transaction after transaction. That manual entry is where duplicate customers and vendors creep in, reports drift, and the "done-for-you" promise breaks down.

This update brings AI predictions to the From/To field on money-in transactions, so deposits arrive with the right payee already suggested.

— money-in now matches to the actual customers and vendors already in your lists and fills the From/To field for you, the same way money-out transactions already do, so you're reviewing a real match instead of typing from scratch.

— money-in runs a dual lookup across both your customer and vendor lists, so a payment from a client resolves to the customer, and a refund from a supplier resolves to the right vendor — roughly 1 in 4 money-in transactions.

— by matching to payees that already exist in the books, the prediction helps you avoid creating duplicate customers and vendors and keeps your reporting clean.

This is now GA to 100% of accountants. Give it a try in the QuickBooks bank feed and let us know what you think in Bank Feed through your comments.