Workday Financials vs QBO vs Business Central for ERP & Core Accounting

For a $180M professional services company running 8 legal entities, Workday's Revenue Management module automates invoice creation through Billing Schedules, where each schedule carries a Company field, billing method (fixed-fee, T&M, milestone, subscription), billing frequency, payment terms, and Invoice Type, meaning invoice generation is entity-scoped by design. Workday automates invoice creation based on contract billing terms and schedules, with billing schedule flexibility for different product and service types including projects, usage, subscription-based, T&M, fixed-fee, prepaid, and milestone billing. At the line level, Customer Invoice data includes Company, Currency, Customer, Payment Terms, and Attachment fields, while line data carries Revenue Category, Quantity, Unit Cost, and Worktags, meaning service-line dimensions are captured transactionally. However, real-world production evidence from a multi-entity Workday implementation reveals the key ceiling: the invoice layout is the same across different companies, with variation limited to different addresses and images per entity, rather than independently structured templates per legal entity or service line. Template-level differentiation per entity is therefore limited to header-level branding elements (logos, remit-to addresses) within a shared layout structure, not fully distinct configurable templates per entity or revenue category.

For a $180M professional services and distribution company operating across 8 legal entities, QBO's invoicing customization works as follows: within a single QBO company file, users build invoice layouts using the Custom Form Styles module (Gear icon > Custom Form Styles > New Style), controlling design, fonts, color schemes, logos, and content fields. The Class tracking feature adds transaction categorization but does not provide the functionality to assign a unique invoice template within the same QBO account; instead, Location Tracking (available on Plus and Advanced) allows multiple templates, each with its unique company name and address. When a user creates an invoice, they manually select the desired template via a Customize dropdown, or the system applies a "sticky" default from the last-used template: in QBO, you can utilize only one template per invoice and can have more than one invoice template active, done by clicking the Customize button within the Invoice window. Critically, template selection is never auto-triggered by entity or service-line dimension: there are no routing rules that detect which legal entity or service line originated the transaction and apply the matching template automatically. For true multi-entity isolation across 8 legal entities, each newly purchased company should have its own company file in QBO; multiple companies can share the same account login, but each company file carries its own paid subscription, requiring users to switch between companies so the correct company name appears on invoice messages. This per-file architecture means templates, chart of accounts, and transaction data are siloed by entity, directly conflicting with the buyer's requirement for consolidated intercompany processing and audited financials across all 8 entities in a single workflow.

For a professional services and distribution company running 8 legal entities, Business Central handles the entity dimension of this requirement natively and well. Each legal entity is modeled as a separate 'Company' within a shared BC environment, and report layouts are set on a per-company basis: the same invoice report can render a completely different layout in each company. Each company's Company Information page independently controls the logo, legal name, address, remit-to details, and payment terms that populate invoice headers, so entity-level branding is automatic and requires no manual override per transaction. The Document Layouts feature on the Customer Card (learn.microsoft.com/ui-define-customer-vendor-document-layouts) extends this further by allowing a specific report layout to be pinned to an individual customer and document type (invoice, order confirmation, etc.), so that when an invoice is posted and sent, BC automatically applies the assigned layout without user selection. Layouts themselves are built as Word (.docx) or RDLC files: Word layouts are editable by a power user directly in Microsoft Word using the BC Word Add-in, while RDLC layouts require SQL Server Report Builder or a developer. The service-line dimension of the requirement, however, is not covered natively: BC has no out-of-box rule engine that automatically selects a different invoice template based on the item category, service type, or dimension value on the invoice lines. Achieving true service-line-level template auto-selection would require AL extension development to inject conditional layout-selection logic.

For a professional services firm running 8 legal entities with Azure Active Directory as the corporate identity backbone, Workday Financials supports full SAML 2.0 federation with Microsoft Entra ID (formerly Azure AD) via a pre-built gallery integration. An administrator adds the Workday enterprise application from the Microsoft Entra app gallery, configures SAML signing certificates, and maps Microsoft Entra user attributes to Workday fields; from that point, users authenticate through Azure AD and are silently passed into Workday without a separate ERP password. The setup flow navigates to Entra ID > Enterprise apps > the Workday application integration page and selects SAML as the single sign-on method. Beyond authentication, when a user accesses Workday, Microsoft Entra ID handles the entire authentication flow; new users provisioned in Entra ID result in new user accounts in Workday via SCIM. Azure AD Conditional Access policies (MFA, device compliance) are enforced upstream, so once Workday is configured, Session Control can be enforced to protect sensitive data in real time, extending from Conditional Access. For user lifecycle management, the Microsoft Entra provisioning service automates account creation when new employees are added to Workday, updates attributes when employee records change, and disables accounts when employees are terminated.

For this buyer migrating from QuickBooks Enterprise to an auditable multi-entity ERP, Business Central's Azure AD SSO story is uniquely native: for Business Central Online (cloud), Microsoft Entra ID (formerly Azure AD) is the sole authentication mechanism, not an optional add-on. Once in place, users access Business Central using their Microsoft Entra account, and Microsoft Entra authentication enables Business Central to integrate with various applications and services through a single sign-on experience. The current protocol is OpenID Connect (OIDC) on OAuth 2.0. In 2022 release wave 1 (version 20), Business Central introduced support for OpenID Connect (OIDC) for Microsoft Entra authentication, replacing the older WS-Federation protocol; OpenID Connect is a modern protocol built on OAuth 2.0 with a standard authentication library. Environment-level access is governed by Entra security groups: access to Dynamics 365 Business Central environments is controlled using Microsoft Entra security groups, and admins assign a security group to an environment to decide which users can access it. Conditional Access policies — including MFA, device compliance, and location-based restrictions — flow directly from the buyer's existing Entra tenant: Conditional Access in Microsoft Entra ID provides granular control of MFA through policies, and for Business Central Online, admins can select Dynamics 365 Business Central as a Cloud app to apply access policies to.

This $180M, 320-user company with an Azure AD-centric identity stack will find no native federation path in QBO. Intuit's own support representatives have confirmed on multiple community threads that QBO operates exclusively on Intuit IDs: there is no support for any external identity providers of any kind; users must log on with Intuit IDs and cannot leverage SAML, OIDC, or OAuth 2.0 authentication, and this includes no support for SCIM or JIT provisioning. The only social login option is Google OAuth: the only authentication option beyond Intuit credentials is Google SSO via OAuth, leaving organizations using Okta, Microsoft Entra, or other identity providers with no direct integration path. Third-party identity brokers (miniOrange, OneLogin) advertise workarounds, but these rely on password vaulting rather than true SAML federation, meaning Azure AD Conditional Access policies, device-compliance checks, and centralized deprovisioning cannot be enforced at the QBO authentication layer. QBO offers no SCIM provisioning capabilities on any plan from Simple Start to Advanced, and it does not support enterprise SSO standards like SAML or OIDC.

For a controller currently relying on spreadsheets across 8 entities, Business Central provides two native self-service reporting layers that require no IT or vendor involvement. The primary layer is the Financial Reports feature (formerly Account Schedules): financial reports arrange accounts from the chart of accounts in ways that make data easier to present, and users can set up various layouts to define the information they want to extract. The controller builds reports by composing a row definition (which GL accounts or totaling formulas appear on each line) and a column definition (which time periods, budget comparisons, or formulas appear in each column); to create a row definition, the user chooses 'Edit Row Definition,' explores existing definitions, chooses New, gives the definition a name, and then has a blank definition to build from. Users can also use formulas to compare two or more financial reports and column definitions, create customized financial reports, and create as many reports as needed, each with a unique name. The second layer is Analysis Mode (Data Analysis feature): this feature allows the controller to analyze finance data directly from list pages without running a formal report or switching to Excel; it provides an interactive and versatile way to calculate, summarize, and examine data by adding multiple tabs that represent different tasks or views. For the buyer's 8-entity consolidation scenario, Business Central gives accountants tools to transfer general ledger entries from two or more companies into a consolidated company, where each company involved is a business unit and the combined data lives in the consolidated company; Financial Reports can then be run on that consolidated entity by the controller without IT. The glass ceiling is that complex operational reports combining data across multiple unrelated tables (e.g., mixing AR aging, payroll allocations, and service line metrics in a single custom layout) exceed what Financial Reports and Analysis Mode can express natively and would require Power BI, which involves IT-managed data model configuration.

For a controller currently running QuickBooks Enterprise with zero native report customization, Workday Financials offers a meaningful step up through its native Report Writer tool, which allows users assigned to the 'report writer' security group to build custom reports by selecting a Workday data source (business object), defining columns/fields, applying filters, sorting, and grouping criteria without writing SQL or opening a vendor support ticket. Report Writer is used to create custom reports and is versatile enough for ad hoc or scheduled report generation; users configure reports by defining report fields, filters, and sorting criteria. Users with access to the report writer security group can parse the wide range of Workday data sources to put together a report with only the information required, and custom reports can be shared, edited, and scheduled as needed. Beyond Report Writer, Workday supports ad hoc, drag-and-drop reporting and analysis for quick data discovery, easy report creation, and hassle-free sharing via Discovery Boards embedded in the financial system of record, allowing users to drill down to source transactions and export results. OfficeConnect for Financial Management also empowers accounting and finance teams with live data in Excel as a fallback self-service layer. The glass ceiling for this buyer is the Report Writer's dependency on Workday's proprietary business object model: Business Objects Management requires users to learn which objects contain the information they need and how to combine data from multiple sources, including understanding reference fields that link objects together. Workday's object-oriented architecture can feel daunting to a new user. Creating custom reports should be coordinated and governed appropriately to prevent proliferation and redundancy, and creating them can be time- and labor intensive.

This buyer runs 8 legal entities and needs their controller to build consolidated custom reports without IT or vendor help: exactly the scenario where QBO's self-service reporting shows a hard ceiling. Within a single QBO Advanced company file, the Custom Report Builder is a genuine self-service tool: the controller opens Reports, selects a starting template or builds a transaction-detail report from scratch, adds or removes columns, applies multi-dimensional filters (class, location, customer, account), groups and subtotals data, saves the result as a named custom report, and schedules automated delivery by email. Available exclusively in QuickBooks Online Advanced, the Custom Report Builder "allows you to customize reports by adding, removing, or rearranging columns, changing fonts and colors, and filtering data according to specific criteria" and "enables you to select the fields you wish to include and group data to provide more meaningful insights." Spreadsheet Sync extends this further: with Spreadsheet Sync, the controller can upload and download QBO Advanced information using customizable templates and pull current data into formatted spreadsheets with pivot tables segmented by slicers. However, the mechanism breaks entirely at the consolidation layer. QBO Online operates on a fundamental limitation: one company per subscription, and you cannot consolidate multiple entities within the platform itself. QBO does not feature native tools for combining reports or eliminating intercompany balances across multiple entities; the accounting team must rely on spreadsheets or external integrations for consolidated reporting. For this buyer's 8-entity consolidated view, the controller would need to export each entity's data separately and reassemble in Excel, replicating the exact manual process they are trying to escape.

For a controller at a $180M multi-entity professional services company whose 12-day close is driven by manual journal re-entry each month, Workday Financial Management addresses this directly through its native Recurring Journal Templates feature within the Accounting Journals module. A controller or accounting manager builds a template that stores the ledger account, debit/credit amounts, currency, memo, worktags (including intercompany affiliate), journal source, and a template start/end date range; once configured, journals are generated from that template each period. The template includes a flag to automatically submit generated journals for posting, reducing the trigger to a single generate action rather than manual re-entry of line data each close cycle. Separately, accrual journal entries support automatic reversal: when a journal is posted with a reversal date, Workday creates the offsetting entry in the subsequent period without additional user input, directly targeting the intercompany accrual and month-end adjustment workload this buyer described. The supporting tier's commitment to 'automate and simplify' accounting processes is consistent with these mechanisms.

For a controller at a $180M multi-entity company spending 12+ days closing books, Business Central's Recurring General Journals module directly addresses the labor of re-entering standard monthly entries. The controller configures journal lines once per template: each line carries a Recurring Method (Fixed to hold the amount after posting, Variable to clear it for re-entry, or Reversing variants that auto-post an opposite entry in the next period for accruals) and a Recurring Frequency using date formula syntax such as '1M' for monthly, so the system advances the posting date automatically on each run. A recurring journal is a general journal with specific fields for managing transactions posted frequently with few or no changes, such as rent, subscriptions, electricity, and heat. For the buyer's multi-entity close cycle, the Recurring General Journals page offers an Allocations action to split amounts across multiple accounts and dimensions; the allocation acts as a balancing account line, is entered once, and persists after posting so amounts and splits do not need to be re-entered each period. Accrual automation is handled natively: when using recurring general journals to post accruals at end of period, the Reversal Date Calculation field controls the date that reversal entries are posted when reversal recurring methods are used; accruals are typically posted with Fixed, Variable, or Balance recurring methods. Period-close checklists in Business Central explicitly include recurring journals: update and post recurring journals is a named step in both the sales/receivables and purchases/payables period-close sequences.

For a company running 8 legal entities through separate QBO company files, QBO's 'Recurring Transactions' feature (accessed via Gear icon > Lists > Recurring Transactions) allows journal entry templates to be saved and set to one of three modes: Scheduled, Reminder, or Unscheduled. Recurring templates will only create transactions automatically when the type is set to 'Scheduled' and the template has not reached its end date or maximum occurrences. The controller can configure the account coding, amounts, descriptions, and frequency (e.g., monthly) once, and choose 'Make Recurring' at the bottom of the journal entry form, select a frequency such as weekly or monthly, and QuickBooks will automatically generate entries based on that template. However, accrual reversal is not automated: there is no option to automate the creation of a reversing journal entry, meaning the controller must open each accrual JE after posting and manually click 'Reverse' to generate the offsetting entry in the next period. Additionally, because QBO is a single-entity system, the Recurring Transactions feature is offered in QBO Plus and Advanced versions per company file, so all 8 entity template libraries must be created and maintained independently with no centralized management console.