SEPA Verification of Payee for Odoo 19
Catch IBAN‑name mismatches before you authorise a SEPA credit transfer. Record your bank's Verification of Payee (VoP) result inside Odoo, block unreviewed mismatches, and keep an audit trail of every payment decision.
The control gap in vendor payments
Since the EU Instant Payments Regulation made payee verification mandatory for payment service providers, the decisive “does this name match this IBAN?” warning often lives only in your bank portal or bank API — outside Odoo. Accounting teams copy results into spreadsheets, resolve close‑matches inconsistently, or discover a misdirected payment only when the bank rejects a batch. Odoo holds the vendor master data and the approval workflow, but not the verification evidence.
How SEPA Verification of Payee solves it
This module adds a VoP control layer to Odoo vendor payments. It records the result returned by your bank, PSP, or imported portal file, enforces a company policy on what each result is allowed to do (allow, warn, or block), and preserves an auditable approval trail. It is not a regulated PSP service — it gives your finance team a controlled, evidenced bridge between Odoo payment preparation and your bank's VoP channel.
Key features
Pre‑payment VoP gate
Every SEPA credit transfer carries a visible VoP status before authorisation or file export, so no payment moves unreviewed.
Multi‑source capture
Bank/PSP API connector, bank‑portal manual entry, imported response file, or a sandbox source for testing — useful before every bank ships an Odoo endpoint.
Policy engine
Per‑company actions for Match, Close Match, No Match, and Not Possible results. Decide what blocks, what warns, and what proceeds.
Override & dual approval
Require a manager second approval to override a No Match above configured thresholds, with an alert when too many exceptions occur in a window.
Append‑only audit log
Every verification, decision, import, and config change is recorded immutably — the evidence trail an internal auditor needs.
Alias management
Record accepted payee name variants (trading names, abbreviations) so a known close‑match is not re‑flagged on every run.
Bulk import pipeline
Upload bank‑supplied result files (CSV, JSON, XML pain.002), validate, reconcile, and apply results with full match statistics.
Batch & PII care
Single and batch payment runs, with explicit opt‑out recording where the PSP permits it. IBANs are masked for non‑managers and never written to logs.
Watch the walkthrough
English — product walkthrough
Español — recorrido del producto
Deutsch — Produktrundgang
See it inside Odoo
Who it is for
- EU and SEPA companies (20–1,000 employees) with recurring vendor payment runs
- CFOs and Finance Directors who own payment‑risk policy and override thresholds
- Accounting managers and AP clerks who run payments and resolve mismatches
- Internal auditors who review payment‑control evidence
- Odoo partners configuring bank‑specific rollout
Compatibility
Odoo 19 Community and Enterprise. Builds on the standard Accounting and vendor‑payment workflow. Batch‑payment integration activates automatically when Enterprise account_batch_payment is present; the core VoP gate works on Community. No external SaaS required.
Free — LGPL‑3
€0
Free and open‑source. Install it, own it, extend it inside your Odoo. Brand‑building release from FlexigoTech.
Frequently asked questions
Does this make my company legally compliant as a PSP?
No. The Verification of Payee legal obligation falls on payment service providers, not on ordinary Odoo accounting users. This module supports your internal controls by recording the PSP's verification result and evidencing your decision — it is not a regulated PSP service and makes no compliance guarantee.
How does it get the verification result from my bank?
Three ways: a bank/PSP API connector, manual entry of a result shown in your bank portal, or import of a bank response file (CSV, JSON, or XML pain.002). A sandbox source is included for testing before your bank exposes an endpoint.
Does it work on Odoo Community?
Yes. The core VoP gate, policy engine, audit log, sources, aliases and imports run on Odoo 19 Community. Batch‑payment integration activates automatically when the Enterprise account_batch_payment module is installed.
What happens on a No Match result?
It depends on your company policy. By default No Match blocks the payment; a manager can override above a configured threshold, optionally requiring dual approval, and the override is recorded in the append‑only audit log.
Is personal data exposed in logs?
No. IBANs are masked for non‑manager users, and the structured logger never writes IBANs, payee names, or credentials to log files. The audit trail stores only what is needed to evidence a decision.
Can I customise the policy and connectors?
Yes. Policy actions are configurable per company and per result category, thresholds can vary by amount and risk, and the source/connector system is pluggable for bank‑specific implementations. The module is LGPL‑3, so you can extend it freely.
Bring payee verification into Odoo
Record the result, enforce the policy, evidence the decision — without leaving your accounting workflow.
Contact FlexigoTech| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 2685 |
| Technical Name |
flexigo_sepa_verification_of_payee_module_for_odoo_19 |
| License | OPL-1 |
| Website | https://flexigotech.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module