How QuickBooks Online works

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: <cite index="4-25,4-26,4-27">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.</cite> The 'Switch Company' function <cite index="4-2,4-4,4-5">allows toggling between companies to manage them separately</cite>, 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 entitie …

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 <cite index="6-18,6-23,6-24">lets users build multi-company reports by selecting a group and running the report to push data into a spreadsheet</cite> — but that export severs the live link to source transactions, making interactive drill-down impossible. …

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: Shared services model: centralized AP team processes invoices for all entities with proper entity coding

Your scenario requires a single centralized AP team to open a vendor bill, select the correct legal entity, and have that transaction post to the right subsidiary ledger without re-keying it elsewhere. QBO cannot do this. Each of your 8 legal entities must be set up as a separate QBO company file with its own paid subscription, and there is no entity-code field on a bill entry form that routes a transaction to a different subsidiary ledger. The only mechanism QBO provides for an AP clerk to work across entities is the 'Switch company' function: the clerk must exit the current company file, select the target entity, and enter the bill fresh in that file. …

Limitations: For this buyer's 8-entity structure, a centralized AP team would have to switch into each entity's isolated company file to enter invoices, with no shared vendor master, no cross-entity entity-coding field, and no automated due-to/due-from entries: this architecture cannot deliver a shared services workflow at the 2,50 …

Requirement evaluated: Ability to report at entity level, entity group level (US vs. Canada), and full consolidated level

For a company with 8 legal entities across the US and Canada needing three reporting layers, the answer differs sharply depending on which Intuit product the buyer actually runs. Standard QBO (the evaluated vendor) has no native multi-entity consolidation: each company is a separate subscription, and the only path to a combined view is manually exporting reports from each entity and combining them in Excel — precisely the spreadsheet workflow the buyer is trying to escape. …

Limitations: For this buyer's specific requirement of three simultaneous reporting levels with automatic eliminations at both the group and consolidated layers, IES covers entity-level and full-consolidated views but lacks documented native support for a configured US-vs.-Canada intermediate sub-consolidation with automatic currenc …

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: <cite index="29-11,29-12">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.</cite> Even on the ADP RUN path, <cite index="31-12">payroll cost allocation by …

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. <cite index="1-3,1-4,1-5">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.</cite> <cite index="19-11,19-12,19-13">Webhooks deliver real-time notifications when data changes in a connected company file; devel …

Limitations: <cite index="10-1">Standard rate limits are 500 requests per minute per realm ID (company), with a maximum of 10 simultaneous requests per company per app.</cite> 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 end …

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: REST API with documented endpoints for custom integrations

For a company like yours running 8 legal entities and needing to connect Salesforce, ADP, and custom tools, QuickBooks Online exposes a publicly documented REST API through the Intuit Developer Portal at developer.intuit.com. <cite index="1-1,1-5">The API supports reading and writing core accounting data including invoices, customers, payments, journal entries, and more, using JSON payloads and OAuth 2.0 Authorization Code flow for authentication.</cite> <cite index="3-5,3-6">It covers the full accounting data model with endpoints for create, read, update, delete, and query operations, and webhooks are supported for real-time event notifications when data changes in a company file.</cite> <c …

Limitations: <cite index="23-1,23-2">Each connected QuickBooks company is a separate realmId with its own OAuth token pair and rate limit bucket, requiring your integration to partition architecture by realmId from day one</cite> -- meaning your 8 legal entities require 8 separate authenticated API connections with no unified cross …

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. <cite index="1-23">Priority Circle is a service for QuickBooks Online Advanced customers that provides in-depth product training and premium support.</cite> On the support contact question specifically, <cite index="1-14,1-15">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.</cite> Third-party reseller documentation describes the program as also including a dedicated account manager or custome …

Limitations: <cite index="1-37">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</cite>; this buyer's Canadian entities are explicitly excluded from Priority Circle benefits, meaning the support model is …

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: Phased implementation: core GL and consolidation first, then AP/AR, then advanced reporting

For a $180M company with 8 legal entities needing multi-entity consolidation as the centerpiece of Phase 1, QBO's architecture presents a fundamental obstacle. QBO operates on a one-company-per-subscription model: each of the buyer's 8 entities requires its own separate paid QBO subscription, and the data across those files remains completely isolated. There is no native mechanism within QBO itself to run intercompany eliminations or produce consolidated financial statements. Intuit's own support documentation confirms this directly: 'Creating consolidated financial statements in QuickBooks Online (QBO) …

Limitations: QBO cannot deliver Phase 1 (GL plus native multi-entity consolidation across 8 entities) without bringing in a third-party consolidation tool from a different vendor, which means the buyer must plan and budget for that dependency before any subsequent phase can proceed. …

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: Unified, segment-based chart of accounts that works across all 8 entities while allowing entity-specific sub-segments

For this buyer's 8-entity US/Canada structure, the answer depends sharply on which Intuit product tier is in scope. Within standard QuickBooks Online (through QBO Advanced), each company is a fully independent subscription with its own isolated chart of accounts. <cite index="6-30">The Combine Reports feature is only available for subscribers using an Advanced plan</cite>, and even then it relies on Spreadsheet Sync, which requires the controller to <cite index="6-2,6-3">make the chart of accounts in each company file identical as much as possible</cite> before combining reports manually. …

Limitations: Within standard QBO (including Advanced), there is no shared or inherited COA architecture across entities at all: the buyer would replicate their current manual-alignment problem. …

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

For a professional services and distribution company with 8 legal entities needing a shared, enforced COA structure, QBO's standard architecture is a direct mismatch. In QuickBooks Online (all tiers through Advanced), each legal entity runs as a fully independent company file: Intuit's own help documentation confirms that 'although your companies share a sign-in, their data remains completely separate' and that 'future changes to a list in one company will not update the other.' There is no native mechanism to designate a parent COA, push account structures to child entities, or enforce a shared account numbering schema across all 8 files. …

Limitations: Migrating from QBO to IES to gain shared COA and dimension-based segmentation is a full product migration, not a plan upgrade, and is incompatible with the buyer's goal of continuing to operate on QuickBooks Online. …

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. <cite index="20-7,20-9,20-10,20-11">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.</cite> <cite index="7-6">The workflow supports up to 5 layers of sequential approval.</cite> Dollar thresholds are supported: <cite index="4-16,4-17">QuickBooks Online Advanced or Bi …

Limitations: <cite index="17-1">According to QBO community and help articles, you cannot have multiple active bill approval workflows for the same transaction type simultaneously,</cite> which prevents entity-by-entity or department-by-department routing within a single subscription. …

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

For a $180M professional services and distribution company that needs system-enforced three-way matching before payment approval, QBO's native AP mechanism falls well short. In QBO, when a user creates a bill, open purchase orders for that vendor appear in a sidebar and the user manually clicks 'Add' to pull PO line items into the bill. The system does not compare a goods receipt or item receipt as a third document: the goods receipt layer (Item Receipts) exists only in QuickBooks Desktop, not in QBO. …

Limitations: QBO natively supports only a manual two-way PO-to-bill linkage with no goods receipt layer and no configurable price or quantity tolerance thresholds; meeting the buyer's 2% price / 5% quantity tolerance requirement with system-enforced exception routing would require replacing or supplementing QBO with a separate vend …

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: Scheduled report delivery (weekly flash report to leadership, monthly board package)

For this $180M, 8-entity company, QBO's scheduled report delivery works as follows for single-entity books: a user customizes any standard or custom report, saves it as a Custom Report, then enables 'Set email schedule' in the Action column to configure a recurring cadence (daily, weekly, monthly, quarterly) with named recipients and a subject line. <cite index="3-7,3-8">With QuickBooks Online Advanced, users can create their own reports using Custom Report Builder and email memorized reports on a recurring schedule.</cite> <cite index="1-11,1-12,1-13">In the Action column, the user selects Edit and turns on 'Set email schedule,' then sets the email recurrence and enters recipient informatio …

Limitations: The scheduling mechanism stops at the single-entity boundary: a board package for 8 legal entities requires consolidated financials that QBO cannot produce natively, so any scheduled delivery would send 8 separate single-entity files rather than one consolidated report. …

Requirement evaluated: Financial statement generator that produces GAAP-compliant balance sheet, P&L, and cash flow

For a company moving off QuickBooks Enterprise with 8 legal entities needing audit-ready financials, QBO's native Reports center produces a Balance Sheet, Profit & Loss, and Statement of Cash Flows for each individual company when accounting is set to accrual basis. Drill-down from any line to underlying transactions is supported. For the buyer's multi-entity consolidation need, the mechanism exists only within Intuit Enterprise Suite (Intuit's own separately priced, higher-tier product): it includes a dedicated Consolidated Reports section in the Reports center, a shared chart of accounts across entities, and automatic intercompany elimination for accounts designated exclusively for interco …

Limitations: For this buyer's 8-entity structure, reaching consolidated GAAP-ready financials requires Intuit Enterprise Suite (a separate, higher-priced tier), and even then partial intercompany eliminations fall back to manual Spreadsheet Sync adjustments in Excel, partially replicating the spreadsheet dependency the buyer is try …

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. …

Requirement evaluated: Customer portal for invoice access and online payment

For a $180M multi-entity professional services company requiring self-service customer AR access, QBO delivers one half of this requirement but not the other. On the payment side, <cite index="2-5,2-6">QuickBooks Payments enables customers to pay online via credit card or ACH bank transfer, processing payments directly against the invoiced amount.</cite> The mechanism is email-driven: <cite index="12-1,12-2">if you have QuickBooks Payments, customers can pay their invoices online by credit card or ACH bank transfer by selecting the Pay Now button in the email.</cite> On the portal side, the mechanism does not exist natively. …

Limitations: For this buyer operating 8 entities with an audit readiness deadline, the absence of a native persistent customer portal means customers cannot self-serve invoice access or initiate payment outside of a single-use email link, creating AR process friction at scale and no centralized portal view spanning entities. …

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

For a $180M professional services and distribution company processing payments from bank lockboxes and ACH batches, QBO's native mechanism is its bank feed with AI-assisted match suggestions. When bank transactions download, QBO suggests matches to existing records such as invoices and sales receipts, but the official help documentation states: "In most cases, QuickBooks automatically suggests transaction matches for you to confirm. Where QuickBooks can't find a match, you'll need to manually find the match yourself" (QuickBooks Help: Match transactions in QuickBooks Online). …

Limitations: For this buyer's volume and audit readiness goal, the absence of native lockbox file import (BAI2) and NACHA/remittance parsing means every ACH and lockbox receipt still requires a human to confirm the match in the bank feed, replicating the manual bottleneck the buyer is trying to eliminate. …

Requirement evaluated: Credit limit management by customer

For a professional services and distribution company pursuing audited financials, QBO offers a Credit Limit field in each customer's profile, accessible via Sales > Customers > Edit > Payments section. <cite index="19-3,19-34">This feature is exclusive to the QuickBooks Plus and Advanced plans.</cite> <cite index="1-24,1-25">QBO tracks the limit and surfaces an alert when you create an invoice that would cause the customer's A/R balance to exceed it.</cite> However, <cite index="14-3">QBO does not have an option to set credit limits that automatically prevent the creation of invoices or orders.</cite> The alert is a soft, dismissible warning: <cite index="12-5">a message appears when the sal …

Limitations: The buyer needs a control that supports an audit trail for AR credit exposure -- the soft-warning mechanism QBO provides can be bypassed by any AR staff member with no override record, which does not meet the documentation standard a company pursuing audited financials requires. …