Business Partner and Vendor Bank Details Change Control Report
Short answer: 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.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 8
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Internal control and internal audit teams, accounts payable managers, treasury and master data owners.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| CDHDRChange Document Header | Change document header: user, date, time, transaction (driving table) | — | ECC + S/4 |
| CDPOSChange Document Items | Old and new values of the bank fields | CDPOS-OBJECTCLAS = CDHDR-OBJECTCLAS AND CDPOS-OBJECTID = CDHDR-OBJECTID AND CDPOS-CHANGENR = CDHDR-CHANGENR | ECC + S/4 |
| BUT0BKBusiness Partner Bank Details | Current bank details and account holder of the business partner (S/4HANA) | BUT0BK-PARTNER = CDHDR-OBJECTID | ECC + S/4 |
| BUT000Business Partner: General Data | Business partner GUID and name | BUT000-PARTNER = BUT0BK-PARTNER | ECC + S/4 |
| CVI_VEND_LINKAssignment Between Vendor and Business Partner | Mapping from business partner to vendor number | CVI_VEND_LINK-PARTNER_GUID = BUT000-PARTNER_GUID | ECC + S/4 |
| LFBKVendor Master: Bank Details | Vendor bank details (for ECC change documents) | LFBK-LIFNR = LFA1-LIFNR | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor name | LFA1-LIFNR = CVI_VEND_LINK-VENDOR | ECC + S/4 |
| REGUHPayment Program Settlement Data | Payments made to the new account after the change | REGUH-LIFNR = LFA1-LIFNR AND REGUH-XVORL = ' ' | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_UDATE | Change date | Range / multiple | CDHDR-UDATE | Yes | 10.11.2026 – 16.11.2026 |
| 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 | 1000 |
| P_PAYDY | Payment check after change (days) | Single value | — | No | 30 |
| P_MASK | Mask account numbers | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Change date | CDHDR-UDATE |
| 2 | Time | CDHDR-UTIME |
| 3 | Changed by | CDHDR-USERNAME |
| 4 | Transaction | CDHDR-TCODE |
| 5 | Business partner | BUT000-PARTNER |
| 6 | Vendor | LFA1-LIFNR |
| 7 | Vendor name | LFA1-NAME1 |
| 8 | Field | CDPOS-FNAME |
| 9 | Change type | CDPOS-CHNGIND |
| 10 | Old value | CDPOS-VALUE_OLD |
| 11 | New value | CDPOS-VALUE_NEW |
| 12 | Account holder | BUT0BK-KOINH |
| 13 | First payment date | REGUH-LAUFD |
| 14 | Amount paid | REGUH-RWBTR |
| 15 | Currency | REGUH-WAERS |
| 16 | Risk | Calculated Payment to new account within N days: High; user outside master data: +1; account holder mismatch: flag |
Sample output
| Change date | Time | Changed by | Transaction | Business partner | Vendor | Vendor name | Field | Change type | Old value | New value | Account holder | First payment date | Amount paid | Currency | Risk |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 11/11/2026 | 16:42:10 | MDVERI01 | BP | 1000245 | 100245 | Atlas Ambalaj | IBAN | U | TR** **** 4417 | TR** **** 9023 | Atlas Ambalaj San. ve Tic. A.Ş. | 11/13/2026 | 186,400 | TRY | High |
| 11/12/2026 | 09:15:33 | SATINALMA03 | BP | 1000512 | 100512 | Ege Kimya | IBAN | I | TR** **** 6610 | Mavi Danışmanlık Ltd. | 0 | TRY | High – account holder mismatch | ||
| 11/14/2026 | 11:03:47 | MDVERI02 | BP | 1000387 | 100387 | Delta Metal | KOINH | U | Delta Metal Ltd. | Delta Metal San. Ltd. Şti. | Delta Metal San. Ltd. Şti. | 0 | TRY | Low | |
| 11/15/2026 | 14:20:05 | MDVERI01 | BP | 1000733 | 100733 | Kuzey Lojistik | BANKL | U | 0062**** | 0046**** | Kuzey Lojistik A.Ş. | 12/04/2026 | 52,750 | TRY | Medium |
How does the report work?
- 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).
- 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.
- 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.
- 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.
- 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.
- With “Mask account numbers” selected, only the last four digits of account and IBAN values are shown.
Performance notes
Always read CDHDR with the object class and date range; access CDPOS with the full key. Read REGUH only for the vendors found and the date range. Running it as a weekly background job and emailing it to internal control is sufficient.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the business partner opens the change history in BP.
- Export to Excel
- Runs as a background job
- Send the result by email The weekly list can be sent to the internal control team.
Authorization objects
- B_BUPA_GRPDisplay authorization by business partner grouping
- F_LFA1_BUKDisplay 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.
Packages that include this solution
SAP Access and Payment Risk Audit Pack
A six-component pack that brings together the controls asked most often in the yearly IT and finance audit: users with critical authorizations, …
Related reports
Duplicate Business Partner Detection Report (Name, Tax Number, Address)
A custom ALV report that finds cases where the same customer or vendor was created under more than one business partner number, using the tax number, …
Vendor Open Items Aging Report
A custom ALV report that ages vendor open items by net due date and spreads the amounts into not-due, 0–30, 31–60, 61–90 and 90+ day buckets. The …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.