FI / FICOadvanced

FICO Accounts Payable Part 5: Automatic Payment Program Configuration and Payment Runs

Key takeaway

Configure and run F110: all company codes and paying company codes, payment methods per country and company code, bank determination (ranking, accounts, available amounts, value date), house banks, payment medium formats, and the daily run — parameters, proposal, review, payment and bank file — plus troubleshooting.

Explanation

📌 KEY POINTS
✅ FBZP covers: all company codes, paying company codes, payment methods (country and company code), bank determination.
✅ Bank determination: ranking order, bank accounts, available amounts and value dates.
✅ Run steps: parameters → proposal → review/edit → payment run → payment medium (bank file) → clearing.
✅ The exception list explains why items were not paid (blocks, missing bank data, method not allowed).
⚠️ Editing the proposal is the last control point — review it before executing the payment run.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered architecture. Now the payment program.

━━━━━━━━━━━━━━━━━━━━
▶ 1. ALL / PAYING COMPANY CODES

Tolerance days, sending company code, forms.

━━━━━━━━━━━━━━━━━━━━
▶ 2. PAYMENT METHODS

Country level (e.g. bank transfer, check); company code level (limits, format).

━━━━━━━━━━━━━━━━━━━━
▶ 3. BANK DETERMINATION

House banks, ranking order, accounts, available amounts.

━━━━━━━━━━━━━━━━━━━━
▶ 4. RUNNING F110

Run date + ID, parameters, proposal, edit, payment, printout/file.

━━━━━━━━━━━━━━━━━━━━
▶ 5. TROUBLESHOOTING

Exception list: payment block, no bank details, amount limits, missing method in supplier master.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Configure FBZP for a company code.
Create run with parameters.
Review proposal and exceptions.
Execute payment and create bank file.

✅ CHECKPOINT: paid items are cleared and the exception list is empty or explained.

Code example

ABAP Code

===== CONFIG MAP (FBZP) =====All company codes: paying company code, tolerance daysPaying company codes: minimum amounts, formsPayment methods in country: T (transfer), C (check) — required master dataPayment methods in company code: limits, payment medium format (PMW/DMEE)Bank determination: ranking order, bank accounts, available amounts, value dateHouse banks: FI12 ===== RUN =====F110: Run date 26.09, ID 0001 → Parameters (company codes, methods, next date, suppliers) → Proposal → Edit → Payment run → Payment medium

Real project scenario

A shared service center found many invoices on the exception list with "no valid payment method" after migrating suppliers. Payment methods were missing in company code data. A mass update and a supplier creation check fixed it.

Common mistakes

Skipping proposal review.
Missing payment methods.
No available amounts control.
Uncontrolled bank changes.
Ignoring exception list.

Best practices

Review proposals.
Maintain supplier payment data.
Control available amounts.
Dual control on bank data.
Analyse exceptions daily.

Interview angle

Questions: "Explain F110 configuration", "What is bank determination?", "Why was an item not paid?"
Strong answer: FBZP components, bank determination, run steps, exception analysis, controls.

Practice this lesson

Quick check

1. In the dunning program configuration for accounts payable-related credit memos or debit-side dunning scenarios, what determines the dunning level assigned to an open item?

2. During the automatic payment program (transaction F110), what is the correct sequence of steps a user must execute to process vendor payments?

3. Many invoices appear on the F110 exception list with "no valid payment method". What is the likely cause?

Interview questions

1. What payment methods are typically configured in the Automatic Payment Program for vendor payments, and what standard report or table would you use during AP month-end close to reconcile the total amount actually paid per payment method against the payment proposal?

Answer it in your own words first, then compare.

2. What payment methods are typically configured for vendor payments in SAP, and what reports would you use to reconcile payment method usage at month-end close?