SAP Advanced Payment Management and In-House Banking: how a payment actually flows

If you run payments in SAP S/4HANA, two components decide what really happens to a payment after the payment run creates it: Advanced Payment Management (APM) controls the payment on its way out, and In-House Banking (IHB) gives the group its own internal bank. This post walks one payment through both, then separates the three scenarios practitioners mix up most: POBO, PINO, and intercompany payments.

What APM does

APM sits between the payment run and the bank. A payment arrives as a payment item, gets enriched with missing data, validated against your rules, and routed — to a house bank account, or to the in-house bank. Payment format converters produce the bank-specific file formats, and Bank Communication Management (BCM) handles approval workflows and the connection to the bank. The value is control: one place where payments can be checked, held, combined, or redirected before money leaves the group.

What IHB does

In-House Banking runs internal current accounts for group companies inside SAP. A subsidiary’s “bank account” becomes an IHB account, with the central treasury entity acting as the bank: account limits, conditions, and fees are configurable, interest can be calculated, and every internal transaction posts to FI like an external one would. Subsidiaries stop needing external accounts for group-internal flows — and treasury sees the group’s cash in one place.

One payment, end to end

1. Intake — the payment item lands in APM from the payment run (or a manual request).
2. Enrichment and validation — bank details, formats, and rules are checked and completed.
3. Routing — APM decides: external house bank, or internal via IHB.
4. Approval — BCM applies the release workflow (who may approve what, up to which amount).
5. Execution — the file goes to the bank, or the IHB posting moves value between internal accounts and posts to FI on both sides.
6. Statement side — the external account statement comes back and is matched; IHB produces its own internal statements for the participating companies.

POBO, PINO, and intercompany — the difference that matters

• POBO (Pay On Behalf Of): the central entity pays a subsidiary’s external obligation from the central external bank account. The money physically leaves from one account; the subsidiary’s books still show its own payment, settled through IHB.
• PINO (Pay In Name Of): the payment is executed centrally through APM/BCM, but from the subsidiary’s own external bank account. Central control, local account.
• Intercompany (internal) payments: both sides are group companies. No external bank is involved at all — value moves between IHB accounts and posts to FI in both company codes.

Confusing POBO with PINO is the most common design error in APM projects: they look similar in a process diagram and behave completely differently in cash pooling, bank fees, and reporting.

Where implementations usually hurt

• Payment routing rules that nobody documented, discovered only when a payment goes to the wrong account.
• BCM approval limits copied from an old org chart.
• IHB fees and interest conditions configured once and never revisited.
• No reconciliation routine between IHB internal statements and FI.

Going further

Aumtech Solutions’ course SAP S/4HANA Advanced Payment Management and In-House Banking (APM + IHB) follows this exact flow in seven recorded lessons, with the configuration behind each step and the companion presentation included: https://www.aumtechsolutions.com/courses/sap-apm-in-house-banking-training/

Not sure where your own payment setup stands? The free SAP Treasury Health Check scores your processes across treasury, payments, and bank statements in about 20 minutes: https://www.aumtechsolutions.com/treasury-health-check/