Reduce Amount to be paid while Payment Link is generated on Sale Order, depending on done Transactions.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0When you generate a payment link from a sale order, this module automatically reduces the amount to pay by the value of payments already completed on that order.
This module changes how the payment link wizard behaves when it is opened from a sale order.
- It looks at the sale order's transactions and keeps only the ones that are completed (done).
- If there are completed transactions and the sale order has no invoices yet, it searches for the related accounting entries (invoices) linked to those payments.
- It adds up the total amount of those entries, ignoring any that are cancelled.
- The payment link amount is then set to the sale order total minus that already-paid amount.
So, if a customer has already paid part of an order through a payment link, the next link you generate will only ask for the remaining balance instead of the full order amount. This avoids asking customers to pay twice for the same amount.
The change appears in the payment link wizard screen, which is opened from a sale order. It touches the payment.link.wizard model and reads data from sale.order and account.move. No new menus, buttons, or reports are added; the module only adjusts the default amount shown in the wizard.
Depends on
Models and fields (1)
- payment.link.wizard · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 14.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/sale-workflow.
terminal Installation and usage
OCA documentation · Odoo 14.0Usage
Source · Odoo 14.0Add Product to Order Lines after first Transaction is made and Generate a Payment Link
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.