FI / FICOintermediate

FICO Accounts Payable Part 2: Supplier Master Data and Core AP Configuration

Key takeaway

Set up suppliers and AP controls: business partner roles and grouping, reconciliation accounts, payment terms, tolerance groups, duplicate invoice check, one-time suppliers, withholding tax basics and the settings that prevent errors and fraud.

Explanation

📌 KEY POINTS
✅ In S/4HANA suppliers are business partners; BP grouping maps to number ranges and the supplier account group.
✅ Company code data holds the reconciliation account, payment terms, payment methods and withholding tax.
✅ Payment terms (OBB8) define baseline date, cash discount and net due periods.
✅ Tolerance groups limit payment differences; duplicate invoice check uses reference, date, amount and supplier.
⚠️ Sensitive fields (bank details) should require dual control before payments.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced AP. Now master data and configuration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. BUSINESS PARTNER SETUP

Roles (supplier, FI supplier), grouping, number ranges.

━━━━━━━━━━━━━━━━━━━━
▶ 2. COMPANY CODE DATA

Recon account, payment terms, methods, house bank, withholding tax.

━━━━━━━━━━━━━━━━━━━━
▶ 3. PAYMENT TERMS

e.g. 2% 10 days, net 30.

━━━━━━━━━━━━━━━━━━━━
▶ 4. TOLERANCES AND DUPLICATE CHECK

Supplier tolerance groups; duplicate invoice check fields.

━━━━━━━━━━━━━━━━━━━━
▶ 5. SPECIAL CASES

One-time suppliers (CPD), alternative payee, withholding tax.

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

Create supplier BP with company code data.
Assign payment terms and recon account.
Test duplicate check with a repeated invoice.

✅ CHECKPOINT: the second invoice triggers a duplicate warning.

Code example

ABAP Code

===== CONFIG MAP =====BP grouping & number ranges → supplier account group mapping (CVI)Payment terms ............ OBB8 (e.g. Z001: 2% 10 days, net 30)Tolerance groups ......... OBA3 (customer/supplier) | OBA4 (users)Sensitive fields / dual control ... SPRO: define sensitive fields for dual control (supplier)Withholding tax .......... SPRO > FI > Financial Accounting Global Settings > Withholding Tax ===== MASTER DATA =====BP roles FLVN00 (supplier) / FLVN01 (FI supplier) | company code: recon account 211000

Real project scenario

A shared service center paid a supplier twice because the invoice reference was keyed with a different format. Standardizing reference entry and adding duplicate check fields reduced duplicates; a monthly duplicate report caught the rest.

Common mistakes

Duplicate suppliers.
No dual control on bank data.
Wrong recon account.
Inconsistent payment terms.
Ignoring duplicate warnings.

Best practices

Govern supplier creation.
Dual control on sensitive fields.
Standardize terms.
Duplicate check and review.
Periodic master data cleanup.

Interview angle

Questions: "How is a supplier created in S/4HANA?", "What controls prevent duplicate payments?", "What is dual control?"
Strong answer: BP roles/grouping, company code data, terms, tolerances, duplicate check, dual control.

Practice this lesson

Quick check

1. During vendor invoice entry, SAP can perform a duplicate invoice check based on certain fields. Which combination of fields is typically used by this standard check?

2. A company configures withholding tax at the time of invoice posting for a vendor. What is the key characteristic of this withholding tax type compared to one configured at payment time?

3. Which control reduces the risk of fraudulent supplier bank changes?

Interview questions

1. In the Business Partner model for Suppliers, what is the relationship between the BP General Data, the Supplier role, and the Company Code segment, and why can a supplier exist as a BP without being usable in FI postings?

Answer it in your own words first, then compare.

2. What is a Business Partner (BP) with the Supplier role, and what basic master data structure supports it in the context of Procure-to-Pay integration with MM?