Bank Transfer & Manual Payment Pro for Odoo

Name: Bank Transfer & Manual Payment Pro for Odoo
Brand: ECOSIRE
SKU: odoo-bank-transfer-manual-payment-pro

Key Features

Per-country and per-currency bank account display — customers see the correct IBAN/account details for their location, driven by configurable rules instead of one static text block

Unique, human-readable payment reference generated per sale order or invoice (e.g. an order-derived token) so every transfer is unambiguously matchable to its source document

Customer proof-of-payment upload from the order confirmation and customer portal — accepts receipts, screenshots and PDFs stored as ir.attachment against the transaction

Admin verification queue: a dedicated backend list/kanban of pending manual payments with reference, amount, currency, customer and attached proof, filterable and grouped

One-click approve or reject with a reason, recorded in the chatter and audit log so decisions are traceable to the reviewer and timestamp

Automated action on approval that auto-confirms the sale order and posts (validates) the linked customer invoice via ir.actions.server, no manual state changes

Reference and amount validation that flags mismatches between the expected order total and the customer-declared paid amount before finance approves

QWeb payment-instructions report and on-screen block rendering the bank details, reference and amount the customer must quote — printable and emailable

Multi-company and multi-bank support so each Odoo company shows its own bank accounts and rules, respecting company-scoped record rules

Configurable payment provider/method entry integrated with Odoo's payment framework so bank transfer appears alongside other acquirers at checkout and in the portal

Status stepper and email notifications keeping the customer informed: awaiting payment → proof submitted → verified/confirmed, using Odoo mail templates

Optional expiry / reminder logic — pending transfers can trigger a follow-up reminder or auto-cancel after a configurable window via a scheduled action (ir.cron)

Role-scoped visibility through ir.model.access.csv + record rules: salespeople see their own submissions, finance/accounting sees and actions the full queue

Full audit trail per transaction: who submitted, who reviewed, reference, declared vs expected amount, currency and decision, exposed in a searchable view

Optional XML-RPC/JSON-RPC exposure so an external portal, mobile app or reconciliation script can read submission status and post approvals programmatically

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

In many markets, bank transfer is not a fallback — it is how most customers actually pay. Yet Odoo's stock "Wire Transfer" acquirer gives shoppers a single block of text and no way to prove they paid, leaving your team to reconcile bank statements by hand and chase references over email. Bank Transfer & Manual Payment Pro is a build-to-order Odoo module that turns that messy manual flow into a structured, auditable checkout experience for Odoo Community and Enterprise on versions 17, 18 and 19.

At checkout the module displays the correct bank account for the customer's country or currency, generates a unique payment reference tied to the sale order or invoice, and lets the customer upload proof of payment (bank receipt, screenshot, or transfer confirmation) directly from the confirmation page. Every submission lands in an admin verification queue — a dedicated backend view where your finance team reviews the proof, matches the reference, and approves or rejects in one click. On approval the module auto-confirms the order and posts the invoice, closing the loop without a single manual status change.

This is not a generic apps.odoo.com download. ECOSIRE designs, builds, and installs the module against your chart of accounts, your bank accounts, your country/currency rules, and your existing sales and invoicing workflow — then hands over the source, documents it, and supports it. It is implemented the Odoo-native way: a proper module with __manifest__.py declaring dependencies on account, sale and payment; models extending payment.transaction, sale.order and account.move with computed fields via @api.depends; access control through ir.model.access.csv and record rules so a salesperson sees only their own submissions while finance sees the full queue; backend views in XML/OWL; a QWeb payment-instructions report; and ir.actions.server automated actions that fire on approval. Nothing is bolted on with hacks — it upgrades cleanly and reads like core Odoo.

The result: customers get a professional, trustworthy way to pay by bank transfer with instant confirmation that their proof was received; your finance team gets a queue instead of an inbox, with every transfer stamped by reference, amount, currency, and reviewer for a clean audit trail.

What you get

Complete, installable Odoo module (source code) for your target version(s) — 17, 18 and/or 19, Community or Enterprise — with a clean __manifest__.py and no encrypted blobs

Configuration of your real bank accounts, per-country/currency display rules, reference format and approval workflow mapped to your chart of accounts and sales flow

Security layer set up for your roles: ir.model.access.csv entries and record rules so finance and sales see exactly what they should

Deployment and installation on your Odoo instance (odoo.sh, self-hosted, or ECOSIRE-managed) with smoke-tested checkout, upload, approval and auto-invoicing paths

Administrator and finance-team documentation plus a short QWeb-based customer payment-instructions template ready to brand

A live handover / training session walking your team through the verification queue, approve/reject flow and configuration screens

A defined post-launch support window covering bug fixes and questions, with clear terms for version upgrades and enhancements

Who this is for

Merchant in a bank-transfer-first market

Runs an Odoo eCommerce or sales operation where customers overwhelmingly pay by bank transfer rather than card. Needs checkout to present the right account, capture a reference, and stop the endless email chase to confirm who paid what.

Finance / accounting manager

Owns reconciliation and invoicing. Wants every incoming transfer tagged with a unique reference and matching proof, reviewed in one queue, and turned into a posted invoice automatically on approval — with a clean audit trail per transaction.

Odoo implementation partner or in-house admin

Responsible for keeping the Odoo instance maintainable across 17/18/19 upgrades. Prefers a properly structured module (models, security, views, automated actions) built to core conventions over fragile customizations or an unsupported marketplace add-on.

How Bank Transfer & Manual Payment Pro for Odoo Compares

Criterion	ECOSIRE	Custom Build	Competitor
Per-country/currency bank account display	Included	Partial support	Partial support
Unique payment reference per order/invoice	Included	Partial support	Partial support
Customer proof-of-payment upload	Included	Partial support	Partial support
Admin verification queue (approve/reject)	Included	Partial support	Partial support
Auto-confirm order + post invoice on approval	Included	Partial support	Not included
Role-scoped security (finance vs sales record rules)	Included	Partial support	Partial support
Built to your chart of accounts & bank setup	Included	Included	Not included
Source code handover + documentation + training	Included	Partial support	Not included
Clean upgrades across Odoo 17/18/19	Included	Partial support	Partial support
Post-launch support window from the builder	Included	Partial support	Partial support

Frequently Asked Questions about Bank Transfer & Manual Payment Pro for Odoo

How long until the module is delivered and installed?

This is a build-to-order module, not an instant download. Typical lead time is 2–4 weeks from confirmed requirements, depending on the number of countries/banks, your version target(s) and how closely it must fit your existing sales and invoicing flow. After a short scoping call we confirm a firm timeline, build against your instance, smoke-test the full checkout → proof upload → approval → auto-invoice path, and deploy. You will not receive a pre-built apps.odoo.com ZIP — you receive a module tailored to your setup.

What support and updates do I get after delivery?

You get a defined post-launch support window (agreed during scoping) covering bug fixes and usage questions, plus the full module source so nothing is locked to us. Because it is written to core Odoo conventions — standard models, ir.model.access.csv security, XML/OWL views and automated actions — it upgrades cleanly. Moving the module to a newer Odoo version (e.g. 18 → 19) or adding new countries, banks or workflow rules is available as a scoped enhancement. We document the code and configuration so your own team or partner can maintain it.

Which Odoo versions and editions does this support?

Odoo 17, 18 and 19, on both Community and Enterprise. The module depends on the standard account, sale and payment modules, so it works whether you run stock Community accounting or Enterprise. We build for the specific version(s) you name; if you plan to migrate soon we can target the newer version or scope a forward-port.

How is the unique payment reference generated and matched?

On checkout the module generates a unique, human-readable reference derived from the sale order or invoice and stores it on the payment.transaction record. The customer is instructed (on-screen and in a QWeb report/email) to quote it in their bank transfer. When they upload proof, finance sees the reference, expected amount and declared amount side by side in the verification queue, making the match unambiguous. The reference format can be customized to fit your bank statement conventions.

What exactly happens when finance approves a payment?

Approval triggers an Odoo automated action (ir.actions.server): the sale order is confirmed and the linked customer invoice is posted, moving the transaction to a verified state and notifying the customer via a mail template. Rejection records a reason in the chatter and returns the order to awaiting-payment so the customer can resubmit. Every decision is stamped with the reviewer and timestamp for the audit trail. No manual status juggling is required.

Can this work alongside Stripe, card payments or other acquirers?

Yes. It integrates with Odoo's native payment framework, so bank transfer appears as one option alongside any other acquirers you have enabled (cards, wallets, etc.) at checkout and in the customer portal. Customers who choose bank transfer follow the structured proof-and-verification flow; other methods are unaffected. This lets you offer bank transfer to the customers who prefer it without disrupting your existing online payment setup.