No bank change pays out until a second person says yes
Vendor Bank Detail Change Control intercepts every bank account edit, holds outbound payments until an independent approver signs off, and keeps a tamper-evident record of who changed what and why.
The problem
An attacker impersonates a vendor, asks accounts payable to update bank details, and the next payment run quietly sends money to the fraudster. Odoo's standard partner form has no approval step, no masking, and no alert — the change looks like any other edit, and by the time the real vendor asks about a missing payment, the funds are gone.
The solution
Vendor Bank Detail Change Control intercepts every create, edit, repoint, trust, and delete on a vendor's bank account. The live account keeps its old, trusted values until a second user approves the change, so pending or rejected edits never disturb a payment run — and the requester can never approve their own change.
Everything a finance team needs to stop bank fraud
Every capability below is implemented in the module.
Enforced maker-checker approval
Every bank account change becomes a request that a second person must approve. The requester cannot approve their own change — enforced structurally by a database constraint, not just application logic.
Payments blocked until approved
A new or changed bank account cannot receive an outbound payment until the change clears approval. The old, trusted account stays payable the whole time, so routine payment runs never stall.
Side-by-side old-vs-new diff
Approvers see exactly what changed — old account number, holder name, bank name and BIC next to the proposed values — before they decide, instead of hunting through a chatter log.
Masked account numbers everywhere
Account numbers show as four asterisks plus the last four digits in every notification, approval screen, and audit entry, so sensitive data never leaks through a message or email.
Append-only, tamper-evident audit trail
Change requests cannot be edited or deleted by anyone, even administrators, and a SQL constraint blocks self-approval at the database level — a record that survives direct data manipulation.
Transparent risk scoring
Every request is scored in plain language against new-vendor, holder-mismatch, invalid-IBAN, repoint, and trust-change signals, so approvers understand exactly why a change needs a closer look.
IBAN validation and normalization
IBANs are checked with a mod-97 checksum and length validation, then normalized to uppercase with spaces stripped, catching format errors before a payment is attempted.
Pending-approval alerts on the vendor and account
A banner on the vendor record and the bank account form shows at a glance that a change is awaiting approval, closing the blind spot where edits and approvals live on separate screens.
Unified approval queue and change history
A kanban queue grouped by state shows pending and overdue items with one-click bulk approve or reject, backed by a full change-history screen for audits and disputes.
How it works
Request
A clerk edits a vendor's bank details or trust flag. Odoo stages the change instead of writing it, and captures the reason for the request.
Review
An approver opens the queue, sees the old-vs-new diff and the plain-language risk explanation, and starts the review.
Decide
A second user — never the requester — approves, rejects, or flags the request as fraud, with a justification recorded either way.
Audit
Approved changes apply automatically; every decision is logged permanently in an append-only history, searchable by vendor, user, or date.
Frequently asked
No sales fog. If your question isn't here, email us and we'll answer it the same way.
It stops it. A new or changed bank account cannot receive an outbound payment until a second person approves the change — the old, trusted account keeps paying normally in the meantime.
Buy it on the Odoo App Store
Purchase, download and install directly from the official Odoo Apps Store — you'll always get the latest supported build.
Vendor Bank Detail Change Control
Maker-checker approval for vendor bank changes with payments blocked until approved, side-by-side diffs and masked account numbers — with risk scoring, IBAN validation and a tamper-evident audit trail.
Buy on Odoo App Store