This is a build-to-order module, not an instant download. Typical lead time is one working week 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.

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.

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.

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.

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.

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.