diff options
| author | Laurent Smet <las@odoo.com> | 2019-10-29 12:21:27 +0000 |
|---|---|---|
| committer | qdp-odoo <qdp@odoo.com> | 2020-04-10 09:47:24 +0000 |
| commit | caeb782841fc5a7ad71a196e2c9ee67644ef9074 (patch) | |
| tree | 28103bc29ab4f0d98162095f607c4c6ab1433f25 /addons/l10n_ch/tests | |
| parent | b4d1360ed1d71c8fda44ca0c3b1a80d5a112b93f (diff) | |
[IMP] account,*: Improve bank statements/payments workflow
- Create journal entries as soon as bank/cash statement lines are created, temporary booked on a suspense account set on the journal.
- Simplify the management of "blue" lines in the reconciliation widget. A "blue" line is now a journal item using a temporary liquidity account (outstanding payment/receipt accounts, set on the journal).
- Adapt and simplify the bank reconciliation report.
- Remove the bank reconciliation threshold date. The reconciliation report will show the not already reconciled journal entries using a liquidity account and the not already reconciled journal entries using a temporary liquidity account. Without accounting, an account.payment will involve directly the liquidity account and then, will be considered as a statement line directly.
- Remove the post_at bank reconciliation feature. The "paid" state will be set on the invoices only if reconciled with a journal entry involving the journal's liquidity account.
With invoicing, the payment will do that so the "in_payment" state should never be shown up.
With accounting, only the statement lines have the power to move an invoice to the "paid" state.
- Fix various corner cases about the management of multi-currency in bank statement lines.
- Fix the conversion dates in multi-currency: Since the bank/cash is always used on the statement lines, it will use always the real "bank" date instead of the fictive payment one.
- Ensure the 'reconcile' method will raise an error if the involved moves are not posted.
related enterprise PR odoo/enterprise#7019
closes odoo/odoo#41301
--task: 2092096
Related: odoo/upgrade#1018
Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>
Diffstat (limited to 'addons/l10n_ch/tests')
| -rw-r--r-- | addons/l10n_ch/tests/test_ch_qr_code.py | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/addons/l10n_ch/tests/test_ch_qr_code.py b/addons/l10n_ch/tests/test_ch_qr_code.py index e46a3a2c1ec..e41dcdd03cc 100644 --- a/addons/l10n_ch/tests/test_ch_qr_code.py +++ b/addons/l10n_ch/tests/test_ch_qr_code.py @@ -28,9 +28,9 @@ class TestSwissQRCode(AccountTestInvoicingCommon): 'move_type': 'out_invoice', 'partner_id': cls.partner_a.id, 'currency_id': cls.env.ref('base.CHF').id, - 'invoice_partner_bank_id': cls.swiss_iban.id, + 'partner_bank_id': cls.swiss_iban.id, 'company_id': cls.company_data['company'].id, - 'invoice_payment_ref': "Papa a vu le fifi de lolo", + 'payment_reference': "Papa a vu le fifi de lolo", 'invoice_line_ids': [ (0, 0, {'quantity': 1, 'price_unit': 100}) ], @@ -61,13 +61,13 @@ class TestSwissQRCode(AccountTestInvoicingCommon): self.ch_qr_invoice.generate_qr_code() # Now, check with a QR-IBAN as the payment account - self.ch_qr_invoice.invoice_partner_bank_id = self.swiss_qr_iban + self.ch_qr_invoice.partner_bank_id = self.swiss_qr_iban with self.assertRaises(UserError, msg="It shouldn't be possible to generate a Swiss QR-cde for a QR-IBAN without giving it a valid QR-reference as payment reference."): self.ch_qr_invoice.generate_qr_code() # Assigning a QR reference should fix it - self.ch_qr_invoice.invoice_payment_ref = '210000000003139471430009017' + self.ch_qr_invoice.payment_reference = '210000000003139471430009017' def test_ch_qr_code_detection(self): """ Checks Swiss QR-code auto-detection when no specific QR-method |
