SAP Payment Program: Configuration, Payment Runs, and SEPA Direct Debit (Part 2)

Book: Financial Accounting in SAP S/4HANA Finance Simplified: Questions & Answers by Narayanan Veeriah | ISBN 978-93-65898-675

Chapter 16 part 2 is the payment program deep dive. Questions 469 through 497. If part 1 was about who you pay and who pays you, this half is about how money actually moves. House banks, payment methods, bank determination, and the F110 payment run process.

Configuring the payment program

Before touching F110, you need to answer five questions:

1. What gets paid (open item selection rules)
2. Whom (payee, including alternative payee)
3. When (due date from payment terms)
4. From where (house bank and account)
5. How (payment method: check, transfer, ACH, bill of exchange)

Parameters live in master records, payment program customizing, line items, and each payment run’s parameter screen.

FBZP is the one-stop configuration transaction. The IMG path under Automatic Outgoing Payments covers:

• Company code setup for payment transactions
• Paying company code settings (centralized payment scenarios)
• Payment methods per country (OBZ3)
• Payment methods per company code (amount limits, grouping, bank selection)
• Payment medium format per company code
• Bank determination (ranking, amount limits, value dates)
• Payment groupings (OBAP)
• Automatic posting keys (OBXC, OBXP)
• Search fields for payment run display (O7FC, O7FE)

House banks and bank determination

A house bank is your company’s bank, identified by a 5-character code plus country key and bank key. Each house bank holds multiple accounts (Chek1, Pybl1, etc.) linked to G/L accounts.

The payment program iterates payment method, currency, and ranking order to pick the right bank. Classic bank determination assigns one account per house bank-payment method-currency combo. Enhanced determination supports multiple accounts with ranking within one house bank.

Leave PM and Crcy blank to make a house bank valid for all payment methods and currencies. Available amount limits control whether outgoing payments proceed based on account balance. The program will not pull shortfall from another account.

Payment methods can be maintained in three places with a clear priority:

1. Line item (single method, highest priority)
2. Master record (up to 10 methods in order, e.g. CDLTX)
3. Payment run parameters (must match methods in master/line item or conflict stops processing)

Open item selection and cash discount strategy

For payables, the program maximizes cash discount in the current run, selects items going overdue next run, groups invoice-related credit memos with invoices, and defers everything else.

For receivables, pay as soon as possible after first discount term to capture maximum discount.

Cash discount strategies in customizing:

• Max cash discount: early payment, take every discount
• Max credit period: enter 99% threshold, pay net, skip discounts
• Middle ground: adjust the percentage in between

Payment run process (F110)

Five steps:

1. Maintain parameters: run date, identification, company codes, payment methods, posting dates (F110 or F110S for scheduling)
2. Create proposal: schedule immediately or later, review log and exceptions
3. Edit proposal: change payment method, house bank, blocks, cash discount, assign items to different payments. Split editing by accounting clerk ID.
4. Execute payment run: schedule with or without payment medium programs
5. Execute payment medium: print forms or create EDI files if not done in step 4

REGUH, REGUP, REGUD, and SPELL structures hold payment data for form printing. Payment forms use SAPScript with country-specific print programs.

Block open items with blocking keys on line items or payment block in master record. Blocked items appear separately in the proposal. Cancel blocks during editing to release for payment.

ACH, SEPA, payment cards, and advice notes

S/4HANA supports ACH-CCD (corporate), ACH-CTX (trade exchange), and ACH-PPD (payroll/personnel). India equivalents mentioned: NEFT (batch) and RTGS (real-time, large amounts).

SEPA direct debit uses mandates authorizing collection. Configure under Incoming Payments > Management of SEPA Mandates. Two variants: Core Direct Debit and B2B Direct Debit.

Payment cards (credit, customer, procurement) flow from SD or SAP Retail into FI documents. Additional FI customizing under Payments with Payment Cards.

Payment advice notes for incoming payments contain header (payment date, amount) and items (document numbers, billing references). Create manually, via EDI, or import. Enter the advice number and the system proposes open items for clearing, flagging differences and on-account payments.

What I took away

The payment program is not one configuration screen. It is a chain of decisions from master data through FBZP through F110 parameters through proposal editing. The book’s emphasis on payment method priority and bank ranking order matches what breaks in real projects. Wrong method in line item overrides everything. Blank PM field makes a house bank universal. Test run the proposal every time before executing.

Chapter 17 shifts to dunning, special G/L transactions, and FI-SD/FI-MM integration.

Previous: Accounts Receivable and Payable Part 1 | Next: AR/AP Advanced Part 1