Checking line by line does not scale
Supplier payment runs carry dozens or hundreds of transfers. Manually reviewing the verification status of every payment before you export is slow, tedious and easy to get wrong.
Regulation (EU) 2024/886 requires you to verify the payee's name against their IBAN before a SEPA credit transfer is processed. In a batch of dozens of payments, one unverified line is all it takes to slip into the pain.001 file. This module extends FlexigoTech's SEPA VoP engine to Odoo's payment batches: it shows verification coverage for every batch and blocks the export while any blocked or pending payment remains.
Verification of Payee works one payment at a time, but treasury works in batches. Without a control at batch level, a single unresolved check ends up inside the SEPA file you send to the bank.
Supplier payment runs carry dozens or hundreds of transfers. Manually reviewing the verification status of every payment before you export is slow, tedious and easy to get wrong.
A single blocked or pending payment inside the batch is enough for the SEPA file to go to the bank with an unverified payee — with real exposure to fraud, misdirected funds and non-compliance with Regulation (EU) 2024/886.
Whoever signs off the payment run needs to see at a glance how many payments pass verification and which do not — before authorising the export, not after the money has already left.
It is a bridge module: it connects FlexigoTech's SEPA Verification of Payee engine to Odoo's batch payments and adds the control gate that was missing before the file is exported.
Each payment batch shows a VoP Coverage section with the count and value of the verified, pending and blocked payments. You know whether the run is clear before you ever click export.
When the file is generated, the module checks that no blocked or pending lines are left. If any remain, the export stops with a clear message stating how many payments fail and why.
The batch payments tab shows the verification status and result of every transfer, with its amount and currency, so you can pinpoint in seconds the lines that are holding up the export.
For the exemption scenarios your policy allows, users with override permission can record a batch opt-out. It is tracked with the user, timestamp and reason, so nothing bypasses the control silently.
Every blocked export, supervisor exception and successful export is logged with its timestamp, ready for internal reviews and for evidencing compliance to an auditor.
It runs on top of FlexigoTech's SEPA VoP engine and Odoo's batch payments (account_batch_payment). Everything happens inside your own instance, and the gate logic is plain Python your team can read and extend.
If you prepare, authorise or review payment batches in Odoo, this control is for you.
Leaders who oversee SEPA payment runs and need the assurance that no unverified payment ever leaves the ERP on their watch.
Teams that build multi-payment supplier runs and want to read verification coverage at a glance, without checking every line by hand.
Roles that have to demonstrate VoP compliance under Regulation (EU) 2024/886 with a traceable log of every block, exception and opt-out.
Companies that already verify payees with our free module and want to carry that same control into the payment-run flow of Odoo's batch payments.
FlexigoTech is Flexibles y Accesorios Gobe, S.L., based in Barcelona. Development is run by a single developer, so when you have a question about the export gate or a VoP status you talk straight to the person who wrote the code, not to a sales rep.
This module controls the batch: coverage, export gate and audited opt-out. The verification of each individual payee is done by FlexigoTech's free SEPA VoP engine, which is a requirement. It also needs Odoo's batch payments (account_batch_payment, an Enterprise feature) — and we tell you that before you buy, not after.
Payment control rarely comes alone: it usually shows up alongside the need to tidy up payment-by-payment verification and the rest of the finance flow inside Odoo.
It is the requirement under Regulation (EU) 2024/886 to check that the payee's name matches the IBAN before a SEPA credit transfer is processed. FlexigoTech's SEPA VoP module handles the technical verification of each individual payment; this bridge module enforces it across the whole batch in Odoo.
Yes. It is a bridge module. It requires FlexigoTech's SEPA VoP engine (free) and Odoo's batch payments feature (account_batch_payment). The bridge connects the two and adds the batch-level control on top.
No. The batch payments feature (account_batch_payment) is an Odoo Enterprise module, so on Community this bridge will not install. You can still use the free SEPA VoP engine to verify payees one payment at a time.
The export is stopped with a clear error message that tells you exactly how many payments are blocked or still pending. You resolve or remove those lines and try again, or record an authorised opt-out if your policy allows it.
Yes. Every opt-out is recorded with the user, timestamp and reason, and Odoo's audit trail lets you review all exceptions when you need to evidence compliance.
The module supports Odoo 17, 18 and 19. It is a one-time purchase of €29 with the full Python source code included, no subscription and no separate SaaS, plus 12 months of updates and direct support from the developer.
Yes. We run a public Odoo demo with all our modules installed and no signup at flexigotech.com/demo (user demo, password flexigodemo). You can log in, open a payment batch and see the VoP coverage panel and the export gate on real data before you decide.
Open the live demo and see the VoP coverage panel and the export gate working on a real batch inside Odoo. No signup, with the actual tool in front of you.