QB Desktop vs Infor CloudSuite vs Acumatica for ERP & Core Accounting

For a controller managing 8 legal entities who needs to escape spreadsheet-based consolidation and feed a Power BI environment, Acumatica delivers on two parallel tracks. First, any report built in the Report Designer can be exported directly as an XLS file for immediate Excel consumption, as documented in Acumatica's help center article 'Report Export: To Export a Report as an XLS file.' Second, and more powerfully for this buyer's multi-entity scenario, the OData formatting option exposes Generic Inquiry data in the Open Data Protocol format supported by BI tools like Power BI; checking 'Expose via OData' on a Generic Inquiry establishes a live data endpoint that Power BI can query directly. Users can create custom Power BI views for their Acumatica instance; out-of-the-box, Acumatica includes a predefined BI access role that governs which Generic Inquiries are exposed to Power BI. Critically for this buyer's 8-entity structure, Generic Inquiries can be built to include branch and sub-account dimension columns as discrete fields, meaning Power BI can slice and drill through by entity without requiring separate data pulls per company. Acumatica ERP supports OData Version 4.0, and enabling OData requires only checking the 'Expose via OData' box in the Generic Inquiry screen, with no firewalls to configure or third-party applications to install.

For a $180M professional services company with 8 legal entities needing audited financials, QB Desktop Enterprise covers one half of this requirement well and the other poorly. On the Excel side, any report in QB Desktop can be exported to an .xlsx workbook directly from the Reports menu via an 'Excel' dropdown that lets users create a new worksheet or update an existing one — a native, documented mechanism. On the Power BI side, there is no native QB Desktop connector: QB Desktop 'doesn't have a Power BI connector as QuickBooks Online does,' and reaching Power BI requires purchasing and configuring a third-party ODBC driver (e.g., QODBC, CData, or Devart), setting up a local DSN, and routing through a Power BI On-Premises Data Gateway. Even after that setup, the multi-entity architecture is the deeper problem: each of the buyer's 8 company files is an independent database, and QB Desktop's 'Combine Reports' utility outputs a combined Excel file rather than a unified, queryable data source — meaning Power BI would need 8 separate ODBC connections and custom data modeling work to stitch entities together, not a live consolidated model.

For a controller managing 8 legal entities who currently relies on QuickBooks and spreadsheets, Infor CloudSuite offers two distinct layers of Excel and Power BI access. For Excel, the platform ships a dedicated 'Infor CloudSuite Financial Reporting Tool Excel Add-In' that provides live GL data retrieval directly into Excel workbooks, supporting multi-site configurations; users define accounts, periods, and dimensions and the add-in pulls current data via IDO Web Service (required for cloud deployments) without a manual export step (docs.infor.com Microsoft Office Add-ins User Guide). Standard reports and data grids throughout the platform also expose a native 'To Excel' and CSV output option, and the embedded Birst analytics layer (the platform's native BI tool, pre-integrated with CloudSuite Financials via the Infor Data Lake) can export charts and reports to Excel or PDF from within its dashboards. For Power BI specifically, the documented pathway routes through the Infor Data Lake: CloudSuite pushes ERP data to the Data Lake via ION messaging in near-real-time, and Power BI can then query that data via an ODBC/JDBC connector (Infor Compass JDBC driver) or, as of the 2025.10 platform release, newly introduced native ODBC and Power BI connectors. However, the Data Lake replicates only a predefined, Infor-controlled set of tables — not the full CloudSuite schema — meaning not all financial dimensions needed for multi-entity consolidated drill-through may be available out of the box.

For a company running 8 legal entities across the US and Canada and processing 2,500 vendor invoices per month, Acumatica's native Approval Maps (configured on the Assignment and Approval Maps form, EP205500) deliver the multi-dimensional routing this buyer needs. Acumatica allows configuring an approval workflow for AP bills where the approval process can be performed by one person or multiple persons, with parallel or successive multi-stage approval steps. Each Approval Map step contains conditions that evaluate document attributes: conditions can combine Branch (entity), AP transaction Account (GL account range), vendor, and PO number using AND/OR logic within a single rule, enabling compound routing such as 'AP Document Branch = Company 1 AND Account Between 1000 and 2000.' Dollar thresholds are a first-class condition type: for example, AP bills can be initially approved by an accountant, and bills whose total amount exceeds a threshold must also be approved by a top manager, configurable as a sequential multistage process. Conditions filter when a rule applies (e.g., dollar amount or document status), while Rule Actions determine the approver, who can be a specific person, a team, or dynamically assigned based on the employee submitting the request. This covers the bill-entry approval stage; a separate downstream control (Approve Bills for Payment, AP502000) can enforce a second approval gate before cash is released, giving this buyer a two-stage control chain from receipt to payment.

For a $180M, 8-entity professional services company that needs approval routing by entity, department, GL account, and dollar threshold, QB Desktop Enterprise's native capability covers only a narrow slice of that requirement. On Platinum and Diamond tiers, admins access 'Set Up Approval Processes' under the Company menu to create bill and PO approval workflows: the feature lets you set up rules for which purchase orders and bills need approval, with trigger conditions limited to Amount, Vendor name, and Vendor type. Dollar threshold routing is therefore present, but a community user confirmed that 'one can only have one approval workflow per transaction type and we are limited to a single approval level,' meaning multi-tiered escalation chains do not exist natively. GL account-based routing and department-based routing are not available as conditions in the workflow engine at all. On the multi-entity dimension, bill and PO approval workflows are included in the Platinum and Diamond subscriptions only, but because QB Desktop manages each legal entity as a separate company file, there is no unified approval engine that can enforce entity-specific rules across all 8 entities simultaneously: each file would require its own independent workflow configuration, and cross-entity visibility is absent. The glass ceiling for this ERP-native module is clear: it operates at a transaction-entry gate (stage 1 of the pre-processing journey), supports only amount and vendor conditions, enforces a single approval level, and has no concept of GL account, cost center, or department as routing dimensions.

For a professional services and distribution company running 8 legal entities, Infor CloudSuite Financials addresses AP approval routing through two layered mechanisms. The first is the native AP Invoice Automation (APIA) module, which is included in CloudSuite Financials and provides a GUI-based system to define workflow routing rules. As documented in the official CloudSuite Financials help center and confirmed by RPI Consultants' practice-level analysis, APIA routing rules are defined primarily by invoice type and dollar amount, and the entire workflow engine is backed by Infor Process Automation (IPA), which 'backs all workflow' and 'allows you to automate and customize' routing beyond what is pre-configured. The second mechanism, documented in Infor M3's AP module (a second CloudSuite engine), supports division-level AP settings via APS905, where authorized users are registered with maximum allowed invoice amounts enforced at approval, and invoices can be split by accounting dimension so that each recoded accounting line routes to a separate authorized user. Entity-scoped and department-scoped assignment of approvers per accounting identity is configurable, as is delegation of authority per accounting identity. However, consolidating all four dimensions (entity, department, GL account, and dollar threshold) into a single dynamically evaluated rule chain requires IPA workflow configuration beyond the base out-of-box setup; the platform provides the components but not a pre-built four-dimensional rule engine.