:100644 100644 d46b1318a23b471a M account_payment_order_return/README.rst
:100644 100644 340d1c771235bcb1 M account_payment_order_return/__manifest__.py
:100644 100644 a341cc9dbe7d7bbb M account_payment_order_return/i18n/account_payment_order_return.pot
:100644 100644 60be6ab8e6b32b37 M account_payment_order_return/readme/CONTRIBUTORS.rst
:100644 100644 a8591d03826c26df M account_payment_order_return/readme/USAGE.rst
:100644 100644 450f2d9ea5f5d975 M account_payment_order_return/static/description/index.html
This module adds an option to generate extra grouped moves for the payment
orders since the refactoring done to use native Odoo payments.
This serves for easing the reconciliation on bank statements of large payment
orders, handling them as one or several journal entries according payment date.
Previous patch by Alexis created a co-dependency between
account_payment_order and account_banking_sepa_direct_debit, which is
not correct.
This patch avoids such problem and fix properly the test, although
the utility of some of them is debatible.
This adapts the old bank.payment.line records to account.payment records
according the new approach, taking into account if you come from v14
with the refactoring applied.
The previous approach creates manually the journal entries and does all
the hard work, plus not being 100% compatible with the bank statement
reconciliation widget (requiring a patch on OCB to see blue lines).
That decision made sense on the moment it was done (v9), where the
native payment model (account.payment) was very limited, and wasn't able
to store all the needed information for the bank transaction.
Now that the limitations are gone, we can get rid off this extra model,
and generate instead `account.payment` records, using both the native
model + methods to perform the same operations.
This serves also to workaround the problem found in #966.
All the code, views and tests of main module have been adapted to this
new approach in this commit. Later commits will adapt the rest of the
modules of the suite, and add migration scripts to transit from the
previous approach to this new one.
TT39832
- Add a hook method to retrieve communication type and communication
- Improve normal communication if there is a credit note
If there is a credit note that partially cancel an invoice, the payment communication
should be the combination of the invoice reference and the credit note one.
- Remove not needed assert as parameter is required
- Use the 'payment_reference' field if filled in
- Add existing payment references to communication
If some movements have been reconciled with the original invoice,
their references should be added in communication too.
e.g.: Manual credit notes
- Don't duplicate communication reference
The test introduced in 7bdb286aa1 is not
valid, as its indentation made it to not be executed. Anyways, the
content and the tested things are also not correct.
This commit split the tests for outbound payment in a base inheritable class that
can be reused in other dependant modules, and the test of this module.
similar to 86bd1a2525
