Moving money between your own accounts — petty cash to the operating bank, one bank to another, a POS till drop to the safe — sounds trivial until you do it in accounting. In stock Odoo, an internal transfer between a cash journal and a bank journal is stitched together from separate outbound and inbound account.payment records (or manual account.move entries) that land in a transfer/suspense account and then have to be matched by hand. When someone forgets the second leg, or reconciles the transfer account against the wrong counterpart, you get a phantom balance in the suspense account that surfaces weeks later at month-end. Finance teams end up policing a control account that Odoo never designed to be a first-class object.

This build-to-order module makes the internal transfer a single, intentional operation. We add a dedicated account.internal.transfer model (with the outbound and inbound account.payment legs generated and linked as a One2many) so that choosing a source journal, a destination journal, an amount, a date, and an optional reference produces both sides atomically, posted through your configured internal-transfer/liquidity-transfer account. Computed fields via @api.depends keep the running source and destination balances visible on the form, @api.constrains blocks same-journal or negative-amount transfers before they post, and the state machine (draft → posted → reconciled / cancelled) mirrors Odoo's own payment lifecycle so nothing feels bolted on. Multi-currency transfers compute the exchange difference and route it to the currency-gain/loss account you nominate. Everything is delivered as clean, upgrade-safe source: a proper __manifest__.py, models under models/, ir.model.access.csv plus record rules for who may create versus post transfers, list/form/search views (and OWL/QWeb where a richer widget helps), and an optional QWeb PDF "transfer voucher" for signature.

We can extend the base scope to match how your team actually works: an approval step (draft transfer requires a manager to post, wired through an automated action or an activity), a transfers dashboard filtered by journal and date, a scheduled reconciliation helper that auto-matches the two legs against the transfer account, cheque/DD reference tracking for bank-to-bank moves, and full XML-RPC/JSON-RPC endpoints so treasury tooling or a bank feed can create transfers programmatically. The module targets Odoo 17.0, 18.0, and 19.0 and works on both Community and Enterprise — where Enterprise-only features (like bank statement auto-reconciliation or accounting reports) exist we integrate with them rather than reinventing them, and on Community we deliver the equivalent behavior in-module.

Because this is made to order, nothing ships until we agree on scope. After you request a quotation we run a short scoping call, confirm your journal setup, transfer/suspense account, currencies, and approval rules, then build against a staging copy of your database, run UAT with your finance users, and deploy with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company transfers, multi-currency exchange-difference handling, approval workflows, and integration with external treasury or bank-feed systems increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise invoice.