SAP ECC vs SAP S/4HANA vs QBO for ERP & Core Accounting

For a company running 8 legal entities the way this buyer does, SAP ECC natively models each legal entity as a distinct 'Company Code' (field BUKRS), which is a required header field on every AP document posted through transactions FB60 (Enter Vendor Invoice) or MIRO (Enter Incoming Invoice). A centralized AP team can be granted cross-company-code posting rights through authorization object F_BKPF_BUK ('Accounting Document: Authorization for Company Codes'), which allows a single AP user's role profile to span all 8 company codes simultaneously without requiring separate logins or siloed sessions. When an AP clerk enters an invoice, the company code is stamped at the header (and can be split to line items via document splitting), ensuring audit-grade entity coding on every document. SAP ECC's cross-company-code transaction framework further supports central procurement and central payment scenarios: one company code can process invoices on behalf of others, with the system automatically generating a separate legal document per entity linked by a common cross-company code reference number, which satisfies intercompany reconciliation requirements.

For a $180M professional services company running 8 legal entities across the US and Canada, SAP S/4HANA handles this through its Company Code construct combined with the Manage Supplier Invoices Fiori app (F0859) and the SAP authorization framework. A centralized AP team operates inside a single S/4HANA client where all entities are represented as distinct company codes: if you want to manage the accounting for several independent companies simultaneously, you can set up several company codes in one client; the company code is the central organizational unit of external accounting within the SAP System. When an AP clerk opens the Manage Supplier Invoices app, they enter the relevant basic data, such as company code, invoice date, and posting date as required fields on every invoice, enforcing entity coding at the point of entry without any workaround. A single AP user can be authorized to post across all 8 entities simultaneously: in the authorizations for each authorization object, you can specify which activities (such as create, change, display, and so on) may be performed in which company code; Authorization 'A' allows the user to perform the activities create, change, and display in company codes 1000 and 2000. The Supplier Invoices List app then aggregates invoices from all authorized company codes into a single worklist, with the option to enter a default value for the company code on the launchpad under Settings, with the default applied in searches so processors can filter by entity without switching logins. For buyers wanting a more robust centralized intake layer on top of core S/4HANA AP, SAP Ariba Invoicing (formerly Central Invoice Management) is a cloud-native solution on SAP Business Technology Platform for receiving and managing supplier invoices from multiple connected systems, enabling centralized invoice processing with embedded OCR capabilities, automated workflows for approvals, and seamless integration with backend ERP systems.

For the buyer's scenario of 8 legal entities with a single centralized AP team, QBO's architecture presents a fundamental structural barrier. Each QBO company is a fully isolated file: although companies share a sign-in credential, their data remains completely separate, users set up in one company do not automatically have access to others, and must be invited to each company separately. The 'Switch Company' function allows toggling between companies to manage them separately, but this is sequential file-by-file processing, not a unified AP queue where a centralized team codes invoices with entity tags across all 8 entities in a single workflow. QBO Plus and Advanced offer Classes and Locations as segmentation dimensions, but these are used to categorize transactions into segments such as departments or product lines to track profitability and expenses by business area within a single company file. They are sub-entity segmentation tools, not legal entity coding for separate books. The key distinction is that QuickBooks is a multi-company tool, not a native multi-entity system: every company file stays isolated, and bank feeds, user permissions, vendor lists, and the chart of accounts are all separate by design. Intuit's separate product, Intuit Enterprise Suite (IES), does offer a Multi-Entity Hub with consolidated AP and vendor expense allocation across entities from a single interface, but IES is a distinct mid-market product requiring a full migration away from QBO, not a QBO module or upgrade tier.

For a $180M multi-entity company needing to connect SAP S/4HANA Cloud Public Edition to Salesforce CRM and ADP payroll, SAP exposes its integration layer through the SAP Business Accelerator Hub (api.sap.com), which serves as the central, publicly accessible catalog of all released APIs. OData, the primary API type for S/4HANA Cloud Public Edition, is a standardized protocol that complies with REST architecture and qualifies as RESTful, allowing consumers to publish and edit resources via simple HTTP messages. OData versions 2 (V2) and 4 (V4) are both supported, with V4 improving processing time and resource consumption. All publicly available APIs for S/4HANA Cloud Public Edition are listed on the SAP Business Accelerator Hub, a web application hosted by SAP to discover, explore, and test APIs. Developers can test APIs using the Try Out functionality with available sandbox and standard data, or against their own SAP S/4HANA Cloud system. Authentication uses OAuth 2.0: modern cloud deployments favor OAuth 2.0 for its flexibility and security, with S/4HANA Cloud supporting several OAuth flows including client credentials for server-to-server integration. For the buyer's specific Salesforce and ADP integration needs, SAP Integration Suite (formerly SAP Cloud Platform Integration) provides pre-built integration content (iFlows) for connecting SAP S/4HANA with third-party systems. The buyer's internal development team can also build custom integrations directly against the documented OData endpoints without requiring a third-party intermediary, as the hub provides access to documentation, API metadata, and a mock-up of the service, along with the option to create code snippets for calling the service in the developer's preferred programming language.

For a $180M multi-entity company needing to connect SAP ECC to Salesforce CRM and ADP payroll via documented REST endpoints, the integration story is materially more complex than the buyer's requirement implies. SAP ECC's native integration layer relies on BAPIs (Business Application Programming Interfaces), RFC (Remote Function Calls), and IDocs rather than REST APIs. REST-style access is achievable through SAP NetWeaver Gateway, which can expose OData v2 services that use standard HTTP verbs (GET, PUT, POST, DELETE); however, this requires deliberate ABAP and SAP Basis configuration work to define, activate, and publish each OData service. There is no pre-built developer portal with turnkey documented REST endpoints comparable to what modern API-first ERP platforms publish out of the box. OAuth 2.0 authentication is not enabled by default on SAP NetWeaver Gateway in ECC: it requires manual activation via transaction SOAUTH, while standard RFC connections authenticate via SAP system user credentials or SNC certificates configured in SM59. A REST-to-RFC proxy is also available via SAP BTP (SAP's cloud middleware), but that path adds a separate middleware layer and corresponding licensing cost.

For a $180M company running 8 legal entities across the US and Canada, QBO does offer a fully documented REST API through the Intuit Developer Portal at developer.intuit.com. QuickBooks Online has a REST API maintained by Intuit, accessible through the Intuit Developer Portal. The API uses OAuth 2.0 for authentication and supports JSON payloads, covering the full accounting data model: customers, invoices, bills, payments, vendors, accounts, and profit/loss reports, with endpoints for create, read, update, delete, and query operations. Webhooks deliver real-time notifications when data changes in a connected company file; developers subscribe by registering a webhook endpoint URL in the Intuit Developer Portal and specifying which entities and event types to monitor, and Intuit sends a POST request to the endpoint with the entity type, operation, and company ID when an event occurs. However, the architecture is scoped strictly per company file: every API call targets a specific company (realm) identified by a realmId, and all requests require a valid OAuth 2.0 access token. Each connected QuickBooks company is a separate realmId with its own token pair and rate limit bucket, requiring the database schema and job queue to partition by realmId from day one. For this buyer's 8-entity shared services model, that means 8 separate OAuth authorization flows, 8 independent token refresh loops, and 8 isolated API connections with no consolidated cross-entity query layer, which adds significant custom engineering overhead when building Salesforce CRM or ADP payroll integrations that need to operate across all entities.

For a company like yours processing 2,500 invoices per month across 8 entities, SAP ECC's F110 Automatic Payment Program handles ACH, check, and wire within a single payment run: each vendor's preferred payment method is stored in the vendor master (transaction FBZP/LFBK), and F110 generates a payment proposal, routes each invoice to the correct method, and produces the corresponding output file in one batch. Check printing (payment methods C, I, S), ACH via NACHA format (payment method T using the Payment Medium Workbench and DMEE/DMEEX format engine), and wire transfers (also via DMEE with bank-specific format trees) all execute within the same F110 run and post automatically to the ledger. Virtual card disbursement, however, is not native to SAP ECC: the SAP Community confirms that virtual card payments in SAP environments are processed outside the system through a bank or third-party card provider platform, with payment advice either created manually or via SAP payment media files and sent externally. Achieving true virtual card AP disbursement on ECC requires integrating a separate third-party product such as Taulia or a bank-provided card platform, which lives outside F110 and introduces a separate reconciliation step.

For your multi-entity professional services and distribution environment processing 2,500 invoices per month across 8 legal entities, SAP S/4HANA's Automatic Payment Program (transaction F110, surfaced in S/4HANA Cloud as the 'Schedule Automatic Payments' Fiori app) handles ACH, wire, and check natively within a single payment run. The payment program supports configurable payment method types including Wire Transfer, ACH, and Check; specific payment methods are linked to bank transactions in configuration to ensure accurate and smooth payments. A single F110 payment run can include multiple methods simultaneously: for example, ACH and wire running daily and checks running on specific days, all resolved from the same proposal. Each vendor's master record stores the preferred payment method, and the system routes each invoice to the correct disbursement rail automatically during the payment run. For bank transmission, following a payment run, payment messages can be sent to the relevant bank automatically via SAP Multi-Bank Connectivity, a SaaS connectivity solution that enables banks and their corporate customers to exchange messages (MBC requires a separate SAP license). Virtual card disbursement for vendor AP payments, however, is not part of this native F110 workflow: virtual card payments for vendors/suppliers are positioned through SAP Ariba and SAP Taulia, which are separate SAP products with their own licensing, workflow, and login surface. SAP does have a 'Supplier Financing with Virtual Card Payment' scope item in S/4HANA Cloud, but its documented scope covers supply chain finance/early payment scenarios rather than a standard AP disbursement rail alongside ACH, check, and wire in a single F110 run.

For your 2,500-invoice-per-month AP operation, QBO's built-in Bill Pay module supports two of the four required payment rails natively within its workflow: ACH bank transfer and paper check. From the Pay Bills screen, your AP team selects a bill, chooses 'Schedule payment online,' and picks either ACH or paper check as the delivery method; reconciliation posts automatically to the QBO ledger. A virtual card option also exists within the Bill Pay workflow, but it is payee-driven: when your team schedules an ACH or check payment, the vendor receives an email and can opt to receive a single-use virtual card instead -- your AP team cannot proactively select virtual card as a payment rail at the time of scheduling. Wire transfers are explicitly absent from QBO Bill Pay as a native disbursement option; Intuit's own support documentation confirms that wire, EFT, and similar transfers are handled only as a manual recording workaround (typing 'wire' in the check number field) rather than as an initiated payment rail, and international wire requires a separate third-party application from a different vendor entirely.