Laurent Smet
5883f0a84c
* Previously, when reconciling journal items in multi-currencies, the exchange difference entry was created only on the full reconciliation. It will now be created directly at each partial to ensure the ratio between amount_residual_currency and amount_residual is always kept identical. * Also when reconciling two lines, one with a foreign currency and one expressed in company currency, the reconciliation is now made based on the foreign currency. ==== RATIONALE ==== This patch allows to fix the following use cases (among others) 1) When everything is expressed in foreign currency, the reconciliation is made in that currency: Suppose EUR is the foreign currency and USD is the company currency. Reconciling: L1: 120 EUR 60 USD (rate 2:1) L2: 240 EUR 80 USD (rate 3:1) ..leads to a partial of 120 EUR and min(80, 60) = 60 USD After the reconciliation, L1 is fully matched but L2 is still open with 120 EUR but only 20 USD. This is the first problem is the current reconciliation because L2 is supposed to have a rate 3:1 so the residual amount should be 120 / 3 = 40 USD. Since the rate is no longer consistent on L2, the user will probably close the reconciliation by using another line in EUR or will close manually the reconciliation with 20 USD but without any additional exchange difference journal items explaining where this unconsistency comes from. 2) When the current lines are mixing multiple currencies, the reconciliation is made using the company's currency. In some countries like Mexico, Ethiopia or Costa Rica, the customer is free to pay an invoice using the company's currency instead of the foreign one. So, suppose USD is the foreign currency and MXN is the company currency. The invoice is expressed by: L1: 120 USD 60 MXN (rate 2:1) If the customer is paying at a date in which the rate is 3:1, he is free to pay either L2: 120 USD 40 MXN (rate 3:1), either L2: 40 MXN. In the second case, he is expecting the invoice to be fully paid because its paiement is equivalent to 120 USD at the payment date. In Odoo, the second case led to an open balance of 20 MXN and the invoice was not completely paid. Even this situation could be easily fixed by a manual write-off, this makes the Mexican payment EDI very complicated to fullfil correctly because the government is expecting a complete matching between the invoice and the payment. When the customer is paying multiple invoices or the invoices are paid using multiple payments, the currently generated mexican EDI file in Odoo was wrong. ==== REFERENCES ==== Original idea suggested by hbto@vauxoo.com. Thanks for the contribution and patience of the many persons having, at some point, helped on that. github issue: https://github.com/odoo/odoo/issues/37469 closes odoo/odoo#84201 Task: 2669371 Related: odoo/enterprise#24268 Signed-off-by: Quentin De Paoli <qdp@odoo.com>
38 lines
1.3 KiB
Python
38 lines
1.3 KiB
Python
# -*- coding: utf-8 -*-
|
|
|
|
from . import test_account_move_reconcile
|
|
from . import test_account_move_payments_widget
|
|
from . import test_account_move_out_invoice
|
|
from . import test_account_move_out_refund
|
|
from . import test_account_move_in_invoice
|
|
from . import test_account_move_in_refund
|
|
from . import test_account_move_entry
|
|
from . import test_invoice_tax_totals
|
|
from . import test_account_journal
|
|
from . import test_account_account
|
|
from . import test_account_tax
|
|
from . import test_account_analytic
|
|
from . import test_account_payment
|
|
from . import test_account_bank_statement
|
|
from . import test_account_move_partner_count
|
|
from . import test_account_move_rounding
|
|
from . import test_account_invoice_report
|
|
from . import test_account_move_line_tax_details
|
|
from . import test_account_journal_dashboard
|
|
from . import test_fiscal_position
|
|
from . import test_sequence_mixin
|
|
from . import test_settings
|
|
from . import test_tax
|
|
from . import test_invoice_taxes
|
|
from . import test_templates_consistency
|
|
from . import test_account_all_l10n
|
|
from . import test_reconciliation_matching_rules
|
|
from . import test_account_onboarding
|
|
from . import test_portal_attachment
|
|
from . import test_tax_report
|
|
from . import test_transfer_wizard
|
|
from . import test_account_incoming_supplier_invoice
|
|
from . import test_payment_term
|
|
from . import test_account_payment_register
|
|
from . import test_tour
|