Module for Odoo 17 · 18 · 19 · 20
SEPA Verification of Payee (VoP) in Odoo: catch the mismatched IBAN before you pay a supplier
A control layer for SEPA supplier transfers under Regulation (EU) 2024/886: records your bank's verification result, applies a per-company policy (allow, warn or block), requires dual approval for overrides and keeps an audit trail of every payment decision.
€9 + €29/month + VAT
Support within 4 working hours and video calls? Pro: €58/month + VAT. Your subscription keeps the module working. Pro support is optional: if you drop it, the module carries on the same with standard support.
What's included
- On FlexigoTech Cloud: official sources checked every day
- Module updates
- Support with a first response within 1 working day
- Your data stays yours: view and export it anytime.
- 14-day trial, no card needed

What it does
- VoP gate before paymentEvery SEPA credit transfer shows its verification status before authorisation or file export; nothing leaves unreviewed.
- Several result sourcesBank-portal file import, manual capture and a sandbox for testing; there is no API connector to the bank.
- Per-company policyDefine what each result (match, close match, no match) is allowed to do: allow, warn or block.
- Dual approval and aliasesSecond approver for high-value overrides and payee alias history to review close matches.
- Audit, evidence and batchesAppend-only event log with retention, attached bank certificates, pain.001 batch coverage and connector health, multi-company.
How the module works
Real screenshots of every screen, with what each one does.

VoP results ledger
Central list tracking every check: IBAN, result status, decision and timestamp per payment.

Per-company policy
Sets what each result does: Allow on Match, Block on No Match, with threshold and dual approval.
What the cloud does for you
Upcoming official deadlines
Terms, data sent and fine print
FlexigoTech Cloud
Monitoring of this module with FlexigoTech Cloud
FlexigoTech Cloud, an external service of FlexigoTech (Flexibles y Accesorios Gobe, S.L., Spain) that runs on our servers, outside your Odoo, adds monitoring for this module. Every day it checks the official sources we follow for this module and alerts you when they change. It also gives you a calendar of their official deadlines and watches the health of the module in your database.
Price
- Module: 9 €.
- The module license is bought separately, at the same price on the Odoo App Store and on flexigotech.com. With the subscription, the module for new Odoo versions is included if you bought it on flexigotech.com; on the Odoo App Store, each Odoo version is bought there. If you have a partner discount, it applies only to subscriptions of single modules, never to packs or to the module price.
- The subscription is separate and is billed by FlexigoTech, not by Odoo: 29 € a month or 290 € a year.
- Pro, with the first response within 4 working hours and a video call if needed: 58 € a month or 580 € a year.
- Per production database, VAT excluded. The staging and test copies of that database are included.
- You see the final amount, with taxes, on the payment screen before confirming.
- You can try each module for 14 days from your Odoo, at no cost and without giving a card: the 14 days count from the first synchronisation, up to 30 days from when you start the trial, and there is one trial per account and module. If you have not subscribed when it ends, the service stops and nothing is charged.
- You pay in advance, every month or every year. The subscription renews automatically at the end of each period until you cancel it, in two clicks and without talking to anyone, from your account at app.flexigotech.com or from your Odoo. Cancellation takes effect at the end of the period you have already paid; there is no pro rata, the part of the period you do not use is not refunded, unless the law requires it, and there is no penalty.
How to activate it
Your database connects from your Odoo, in Settings → FlexigoTech Cloud, with the free FlexigoTech Cloud base module; then you subscribe there or in your account.
An administrator first reads and accepts the list of data below: nothing is sent before that. Then you can start the trial or subscribe; you accept the subscription terms there, and payment is made outside Odoo.
You need Odoo.sh or your own server: Odoo Online does not accept third-party modules.
You accept the Subscription Terms when you start the trial in your Odoo or when you subscribe.
What the subscription includes
- If you bought the module on flexigotech.com: the new versions we publish, including for new Odoo versions, at no extra cost, and their download from your account (not during the trial).
- The monitoring of the official sources of the module, with its alerts and the calendar of their deadlines, and of the health of the module in your database.
- Support: whoever buys a module always gets help to configure it and fixes for its bugs, with or without a subscription. The subscription adds times for the first response, in Barcelona working days and hours (Standard, 1 working day; Pro, 4 working hours, and a video call if needed). Resolving each case takes the time it needs.
- The service on the staging and test copies of your database.
What it does not include
- The customisation of the module or custom development.
- Migrations: we give you the module for each new Odoo version, but we do not take care of migrating your database to that version.
- Configuring the module for you (the setup).
- Importing historical data.
- Support for modules that are not ours.
- Third-party costs: you contract and pay for your account on each platform, Odoo and your hosting yourself.
What your Odoo sends to FlexigoTech Cloud
- The identifier (uuid) of the database, its address (URL) and the Odoo version.
- The FlexigoTech modules installed, with their version, and whether the database is a neutralized copy (staging or test).
- The company name, and the email of the person who accepts, with the date and version of the text accepted.
- A request for its service permit every 6 hours, and the health of the module: counters and errors (type and code), without the content of your records.
- Its requests for the alerts and the calendar of this module, with the date of the last alert received: the database identifies itself and sends nothing else.
What happens if you do not pay
If a payment fails, you have a 7-day grace period with the service. On day 7 the service is suspended; if you pay before day 21, it comes back at once. On day 21, if it is still unpaid, the subscription ends and a later payment does not reactivate it: to come back, you take out a new one.
Without a subscription, or with the service suspended, what the subscription gives stops: the cloud, the module for other Odoo versions and its download, and the subscription's support, with its response times. What the purchase of the module includes does not change: you always have help to configure it and fixes for its bugs and, if you bought it on flexigotech.com, the download of that Odoo version with its updates. The installed module stays in your Odoo with the version you have, and all your data stay there: we never delete anything in your Odoo and we do not block Odoo.
Without the service, the alerts, the calendar and the monitoring of the module stop. Your data is still yours, and you can always view and export it.
Configuration help and bug fixes are always provided to buyers, with or without the subscription.
The control gap in supplier payments
Since the EU Instant Payments Regulation made beneficiary verification mandatory for payment service providers, the decisive question "does this name match this IBAN?" often lives only in your bank's portal or API, outside Odoo. Accounting teams copy the results into spreadsheets, resolve partial matches inconsistently, or discover a misdirected payment only when the bank rejects the run. Odoo holds the supplier master data and the approval workflow, but not the verification evidence.
Key features
A VoP control layer on top of your Odoo supplier payments: records the bank's result, applies your policy and keeps the evidence. It is not a regulated PSP service; it is the controlled bridge between Odoo and your bank's VoP channel.
VoP gate before payment
Every SEPA transfer shows its VoP status before it can be authorised or exported to a file. No payment leaves unreviewed.
Multi-source capture
Manual entry from the bank portal, response file import, or a sandbox source for testing (synthetic result). There is no API connector to the bank.
Policy engine
Per-company actions for Match, Partial match, No match and Not possible results. You decide what blocks, what warns and what passes through.
Override and dual approval
Requires a second approval from a manager to override a "No match" above configured thresholds, with an alert when too many exceptions pile up in a period.
Append-only audit log
Every verification, decision, import and configuration change is recorded immutably: the evidence trail an internal auditor needs.
Alias management
Record accepted name variants (trading names, abbreviations) so a known partial match is not flagged again on every run.
Bulk import
Upload your bank's result files (CSV, JSON, pain.002 XML), validate them, reconcile and apply results with full matching statistics.
Batch payments and data care
Individual and batch payment runs, with an explicit record of exclusion when the PSP allows it. IBANs are masked for users without permission and never written to logs.
How it works
Record the VoP result by hand from your bank's portal or import it from the bank's response file. Includes a sandbox source (synthetic result) for testing. It does not query the bank through an API.
The policy engine decides, per company and per result category, what blocks, what warns and what proceeds. Thresholds can vary by amount and risk.
Any override of a "No match" can require dual approval and is recorded in the append-only log, alongside every verification, import and configuration change.
Who it's for
- Companies in the SEPA zone (20-1,000 employees) with recurring supplier payment runs
- CFOs who set the payment risk policy and the override thresholds
- Accounting managers and accounts payable staff who run payments and resolve mismatches
- Internal auditors reviewing payment control evidence
- Odoo partners configuring the bank-specific deployment
Requirements and compatibility
Odoo 17, 18, 19 and 20, on Community and Enterprise. Builds on the standard Accounting module and the supplier payment workflow.
Batch payment integration activates automatically when the Enterprise
account_batch_payment module is present; the core VoP gate works on Community.
€9 per Odoo version, full source code included (OPL-1)
Install it, make it your own and extend it inside your Odoo. A FlexigoTech module: per Odoo version, source code included; works with a FlexigoTech Cloud subscription.
Frequently asked questions
Does this module make my company legally compliant as a PSP?
No. The legal obligation for Verification of Payee sits with payment service providers, not with 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 offers no compliance guarantee.
How does it get the verification result from my bank?
Two ways: manual entry of the result shown in your bank's portal, or the import of a bank response file (CSV, JSON or pain.002 XML). Includes a sandbox source (synthetic result) for testing. There is no API connector to the bank.
Does it work on Odoo Community?
Yes. The core VoP gate, the policy engine, the audit log, the sources, the aliases and the imports all work on Odoo 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, a "No match" blocks the payment; a manager can override it above a configured threshold, optionally requiring dual approval, and the override is recorded in the append-only audit log.
Is personal data exposed in the logs?
No. IBANs are masked for users without manager permission, and the structured logging never writes IBANs, beneficiary names or credentials to log files. The audit trail keeps only what is needed to evidence a decision.
SEPA VoP Payment Gate guides
3 practical guides on this module: error guides, comparisons and versions.


