D365 Finance vs Epicor Kinetic vs QBO for ERP & Core Accounting

For a controller managing 8 legal entities across the US and Canada, D365 Finance delivers this capability through its Financial Reporting module (formerly Management Reporter) combined with reporting tree definitions. A consolidated P&L is built using a reporting tree that maps each legal entity as a node; the user opens the consolidated report and can drill down through the financial level, to the account level, and then to individual voucher transactions, all within the same session. Financial reporting provides full drill-back to the original transaction in any of the legal entities that are consolidated. When a user wants transaction-level detail for each company, Financial reporting is the solution, because it can show transaction-level detail for as many companies as are included in the reporting tree definition. Mechanically, financial reports include multiple levels of detail: the user selects a summary line to reach the account level, then drills further to view transactions either as report transactions (formatted view) or as voucher transactions via the voucher transaction inquiry, which opens filtered to the period, year, account, and dimension combination of the selected account. When drilling into a previously generated report, the detail is recalculated using current transaction data, meaning the drill path is a live link to the sub-ledger rather than a static snapshot. Intercompany eliminations are also transparent: users can filter the accounts and financial dimensions used to determine intercompany activity on a row or column definition in Financial Reporting and use full drill-down capabilities, then use a calculated column or row to remove those accounts and dimensions from the consolidated total.

For a controller managing 8 US and Canada legal entities who needs to click from a consolidated P&L line into the originating entity transaction, Epicor Kinetic's path runs through two layers. At the ERP layer, the Multi-Site Management module supports native multi-company consolidation: each legal entity runs as a separate company with its own GL, and balances are consolidated into a parent company either continuously or periodically. This resolves the buyer's current spreadsheet-based manual elimination problem. For consolidated financial statement drill-through, Epicor's own documentation identifies Epicor FP&A as 'the mainstream consolidation solution for Epicor today,' and states that 'FP&A reports can drill down to transactions, attachments, invoices, and run the respective Kinetic applications,' meaning FP&A can launch the originating entity's Kinetic application screen from a consolidated view. However, because Epicor Kinetic stores each legal entity in a separate company database, the drill-through from a consolidated FP&A row transitions the user into a different company context within Kinetic rather than navigating within a single unified ledger. The core Financial Report Designer (FRD) in base Kinetic does not provide out-of-the-box financial statements with live drill-through; that capability requires licensing Epicor FP&A or EDA Financial Statements (both Epicor's own separately priced add-ons), and the drill-through depth documented reaches 'journal details' rather than a confirmed single-click path to the entity sub-ledger source document.

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. Intuit does offer the full drill-through mechanism, but only through Intuit Enterprise Suite (IES), a separately licensed and priced product distinct from standard QBO. IES introduced drill-down capability that lets users click into any consolidated P&L value to reach the underlying detailed transaction report, with a company column showing which entities contributed each amount. Intuit's IES marketing confirms users can drill from a consolidated P&L to any entity or department without leaving the platform, with no spreadsheets required.

For a professional services and distribution company running 8 legal entities, D365 Finance's native Workflow framework handles all four routing dimensions the buyer requires. Administrators configure vendor invoice workflows under Accounts Payable > Setup > Accounts Payable Workflows, with a separate workflow instance available per legal entity. An active vendor invoice workflow is set up per legal entity, and invoices can be automatically submitted to that workflow system once configured. Within each workflow, conditional decisions split the workflow into branches, with the system evaluating the document against specified conditions to determine which branch to use. Dollar thresholds are applied directly at the approval-step level: an approval step can be required only when specific conditions are met, such as when the amount of an invoice exceeds a defined threshold like USD 10,000. Department and GL account routing is handled through the Expenditure Reviewers feature: expenditure reviewer configurations dynamically route expenditures for review based on the financial dimension where the expenditure is charged, with the workflow process using the specified financial dimension owner to determine who the invoice is routed to. Critically, expenditure reviewer values can be configured for each legal entity in the organization, and a department financial dimension drives one reviewer while a cost center financial dimension drives a separate reviewer, each resolved from the invoice's distribution data. The main account (GL account) is likewise available as a workflow condition, since financial dimensions play a crucial role in optimizing the invoice processing workflow, ensuring invoices are redirected to the appropriate individuals for approval. Workflow also applies at both header and line level: organizations can use workflows to manage the review process for vendor invoices, with workflow review required for the invoice header, the invoice line, or both.

For a $180M multi-entity professional services and distribution company running 8 legal entities across the US and Canada, Epicor Kinetic addresses AP invoice approval workflows through two complementary layers, each covering different parts of the buyer's required dimensions. For the requisition and purchase order side, Epicor's own Advanced Requisition Management (ARM) add-on delivers multi-dimensional, configurable approval workflows: ARM supports multiple levels, tolerance (dollar) limits, and dimensions including GL Account and location, and explicitly supports multiple company and multiple location requisitions with non-linear approval flows. For non-PO and PO-matched AP invoice approval, Epicor ECM (formerly DocStar) is the documented mechanism: ECM supports tiered approval thresholds, multi-GL account routing, and grouping of approvers by document type, department, or company, covering the threshold and GL account dimensions the buyer requires. The ARM page documents 'Design approval trees by GL Account, Part Class, Location, and more,' and the ECM documentation confirms approvers can be grouped 'by document type, department, or company.' However, the native Kinetic AP module does not natively surface a configurable rules-driven approval engine for posted AP invoices by entity, department, GL account, and dollar threshold in a single unified interface: both ARM (for requisitions/POs) and ECM (for invoice document routing) are separately licensed Epicor add-ons that must be combined to cover all four dimensions the buyer named, and the user forum activity from 2024 shows that native in-system AP invoice approvals (without ECM) require significant configuration effort with no out-of-box rules engine.

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. Dollar thresholds are supported: QuickBooks Online Advanced or Bill Pay Elite customers can add roles and permissions to bill payment flows, for example setting up workflows so every bill above $2,000 requires approval before being recorded and paid. However, the conditions available in the workflow builder are limited to amount, vendor, and location: GL account and department (Class) are not documented as available trigger dimensions. Location in QBO is a single-company field used to tag a branch or office, and is not a true legal-entity separation; QBO Advanced supports only one active bill approval workflow at a time, with a single set of conditions applied to all bills. Because each of the buyer's 8 legal entities requires its own separate QBO subscription, there is no native mechanism to orchestrate or centrally manage workflows across all entities from a single interface.

For a $180M multi-entity company moving off QuickBooks and targeting audited financials, Epicor Kinetic addresses the customer portal requirement primarily through Epicor Cash Collect, a separately priced, cloud-based AR add-on sold and branded by Epicor. Customers are given online account access where they can log in to view open invoices, review account statements and aging detail, submit payments via ACH, EFT, or credit card, and manage disputes and payment promises without contacting AR staff directly. Cash Collect pulls live AR data from Kinetic so invoice status and payment records stay in sync with the ERP ledger. A complementary path exists via third-party processors such as EBizCharge, which integrates natively with Kinetic and provides a branded self-service payment portal where customers can select and pay multiple invoices in a single transaction, with payments automatically posted back to Kinetic's AR and GL.

For a $180M multi-entity professional services and distribution company preparing for audited financials, D365 Finance does not ship a turnkey customer-facing AR portal. The native AR module manages invoice creation, posting, customer account statements (emailed PDFs), and internal collections workflows for your AR staff, but there is no out-of-box externally accessible login environment where your customers can view their invoices and submit payments online. To deliver invoice visibility, the documented approach in the Microsoft ecosystem is to build a portal on Microsoft Power Pages (formerly Power Apps Portals), connected to D365 Finance data via Dataverse. Microsoft partner Avantiico's Finance Portal, for example, is built on this pattern and gives customers secure access to invoice headers, line items, payment settlements, invoice PDFs, and CSVs pulled from D365 Finance data stored in Dataverse. However, this portal pattern covers invoice access and payment history display; it does not include a native embedded payment gateway that lets customers submit ACH or credit card payments and have those transactions settle directly back into the D365 Finance AR subledger. That online payment submission step requires separately sourcing and integrating an ISV solution such as Versapay or Billtrust, both of which maintain their own D365/Microsoft Dynamics integrations but are independently licensed and implemented platforms.

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, QuickBooks Payments enables customers to pay online via credit card or ACH bank transfer, processing payments directly against the invoiced amount. The mechanism is email-driven: 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. On the portal side, the mechanism does not exist natively. QB does not offer such a customer portal; a third-party app is needed to integrate with QBO. Intuit support has confirmed this gap repeatedly: the feature to make a link or customer portal that allows customers to access and update their billing information is unavailable. Customers cannot log in to browse invoice history or aging; the only alternative is that QBO can generate and send customer statements (Balance Forward, Open Item, or Transaction Statement formats) to remind customers of unpaid balances, but these are outbound email/PDF documents, not a login-accessible portal.