Intuit Enterprise Suite Multi-Entity Features, Explained

Intuit Enterprise Suite (IES) is Intuit's product for companies that outgrew QuickBooks Online Advanced but do not want a full ERP implementation. The clearest way to understand what it is: it takes the parts of multi-entity accounting that firms currently handle in spreadsheets, and moves them inside the ledger.

Most of that work falls into three buckets. Getting transactions posted correctly across entities. Getting eliminations right so consolidated reports mean something. Slicing the results by something other than the chart of accounts. IES has a feature for each, and Intuit shipped a round of updates to all three in August 2026, described at its monthly "In the Know" session on August 20.

Here is what each feature does, what it replaces, and where it still has edges.

Intercompany journal entries, with the due to and due from filled in

An intercompany journal entry in IES posts to more than one entity at once. That part is not new. The tedious part has always been the balancing act: every entity you touch needs a due to or due from line pointing at the entity on the other side of the transaction, plus the right contact and partner company on each row so the entry can be eliminated later.

The August release automates that. You enter only the business side of the entry, the part you actually care about, meaning the P&L lines or the cash movement, and you pick which companies are involved. A smart complete action then reads the entry and generates the intercompany rows for you, including the contacts and the partner company assignment.

There is a setup cost. The system has to know which account to use for the due to and due from on each entity, so the mapping has to exist before autocomplete has anything to work from. Once it does, the saving scales with entity count. Two entities is a rounding error. Fifteen entities that transact with each other is the difference between a five-minute entry and a forty-minute one.

Cross-company bill pay

A common cash management pattern: the bill lands on entity A, but entity B is the one with money in the bank. Handled manually, that is a bill, a payment from the wrong entity, a journal entry to record the loan between them, and an elimination entry at consolidation.

IES now handles it as one action. On the bill itself you choose which company pays it and which of that company's bank accounts the money leaves from. The intercompany balances get written on both sides automatically, and the elimination entry needed for consolidation is generated too. You can have that elimination post automatically, or hold it for review first, which is the setting most firms will want for the first month or two.

Templates for repeating journal entries and allocations

Recurring intercompany entries and dynamic allocations have the same problem: they are structurally identical every period, but somebody rebuilds them by hand anyway.

You can now save either one as a template with the allocation logic and line detail already in it, then use that template two ways. Call it up on demand when you need it, or attach a schedule so it posts on its own each month or quarter. If you run management-fee allocations, shared-overhead pushdowns, or a standing intercompany charge, this is the feature that pays for itself first.

Intercompany sales mapping

Intercompany sales have been in IES for a while, and the friction was always on the receiving side. The selling entity raised the invoice, and somebody had to decide what the matching bill on the buying entity should be coded to.

That mapping is now explicit. You map the product or service on the selling side to the expense category the buying entity should use, so when you select an intercompany vendor on the bill, the category populates itself. As with the other features, you choose whether it posts automatically or waits for review. Intuit noted that most customers using it have moved to auto-post, which tells you something about how much manual review those entries were really getting.

Dimensions caught up with classes

Dimensions are the IES answer to classes and locations: more of them, nested, and reportable. The catch since launch has been coverage. Anything you could do with a class, you could not necessarily do with a dimension, which made dimensions hard to commit to.

Three changes in the August release close most of that gap.

• Project reports now support dimensions in general availability, not just beta, so you can filter and pivot project reporting by dimension using the custom report builder.
• Dimensions can now be set at the transaction header level instead of only line by line, which matters for any transaction where every line carries the same dimension value.
• Dimension list items can be reparented, so a value filed under the wrong dimension can be moved rather than deleted and rebuilt.

Intuit's own framing is that dimensions are now available on nearly all of the reports where classes are available. Nearly is doing some work in that sentence, so if a specific report is load-bearing for one of your clients, check that report before you migrate them off classes.

If you are still on QuickBooks Online and weighing the same problem, the class and location equivalents are covered in Profit and Loss by class, Profit and Loss by location, and Balance Sheet by class.

Proportionate consolidation, with a caveat worth repeating

Partial ownership is where multi-entity reporting usually breaks. IES supports proportionate consolidation through custom ownership structures, so a 40 percent owned entity can flow into the consolidated report at 40 percent.

Two things to know. It is in early access rather than general availability at the time of writing, and Intuit is explicit that this treatment is not necessarily GAAP compliant. It exists because management reporting and financial reporting are different jobs and firms kept asking for the first one. Use it for internal reporting and keep the statutory treatment separate.

How to get into the early access features

Several of the items above live behind Intuit's early access program. Opting in is done per company file: open the gear menu, choose early access, read the terms on the landing page, and opt in. Intuit quotes up to three days for access to take effect, though in practice it is usually much faster.

A subset of features carries an extra requirement and cannot be self-enabled. Multicurrency is the current example. Those need your customer success manager to turn them on, because eligibility depends on how the account is configured. If a feature you expected does not appear after opting in, that is the likely reason.

You may not need Intuit Enterprise Suite to get a consolidated report

Every feature above improves what happens inside the ledger. That is a real gain, and for some groups it is the whole reason to move.

It is also worth separating from the thing most firms actually came looking for. Ask a controller why they are evaluating IES and the answer is usually a report: one P&L that covers all the entities, updated monthly, that the owner or the bank will accept. Automated intercompany posting is how IES gets there. It is not the only way to get there.

What IES costs

Intuit does not publish list pricing for Intuit Enterprise Suite. Its pricing page is quote-based, directing you to schedule a call or ring sales (erp.intuit.com/pricing, accessed August 26, 2026). Accountants can get up to 60 percent off list through ProAdvisor Preferred Pricing, per the same page.

Independent estimates fill in the gap. ERP Research puts a single-entity deployment at roughly $7,800 to $8,000 a year, two to five entities at $12,000 to $15,000, and larger groups above $15,000, covering software subscription only, with implementation and migration quoted separately (erpresearch.com, accessed August 26, 2026). Those are third-party estimates, not Intuit figures. Your quote will be your quote.

When IES is genuinely the right answer

Be honest with yourself about which of these you need:

• Intercompany transactions posted and eliminated inside the ledger, with an audit trail, because your auditor or your lender looks at them
• Cross-company bill payment recorded as a real intercompany balance rather than a memo
• Dimensional reporting deeper than one flat class list can carry
• Consolidated statements that have to hold up as financial reporting, not management reporting

If you need those, IES is doing work no spreadsheet replicates, and this section is not an argument against it.

When a consolidated workbook is enough

Now the other case, which is more common than the sales cycle suggests. You have a handful of QuickBooks Online companies. Intercompany activity is light, a few entries a month that your bookkeeper already handles correctly. What you actually need is one report that adds the entities together and stays current.

That is a reporting problem, and it is solvable at a different price point. Retriever connects each QuickBooks Online company to Google Sheets, pulls the reports you choose, and refreshes them on a schedule, so a consolidated workbook updates itself instead of being rebuilt every month. It is read-only, so it never writes to your books, and it works on any QuickBooks Online plan rather than requiring the top tier.

The comparison is not like for like, and it should not be presented as one. IES automates posting. Retriever reports on what was posted. If the posting is already fine and the reporting is the bottleneck, you are paying an ERP price to fix a spreadsheet problem.

Frequently asked questions

See also

Source: Intuit, "In the Know" live webinar, August 20, 2026, with product details presented by Daniel Malinov, product manager for Intuit Enterprise Suite. Pricing references accessed August 26, 2026.