1. Mailing Lists
  2. Contributors
  3. Re: The future of oca/bank-payment

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: The future of oca/bank-payment

Re: The future of oca/bank-payment

Avatar

Re: The future of oca/bank-payment

by
Alexinux, Alexis de Lattre
- 26/03/2025 18:09:46
Dear Enric,

Le mer. 26 mars 2025 à 12:47, Enric Tobella Alomar <notifications@odoo-community.org> a écrit :
For example with the current system we can decide the bank to pay at the end in a simple way, no complication on that side. With this change, everything becomes more complicated, removing part of the functionality that we have and it was much better that the current Odoo behavior. Also, it implies that users will see one TRansference payment method for each journal, and that is a nonsense.

Did you test my v18 PR that adds the module account_payment_base_oca https://github.com/OCA/bank-payment/pull/1401 ?
My goal was to use the native object account.payment.method.line (used in v18 as "payment mode" on partners and invoices) while keeping the feature "decide the bank to pay at the end in a simple way". And I managed to implement it without breaking the native behavior. It was important to keep this feature !
 
Personally, I think that we can imagine some benefits, but we will loose functionalities on the change and that is something that is not interesting.

With my implementation in PR 1401, we don't loose functionalities. It's important !
 
Trying to reuse something that Odoo SA did for EE might have sense, but in this case, it doesn't fit the effort IMO. So, I would prefer to avoid this big change.

I don't know about EE because I don't use EE. All I know is that Odoo SA added a "payment mode" on partners and invoices in v18 (at last !) using account.payment.method.line. I think that, as implemented in my PR 1401, we can adopt this new native "payment mode" and not loose functionalities.

Alexis

Reference