Payment Hub for SAP S/4HANA, payment automation built into your enterprise digital core.

Why SAP S/4HANA customers add Payment Hub, and what changes when they do

SAP S/4HANA sits at the top of SAP's cloud-and-on-premise ERP portfolio, the enterprise digital core, designed to run the world's largest organizations. Per SAPinsider's 2025 Buyer's Guide, 25,000+ customers have licensed S/4HANA, about a quarter of SAP's total ERP customer base. Another 35,000+ customers are still on SAP ECC or SAP Business Suite, with mainstream maintenance ending in 2027, the single biggest migration event in enterprise software. SAP has emphasized RISE with SAP and GROW with SAP as the modern cloud-deployment paths over traditional licensing.

SAP S/4HANA's signature architectural commitment is the simplification of the SAP Digital Core powered by SAP HANA's in-memory engine. The Universal Journal (ACDOCA) collapses what was previously spread across BSEG, BSAS, ANEK, COEP, and a dozen other ECC tables into one unified table, the single source of truth for finance with full line-item granularity. SAP Fiori provides the role-based responsive UX across desktop, tablet, and mobile. Embedded Analytics, CDS views, queries, KPI tiles, analytical Fiori apps, runs directly against operational data without an ETL layer. SAP Business Technology Platform (BTP) provides the side-by-side extensibility framework for keeping the S/4HANA core clean while building custom applications and extensions. SAP Integration Suite (which includes Cloud Platform Integration / CPI) is the dedicated middleware tier orchestrating SAP and non-SAP integrations.

The gap, common across globally diversified S/4HANA enterprise installations, is the certified-PSP lock-in inherited from the ERP lineage. SAP S/4HANA carries forward the SAP-certified Payment Service Provider integrations (typically Worldline, ConCardis, certain regional acquirers, plus the native SEPA SCT/SDD support for European operations). For globally operating S/4HANA enterprises, the typical large-customer deployment runs 25-500+ Company Codes across global subsidiaries, this is a particularly painful constraint at enterprise scale: single-gateway, single-MID across all Company Codes / Currencies, no Level III interchange enrichment, no surcharging where legal, limited dunning beyond standard SAP dunning levels, customer portal payment surface limited to what SAP Customer Checkout or partner portals provide. Payment Hub fills this gap through SAP's published OData / SAP Gateway / Integration Suite / BTP paths, gateway- and processor-agnostic, 19+ gateway choices behind one consistent integration, with per-Company-Code / per-Country / per-Currency routing matching S/4HANA's enterprise multi-entity architecture, and a clean Universal Journal posting via Incoming Payment.

The three SAP S/4HANA editions, all served by Payment Hub

SAP S/4HANA ships in three editions covering the deployment spectrum from customer-managed on-premise to SAP-managed cloud. Payment Hub integrates the same way across all three, same OData / SAP Gateway path, same BTP-side extensibility option, same feature set. What changes is the deployment topology and the customization boundary.

The integration path is the same across all three editions. What differs is the customization boundary and deployment topology. On-Premise customers have the most flexibility, they can deploy Payment Hub via OData services with a full BTP-side orchestration layer, or alternatively integrate ABAP-side extensions where appropriate. RISE with SAP customers on Private Cloud Edition follow SAP's "keep the core clean" guidance, Payment Hub deploys as a BTP side-by-side extension with OData connectivity to the SAP-managed S/4HANA tenant. The Payment Hub orchestration logic, gateway routing, and customer-portal-side surfaces all run on BTP, leaving the core S/4HANA tenant unmodified and upgrade-safe under the RISE managed-service contract. GROW with SAP customers on Public Cloud Edition use the published public-cloud APIs plus BTP / SAP Build extensibility. The multi-tenant SaaS architecture means stricter customization boundaries, but the Payment Hub feature set is fully available through the API surface. For customers planning an on-premise → RISE migration, or RISE → GROW migration, Payment Hub configuration developed on the source carries forward to the destination.

The three ECC → S/4HANA migration paths, Payment Hub plugs into all of them

35,000+ SAP customers still run ECC or SAP Business Suite ahead of the 2027 mainstream-maintenance end. Per SAPinsider's research, projects typically run 12-24 months and require months of preparation. Payment Hub plugs into all three SAP-supported migration approaches, the choice typically reflects how much of the existing system to keep vs. rebuild.

For all three migration approaches, Payment Hub deploys post-cutover on the target S/4HANA tenant. The migration project itself focuses on the SAP core (data harmonization, custom-code adaptation, role redesign, process redesign). Payment Hub is a clean overlay on top of the running S/4HANA configuration once the cutover is complete. Brownfield migrations typically retain existing customizations and configurations, including legacy certified-PSP add-ons. Payment Hub takes over from these add-ons post-conversion, providing the broader gateway choice and L3 enrichment that the legacy add-ons couldn't deliver. Greenfield migrations design the target architecture from the ground up, Payment Hub is included in the new-system blueprint from day one, so the customer never inherits the certified-PSP lock-in. Selective data transition projects bring forward cleared invoice history, customer master, and selected configurations. Payment Hub deploys on the destination system and the transitioned data retains its payment-allocation links via the migration data-mapping. For customers planning their migration approach, Payment Hub's deployment doesn't constrain the choice, all three paths work.

Universal Journal, Fiori, BTP, hyperscaler, the architecture Payment Hub plugs into

SAP S/4HANA's distinctive architecture has four pillars that distinguish it from ECC and from competitor enterprise ERPs. Payment Hub plugs into each cleanly.

The architectural pillars define how Payment Hub integrates. Universal Journal (ACDOCA): Payment Hub creates Incoming Payment journal entries that post directly into the unified table with full line-item granularity (cleared invoice references, payment-method detail, gateway transaction reference, Profit Center, Cost Center, Functional Area, Segment, Customer, Currency on the same row). The simplified financial architecture means payment data lives where finance lives. No shadow tables, no batch flattening. SAP HANA: Embedded Analytics queries (CDS views) drilling on payment KPIs work natively because ACDOCA is HANA-resident. Days-sales-outstanding, payment-method mix, dispute rate, retry success surface through standard CDS-based reporting without separate BI tooling. SAP Fiori: Payment Hub's customer-facing payment surfaces align with Fiori design language for embedded portal experiences. Fiori KPI tiles on the Launchpad consume payment metrics via Embedded Analytics. SAP BTP: Payment Hub's orchestration logic (gateway routing, L3 enrichment, dunning, customer-portal logic) deploys as BTP-hosted application with native S/4HANA connectivity through OData destinations, preserving "keep the core clean" for cloud-edition deployments and respecting the RISE managed-service contract.

SAP S/4HANA industries and module map, all touched by Payment Hub

SAP S/4HANA serves the full SAP industry portfolio across discrete and process manufacturing, financial services, public sector, retail, and services. Payment Hub plugs into every industry. B2B-heavy verticals drive the highest L3 use at enterprise scale.

S/4HANA's industry breadth is the broadest of any enterprise ERP. Discrete Manufacturing &, Industrial verticals (Automotive, Aerospace, High Tech, Industrial Machinery) drive the highest B2B card volume and the largest L3 use at enterprise scale, Tier-1 OEM customers commonly run multi-million-dollar transactions where line-level enrichment yields substantial savings. Process Manufacturing (Chemicals, Pharmaceuticals, Consumer Products) drives formula-driven and batch-driven payment patterns. Retail &, Distribution with SAP CAR (Customer Activity Repository) and S/4HANA Fashion drives high-volume B2C captures plus B2B wholesale. Services drives project-billing and milestone-based capture patterns through the Project System (PS) module. Financial Services &, Public drives portfolio-level dimensional reporting and regulatory compliance. Cross-Industry Modules (FI / CO / SD / MM / PP / QM / PM) plus the integrated SuccessFactors / Ariba / Concur ecosystem are where Payment Hub touches the integration surface. FI is the primary finance touch point for Universal Journal posting, SD drives order-to-cash, MM drives procurement on the AP side.

Payment Hub vs SAP S/4HANA's certified-PSP integrations, enterprise-scale comparison

SAP S/4HANA inherits SAP-certified Payment Service Provider integrations from the ERP lineage. These work for simple invoice-payment scenarios. For globally diversified S/4HANA enterprises with 25-500+ Company Codes, the integration multiplicity becomes the enterprise-scale constraint. Payment Hub is the orchestration alternative.

How the integration works, OData + SAP Gateway + Integration Suite + BTP

Payment Hub plugs into SAP S/4HANA through SAP's published integration paths. OData services (the modern primary path) via SAP Gateway. SAP Integration Suite / Cloud Platform Integration (CPI) for middleware orchestration. SAP BTP for side-by-side extensions. BAPI / RFC and IDoc for legacy scenarios where appropriate. No core S/4HANA modifications. "Keep the core clean" preserved for cloud editions. Eight features that come online when S/4HANA gets Payment Hub:

The integration workflow, a Tier-1 EV-drivetrain manufacturer on S/4HANA across 24 countries, end to end

Walk through one realistic SAP S/4HANA scenario. Helios Mobility Group, a $5.2B global Tier-1 automotive supplier of electric drivetrain components for major EV OEMs, headquartered in Stuttgart, Germany. Running SAP S/4HANA Private Cloud Edition (RISE with SAP) on Microsoft Azure across 24 countries (Germany / France / Italy / UK / Spain / Netherlands / Sweden / Czech Republic / Romania / Poland / Hungary / Turkey / US / Mexico / Brazil / China / Japan / South Korea / India / Thailand / Vietnam / Australia / South Africa / UAE). 78 Company Codes (multiple per country for legal-entity structures). 18,500 employees. Migrated from SAP ECC in a 24-month brownfield-with-selective-data-transition project completed late 2024. Heavy use across all S/4HANA modules, Universal Journal in finance, Sales &. Distribution for OEM orders, Materials Management for supply chain, Production Planning for manufacturing, Project System for engineering services, integrated SuccessFactors for HR, Ariba for procurement, Concur for T&E. Multi-currency footprint: EUR primary group reporting, plus USD, GBP, JPY, CNY, KRW, INR, BRL, MXN, and 12 others. Currently uses one Worldline-certified PSP integration globally (carried over from ECC) plus native SEPA SCT/SDD for European receivables. Eight steps showing how Payment Hub modernizes the global enterprise payment layer.

Use cases that light up on SAP S/4HANA

All eleven Payment Hub use cases run on SAP S/4HANA at enterprise scale. These are the patterns where the S/4HANA integration shines, and where global enterprise S/4HANA customers across the full SAP industry portfolio get the highest use.

Technical details, for the SAP S/4HANA admins, Basis teams, and BTP developers

For SAP Implementation Partners (Applexus, Argano, EY, KPMG, PwC, Deloitte, cbs, Syniti, others), SAP-certified consultants, and S/4HANA-running enterprise IT teams: the connection model, record surface, multi-Company-Code posture, security posture, and customization compatibility.

Integration paths in detail

OData services via SAP Gateway: modern primary integration path, RESTful endpoints, JSON/XML payloads. Same path SAP Fiori uses internally. SAP Integration Suite / Cloud Platform Integration (CPI): the dedicated middleware tier on BTP. Common where Integration Suite is the customer's central iPaaS. SAP Business Technology Platform (BTP): for side-by-side extensions (the SAP-recommended cloud extensibility pattern). Payment Hub orchestration logic deploys here. SAP API Business Hub: catalog of pre-built APIs and integration content. Payment Hub registers via API Hub-discoverable artifacts. BAPI / RFC: legacy programmatic interface, used selectively for on-premise scenarios where OData isn't applicable. IDoc: for legacy EDI-style partner messaging where required. BAdIs (Business Add-Ins): in-system extension points for customer-specific logic on financial events. Respected on Payment Hub-driven postings. Authentication via communication arrangements, OAuth 2.0, X.509 certificates, or SAP Cloud Identity Services.

SAP S/4HANA records consumed and posted

• KNA1 / KNB1 / KNVV (Customer master, General / Company Code / Sales), read/write via OData. Stored credentials linked back via custom field.
• VBAK / VBAP (Sales Document header / line items), read for order-state events and L3 enrichment.
• LIKP / LIPS (Outbound Delivery header / line items), read for delivery-triggered captures.
• VBRK / VBRP (Customer Invoice header / line items), read for invoice payment + L3 enrichment. Full multi-currency / localized-tax context.
• BSEG / BSAS (legacy ECC document line items / cleared items, preserved as compatibility views in S/4HANA).
• ACDOCA (Universal Journal, the signature S/4HANA single source of truth for finance), written via OData on every capture. Full line-item granularity for cleared invoice references, payment-method, gateway transaction, Profit Center, Cost Center, Functional Area, Segment, Customer.
• BKPF (Accounting Document header, backwards-compatible header view), written for Incoming Payment headers.
• FAGLFLEXA (legacy general ledger flex table, preserved for compatibility in S/4HANA).
• PROJ / PRPS (Project / Project WBS), subscribed for project-milestone events. Read for project-billing cash application.
• T001 / T001W (Company Code / Plant master), read for routing rule lookup.
• TCURR / TCURF (Currency / Exchange Rate tables), read for cross-currency routing and capture conversion.
• T007A / T007S (Tax Codes / Tax Code Names), read for tax engine integration. Country localization applies automatically.

Universal Journal posting posture

• Payment Hub creates Incoming Payment journal entries that post directly into ACDOCA, the unified Universal Journal table.
• Full line-item granularity preserved: cleared invoice references, payment-method detail, gateway transaction reference (custom field via BAdI / append structure), Profit Center, Cost Center, Functional Area, Segment, Customer, Currency, all on the same row.
• HANA's in-memory engine makes Embedded Analytics CDS queries on the unified table trivially performant, sub-second response across enterprise-scale datasets.
• Compatibility views (BSEG, BSAS, BKPF, FAGLFLEXA) continue to read correctly for legacy reports and custom ABAP code that references the ECC-era table structure.
• Multi-invoice batch pay creates multiple Universal Journal entries linked via clearing reference, cleared-line-item drill-through preserved.
• Multi-Company-Code consolidated batch creates separate journal entries per Company Code with appropriate intercompany clearing where applicable.
• BAdIs and workflow events fire normally on Payment Hub-driven journal postings.

Multi-Company-Code posture

• Per-Company Code (BUKRS) / per-Country (LAND1) / per-Currency / per-Language gateway routing through Company Code + tax-jurisdiction lookup.
• Cross-currency capture: authorize in one currency, capture in another, settle through S/4HANA's standard exchange-rate revaluation tables.
• Scales to 500+ Company Codes, typical large-enterprise S/4HANA deployments run 25-500+ Company Codes across global operations.
• Group reporting currency conversion handled natively through S/4HANA Universal Journal's parallel-currency capability (up to 10 parallel currencies per Company Code).
• Inter-Company Sales / Inter-Company Stock Transfer flows preserved for cross-Company-Code production / services flows.

Customization respect &, "keep the core clean"

• For RISE with SAP / GROW with SAP customers, Payment Hub orchestration deploys on BTP side-by-side, zero ABAP modifications, zero impact on RISE managed-service contract, zero impact on GROW Public Cloud upgrade cadence.
• For on-premise customers, BAdIs and append structures provide controlled in-system extension points where appropriate. Pure BTP option also available.
• Custom fields on Customer / Customer Invoice / Sales Order records preserved through OData introspection.
• BAdIs and workflow events fire normally on Payment Hub-driven postings.
• Existing SAP-certified PSP add-ons can coexist during transition. Payment Hub becomes the orchestration layer behind one Company Code at a time during phased rollouts.
• SAP S/4HANA's release cadence (annual on-premise, quarterly cloud) is non-disruptive, Payment Hub uses stable OData endpoints with backward-compatibility guarantees per SAP's release policies.

Security and compliance

• SAP communication arrangements + communication user authentication. OAuth 2.0 for token-based scenarios. X.509 certificates for hardened production. SAP Cloud Identity Services for federated identity.
• PCI DSS Level 1 service provider, with PCI scope minimized via tokenization at gateway.
• Card data never lands in S/4HANA. Tokens stored as custom field on Customer master.
• SOC 2 Type II (Clarity).
• 3DS2 / SCA support natively across all gateways for European compliance (PSD2).
• GDPR-aligned data handling for EU Company Codes. Right-to-be-forgotten cascades from S/4HANA Customer master deletion.
• Country-specific compliance overlays per Company Code (EU VAT / Intrastats, UK MTD. US sales tax via Avalara, APAC GST/SST, Brazilian NFe / SPED, Mexican CFDI, Indian GST).
• SAP's own platform compliance (SOC, ISO 27001, ISO 27017, ISO 27018, FedRAMP for cloud editions) extends through the integration on RISE / GROW deployments.
• For RISE customers, SAP's underlying hyperscaler (AWS / Azure / Google Cloud) compliance posture extends naturally.

Deployment scenarios

• S/4HANA on-premise (customer-managed): OData + BTP integration, full BAdI / append-structure flexibility where appropriate.
• S/4HANA Private Cloud Edition (RISE with SAP): OData + BTP side-by-side, "keep the core clean". RISE managed-service contract preserved.
• S/4HANA Public Cloud Edition (GROW with SAP): public-cloud APIs + BTP / SAP Build extensibility, ABAP Cloud / fit-to-standard.
• Brownfield ECC → S/4HANA conversion: Payment Hub deploys post-conversion, certified-PSP add-ons retire.
• Greenfield S/4HANA implementation: Payment Hub designed into target architecture from day one.
• Selective data transition: Payment Hub on destination. Transitioned cleared invoices retain payment-allocation links.
• Multi-hyperscaler / hybrid environment: Payment Hub hyperscaler-agnostic, same integration on AWS / Azure / GCP / T-Systems / VMware / on-premise / hybrid.
• S/4HANA + Integration Suite (CPI): Payment Hub registers as another integration flow. Coexists with SuccessFactors / Ariba / Concur orchestration.

SAP Business One vs Business ByDesign vs S/4HANA

SAP S/4HANA sits at the top of SAP's ERP portfolio. The natural step up from SAP Business One (small business) and SAP Business ByDesign (mid-market multi-tenant cloud) when the enterprise reaches global scale and needs the deeper industry breadth of the SAP Digital Core. For customers eventually moving up the SAP stack, Payment Hub's configuration ports forward, same gateway connections, routing rules, surcharging, dunning, customer portal, L3 mappings carry across product transitions. The integration surface evolves (Service Layer / DI API on Business One → Web Services / OData on Business ByDesign → OData / Gateway / BTP on S/4HANA at the destination), but the application configuration carries forward without re-implementation. For S/4HANA customers eventually evaluating GROW with SAP for new entities or ByDesign for divisional rollouts, Payment Hub spans both with the same orchestration layer.

Related, explore other Payment Hub topics