SAP Vendor Master Change Request Form Template
Vendor bank detail changes are the entry point for most business email compromise losses against accounts payable. This form forces the evidence to be written down: how the request arrived, who verified it, and who approved it separately from who entered it.
Fill in
SAP Vendor Master Change Request Form Template
Vendor Master Change Request
Company: Acme Precision Ltd Date: 2026-10-20 Vendor: 100245 Northfield Castings Inc. Company code and purchasing organization: 1000 / 1000 Change type: Bank details
Requested change
| Item | Current value | New value |
|---|---|---|
| Bank details | Bank: First Commerce Bank, Acct ending 4471 | Bank: Lakeshore Trust, Acct ending 9082 |
Source and verification
Request received by: Signed letter on vendor letterhead Call back to number held on file: Yes Verified by: R. Nair, 2026-10-20
Contact details from the request itself must not be used for verification.
Controls checklist
| Control | Done | Initials |
|---|---|---|
| Vendor identity confirmed against existing master record | ||
| Bank country and IBAN or account format validated | ||
| Duplicate bank account search across vendors | ||
| Payment proposal reviewed for open items before change | ||
| Change entered by person other than the approver | ||
| Change documents reviewed after posting (SCDO or report RFKABL00) |
Approvals
In ECC the transactions are XK02 central, FK02 accounting and MK02 purchasing. In S/4HANA vendors are maintained as business partners in BP with customer vendor integration. Change documents are written for master data, check your own display transaction. This is a control template, adapt thresholds to your policy.
Want vendor change alerts from your ERP data?
We can discuss a read only report that lists bank detail changes and duplicate accounts for review.
Optional. The tool and every export work without this. No spam.
How to use the form
Complete one form per vendor and per change type. Record the current value as it appears in the master, the requested value, and the source of the request. The verifier must call the vendor on a telephone number that was already in the master before the request, not a number from the request. Attach the supporting letter, and file the exported PDF with the change record. A different person should key the change into SAP than the one who approves it.
Segregation of duties
The control that matters most is that the same person cannot create a vendor, change its bank data and run the payment. Many SAP clients rely on authorization objects such as F_LFA1_GRP and F_LFA1_BUK to separate roles. The form makes the split visible by having an entered by signature and a separate approved by signature. For bank changes add treasury review, because treasury is often the last human check before the payment run.
What to review after the change
After posting, review the change documents to confirm that only the fields on the form changed. Many teams run a periodic report of bank changes in the last seven days and compare it with the forms on file. Also search for duplicate bank accounts across vendors: two vendors sharing an account is a classic fraud and duplicate vendor signal. Check the payment proposal before the next payment run, so a change made yesterday does not release a payment today without review.
Common mistakes
Teams often verify using the contact details inside the email requesting the change, which defeats the control. Another mistake is changing the master record before a pending payment run finishes, so the old invoice pays to the new account. Some teams also forget that reconciliation account changes require care because open items exist, and that payment terms changes affect only new invoices unless open items are reassigned.
Frequently Asked Questions
Which SAP transaction changes vendor bank details?
In ECC use XK02 for central data or FK02 for company code data. In S/4HANA use the BP transaction on the business partner, which updates the vendor role. Bank details are on the Payment Transactions tab.
Do I need approval for every vendor change?
Not necessarily. Most policies require dual control for bank, tax number and payment method changes, and allow single entry for low risk changes like a phone number. Set the threshold in your policy and mark it on the form.
Where can I see who changed a vendor?
Display the vendor change documents from the master record, or use a change document report on the vendor object. Standard reports such as RFKABL00 list the master data changes for a period.
Can this form be used for customer master changes?
The structure works, but replace the vendor fields with customer data and use FD02 or BP. Customer credit limit and reconciliation account changes need their own checks, so create a variation rather than reusing it unchanged.
If you want vendor change monitoring and duplicate bank detection built into your ERP reporting, we can scope it with you using read only access.
Related Tools
SAP GL Account Master Data Request Template
A fill-in request form for creating or changing a G/L account in SAP, with the settings your FS00 or master data team needs to see.
SAPSAP Accrual Journal Entry Worksheet
Month end accrual list with a calculated accrual per item, based on service period, days received and amount already invoiced.
SAPSAP Intercompany Reconciliation Worksheet
Pairwise intercompany balance comparison with difference, percent difference and reason tagging, ready for the close meeting.
SAPSAP Foreign Currency Valuation Worksheet
Open item list with historic and closing exchange rates that calculates unrealized gain or loss, for checking an FAGL_FCV valuation run.
More SAP tools
See all- SAP Sales Document Types Reference
- SAP Pricing Procedure Design Worksheet
- SAP Item Category Determination Reference
- SAP Delivery Block Reasons Template
- SAP Credit Management Checklist
- SAP Output Determination Checklist
- SAP Billing Types Reference
- SAP Incompletion Log Checklist
- SAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)