Xero vs Sage Intacct vs QB Desktop for ERP & Core Accounting

For a $180M professional services and distribution company moving off QuickBooks Enterprise with 8 legal entities in the US and Canada, Sage Intacct's Global Consolidation module directly addresses the cross-entity drill-down requirement. From a consolidated P&L, any line item or total rendered as a blue hyperlink can be clicked to reveal the entity-level GL entries that compose that total; the user can continue clicking through successive layers until reaching the individual source transaction, with each level identifying the operating currency of that entity. Per the Sage Intacct help documentation: 'You can continue to drill down through any blue links available, until you reach the transaction level.' The mechanism is native to the Financial Report Writer and Global Consolidation module: reports output in HTML expose clickable totals that resolve first to the consolidation journal entries and then to the originating transaction in each entity's books, with both the consolidated reporting currency and the entity's operating currency displayed at each step. This capability is available through Sage Intacct's Consolidation subscription (Domestic Consolidation for same-currency entities, Global Consolidation if USD and CAD entities require multi-currency books), priced as a separately licensed module but delivered entirely within the Sage Intacct platform.

For a company like yours with 8 legal entities across the US and Canada, the core issue is architectural: Xero treats every organisation as a fully isolated ledger. As multiple independent analyses and Xero's own community responses confirm, there is no native group-level P&L, no consolidated balance sheet, and no cross-entity drill-down within Xero itself. Each of your 8 entities would have its own separate Xero organisation, its own chart of accounts, and no awareness that the other entities exist. Clicking from a consolidated P&L figure to the originating entity-level transaction — without leaving a single interface — is not a capability Xero's product delivers. Xero acquired Syft Analytics (a consolidation reporting tool) in 2024 but has not merged that capability into its core product; Syft remains a separately operated tool. All other consolidation options (Joiin, Fathom, Spotlight Reporting, dataSights, Translucent, etc.) are products from separate vendors that the buyer would have to source and integrate independently. When those third-party tools do offer drill-down, it routes back into the individual Xero organisation file rather than operating as a single-interface, real-time drill-through — which reintroduces the fragmentation your team is trying to eliminate.

Your scenario involves 8 legal entities and a controller spending 12+ days on manual consolidation: this is precisely the workflow QB Desktop Enterprise's multi-company feature was designed to help, but its architecture does not support the interactive drill-through you require. QB Desktop Enterprise offers a 'Combine Reports from Multiple Companies' feature, available in the Enterprise tier, where a user selects multiple company files, picks a report type (P&L, Balance Sheet, etc.), sets a date range, and clicks 'Combine Reports in Excel.' The output is a Microsoft Excel spreadsheet containing the combined financial data from each entity. Because the consolidated view exists only inside that Excel file and not inside the QB Desktop application itself, there is no mechanism to click a line on a consolidated P&L and navigate to the originating entity-level transaction: the user must manually switch back to the relevant company file and locate the transaction there. The supporting fact sheet claim describes intercompany transaction tracking and reporting via a dashboard, but this covers tracking intercompany entries within the product, not a consolidated P&L with interactive drill-through to sub-ledger transactions across separate company files.

For a company running commercial accounts at Bank of America, Sage Intacct addresses positive pay through two documented paths. First, the platform's native Custom Report Writer (CRW), included in the core subscription, lets the AP team build a positive pay report directly against the AP Payment data source: columns are ordered and renamed to match the bank's required layout, filtered to check payments for a selected date range, and exported as CSV or Excel for manual upload to Bank of America's CashPro portal after each check run. Second, and more robustly, Sage Intacct's own Marketplace lists Wipfli's PositivePay add-on, which is built on Intacct Platform Services and fully integrated with the Cash Management module; it generates structured positive pay files with configurable headers, footers, and detail lines to match any bank's required format, supports unlimited separate file layouts per bank account, and automatically captures voided checks without manual re-entry. The Wipfli product explicitly states it is compatible with all U.S. banks and credit unions, which covers Bank of America commercial accounts. Files are generated based on a cutoff date and historical files are archived for reporting purposes.

For a $180M multi-entity company relying on Bank of America commercial accounts, QB Desktop has no native positive pay file generation feature. Intuit support staff have confirmed this across multiple community threads: "The option to create a positive pay file in QuickBooks Desktop (QBDT) is unavailable at this time" and "At this time, this feature isn't available in QuickBooks Enterprise." The closest native path is to run the Missing Check or Check Detail report, customize it to display Date, Check Number, Payee Name, and Amount, export to Excel, reformat the columns to match Bank of America's fixed-width or CSV spec, and upload manually. However, this path has a confirmed field gap: QB Desktop does not expose the 'Print Name on Check As' field in any check report export, only the internal Vendor Name, which breaks payee-name matching that Bank of America's commercial positive pay requires. The clean mechanism requires a separate third-party tool such as BRC PositivePay file Creator for QB Desktop (by Big Red Consulting) or Treasury Software's Bank Positive Pay, both listed on the QuickBooks Desktop App Marketplace. These tools pull check data directly from the QB company file and output bank-spec CSV or fixed-width files; BRC supports approximately 140-160 predefined bank formats plus custom layouts, and Treasury Software claims 350+ verified layouts. Both vendors state they can add unsupported banks on request. Bank of America, as one of the largest US commercial banks, is likely already in either library, but the buyer must confirm before committing.

For a $180M multi-entity company running commercial accounts at Bank of America, positive pay requires generating a structured check-issuance file (fixed-width or bank-specific format containing check number, account number, issue date, and dollar amount) and transmitting it to BoA after each check run. Xero's documented AP payment file export covers batch payments to a set of specific ANZ, BNZ, Kiwibank, ASB, Rabobank, Westpac, TSB, and Nelson Building Society accounts in New Zealand; for any bank outside that list, Xero exports only a generic CSV that Xero Central explicitly notes 'might not be in the specific format required to upload to your bank account.' No Xero help article, product page, or App Store listing documents a native positive pay file template for Bank of America or any US bank. Xero's US fraud-prevention guidance covers access controls and audit logs, with no mention of check issuance file generation.

For your US entities banking with Bank of America, Xero provides a documented direct bank feed partnership: once connected, statement lines flow automatically into each Xero organisation on a regular basis and land in the Bank Reconciliation screen, where Xero's matching engine (Match, Create, Transfer tabs) compares statement lines against outstanding invoices, bills, and rules, with JAX AI auto-reconciliation available to categorise and match high-confidence transactions without manual review. For your Canadian entities banking with TD Canada Trust, the situation is different: Xero Central's Canadian-specific connection guide lists TD Bank under the manual-download fallback path (OFX/QIF/CSV export from TD's EasyWeb portal, then import into Xero), and the documented Yodlee credential-sharing feed for TD Canada Trust requires manual refresh for most accounts rather than automatic polling. A BetaKit report from February 2024 confirmed that TD Bank's Canadian open-banking data agreement runs through Plaid, not through Xero's aggregator (Flinks/Yodlee), leaving no confirmed automatic direct feed from TD Canada Trust into a Canadian Xero organisation.

For your Bank of America commercial accounts, Sage Intacct's Cash Management module includes a named, direct API connection to Bank of America CashPro. You request API credentials through the Bank of America Developer Studio, provision a Client ID and Client Secret via the CashPro portal, then connect each account on the Banking cloud tab of the account record in Cash Management; the provisioning process typically takes a couple of weeks on BofA's side, after which the feed connection itself takes only minutes. Once connected, Sage Intacct receives daily transaction data and applies automated Create Rules (drafting journal entries from bank feed transactions) and Match Rules (matching bank activity to existing Intacct transactions), directly cutting the manual reconciliation work that currently drives your 12-day close. For your TD Canada Trust accounts in the Canadian entities, the documented path runs through FISPAN, Sage's recommended bank feed partner that explicitly covers Sage Intacct clients in the U.S. and Canada, and has a documented TD plugin for Sage Intacct; a secondary path is AccessPay, Sage's premium bank feed provider (Canada is an approved integration country), which connects via the SWIFT network using MT940/BAI2 statements. Both FISPAN and AccessPay are accessible directly from within Sage Intacct's Banking cloud tab and are Sage's own recommended solutions, not separate third-party products requiring independent procurement. Each of your 8 entities can maintain independent bank account connections within Sage Intacct's native multi-entity architecture.

For a company running 8 legal entities across the US and Canada, QuickBooks Desktop's Bank Feeds module offers two connection modes per company file: Direct Connect (a live server-to-server link requiring bank enrollment and a bank-issued PIN or password) and Web Connect (a manual .QBO file download from the bank's website, then imported via Banking > Bank Feeds > Import Web Connect Files). For Bank of America, Intuit support documentation has explicitly confirmed that for certain commercial account types 'QuickBooks Desktop doesn't have the option to directly connect your Bank of America account,' leaving Web Connect as the only path; and community threads document persistent Direct Connect outages and error codes even where enrollment was attempted. For TD Canada Trust, Direct Connect availability for QB Desktop commercial accounts is not confirmed in Intuit's own documentation; the Canadian QB Desktop help center covers only the Web Connect (.QBO file) path as the reliable fallback. Critically, bank feeds in QB Desktop are scoped to a single company file, with a hard cap of 40 linked accounts per file: the buyer's 8 legal entities each require a separate company file and a separate reconciliation workflow, so there is no unified bank reconciliation view across entities.