QuickBooks Desktop vs QuickBooks Online

Requirement evaluated: Automated elimination entries during consolidation without manual journal entries

This buyer's core pain point is a 12-day close driven by manual intercompany eliminations across 8 legal entities, and QB Desktop Enterprise does not resolve it. The product's consolidation mechanism is the 'Combine Reports from Multiple Companies' feature, which pulls matching financial data from each separate company file and exports it into a Microsoft Excel workbook. …

Limitations: <cite index="17-41,17-42">The consolidation workflow ends with 'Combine Reports in Excel,' opening a Microsoft Excel spreadsheet with the combined information</cite>, meaning every elimination entry for all 8 entities still requires manual intervention in a spreadsheet. …

Requirement evaluated: Automated elimination entries during consolidation without manual journal entries

This buyer operates 8 legal entities across the US and Canada and needs automated elimination entries at period close to replace the manual intercompany reconciliation that currently drives a 12-day close. QuickBooks Online (Simple Start through Advanced) has no native multi-entity consolidation engine: <cite index="16-10,16-11,16-12">QBO operates on a fundamental limitation of one company per subscription, meaning you cannot consolidate multiple entities within the platform itself, and there are no native elimination features for intercompany transactions; manual export to Excel is required for any consolidation work.</cite> Intuit does offer automated intercompany account elimination in it …

Limitations: Standard QBO (Advanced and below) cannot consolidate across 8 legal entities or generate any elimination entries without third-party add-ons; automated elimination is only available in Intuit Enterprise Suite, a separately priced product that the buyer would need to evaluate independently. …

Requirement evaluated: Support for multiple fiscal calendars (our Canadian entities have a different fiscal year-end)

This buyer operates 8 legal entities across the US and Canada where Canadian entities carry a different fiscal year-end. In QB Desktop, each company file stores its own fiscal year start month independently via Company > My Company > Reporting Information; an admin selects the first month of the fiscal year per file, meaning a Canadian entity's file can technically be configured with a March 31 year-end while US files use December 31. …

Limitations: <cite index="14-3">It is crucial to have each company on the same fiscal year and standardize the chart of accounts across all companies for consistency and accuracy when consolidating in QB Desktop Enterprise.</cite> For this buyer, whose Canadian entities have a materially different fiscal year-end, the consolidation …

Requirement evaluated: Support for multiple fiscal calendars (our Canadian entities have a different fiscal year-end)

This buyer operates 8 legal entities across the US and Canada with different fiscal year-ends and needs those calendar structures to coexist inside a unified, consolidation-capable platform. QBO's architecture makes this impossible natively: <cite index="26-1,26-2">QBO operates on a fundamental limitation of one company per subscription, and you cannot consolidate multiple entities within the platform itself.</cite> Each of the buyer's 8 entities would require a separate, fully siloed QBO file. …

Limitations: For a buyer with 8 legal entities spanning US and Canadian fiscal year-ends who also needs consolidated financials for an audit, QBO is structurally mismatched: it has no single-instance multi-entity model, no native cross-entity period management, and no native elimination or consolidation engine -- meaning the buyer' …

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

For a $180M company looking to consolidate all vendor disbursement rails into a single AP workflow, QB Desktop Enterprise covers two of the four required rails natively. Through Bill Pay powered by Melio (available on Enterprise 2022 and later), users select bills from the Pay Bills screen and choose 'Schedule Online Payment'; <cite index="3-1,3-2">the delivery options within Bill Pay are ACH bank transfer or paper check, selectable per vendor at time of payment.</cite> <cite index="3-29">Batch payments support up to 20 bills at once.</cite> However, the workflow breaks at wires and virtual cards: <cite index="17-1,17-2">QuickBooks Desktop has no direct function for ACH or wire transfer nati …

Limitations: Wire transfer execution is absent from the native AP workflow and requires a separate bank portal step with manual bill matching afterward, breaking unified audit trail continuity. …

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

This $180M multi-entity company currently routes vendor payments through manual bank portals and spreadsheets; consolidating all four payment rails into a single AP workflow is a core requirement. QuickBooks Online's native disbursement module is QuickBooks Bill Pay (Basic is now included with all QBO subscriptions). Within that module, the user opens a bill, selects 'Schedule Payment,' chooses a funding bank account, and then selects the delivery method: ACH bank transfer or Intuit-mailed paper check. These two rails write back to the GL automatically and payments sync in real time with the books. …

Limitations: Two of the buyer's four required payment rails (wire transfer and payor-initiated virtual card) are absent from QBO Bill Pay's native AP workflow; wires must be executed outside QBO and manually recorded, and virtual cards cannot be issued by the payor, which breaks the single-workflow audit trail the buyer explicitly …

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

For a $180M company running ADP Workforce Now alongside QB Desktop, payroll GL posting works through a file-based workflow rather than a live integration. After each ADP pay run, a user logs into ADP, navigates to the General Ledger section, and downloads an IIF-formatted GL export file; the user then opens QB Desktop, switches to Single User Mode, and imports the file via File > Utilities > Import > IIF Files, at which point QB Desktop posts the journal entry against the pre-mapped chart of accounts. …

Limitations: The IIF mechanism is a human-initiated file pull after each pay run, not automated event-triggered posting; it replicates the manual data-transfer burden the buyer is trying to eliminate. Departmental cost allocation requires either QB's own payroll module (displacing ADP entirely) …

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

For a $180M company running ADP across 8 entities, QBO's integration path relies on ADP's native General Ledger module. In ADP RUN (the small-business ADP product), a user enables the GL feature, maps each payroll expense item to a QBO chart of accounts account, and upon accepting a payroll run, <cite index="1-1,1-22,1-23">GL entries are automatically transmitted back to QBO after payroll is run, so that once the payroll is accepted, GL transactions are automatically sent to QBO and appear in the register.</cite> The ADP GL mapping guide confirms this is a <cite index="33-1,33-2,33-11,33-12">COA-mapping process where the user accesses General Ledger settings in ADP, and for each payroll expe …

Limitations: <cite index="17-6,17-7,17-8">ADP Workforce Now GL imports into QBO are frequently broken in practice and are better suited for ADP RUN, which is recommended for businesses with fewer than 50 employees</cite> - well below this buyer's 320-employee, 8-entity footprint. …

Requirement evaluated: Role-based training plan (not generic): controller, AP clerk, entity bookkeeper, executive

For a $180M multi-entity company preparing for its first audit and migrating a controller, AP clerks, entity bookkeepers, and executives onto a new system simultaneously, QB Desktop Enterprise offers no native role-segmented implementation training plan. What Intuit provides natively is two distinct things that are commonly conflated with this requirement but are not it. First, QB Desktop Enterprise's access-control layer supports 14 predefined roles (Finance, Payroll Manager, Inventory, etc.) and permissions across 115 individual activities, as documented in the Enterprise In-Depth Guide: these are security and access-control roles, not learning paths. …

Limitations: Intuit does not publish or deliver a structured implementation training plan segmented by functional role (controller, AP clerk, entity bookkeeper, executive); the buyer would need to procure a QuickBooks ProAdvisor or Solution Provider separately to design and deliver role-tiered training, adding cost and timeline ris …

Requirement evaluated: Role-based training plan (not generic): controller, AP clerk, entity bookkeeper, executive

This $180M, 8-entity professional services firm needs a structured onboarding program with distinct training tracks for each functional persona: controller, AP clerk, entity bookkeeper, and executive. QBO Advanced does not deliver this natively. The closest analog is Priority Circle, included with QBO Advanced, which provides access to self-paced online training. …

Limitations: For this buyer's 8-entity configuration with 4 distinct functional personas, Priority Circle's self-paced library provides no structural differentiation between a controller managing intercompany eliminations, an AP clerk processing 2,500 invoices, an entity bookkeeper with scoped access, and an executive reviewing con …

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

For a $180M company with 8 legal entities, QuickBooks Desktop Enterprise provides a native single-entity budget vs. actual reporting mechanism via Company > Planning & Budgeting > Set Up Budgets, with pre-built 'Budget vs. Actual' reports accessible under Reports > Budgets & Forecasts. Within a single company file, users can segment budgets by class or customer/job and run Budget vs. Actual by those dimensions. …

Limitations: There is no native cross-entity consolidated budget vs. actual report with in-system drill-down to transactions; the only multi-company path pushes data into Excel, destroying the audit trail and drill-down capability that the buyer's board-audit readiness requires. …

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

For a company with 8 legal entities like this buyer, QBO's budget vs. actual capability works as follows within a single company file: on QBO Plus or Advanced plans, users create a budget (manually or via CSV/Spreadsheet Sync import) and then run the pre-built Budget vs. Actuals report from the Reports menu under Business Overview. <cite index="12-42,12-43">The Budget vs. …

Limitations: The most material ceiling for this buyer is the complete absence of a native consolidated budget vs. actual report across all 8 (or future 15+) legal entities: each entity is a separate QBO file, and cross-entity variance reporting requires manual Excel exports and manipulation, which directly reintroduces the spreadsh …

Requirement evaluated: Customer portal for invoice access and online payment

For your professional services and distribution company, QuickBooks Desktop Enterprise handles online payment collection through QuickBooks Payments, Intuit's own add-on payment service. When your AR team sends an invoice via email, the system embeds a 'Pay Now' button in the message; the customer clicks it and pays that specific invoice by credit card, ACH, or eCheck. Your staff can then see when the invoice was sent, viewed, and paid from within Desktop. This is the full extent of the customer-facing mechanism: it is a per-invoice, email-triggered payment action, not a persistent portal. …

Limitations: QuickBooks Desktop Enterprise has no native customer portal where clients can log in and self-serve their invoice history or payment status; Intuit support has confirmed this gap directly in community threads, and third-party testing of the limited CAMPs interface found no option to review past transactions. …

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