How QuickBooks Online works

Requirement evaluated: Real-time consolidated financial statements (not batch/overnight)

For a company running 8 legal entities like yours, standard QuickBooks Online provides no native multi-entity consolidation at all. QuickBooks Online treats every company as a separate, isolated file with no built-in way to produce consolidated financial statements across entities. The real-time consolidation capability exists only in Intuit Enterprise Suite (IES), Intuit's separately licensed, higher-tier product above QBO Advanced. IES allows you to view consolidated, real-time KPI performance across all entities, covering profit and loss, sales, expenses, accounts receivable, and accounts payable. …

Limitations: For your 8-entity scenario, eliminations are a core need, and IES currently handles them through a manual Spreadsheet Sync workflow whose adjustments do not write back to the platform: your controller would still be managing elimination entries outside the system. …

Requirement evaluated: Cross-entity drill-down; from consolidated P&L, click into the entity-level transaction

For a company running 8 legal entities across the US and Canada like yours, standard QuickBooks Online and QBO Advanced do not offer any native cross-entity consolidated P&L. Each entity lives in its own separate company file, with no built-in mechanism to roll up the P&L and balance sheet across those files, eliminate intercompany accounts, or produce a group-level consolidated report without manual intervention. The capability the buyer needs lives in Intuit Enterprise Suite (IES), Intuit's separately priced multi-entity product. …

Limitations: The buyer's requirement is specifically to 'click into the entity-level transaction' from the consolidated P&L in a single navigation step; as of the most recent ProAdvisor documentation (approximately August 2026), IES stops at a consolidated transaction list rather than opening the source transaction record directly, …

Requirement evaluated: Shared services model: centralized AP team processes invoices for all entities with proper entity coding

For the buyer's scenario of 8 legal entities with a single centralized AP team, QBO's architecture presents a fundamental structural barrier. Each QBO company is a fully isolated file: although companies share a sign-in credential, their data remains completely separate, users set up in one company do not automatically have access to others, and must be invited to each company separately. The 'Switch Company' function allows toggling between companies to manage them separately, but this is sequential file-by-file processing, not a unified AP queue where a centralized team codes invoices with entity tags across all 8 entities in a single workflow. …

Limitations: For this buyer's 8-entity centralized AP model, QBO requires processing invoices entity by entity in separate isolated files with no shared queue, no cross-entity invoice entry screen, and no audit-grade legal entity coding at the line level. …

Requirement evaluated: Cross-entity drill-down; from consolidated P&L, click into the entity-level transaction

For a controller managing 8 legal entities who needs to click from a consolidated P&L line into the underlying entity-level transaction, standard QuickBooks Online falls materially short. Within QBO, the only multi-entity consolidation path is Spreadsheet Sync in QBO Advanced, which lets users build multi-company reports by selecting a group and running the report to push data into a spreadsheet — but that export severs the live link to source transactions, making interactive drill-down impossible. Intuit's own support confirms that the only way to consolidate P&L across companies in QBO is by exporting reports to Excel and manually modifying and consolidating the data. …

Limitations: Standard QBO's consolidation path (Spreadsheet Sync to Excel) is a static export that breaks the live transaction link the buyer requires; achieving true cross-entity drill-through demands migrating to Intuit Enterprise Suite, which is a full product replacement, not a module or plan upgrade within QBO. …

Requirement evaluated: Bidirectional integration with Salesforce CRM: customer master sync, closed-won opportunities create billing events

For a company running 8 legal entities with audit-ready financials as a near-term goal, the Salesforce-to-QBO integration architecture matters enormously, and QBO's native capability falls well short of the buyer's requirement. QBO does offer a built-in Salesforce connector, surfaced through its KPI/reporting dashboard (available on QBO Advanced and Intuit Enterprise Suite), but Intuit's own help documentation is explicit that this connection is strictly one-directional: 'Data flows one way from your CRM into your Intuit product' and 'Changes made in Intuit products won't affect anything in your CRM app.' The connector syncs Salesforce leads, deals, customers, and products into QBO's reporti …

Limitations: For a buyer targeting audited financials across 8 legal entities, relying on third-party middleware (Breadwinner, DBSync, Workato) to bridge Salesforce and QBO introduces a second vendor relationship, separate failure points, and added complexity in ensuring customer master records are correctly entity-tagged across al …

Requirement evaluated: ADP payroll integration: automated journal entry posting after each pay run with departmental cost allocation

For this $180M company running 320 employees across 8 entities with ADP, the integration path depends entirely on which ADP product is in use. ADP offers a native General Ledger connector specifically for ADP RUN (its small-business payroll product, typically suited for companies under roughly 50 employees): after setup, ADP RUN pushes a GL file to QBO automatically after each pay run, mapping pay codes to QBO chart of accounts, with an option for employee-level or company-level summarization. …

Limitations: The native connector only supports ADP RUN, not ADP Workforce Now, which is the expected ADP product for a company of this size; Workforce Now users are directed to manual journal entries or third-party connectors. …

Requirement evaluated: REST API with documented endpoints for custom integrations

For a $180M company running 8 legal entities across the US and Canada, QBO does offer a fully documented REST API through the Intuit Developer Portal at developer.intuit.com. QuickBooks Online has a REST API maintained by Intuit, accessible through the Intuit Developer Portal. The API uses OAuth 2.0 for authentication and supports JSON payloads, covering the full accounting data model: customers, invoices, bills, payments, vendors, accounts, and profit/loss reports, with endpoints for create, read, update, delete, and query operations. …

Limitations: Standard rate limits are 500 requests per minute per realm ID (company), with a maximum of 10 simultaneous requests per company per app. With 8 legal entities, the buyer's internal development team must build and maintain 8 separate API connections and token management flows with no single endpoint to query or write ac …

Requirement evaluated: SSO via Azure Active Directory

Your organization runs on Azure Active Directory and needs users to authenticate to the ERP with corporate credentials, subject to Conditional Access policies and centralized user lifecycle management. QBO does not offer this mechanism. Authentication is handled exclusively through Intuit's proprietary identity system: every user must maintain a separate Intuit Account credential (email and password, verified via Intuit's own MFA flow) to access qbo.intuit.com. QBO does not accept Azure AD (Microsoft Entra ID) as an external identity provider via SAML 2.0, OIDC, or OAuth 2.0, and it does not support SCIM-based user provisioning or deprovisioning tied to Azure AD groups. …

Limitations: For your 8-entity, 320-employee organization preparing for audit, the absence of Azure AD SSO means your IT team cannot centrally deprovision QBO access when employees leave, users must manage separate Intuit credentials outside your corporate identity governance, and your Azure Conditional Access policies (device comp …

Requirement evaluated: Unified, segment-based chart of accounts that works across all 8 entities while allowing entity-specific sub-segments

For a company managing 8 legal entities with 8 divergent charts of accounts, the relevant mechanism lives in Intuit Enterprise Suite (IES), Intuit's own multi-entity product tier built on the QuickBooks Online platform. Within IES, a parent company administrator creates and manages a single shared chart of accounts from a central dashboard; child entities then map their existing accounts to that shared structure. The parent admin can add new accounts and selectively share them with specific entities, while each subordinate entity retains account-level mappings that accommodate entity-specific variations. …

Limitations: This capability requires Intuit Enterprise Suite, a separately priced product above standard QuickBooks Online subscriptions; buyers on standard QBO plans (Simple Start, Essentials, Plus, or even Advanced) …

Requirement evaluated: Unified, segment-based chart of accounts that works across all 8 entities while allowing entity-specific sub-segments

For your 8 US and Canadian entities, the QuickBooks route that fits is Intuit Enterprise Suite, not standard QuickBooks Online, where each company file keeps its own isolated chart of accounts. In Enterprise Suite, the parent company administrator can set up a Shared Chart of Accounts and manage it for multiple related entities from a single interface. An AI-assisted setup recommends a standardized chart for multi-entity companies, including a shared chart across all or multiple child entities. The segment layer is Dimensions. You can nest up to five levels of sub-values. …

Limitations: Standard QuickBooks Online plans (Plus and Advanced) do not meet this: each company file keeps its own chart of accounts, so you would need Intuit Enterprise Suite. Segments are dimension tags on transaction lines, not positions in a structured account string. …

Requirement evaluated: Period-close controls that prevent posting to closed periods while allowing adjustments with proper authorization

For a $180M company pursuing audited financials, QBO's period-close mechanism works as follows: an admin navigates to Settings > Account and Settings > Advanced > Accounting and enables 'Close the Books,' setting a closing date. Once set, any user who attempts to edit or delete a transaction dated on or before that date will either receive a warning message or be prompted to enter a shared password, depending on which option the admin selected. If someone proceeds past the warning or enters the password, the change is logged in the 'Exceptions to Closing Date' report, which records who made the change and what was altered. …

Limitations: The control is a soft lock, not a hard block: any company admin or primary admin can silently change or remove the closing date without a formal in-system approval workflow, and the override mechanism is a shared password rather than an individual role-based authorization with mandatory reason codes. …

Requirement evaluated: Period-close controls that prevent posting to closed periods while allowing adjustments with proper authorization

For a company preparing for its first audit across 8 entities, QBO's period-close control works as follows: an admin navigates to Account and Settings > Advanced > Accounting and turns on 'Close the books,' setting a closing date. Once set, any user who attempts to add, edit, or delete a transaction dated on or before that date will either see a warning or be required to enter a shared password before the change is saved, depending on which mode the admin configures. The official QBO help article 'Lock your books in QuickBooks Online' describes this as a hard enforcement at the transaction-posting layer, not merely a report filter. …

Limitations: The authorization pathway for posting to a closed period is a single shared password held by any admin, with no workflow-gated approval chain, no named-approver record tied to a specific prior-period posting, and no multi-tier role hierarchy (e.g., Staff can request, Controller approves). …

Requirement evaluated: Chart of accounts redesign assistance; we need help rationalizing 8 divergent charts into one unified structure

For your 8 entities running on QuickBooks Enterprise, the chart-of-accounts help sits in Intuit Enterprise Suite (IES), not in standard QuickBooks Online. IES offers AI-assisted setup with suggestions for standardizing the chart of accounts, dimensions and vendors, and it recommends a chart for multi-entity companies, including a shared chart across child entities. The parent company is the source, its chart syncs to the other companies, and a standardization page shows how each entity's accounts were mapped, organized by account type and detail type. You can unmap an account or map it to a different account. …

Limitations: The in-product tooling maps legacy accounts onto a shared chart and suggests standardization. It does not design the target structure or decide which of your 8 charts' distinctions become accounts and which become dimensions, so that design work falls to your controller or to paid ProAdvisor/implementation partners. …

Requirement evaluated: Dedicated support contact (not ticket-only) during the first year

For a $180M multi-entity company migrating from QuickBooks Enterprise and targeting audited financials, the relevant support mechanism in QBO is Priority Circle, included at no extra charge with a QuickBooks Online Advanced subscription. Intuit's official Priority Circle page describes it as a 'direct line to top-tier QuickBooks support agents' reachable by phone or chat, with callbacks and screen sharing, and Intuit's 2018 press release described it as including 'a dedicated Customer Success Manager, a single point of contact.' However, the current official Priority Circle page no longer prominently describes a single named CSM: the documented mechanism has evolved toward a pooled 'dedicate …

Limitations: The buyer's requirement is for a dedicated, named human contact (not ticket-only) for the first year; Priority Circle as currently documented provides priority access to a pooled top-tier agent team rather than a persistently assigned individual, falling short of that bar. …

Requirement evaluated: Dedicated support contact (not ticket-only) during the first year

For a $180M, 8-entity company pursuing audit readiness, QBO Advanced includes Priority Circle, a premium support program bundled at no additional charge with an active QBO Advanced subscription. Priority Circle is a service for QuickBooks Online Advanced customers that provides in-depth product training and premium support. On the support contact question specifically, Priority Circle gives you a direct line to top QuickBooks technical support agents; when you need a fast answer, specialists are available via phone or chat. …

Limitations: Priority Circle is included at no extra charge only to customers located in the 50 United States and the District of Columbia who have an active paid subscription to QBO Advanced; this buyer's Canadian entities are explicitly excluded from Priority Circle benefits, meaning the support model is fragmented across their 8 …

Requirement evaluated: Data migration of 3 years of transactional history from QuickBooks plus open balances

For a company moving from QuickBooks Enterprise to QBO, Intuit provides a native 'Export Company File to QuickBooks Online' utility accessed within QuickBooks Desktop Enterprise (Ctrl+B+Q). The tool presents two options: 'Bring all of your company data' or 'Bring only lists and balances.' The 'all data' path transfers customer and vendor lists, transactions, chart of accounts, and account balances, but it is gated by a hard file-size limit: Intuit's own community documentation states that Enterprise files exceeding 750,000 targets cannot be fully converted to QBO, at which point only lists and balances can be imported or the buyer must start fresh. …

Limitations: The native migration tool cannot directly migrate Canadian QuickBooks Enterprise files and imposes a 750,000-target file size cap that forces large Enterprise files into a lists-and-balances-only import, meaning 3 years of full transactional history likely cannot be brought over natively for all 8 entities; advanced En …

Requirement evaluated: Self-service report builder; our controller must be able to create custom reports without IT or vendor assistance

For a controller at a company like yours with 8 legal entities seeking to build custom reports without IT help, QuickBooks Online Advanced includes a dedicated Custom Report Builder that is entirely self-service. The controller navigates to Reports > Custom reports, selects 'Create new report,' and chooses either a guided report creation wizard or a blank canvas to manually add, remove, and reorder data columns; apply filters by account, customer, or vendor; group and pivot data; and visualize results as charts. Reports can be saved, named, shared with other users, scheduled for automated email delivery, and exported to Excel, Google Sheets, PDF, or CSV without any IT or vendor involvement. …

Limitations: The Custom Report Builder is confined to one QBO company file at a time, so this buyer's core need (custom reports that reflect all 8 entities in a consolidated view) …

Requirement evaluated: Budget vs. actual variance reporting with drill-down to transaction level

For a company with 8 legal entities running separate QBO files, budget vs. actual reporting works as follows at the single-entity level: QBO Plus and Advanced include a native 'Budget vs. Actuals' report under Reports > Business Overview. Users create annual budgets with monthly phasing, and can subdivide by Class, Customer, or Location (one dimension at a time). The report displays budgeted amounts, actual account totals, and variance columns ($ over budget / $ remaining) for the selected period. Clicking an actuals cell opens a transaction list for that account, providing a shallow one-step drill into posted transactions. …

Limitations: First, QBO cannot produce a consolidated budget vs. actuals across the buyer's 8 US/Canada legal entities without manual Excel exports, leaving cross-entity variance analysis outside the system. …

Requirement evaluated: Scheduled report delivery (weekly flash report to leadership, monthly board package)

For a company like yours that needs a weekly flash report and a monthly board package, QBO offers a native 'Set email schedule' feature on saved Custom Reports. The user customizes a report, saves it to the Custom Reports tab, and then enables the email schedule toggle, setting a recurrence (daily, weekly, monthly, or quarterly), recipient email addresses, and a subject line; QBO then pushes the report automatically as a PDF or Excel attachment on the configured date. This covers the weekly flash report cadence well: any single-entity P&L, cash summary, or AR aging can be scheduled to push to leadership inboxes without manual intervention. …

Limitations: The scheduling mechanism delivers single-entity reports only; a consolidated board package spanning all 8 entities cannot be scheduled for automated push delivery natively in QBO, requiring either manual assembly each month or a third-party consolidation tool. …

Requirement evaluated: Real-time executive dashboard showing consolidated cash position, revenue by segment, and AP/AR aging

For an 8-entity professional services company migrating from QuickBooks Enterprise, the native QBO dashboard is single-entity only: each company file is a separate subscription and the standard Business Overview dashboard cannot aggregate data across entities. Cross-entity consolidation in QBO Advanced is delivered via Spreadsheet Sync, which pushes multi-company financial data into Microsoft Excel rather than an in-app executive dashboard, replicating the manual aggregation workflow the buyer is trying to eliminate. The full consolidated executive dashboard the buyer needs is available through Intuit Enterprise Suite (IES), Intuit's own higher-tier offering. …

Limitations: The 2-hour dashboard refresh interval is a documented mechanism gap against the buyer's real-time requirement: an executive checking cash position or AP aging mid-day may see data that is up to 2 hours stale. …

Requirement evaluated: Three-way matching for PO-based invoices with configurable tolerance (we need 2% on price, 5% on quantity)

For your 2,500 invoices a month across 8 entities, QBO stops at PO-to-bill linking and does not run a three-way match. A user creates a bill, picks the vendor, and clicks Add on an open PO. The PO details are copied onto the bill lines, and the user edits quantity or amount to reflect what was partially received or paid. QBO automatically closes a PO once all quantities are added to bills, expenses, or checks. The fact sheet only says QBO lets you track inventory and create purchase orders (claim 26195b34). Its invoice-from-PDF/email automation covers capture and bill creation, not comparison against POs (claims 35b24edc, 97dd12af). …

Limitations: Neither the 2% price nor the 5% quantity tolerance can be configured, and with no receipt object, matching 2,500 invoices a month would mean manual comparison or a separate AP product. Your current QuickBooks Enterprise has item receipts. …

Requirement evaluated: Three-way matching for PO-based invoices with configurable tolerance (we need 2% on price, 5% on quantity)

For a $180M distribution company processing 2,500 invoices per month and preparing for audited financials, QBO Online's PO-to-bill workflow is manual and does not perform automated matching of any kind. When a vendor bill arrives, a user navigates to Expenses > Bills, opens the bill, and manually links it to an open PO for that vendor; the system then copies PO line items into the bill. There is no automated comparison engine that validates the bill's unit price against the PO price, no goods-receipt layer that captures confirmed quantities separately from the bill, and no configurable tolerance thresholds (percentage or dollar-based) on either the price or quantity dimension. …

Limitations: The buyer's specific requirement for automated three-way matching (PO, goods receipt, vendor bill) with separate configurable percentage tolerances per dimension (2% price, 5% quantity) …

Requirement evaluated: Support for ACH, check, wire, and virtual card payments in a single workflow

For your 2,500-invoice-per-month AP operation, QBO's built-in Bill Pay module supports two of the four required payment rails natively within its workflow: ACH bank transfer and paper check. From the Pay Bills screen, your AP team selects a bill, chooses 'Schedule payment online,' and picks either ACH or paper check as the delivery method; reconciliation posts automatically to the QBO ledger. …

Limitations: Wire transfer as an initiated payment rail is not available in QBO Bill Pay at any plan tier, requiring a separate third-party product (such as Bill.com, Melio standalone, or MineralTree) …

Requirement evaluated: Configurable approval workflows by entity, department, GL account, and dollar threshold

For a company managing 8 legal entities and needing dimension-specific routing, QBO Advanced's native bill approval workflow (available in QuickBooks Online Advanced or Bill Pay Elite) provides a workflow builder under Settings > Workflows where users define trigger conditions and assign approvers. The Bill Multi-Condition Approval template lets you choose conditions for amount, vendor, and location, and you can combine conditions using 'Add Condition' to build compound rules. The workflow supports up to 5 layers of sequential approval. …

Limitations: According to QBO community and help articles, you cannot have multiple active bill approval workflows for the same transaction type simultaneously, which prevents entity-by-entity or department-by-department routing within a single subscription. More critically, GL account and department (Class) …

Requirement evaluated: Automated invoicing with configurable templates per entity/service line

For your professional services and distribution company with 8 legal entities, QBO offers automated invoicing through recurring invoice templates, scheduled email delivery, and batch invoicing (on the Advanced plan), with an AI agent that can draft multiple invoices in bulk. Within a single QBO company file, users can create multiple Custom Form Styles (design, content columns, fields, footer, email message) and select any of them per invoice at send time, which supports service-line-level template differentiation. …

Limitations: The most material ceiling for an 8-entity buyer is that QBO is architecturally one-entity-per-subscription: managing 8 separate subscriptions means 8 disconnected invoice template libraries with no unified oversight, and within any single file the documented constraint that templates cannot carry different company info …

Requirement evaluated: Automated payment application from bank lockbox and ACH receipts

For your 8-entity, QuickBooks Enterprise-based close, QBO handles cash application in two different ways. When a customer pays an invoice through QuickBooks Payments (card or ACH 'Pay Now'), QuickBooks automatically applies the payment to the invoice and creates the deposit. Each day, QuickBooks Payments combines that day's payments into a single deposit. Cash that arrives outside that channel, such as a bank lockbox or an inbound ACH or wire, comes in through the bank feed. For these, QuickBooks suggests matches for transactions with the same amount within a date window (90 days before to 20 days after), and a user then reviews and posts each match. …

Limitations: I found no documented ingestion of lockbox or remittance files (such as BAI2 or remittance advice parsing) and no automatic split of a lump-sum receipt across multiple invoices. …

Requirement evaluated: Automated payment application from bank lockbox and ACH receipts

For a $180M professional services and distribution company receiving payments via bank lockbox files and third-party ACH deposits, QBO does not provide native automated cash application against open AR invoices for these payment types. QBO's automatic matching capability applies only to transactions processed through its own QuickBooks Payments product (Autopay on recurring invoices, Bill Pay, and Payroll); when bank transactions are downloaded from an external feed, QBO's help documentation confirms they 'must be matched manually,' with automatic matching limited to QuickBooks-originated transactions. …

Limitations: QBO has no native mechanism to ingest BAI2, NACHA, or CSV lockbox files and auto-match them to open AR invoices; the bank feed matching engine covers only same-amount, full-payment scenarios for QBO Payments-processed transactions, leaving lockbox batch receipts and externally-initiated ACH deposits requiring manual ap …

Requirement evaluated: Credit limit management by customer

For a $180M multi-entity professional services firm preparing for audited financials, credit limit enforcement at the point of transaction is a control requirement, not just a data storage request. QBO does have a Credit Limit field on the customer profile (found in the Payments section of the customer record), and community documentation indicates it may surface a non-blocking pop-up warning when an invoice would breach the limit. However, Intuit support staff have consistently confirmed across multiple threads that QBO does not have the ability to automatically prevent the creation of invoices or orders when a customer exceeds their credit limit. …

Limitations: For a company targeting audited financials, a non-blocking warning that any user can dismiss and a Notes field with no system enforcement provide no audit-defensible control over customer credit exposure across 8 entities. …