FBZP — Automatic Payment Program Configuration
FBZP is used to configure company-code, payment-method, house-bank and bank-determination settings used by F110. It is most useful when implementing or troubleshooting automatic outgoing/incoming payment selection and bank determination. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains FBZP — Automatic Payment Program Configuration — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 607 words
Purpose
configure company-code, payment-method, house-bank and bank-determination settings used by F110. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
FBZP is typically used when implementing or troubleshooting automatic outgoing/incoming payment selection and bank determination. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Identify the exact F110 proposal error before changing configuration.
- Review payment method at country and company-code levels.
- Check bank determination, ranking order and available accounts.
- Validate amount/currency restrictions and required master data.
- Retest with a small payment proposal before broad production use.
Key data objects
These are the fields and business objects that usually explain the result in FBZP. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- paying company code — verify the exact value, validity/date context and source of derivation.
- payment method — verify the exact value, validity/date context and source of derivation.
- house bank/ranking order — verify the exact value, validity/date context and source of derivation.
- bank account — verify the exact value, validity/date context and source of derivation.
- form/payment medium settings — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
FBZP remains foundational for classic automatic payments in S/4HANA, even where payment media and bank communication use newer frameworks. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Changing bank determination to fix one vendor whose master data is wrong. Reconcile the exact document and period before making a configuration change.
- Opening payment methods too broadly across currencies/countries. Reconcile the exact document and period before making a configuration change.
- Testing configuration only by posting a live payment instead of a controlled proposal. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/fbzpERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.