Intuit Enterprise Suite balance sheet by dimension: A September Pilot
Intuit Enterprise Suite balance sheet by dimension deserves a controlled pilot before accounting firms use it in client reporting. Start with one entity, reconcile opening balances and period activity, and keep unassigned amounts visible. Approve the report only when its dimension totals tie to the ledger and its allocation rules are documented.
Why this reporting change matters now
Intuit's September product update, published 2026-09-10, identifies balance sheet by dimension for a single entity as a beta capability. Its summer release notes, published 2026-08-12, also describe single-entity reporting, invoice-header dimensions, and dimension reparenting. Those notes say the release includes beta features rolling out until October.
For the September 23 planning decision, treat these announcements as a reason to arrange a pilot. Confirm access in the client's subscription and obtain current scope information before scheduling delivery. An announced capability does not establish that a particular client can use it today, or that historical data will produce the intended report.
Recent Peak Advisers coverage of the release emphasizes intercompany improvements and revisiting earlier platform evaluations. This article addresses a narrower implementation question: what evidence should an accounting firm require before accepting a dimensional balance sheet? The following procedures are proposed accounting controls, not claims about controls that the software automatically performs.
The decision matters because a useful profit and loss split does not establish a useful balance sheet split. September sales can carry a department tag while cash, old receivables, and opening equity remain shared or unassigned. A report may be arithmetically complete at entity level and still give a misleading impression of a department's resources.
Define the report before testing the feature
Choose one client entity and one reporting dimension, such as operating division. Write down the question the client wants answered. Comparing receivables by division requires less attribution than presenting a complete balance sheet for every division. Agreeing on that difference early prevents the team from spending days allocating balances the client never needed.
Record the accounting basis, reporting currency, cutoff date, account population, and dimension hierarchy. Retain an approved version of the hierarchy with its effective date. A renamed or moved division can change how a reader interprets comparative balances even when no accounting transaction changes.
Separate legal ownership from management attribution. A division within one company does not automatically own the cash shown in its column. A departmental cash allocation is also not evidence that the money is available for distribution. Loan restrictions, operational commitments, and other obligations require their own assessment outside this reporting exercise.
Define an explicit shared or unassigned category. Some balances may legitimately remain central, such as a common bank account or entity-level financing. Document why each shared balance stays there and who approves the treatment. Do not distribute a difficult amount across divisions merely to remove an empty-looking column.
If the firm already uses a shared chart of accounts mapping, keep account mapping and dimensional attribution as separate decisions. Mapping determines which financial statement line contains an account. Attribution determines which division receives its balance or activity. Combining these decisions can hide whether an error came from the account classification or the dimension.
Finally, establish what constitutes acceptance. A receivables analysis may pass when every open invoice is attributed and reconciled. A full divisional balance sheet needs a defensible treatment of opening equity, shared assets, liabilities, and settlement activity. Give the engagement lead a written deliverable definition before anyone adjusts historical tags.
Work through opening balances and settlements
Consider an illustrative company testing receivables by division as of September 30. Its August 31 receivables balance is $100,000: $60,000 belongs to East, $30,000 to West, and $10,000 is unresolved. During September, East invoices $40,000 and collects $35,000. West invoices $20,000 and collects $15,000. Assume no credits, write-offs, foreign exchange, or other movements.
Receivables are assets with a normal debit balance. In this example, invoices debit receivables and collections credit receivables. The calculation for each column is opening receivables plus invoices minus collections. It produces the following reconciliation, with amounts in dollars:
| Receivables movement | East | West | Unassigned | Entity total |
|---|---|---|---|---|
| August 31 opening balance | 60,000 | 30,000 | 10,000 | 100,000 |
| September invoices | 40,000 | 20,000 | 0 | 60,000 |
| September collections, subtracted | 35,000 | 15,000 | 0 | 50,000 |
| September 30 closing balance | 65,000 | 35,000 | 10,000 | 110,000 |
The assigned columns total $100,000, while entity receivables total $110,000. Hiding the unassigned column would omit $10,000 from the visible breakdown. Allocating that amount equally without invoice evidence would preserve the entity total but invent divisional precision. Keep the exception visible until the reviewer establishes its treatment.
This example distinguishes a stock from a flow. The $110,000 receivables balance is measured at September 30. The $60,000 of invoices and $50,000 of collections are activity during September. Adding monthly closing receivable balances together would not produce quarterly receivables. Use the quarter-end balance for the closing position and period movements for the reconciliation.
Next, test a settlement that crosses dimensions. Suppose a central bank account receives East's $35,000 collection. At entity level, the entry debits cash and credits receivables. If cash is reported centrally while the receivable reduction belongs to East, each dimension column may not form a self-balancing statement. That is a report-design issue to investigate, not permission to invent a balancing entry.
The firm should decide whether it needs selected account analysis, an approved management allocation, or a complete divisional statement with a documented balancing method. Any management-only allocation belongs in an identified reporting layer unless an authorized accounting conclusion supports a ledger entry. Preserve the ability to reconcile that layer back to the entity books.
Repeat the exercise for one liability account. A supplier bill normally increases accounts payable with a credit; payment reduces it with a debit. A preparer using a debit-positive export must apply the appropriate sign convention rather than copying the receivables formula blindly. Label display signs and movement signs so another reviewer can reproduce the result.
Accounting controls for accepting the report
Source data: retain the opening trial balance, closing trial balance, account detail, open-item listings, dimension mapping, and report settings. Record the extraction time and any changes posted afterward. An unexplained difference can otherwise be caused by comparing two reports produced from different ledger states rather than by a dimension error.
Include the complete population. Select a reporting date, capture all relevant balances, and identify excluded accounts or records explicitly. A test of ten clean invoices can demonstrate a transaction path, but it cannot establish that every receivable has been included. Combine targeted transaction tests with a full population reconciliation.
Calculation: build an independent bridge from opening balance to closing balance for each tested account. Sum mutually exclusive dimension values plus shared and unassigned amounts, then compare that total with the entity account balance. Also compare total debits and credits for the activity population. Keep the formulas visible and protect approved mapping tables from casual edits.
Test one dimension at a time before evaluating nested views. A division breakdown and a project breakdown may each describe the same underlying dollar. Adding the grand totals from both views would double count it. For a combined analysis, define the intersection of division and project, and verify that each source amount appears once in the chosen population.
Review: have someone other than the preparer inspect opening attribution, large unassigned balances, mixed-dimension invoices, credit notes, payments, and manual journals. Include a transaction whose business activity belongs to more than one division. Establish through observation how the available workflow represents that case; do not assume a header tag resolves every accounting split.
The reviewer should distinguish arithmetic agreement from economic accuracy. A wrong division tag can leave the entity balance unchanged and make every total tie. Trace selected amounts back to contracts, invoices, asset records, or other relevant evidence. Retain the reason for each attribution decision so the next preparer does not have to recreate it.
Decision: the engagement lead owns authorization to use the report with the client. The preparer owns the reconciliation, and the reviewer owns the documented challenge. Acceptance should identify unresolved items, permitted uses, and excluded uses. A report approved for internal receivables follow-up need not be approved as a complete divisional financial statement.
For the wider engagement, connect this evidence to the firm's documented close controls. A signoff is useful only when it points to the actual population, calculations, exceptions, and final report version that the reviewer examined.
Run the pilot without disrupting September reporting
Keep the existing approved reporting process available while the pilot runs. Begin with a closed opening date and a manageable transaction population. Preserve the original exports and reports before changing mappings. This gives the team a comparison point if a revised hierarchy or corrected tag changes a historical presentation.
Use a short test register with one row per scenario. Include opening balances, a new invoice, a partial collection, a credit note, a supplier bill, a payment from a shared bank account, and a manual adjustment. Record the expected accounting effect, observed report effect, supporting evidence, exception owner, and resolution. The register should explain a failure without requiring a meeting.
Set two kinds of acceptance criteria. Reconciliation differences should be resolved, with any rounding policy explicit. Judgment exceptions need a stated treatment and reviewer acceptance. An unexplained missing account should not pass because its current balance happens to be small; it could become material in the next period.
Measure preparation time, review time, and correction time separately. A faster initial export may be offset by additional attribution work. For example, saving 45 minutes preparing a report while adding 60 minutes of exception review increases total effort by 15 minutes. These are illustrative figures, not an expected result from the product.
After a successful first reconciliation, repeat the process at the next close before making the report a standard deliverable. Include a change case, such as a new division or a revised mapping. The pilot should show who notices the change, who approves it, and whether comparative reporting remains understandable.
Keep single-entity dimensional reporting separate from a group's consolidation process. A reliable departmental breakdown does not demonstrate that ownership, account mappings, or intercompany eliminations are correct across legal entities. The firm's intercompany elimination workflow still needs its own evidence and approval.
Common mistakes are accepting a balanced grand total as proof of correct attribution, hiding unassigned amounts, treating every column as independently spendable cash, and correcting reports by posting unsupported journals. Another is promising a delivery date before confirming beta access. Each mistake is avoidable if the engagement specifies the intended decision and tests the data needed to support it.
Give the client a concise acceptance note: the report's purpose, accounting basis, date, approved attribution policy, remaining limitations, and responsible reviewer. This makes the deliverable usable without implying more assurance than the work supports. Revisit the note when report scope, account treatment, or software behavior changes.
Frequently Asked Questions
Is this a consolidated balance sheet feature?
The cited release describes single-entity reporting. Confirm availability and scope with Intuit before planning a consolidated workflow.
Should every dimension column balance?
Only if the approved reporting design supports a complete balance sheet for each dimension. Document shared balances and investigate unexplained differences.
Can current-month tags establish opening balances?
No. Opening balances need their own supported attribution before current-month activity can produce reliable closing balances by dimension.
Who should approve client use of the report?
The engagement lead should approve client use after the preparer reconciles the report and an independent reviewer clears or documents the exceptions.
For your broader client reporting workflow, explore FinBoard and assess how it fits the reporting requirements your firm has documented.
