Lesson 3 of 5
Sensitive fields and dual control
9 min
Some BP fields can move money. The most important is the supplier's bank account. A fraudster who gets a supplier's bank details changed, often with a convincing email and a letter that appears to come from the supplier, can redirect real payments for weeks before anyone notices. This "payment diversion" fraud is common, and the defense is partly in SAP and partly in process.
Dual control in SAP
SAP lets you define sensitive fields for customers and suppliers in Customizing (for example, bank details, payment method or alternative payee). When a user changes a sensitive field, the account is blocked for payment until a second, authorized person confirms or rejects the change. The change is visible immediately, but money cannot flow on it until it is confirmed. Confirmation is done per account, in SAP GUI with transactions such as FK08 (confirm a single supplier) and FK09 (list of suppliers to confirm), and FD08/FD09 for customers; Fiori apps cover the same step in many releases. Reports list the changes awaiting confirmation.
- ChangeA master data clerk changes the bank account of Lakeside Components
- BlockThe supplier is automatically blocked for payment because a sensitive field changed
- VerifyThe approver calls Lakeside on a known number from the existing record, not from the request
- Confirm or rejectA second, authorized user confirms the change; the payment block lifts
- PayThe next payment run pays to the new account; the change history shows who changed and who confirmed
The process around the system
The system enforces two people; it cannot judge whether the change is genuine. That is the process's job. Contoso's rules for bank changes: requests arrive only through the supplier portal or on a signed letter, never by email alone; the approver verifies by calling a contact from the existing record, not from the request; the person who changed the field cannot confirm it; and changes within 30 days of a large payment get a second verification. Authorization design must back this up: the clerk's role must not include confirmation, and nobody should hold both for the same accounts.
- Did the request arrive through an approved channel with supporting evidence?Yes → continue · No → reject and inform the supplier through known contacts
- Was the change verified with the supplier using contact details already on file?Yes → continue · No → do not confirm; verify first
- Is the confirmer a different, authorized person from the one who made the change?Yes → confirm · No → route to an authorized second person
- Is a large payment due soon after the change?Yes → apply the extra verification step · No → normal confirmation
Change documents as evidence
Every BP change is recorded in change documents: which field, old value, new value, who and when. In the BP transaction and the Fiori master data apps you can display the change history for a record. Together with the confirmation record, this is the evidence auditors ask for and the first place to look when a payment went to the wrong account.
Customers have sensitive fields too. A changed customer bank account matters for direct debits and refunds, and a changed alternative payer or payment method can redirect money in subtler ways. Contoso defined bank details, payment methods and alternative payee or payer as sensitive for both customers and suppliers, after the finance team walked through which fields could cause money to move to the wrong place. The list is reviewed whenever new payment methods are introduced.
What would you do?
An email from "Lakeside Components accounts" asks Contoso to update the bank account before tomorrow's payment run, attaching a letter on Lakeside letterhead. The clerk has changed it. The approver, under time pressure, is asked to confirm. What should the approver do?
- Bank details are the prime target for payment diversion fraud.
- Sensitive fields trigger a payment block until a second authorized person confirms the change.
- Verify through contacts already on file; never confirm on the strength of the request alone.
- Change documents plus confirmation records are the audit evidence.
Check your understanding · not graded
Lesson check
1. Why should bank detail changes on a supplier BP be controlled?
2. What happens when a sensitive field on a supplier is changed?
3. Which SAP GUI transaction confirms a change for a single supplier?
4. Which evidence shows who changed a BP field and when?