# Business Partner and Vendor Bank Details Change Control Report

> A custom ALV report that lists every change to business partner or vendor bank details (IBAN, account, bank key, account holder) in a period with old and new value, changing user and transaction, and flags cases where a payment was made to the new account shortly after the change. The weekly control against payment fraud comes down to one list.

- Type: Report, Custom development, ALV report
- Module: CA
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/vendor-bank-details-change-control-report/


## Why is the standard not enough?

The change history in transaction BP works for one business partner at a time; although change documents can be displayed in general, no standard report gives the bank fields per period, for all vendors and matched with the next payment. Auditors answer the question "was any vendor paid right after a bank detail change?" by comparing change documents with payment run lists by hand. The custom report does this matching automatically.

### Closest standard alternatives

- BP: Shows the change history for one business partner; no view of all vendors per period and no matching with the next payment.
- F110: Provides the payment list of a payment run; it does not compare it with bank detail changes.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| CDHDR | Change document header: user, date, time, transaction (driving table) | Read | - | ECC + S/4 |
| CDPOS | Old and new values of the bank fields | Read | CDPOS-OBJECTCLAS = CDHDR-OBJECTCLAS AND CDPOS-OBJECTID = CDHDR-OBJECTID AND CDPOS-CHANGENR = CDHDR-CHANGENR | ECC + S/4 |
| BUT0BK | Current bank details and account holder of the business partner (S/4HANA) | Read | BUT0BK-PARTNER = CDHDR-OBJECTID | ECC + S/4 |
| BUT000 | Business partner GUID and name | Read | BUT000-PARTNER = BUT0BK-PARTNER | ECC + S/4 |
| CVI_VEND_LINK | Mapping from business partner to vendor number | Read | CVI_VEND_LINK-PARTNER_GUID = BUT000-PARTNER_GUID | ECC + S/4 |
| LFBK | Vendor bank details (for ECC change documents) | Read | LFBK-LIFNR = LFA1-LIFNR | ECC + S/4 |
| LFA1 | Vendor name | Read | LFA1-LIFNR = CVI_VEND_LINK-VENDOR | ECC + S/4 |
| REGUH | Payments made to the new account after the change | Read | REGUH-LIFNR = LFA1-LIFNR AND REGUH-XVORL = ' ' | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_UDATE | Change date | Range / multiple | CDHDR-UDATE | Yes |
| S_USER | Changed by | Range / multiple | CDHDR-USERNAME | No |
| S_PARTNR | Business partner | Range / multiple | BUT000-PARTNER | No |
| S_LIFNR | Vendor | Range / multiple | LFA1-LIFNR | No |
| S_ZBUKR | Paying company code | Range / multiple | REGUH-ZBUKR | No |
| P_PAYDY | Payment check after change (days) | Single value | - | No |
| P_MASK | Mask account numbers | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Change date | CDHDR-UDATE |
| Time | CDHDR-UTIME |
| Changed by | CDHDR-USERNAME |
| Transaction | CDHDR-TCODE |
| Business partner | BUT000-PARTNER |
| Vendor | LFA1-LIFNR |
| Vendor name | LFA1-NAME1 |
| Field | CDPOS-FNAME |
| Change type | CDPOS-CHNGIND |
| Old value | CDPOS-VALUE_OLD |
| New value | CDPOS-VALUE_NEW |
| Account holder | BUT0BK-KOINH |
| First payment date | REGUH-LAUFD |
| Amount paid | REGUH-RWBTR |
| Currency | REGUH-WAERS |
| Risk | Calculated: Payment to new account within N days: High; user outside master data: +1; account holder mismatch: flag |

## How does the report work?

1. Change documents in the selected date range are read from CDHDR: in S/4HANA the business partner bank details object (BUPA_BUK, table BUT0BK), in ECC vendor master data the object KRED (table LFBK).
2. Lines for the bank fields are taken from CDPOS (BANKS, BANKL, BANKN, IBAN, KOINH); the change type (CHNGIND: I insert, U update, D delete) and the old and new values are read.
3. The business partner is derived from the object key; through CVI_VEND_LINK and BUT000-PARTNER_GUID it is mapped to the vendor number and the vendor name is read from LFA1. In ECC the vendor number is in the key directly.
4. Payment check: in REGUH entries of real runs (XVORL blank), a payment to the same vendor within N days after the change date and to the new account (ZBNKN/ZBNKL or ZIBAN) is searched; the first payment date and amount are added.
5. Risk: a payment to the new account within N days after the change is High; one level higher if the changing user is not in the master data group; a mismatch between the account holder name and the vendor name is flagged as well.
6. With "Mask account numbers" selected, only the last four digits of account and IBAN values are shown.

## Authorization objects

- B_BUPA_GRP: Display authorization by business partner grouping
- F_LFA1_BUK: Display authorization for vendor data by company code

## Frequently asked questions

### Does the report show the full IBAN?

Not by default; account and IBAN values are masked and only the last four digits are visible. The unmasked view can be restricted with a separate authorization.

### Is a vendor bank change caught if it was made with old transactions instead of BP?

In ECC systems vendor master changes are written to the KRED change document object, which the report also reads. In S/4HANA vendor bank details are kept on the business partner, so changes appear in the business partner bank object.

### What if no change documents are written?

Bank fields write change documents as standard. At installation the report warns if the selected objects have no entries in the last 90 days, so a problem with the change document settings gets noticed.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=ca-business-partner-bank-details-change-control
