示意预览Bank-transfer checkout for Odoo with per-country accounts,
unique references, proof upload and an admin verification queue.
什么是 Bank Transfer & Manual Payment Pro for Odoo？
Bank-transfer checkout for Odoo with per-country accounts, unique references, proof upload and an admin verification queue. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
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.
你得到什么
- 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
这是给谁的
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.
Bank Transfer & Manual Payment Pro for Odoo 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Per-country/currency bank account display | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Unique payment reference per order/invoice | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Customer proof-of-payment upload | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Admin verification queue (approve/reject) | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Auto-confirm order + post invoice on approval | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Role-scoped security (finance vs sales record rules) | 包含 | 部分支持 | 部分支持 | 部分支持 |
| Built to your chart of accounts & bank setup | 包含 | 包含 | 不包括在内 | 部分支持 |
| Source code handover + documentation + training | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Clean upgrades across Odoo 17/18/19 | 包含 | 部分支持 | 部分支持 | 包含 |
| Post-launch support window from the builder | 包含 | 部分支持 | 部分支持 | 不包括在内 |
关于Bank Transfer & Manual Payment Pro的常见问题
How long until the module is delivered and installed?
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.
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.
相关模块
Bank Transfer & Manual Payment Pro
Bank-transfer checkout for Odoo with per-country accounts, unique references, proof upload and an admin verification queue.
- 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