Account Payment Internal Transfer
This module restores the internal transfer functionality for payments that was available in previous Odoo versions but was removed.
Now the recommended approach for internal transfers requires waiting for bank statement lines to be imported and then using reconciliation models. This workflow has significant drawbacks:
Users cannot register transfers at the moment they occur
There is a risk of forgetting unreconciled transactions if bank statements are delayed
Users without direct bank access have no way to track pending transfers
The workflow is tedious and error-prone
This module allows users to register internal transfers immediately when they happen, creating the intermediate journal entries with outstanding accounts. Later, when bank statements are imported, each side can be reconciled independently. This results in 4 journal entries total (2 payments + 2 bank statement reconciliations).
Features:
Create internal transfers directly from the Accounting Dashboard
A paired payment is automatically created in the destination journal
Their journal entries are automatically reconciled
Proper labels are set on journal items for easy identification
Cancel and reset to draft cascades to the paired payment
Deleting a transfer also deletes the paired payment
Search filter to easily find internal transfers in the payments list
Table of contents
Usage
To create an internal transfer:
Go to Accounting Dashboard
Click on the menu (three dots) of a Bank or Cash journal
In the “New” section, click on “Internal Transfer”
Select the destination journal
Enter the amount
Confirm the payment
The system will automatically:
Create a paired payment in the destination journal
Use the company’s transfer account for the counterpart
Reconcile both transfer lines automatically
To find existing transfers, use the “Internal Transfers” filter in the payments search view.
When cancelling, resetting to draft, or deleting one side of the transfer, the paired payment is automatically updated as well.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Joan Sisquella <joan.sisquella@forgeflow.com>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/account-payment project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-account-payment-internal-transfer 18.0.1.0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_account_payment_internal_transfer-18.0.1.0.0.4-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_account_payment_internal_transfer-18.0.1.0.0.4-py3-none-any.whl |
Release files / odoo_addon_account_payment_internal_transfer-18.0.1.0.0.4-py3-none-any.whl
| Download URL | odoo_addon_account_payment_internal_transfer-18.0.1.0.0.4-py3-none-any.whl |
|---|---|
| Size | 31.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d57876a3c3371a2612db859897546e3619747bef16e49da97e767eb8cf7092b8
|
|
BLAKE2b-256 checksum How to use checksums |
fc8f148a85ca2004e6208b304e4e3c3143730132c228467362b80fb49bab237b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-account-payment-internal-transfer 18.0.1.0.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.