Vendor Onboarding & Compl
Onboard suppliers, collect bank/tax/insurance docs, approve and track expiry
A dirty vendor master — missing bank details, lapsed insurance, no VAT certificate — creates payment errors and compliance risk. This portal puts every new supplier through a controlled onboarding lifecycle: capture company, tax and bank details, collect the required documents, compute a compliance score, route an approval, then create or update the res.partner supplier record on sign-off. A nightly expiry engine keeps the whole vendor base compliant. It supports UK due-diligence fields (sort code, company number, VAT and insurance evidence).
Key Features
Onboarding Lifecycle
Draft → submitted → under review → approved / rejected, with a reviewer, a live compliance score and a checklist of required document types per request.
Document Requirements
Configurable document types by category — bank mandate, VAT certificate, public/employer's liability insurance, certificate of incorporation, modern-slavery statement and more — each with required and expiry settings.
Expiry Status Engine
Each document is automatically classified valid / expiring soon / expired with days-to-expiry; a nightly cron recomputes status and raises activities for documents inside a configurable warning window.
Bank Detail Capture
Collect account name, number, sort code and IBAN with length checks and a verification flag, so payment details are validated before a vendor goes live.
One-Click Approval
Approving creates or updates the supplier res.partner, writes back the bank account and stamps the due-diligence fields — no manual re-keying.
Request Missing Docs
A wizard requests any missing or expiring documents from the supplier in a single action, keeping the chase auditable.
End-to-End, Not Native
Core Odoo has no supplier onboarding, document checklist, compliance score or expiry tracking — this delivers the full process in one app.
UK Due Diligence
Sort code, company number, VAT and insurance evidence are first-class fields, matching how UK procurement vets suppliers.
Screenshots
Document Types
Onboarding Requests
Why Choose This Module
Procurement and finance teams that must vet suppliers before payment, organisations with insurance or modern-slavery evidence requirements, and any business wanting a clean, auditable vendor master instead of email attachments and spreadsheets.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: base, mail, contacts
- Support: support@pokutsoft.com
Update date: 2026-10-16
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Discuss (mail) |
| Lines of code | 1119 |
| Technical Name |
gb_vendor_onboarding_compliance_portal |
| License | OPL-1 |
| Website | https://pokutsoft.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