The Intuit Enterprise Suite Summer Release goes live on August 12, 2026. Every feature in this rollout is now available directly in product. This release adds real depth in two areas. It changes how you report on your business, and how fast you can close the books across entities. That matters for businesses running multiple entities, tracking project profitability, or managing inventory across locations. It also introduces smaller updates across multi-entity operations, projects, inventory, AI, business intelligence, single sign-on, and workforce management. For background on the platform, see what Intuit Enterprise Suite is and who it is built for and Intuit’s own product overview.

Release Highlight: Reporting That Finally Matches How Your Business Runs

More Updates Across Intuit Enterprise Suite

Multi-entity

Multi-entity operations pick up Cross-Company Bill Payment. It lets a business record a bill payment in one entity using a bank account that belongs to another. The intercompany accounting is handled automatically. Multi-level entity hierarchies, introduced last spring for consolidated reporting, now extend into KPIs and dashboards as a beta feature. Multi-currency management is also getting a significant upgrade in beta. Exchange rates are now managed in a single protected table. Businesses get clearer visibility into how rate changes affect transactions, plus automatic unrealized gain and loss calculations. That multi-currency beta is currently limited to organizations with a U.S. dollar functional currency, with support for international currencies expected this fall. These additions build on the multi-entity hub and hierarchy work from the Intuit Enterprise Suite Spring 2026 release, continuing a pattern of quarterly investment in cross-entity operations.

Projects

Project-based businesses gain two new reports: Open Purchase Orders by Project and Project Costs by Vendor. Users can also apply dimension filtering directly on project reports. Ship-to addresses on purchase orders now default automatically to a project’s site address, and payroll can be split across projects. A beta feature for project-specific user permissions will let businesses restrict project manager access to only their assigned projects. AI suggests assignments where a company has multiple managers and projects in play.

Inventory

Units of Measure let businesses order, receive, and sell the same item in different quantities, such as the case, the pack, or the individual unit. No more forcing every transaction into a single measurement. Invoices now also support multiple shipping addresses per customer. Users can select from a saved list instead of retyping an address each time a customer orders to a different location.

AI

Intuit Intelligence is expanding with a new natural-language chat interface in beta. Users can ask questions and generate insights across entities without building a custom report first. Chart of Accounts standardization now supports applying a standard structure to a subset of entities rather than the whole organization. Businesses migrating from QuickBooks Online or QuickBooks Desktop also gain a beta tool. It suggests how to reclassify existing Locations or Custom Fields into dimensions, based on prior transaction history.

Business Intelligence

Business Intelligence tools are also getting sharper. The KPI scorecard now supports Class and Dimension filters, along with drill-down access into any individual metric. Management reports in the consolidated view can generate AI-written executive summaries. They also include smart chips that update automatically as underlying data changes. Multi-level grouping now supports up to six nested dimensions with drag-and-drop reordering. Two beta features, multi-dimension Display By reports and multi-dimensional pivots, allow deeper cross-tabulation directly in the platform, with no need to export to a spreadsheet.

Single sign-on

Single sign-on support now allows businesses to provision and manage Intuit Enterprise Suite access through Google, Okta, or EntraID. Access is revoked automatically the moment an employee leaves the company.

Workforce Solutions

Workforce Solutions adds dimension integration with Time and Payroll in beta. Payroll admins can split paychecks across dimension values. A beta custom report builder for Payroll is also included.

Private equity firms are sitting on close to $1.1 trillion in dry powder in the United States, and after several slower years, 2026 is shaping up as a year of real deployment. According to Cherry Bekaert’s 2026 private equity outlook, aggregate deal value crossed $1 trillion in 2025 for only the second time on record, and lower borrowing costs are expected to carry that momentum forward. For a business owner weighing a sale, that sounds like good news. It is, but only for the right kind of company.

PwC’s midyear 2026 deals outlook found that buyers are increasingly rewarding businesses with durable, demonstrated growth rather than speculative upside, and the middle market has grown less forgiving of the gap between what a seller believes a business is worth and what a buyer’s due diligence team can actually support. Sponsors have capital to deploy and more competing opportunities than they can act on, and they walk away quickly the moment a data room raises more questions than it answers.

What private equity buyers evaluate, underneath the deal terminology, comes down to two questions: how much risk is hiding in the numbers, and how much growth is realistically ahead. Private equity accounting, done well ahead of a sale process, is what answers the first question before a buyer ever has to raise it. The companies that earn premium valuations tend to share one trait long before a deal is ever discussed. They operate as though a buyer could walk through the door tomorrow, because for the ones who prepare early, eventually one does.

Run the Business Like It Is Always for Sale

The biggest mindset shift a business owner can make has little to do with accounting software or reporting templates. It comes down to a decision, made well before a sale is on the table, to run the company as though due diligence could begin next quarter.

In practice, that means closing the books on a monthly cadence instead of catching up every quarter, documenting the reasoning behind pricing decisions, vendor contracts, and compensation instead of keeping that knowledge with the owner alone, and separating personal expenses from the business rather than running them through it. A buyer’s advisors will find those expenses eventually, and every dollar they flag gets subtracted from the number used to calculate value.

Owners who hold themselves to this standard tend to notice something else along the way. The business gets healthier and more profitable, independent of any future transaction. Clean financials surface problems early. Documented processes reduce the business’s dependency on any one person’s memory. None of it requires an active sale process to pay off.

The alternative is expensive. A rushed cleanup effort in the final six months before a deal, once a business is already mid-process, means reconstructing records under deadline, explaining gaps to a skeptical buyer, and negotiating from a weaker position because the seller needs the deal to close more than the buyer needs it to happen. Sponsors read that urgency in the data room, and it shows up in the price.

If one factor kills more deals or compresses more multiples than anything else, it is the state of the books. Research from CLA’s transaction advisory practice found that quality of earnings issues and discrepancies in earnings before interest, taxes, depreciation, and amortization (EBITDA) uncovered during diligence, together, account for nearly half of failed transactions, ahead of financing problems or a change of heart on either side of the table. Roughly one in three signed letters of intent never reaches a closing, and accounting is usually the reason.

Private equity accounting is less a one-time clean-up project than a standard the business holds itself to every month. Private equity firms scrutinize financials before almost anything else because financials are the input to every other decision they make. The purchase price, the debt structure, and the earnout terms all trace back to a number the buyer’s diligence team has to trust. A business that cannot produce clean, consistent financials is asking a sponsor to underwrite a guess.

One of the more consequential decisions many owners face along the way is whether to remain on cash basis accounting or move to accrual. Cash basis books record revenue and expenses when money changes hands, which is simple but distorts the timing of both. Accrual accounting matches revenue to the period it was earned and expenses to the period they were incurred, which is what most buyers and their lenders expect to see, and what a quality of earnings analysis is built to evaluate. Making that switch well before a sale process begins, rather than converting historical records under deadline, keeps the transition itself from becoming a red flag.

The payoff for clean, timely financials goes beyond avoiding trouble. A business that can produce audit-ready records on short notice expands its own buyer pool, because more sponsors and lenders are willing to move quickly on it, and a wider pool of interested buyers is what creates real competition for a deal. Whether a given business needs a full audit or a lighter review depends on its size, its industry, and what a particular buyer’s lenders require, and that question is worth a direct conversation with an accounting partner rather than a guess. Cleaning up historical books before that conversation happens tends to shorten it considerably.

The red flags that trigger a re-trade or a walked deal stay fairly consistent across industries: revenue recognized before it is actually earned, expenses capitalized instead of recorded when incurred, sub-ledgers that will not reconcile to the financial statements, and reported earnings that outpace operating cash flow. That last item is worth checking before a buyer ever does. Analysts often compare cash flow from operations to net income as a quick test, and a ratio that sits consistently below 1.0 tends to raise questions about whether the earnings are as real as they look on paper.

What a Larger Buyer Pool Means for the Deal

Clean financials and clear KPIs do more than pass a diligence checklist. They widen the field of buyers who can seriously consider a business, and a wider field is what creates competitive tension.

Strategic buyers and financial buyers look at the same data room with different questions in mind. A strategic acquirer wants to understand how the target fits an existing operation and what a combined entity looks like. A financial buyer, private equity among them, wants to understand standalone performance, the path to further growth under new ownership, and how the numbers support the debt structure the deal will likely carry. A business with organized, well-documented financials can answer both sets of questions from the same data set, without reformatting everything for each new prospective buyer.

When multiple bidders are seriously evaluating a deal at the same time, sellers hold real negotiating power on price and terms. When only one buyer is engaged, that power tends to evaporate. Financial clarity also determines how quickly a process moves. A business that can answer diligence questions in days rather than weeks keeps a competitive process alive. One that cannot tends to lose bidders to fatigue before the process ever resolves.

The chart of accounts is the spine of your financial reporting system. Get the migration right and Intuit Enterprise Suite delivers on its promise of dimensional, multi-entity, audit-ready reporting. Get it wrong and you will spend the next two years apologizing to the board for inconsistent comparatives, broken dashboards, and reports that do not tie.

Most teams default to lift-and-shift. It is the wrong default.

Your chart of accounts migration is the single best opportunity to fix structural problems that have been silently degrading your reporting for years. This guide walks through exactly how to do it: design principles, a five-step migration framework, dimension architecture, and the strategies that preserve historical comparability so your first quarterly report in Intuit Enterprise Suite does not come with a footnote.

Why the COA Migration Is the Highest-Leverage Decision in the Project

Every transaction flows through the chart of accounts. Every report, every dashboard, every integration, every audit schedule pulls from the same structure. That is not an exaggeration. It means the COA migration decision ripples into every corner of your Intuit Enterprise Suite implementation.

Mistakes are expensive to undo after go-live. A post-launch COA restructure is not just a cleanup project. It triggers reporting comparability gaps, requires re-mapping of historical data, and forces you to rebuild any dashboards or integrations that relied on the original account structure. The cost of a rebuild is typically three to five times the cost of doing it correctly the first time.

This is the one decision an implementation partner should never let a client rush. At Out of the Box Technology, we have seen it done well and we have seen it done poorly. The difference shows up within the first reporting period.

The First Principle: Do Not Lift and Shift

This is the central argument of this article, and it is worth stating plainly: do not migrate your existing chart of accounts verbatim into Intuit Enterprise Suite.

Most QuickBooks Desktop and QuickBooks Online Advanced charts of accounts have accumulated 10 to 20 or more years of additions that no longer reflect how the business actually operates. What you are looking at is a living document of every workaround, every new hire’s personal preference, and every one-off reporting request anyone ever made.

The patterns are consistent across clients. A 200-account COA where only 50 accounts have any activity in the last 12 months. Sub-accounts used to track things that dimensions should track. Revenue accounts proliferated per customer because there was no better way to slice the data. Expense accounts that are multiplied per vendor for the same reason.

None of that needs to follow you into Intuit Enterprise Suite. The migration is the cheapest time to clean it up. After go-live, every cleanup creates a reporting comparability gap that you will have to explain. Before go-live, it is just good design.

The Intuit Enterprise Suite COA Model: What Is Different

Before designing your new chart of accounts, it helps to understand what changed in the underlying architecture. Intuit Enterprise Suite is not QuickBooks with more users. The data model is meaningfully different in ways that change how a well-designed COA should look.

Native Multi-Entity Support

Intuit Enterprise Suite supports a single shared chart of accounts across multiple entities, with per-entity overrides where needed. This alone eliminates one of the most painful structural problems in multi-entity QuickBooks environments: parallel files with diverging account numbering that makes consolidated reporting a manual exercise. A well-designed Intuit Enterprise Suite COA treats the multi-entity structure from the start, not as an afterthought.

Dimensions Replace Class and Location Proliferation

In QuickBooks Desktop and QuickBooks Online Advanced, classes and locations carried most of the burden of segment reporting. The problem is that they can only stack in limited ways. Teams compensated by creating more accounts.

Intuit Enterprise Suite dimensions change the equation. You can track by region and by project and by department simultaneously, without any of that complexity landing in the chart of accounts itself. If your current COA has accounts that exist purely to slice data, those accounts are almost certainly dimension candidates in Intuit Enterprise Suite.

Account Hierarchy Depth

Intuit Enterprise Suite supports multiple levels of parent-child account hierarchy. More depth is not automatically better. The accounts that matter are the ones that reflect how your business actually generates revenue and incurs costs. Discipline in hierarchy design matters more than depth.

Calculated Fields and Business Intelligence Dimensions

Some reporting needs that previously required a new account can now be served by calculated fields or BI-level aggregations. This is another reason the lift-and-shift approach underserves the platform. An account that existed in QuickBooks to produce a specific line in a management report may not need to be an account at all in Intuit Enterprise Suite.

The Five-Step Chart of Accounts Migration Framework

Step 1: Inventory and Audit the Current COA

Pull every account in your current system with three pieces of information: last-12-month activity, current balance, and a written description of what each account is actually used for. Do not rely on account names alone. Account names in legacy systems are notoriously imprecise.

This exercise is diagnostic. Most clients discover that a significant portion of their accounts have no activity, no balance, and no clear owner. That is a signal, not a surprise.

If your team cannot produce a clear written description for every active account, that is also a signal. Undocumented accounts are accounts with unclear ownership and unclear reporting purpose. They are candidates for consolidation.

Step 2: Decide What Is a Dimension and What Is an Account

This is the most consequential design decision in the migration, and there is a reliable heuristic for making it: if you want to see it on the profit and loss statement as its own line, it is likely an account. If you want to filter or slice the P&L by it, it is likely a dimension.

Customer, project, location, department, and region are almost always dimensions in Intuit Enterprise Suite. If your current COA has accounts segmented by any of those categories, they belong in the dimension structure, not the account list.

Revenue segmented by product line or service type is typically an account question. Revenue segmented by which sales rep closed the deal is a dimension question.

Step 3: Design the Target COA

With the inventory complete and the dimension decisions made, design the target structure. This includes an account numbering scheme, a documented parent-child hierarchy, and account naming conventions that a new controller could understand without a decoder ring. Numbering conventions are customized to the business, but the principle is consistent: logical groupings with enough numeric space between ranges to accommodate future additions without forcing a full renumber.

Document everything. The decisions you make here will outlast everyone on the implementation team.

Step 4: Build the Mapping Document

Every legacy account needs a migration decision documented before a single transaction moves. There are three possible outcomes for each account: it maps to a target account, it maps to a target account plus a dimension combination, or it is sunset with no activity going forward.

No legacy account should be unmapped. An unmapped account is a decision deferred to go-live week, which is exactly when you do not want to be making COA design decisions under pressure.

The mapping document becomes the source of truth for data migration, historical data conversion, and any future audit or regulatory inquiry about why accounts changed.

Step 5: Validate Against Historical Reports

Before go-live, re-run last year’s profit and loss statement and balance sheet using the new mapping. If the totals tie and the roll-ups match the original reports, the design is sound. If they do not, you have a mapping error to debug in a controlled environment rather than a reporting discrepancy to explain after your first month close.

This validation step is non-negotiable. It is the difference between a confident go-live and a go-live with an asterisk. For a broader look at what a well-run implementation involves, see our Intuit Enterprise Suite implementation best practices guide.