Why SAP S/4HANA customers add Payment Hub
Use Clarity Payment Hub for SAP S/4HANA payment processing and add the receivables side across every Company Code, alongside SAP Digital Payments.
Payments post to the Universal Journal as Incoming Payments, on-premise or in RISE and GROW with SAP.
So, how does Payment Hub help? S/4HANA's own route to card and wallet payments is the SAP Digital Payments add-on, which connects to payment service providers through SAP BTP, and European operations also have native SEPA credit transfer and direct debit. Large S/4HANA groups run many Company Codes across their subsidiaries, and Payment Hub adds the receivables side on top: a customer portal across Company Codes, Level III data on commercial cards, surcharging where it's allowed, and dunning beyond standard SAP dunning levels. It connects through SAP's published OData / SAP Gateway / Integration Suite / BTP paths, gateway- and processor-agnostic, with 19+ gateway choices behind one consistent integration, per-Company-Code / per-Country / per-Currency routing, and a clean Universal Journal posting via Incoming Payment.
Incoming Payments posted to the Universal Journal
AR automationDunning and reminders for each Company Code beyond standard SAP dunning levels, with a pay-link in every notice.
Cash application and payment reconciliationPayments post as Incoming Payments in the Universal Journal, applied to the billing documents they settle in each Company Code.
One payment, cleared in S/4HANA
- DUNNING NOTICEWith a pay-link
- PAYMENTCaptured on your gateway
- INCOMING PAYMENTPosted to ACDOCA
- COMPANY CODECleared against the open item
Batch payment across Company Codes and currencies
B2B payments across Company CodesBatch payment across invoices, Company Codes and currencies in one transaction, with each receipt posting to the right Company Code.
Credit card processing fees and surchargingA disclosed surcharge in the U.S. and Canada where card-network and local rules allow it. Debit cards are never surcharged.
One payment, several Company Codes
- BATCH PAYMENTSeveral invoices, one transaction
- COMPANY CODESEach receipt posts to its own
- CURRENCIESCaptured in each invoice's currency
- SURCHARGEDisclosed where rules allow
One portal across every Company Code
Customer payment portalOne portal across every Company Code a customer buys from.
ACH paymentsACH for North American customers alongside SEPA Direct Debit in Europe, on the same customer master.
Lower card costs on commercial cards
Level 2 and Level 3 interchangeLine-item data from sales order and billing document lines goes with each eligible commercial card payment.
Visa CEDPIn the U.S., Visa's Commercial Enhanced Data Program now grades that data: on its April 18, 2026 schedule failed data is priced like none and the criteria are unpublished, so the data comes from S/4HANA's own billing lines.
Card cost controls
- COMMERCIAL CARDLevel III from sales order and billing lines
- VISA CEDPLine-item data validated
- DEBIT CARDNever surcharged
Payment Hub vs SAP Digital Payments and certified PSPs, enterprise-scale comparison
SAP's own route is the SAP Digital Payments add-on, a service on SAP BTP that connects S/4HANA to payment service providers for cards and wallets and lets you add or switch providers. Payment Hub works alongside it on the receivables side, where global S/4HANA groups with many Company Codes need a customer portal, Level III data, surcharging and dunning across entities.
| Capability | SAP Digital Payments / certified PSPs | Payment Hub on SAP S/4HANA |
|---|---|---|
| Gateway / processor choice | ✗ Payment service providers connected through SAP Digital Payments | ✓ 19+ gateways (Worldpay, Adyen, Fortis, PayTrace, Stripe, Authorize.Net, NMI, USAePay, plus regional acquirers, plus SAP-certified gateways if you keep them) |
| Universal Journal (ACDOCA) integration | ✓ Native, PSP creates journal entry | ✓ Same, Payment Hub creates Incoming Payment journal entry via OData. Full line-item granularity preserved |
| Multi-Company-Code / multi-Currency routing | ~ Single-MID typical at enterprise scale, multi-CoCd support varies | ✓ Per-Company-Code / per-Country / per-Currency routing, scales to 500+ entities. Different MIDs, gateways, surcharging policies |
| Level III interchange enrichment | ✗ Not auto-enriched, enterprise volume non-qualified or partial-qualified | ✓ Auto-enriched from VBAK/VBAP / VBRK/VBRP / Project Billing line records, 20+ fields per transaction. |
| SEPA SCT and SDD direct debit | ✓ Native to S/4HANA European localizations | ✓ Augmented, multi-bank SEPA SDD routing, B2B vs CORE scheme selection, return automation, ACH bridging on same Customer master |
| SAP BTP "keep the core clean" extensibility | ~ Some certified PSPs deploy ABAP-side. Impacts upgrades and RISE | ✓ Pure BTP side-by-side extension pattern, zero ABAP modifications, RISE-friendly, GROW-compatible |
| Hyperscaler-agnostic deployment | ~ Per-PSP infrastructure dependencies vary | ✓ Identical integration on AWS / Azure / Google Cloud / T-Systems / VMware / on-premise |
| Embedded Analytics & Fiori KPI tiles | ~ Standard FI reports include cash data | ✓ Dedicated payment KPI Fiori tiles, CDS view-based dashboards, real-time HANA-powered metrics |
| Multi-invoice consolidation across Company Codes | ✗ Depends on the provider | ✓ Batch pay across multiple invoices, multiple Company Codes, multiple currencies, single capture, line-level Universal Journal entries |
| Surcharging / convenience fees | ✗ Not native | ✓ Compliant surcharging engine (per-state, per-country, per-card-brand, per-merchant, auto-disabled where illegal) |
| ECC → S/4HANA migration support | ~ Some certified PSPs require re-implementation post-migration | ✓ Plugs into all 3 migration paths (brownfield / greenfield / selective), configuration carries forward |
| SAP Integration Suite / CPI compatibility | ~ Some PSPs integrate with CPI, varies | ✓ Native, Payment Hub registers as another Integration Suite flow alongside SuccessFactors / Ariba / Concur / non-SAP integrations |
See it running on your own S/4HANA tenant
A 30-minute walkthrough: Universal Journal cash application via ACDOCA, multi-Company-Code routing and SEPA augmentation.
Across every Company Code
SAP S/4HANA runs global enterprises, often as many Company Codes across subsidiaries, on-premise or through RISE and GROW with SAP. SAP's own Digital Payments add-on connects it to payment service providers for cards and wallets. Integrating Payment Hub with S/4HANA works alongside that and adds the receivables side:
Every ERP Payment Hub works with is on the ERP payment processing page.
Questions
Does Clarity Payment Hub integrate with SAP S/4HANA?
Yes. Clarity Payment Hub integrates with SAP S/4HANA across all three editions, on-premise, Private Cloud Edition (RISE with SAP), and Public Cloud Edition (GROW with SAP), through SAP's published integration paths: OData services exposed via SAP Gateway, SAP Integration Suite / Cloud Platform Integration (CPI) for middleware orchestration, SAP Business Technology Platform (BTP) for side-by-side extensions, plus traditional BAPI / RFC and IDoc paths where appropriate. Authentication via SAP communication arrangements, OAuth 2.0, X.509 certificates, or SAP Cloud Identity Services.
Does Payment Hub work across SAP S/4HANA's three editions (on-premise, RISE, GROW)?
Yes. SAP S/4HANA on-premise, traditional licensing, customer-managed infrastructure, full ABAP customization flexibility, Payment Hub integrates via OData / SAP Gateway plus BTP-side extensions where customers use BTP. SAP S/4HANA Private Cloud Edition (RISE with SAP), SAP-managed subscription model on hyperscaler infrastructure (AWS, Microsoft Azure, Google Cloud) with the customer's own dedicated tenant, Payment Hub integrates via the same OData / SAP Gateway path, with BTP-side extensions becoming the preferred customization path (keep the core clean).
How does Payment Hub work with the SAP S/4HANA Universal Journal?
The Universal Journal (ACDOCA) is SAP S/4HANA's signature simplification, one table that combines what was previously spread across BSEG, BSAS, ANEK, COEP, and a dozen other tables in ECC. It's the single source of truth for finance.
Does Payment Hub support SAP S/4HANA's multi-Company-Code architecture?
Yes. Multi-Company-Code is SAP's foundational architectural pattern, the enterprise's legal-entity structure modeled as Company Codes with their own currencies, fiscal years, charts of accounts (often shared via the Group Chart), and country-specific tax / localization configurations. Large enterprises commonly run 50–500+ Company Codes across global operations.
What's the implementation timeline for SAP S/4HANA?
A typical Payment Hub + SAP S/4HANA integration goes live in 48 hours once Clarity receives S/4HANA test environment access (OData service activation, communication arrangements set up, communication user with appropriate per-Company-Code authorizations provisioned, X.509 certificates configured, BTP destinations registered if used), gateway credentials, and your baseline routing configuration. SAP S/4HANA enterprise implementations themselves typically run 12-24 months for the platform, Payment Hub's overlay deploys substantially faster because it sits on top of an already-running S/4HANA configuration.
Related resources
Enterprise digital core payment automation on SAP S/4HANA.
Live in 48 hours across all 3 editions.
Book a Live Demo