Skip to content

Conversation

@antoine162
Copy link
Contributor

Mexican companies very commonly issue invoices in USD, to be fulfiled
in MXN, at the official exchange rate defined by the Banco de Mexico
on the day of payment.

(Presumably, this is to insure against the volatility of the Mexican
peso.)

Odoo supports this workflow, but only if the payment is registered
directly on the invoice using the 'Register Payment' button.

If the payment is created separately, and then reconciled manually
with the invoice, a whole host of problems occur:

  • the payment typically can't be reconciled fully with the invoice,
    (even though that can usually be solved by manually creating
    an exchange move)
  • but more problematically, the amounts on the payment CFDI will
    be wrong, and even manually creating an exchange move won't solve
    that.

So, we absolutely need to warn users not to try to do that.

(We've been encountering lots of tickets lately in the tech-support
pipe because of users who tried this and then wonder why it doesn't
work.)

This is currently an issue in 14.0, 15.0 and master.

@robodoo
Copy link
Collaborator

robodoo commented Mar 18, 2022

@C3POdoo C3POdoo requested a review from a team March 18, 2022 17:03
@antoine162 antoine162 requested a review from smetl March 18, 2022 17:06
@antoine162
Copy link
Contributor Author

antoine162 commented Mar 18, 2022

@smetl since you're well aware of the technical roots of this issue, could you just please confirm for the marketing team that it is indeed an issue?

@jcs-odoo
Copy link
Contributor

cc @vbe-odoo .

Copy link
Contributor

@jcs-odoo jcs-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR @antoine162 !
I hope it will help reduce the amount of errors and tickets the support gets :)

  • I wouldn't put this warning at the beginning of this section as we want to explain the "normal" behaviour first.
  • if you want to emphasize something with bold, better put it on relevant information rather than on "must".
  • Use the present tense for normal behavior (not the future) see guidelines
  • ' doesn't work to highlight a button. prefer using :guilabel: or double backticks `` for "technical" display. (see suggestion)
  • 100th characters max per line (see rst guidelines)

cc @vbe-odoo since it's your content.

Comment on lines 499 to 505
.. warning::
- When creating a payment in MXN for an invoice in USD, the payment **must** be created using the
'Register Payment' button on the invoice view and not separately as a payment. Otherwise, the
payment CFDI will not be correctly generated.
- As such, a payment in MXN cannot be used to pay multiple invoices in USD. Rather, the payment
should be separated into multiple payments, and each payment created using the 'Register Payment'
button on its corresponding invoice.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.. warning::
- When creating a payment in MXN for an invoice in USD, the payment **must** be created using the
'Register Payment' button on the invoice view and not separately as a payment. Otherwise, the
payment CFDI will not be correctly generated.
- As such, a payment in MXN cannot be used to pay multiple invoices in USD. Rather, the payment
should be separated into multiple payments, and each payment created using the 'Register Payment'
button on its corresponding invoice.
.. warning::
- When making a payment in MXN for an invoice in USD, the payment must be created using the
:guilabel:`Register Payment` button **on the invoice view** and not separately as a payment.
Otherwise, the payment CFDI is not correctly generated.
- As such, a payment in MXN cannot be used to pay multiple invoices in USD. Rather, the payment
should be separated into multiple payments created using the :guilabel:`Register Payment`
button on the corresponding invoices.

@vbe-odoo
Copy link
Contributor

Hi, @jcs-odoo @antoine162 many thanks for the PR with the changes and the review.
LGTM in terms of the text and the description of the issue being solved here.
Thanks!
cc' @ren-odoo @fvz-odoo

@jcs-odoo
Copy link
Contributor

@smetl since you're well aware of the technical roots of this issue, could you just please confirm for the marketing team that it is indeed an issue?

@antoine162 We won't check all localizations behaviors, so I assume that it was needed if you made this PR. Let me know once you've updated your commit.

Thanks :)

@smetl
Copy link

smetl commented Mar 29, 2022

@antoine162 Yeah ... I confirm I confirm!

…voices in USD

Mexican companies very commonly issue invoices in USD, to be fulfiled
in MXN, at the official exchange rate defined by the Banco de Mexico
on the day of payment.

(Presumably, this is to insure against the volatility of the Mexican
peso.)

Odoo supports this workflow, but only if the payment is registered
directly on the invoice using the 'Register Payment' button.

If the payment is created separately, and then reconciled manually
with the invoice, a whole host of problems occur:
- the payment typically can't be reconciled fully with the invoice,
  (even though that can usually be solved by manually creating
  an exchange move)
- but more problematically, the amounts on the payment CFDI will
  be wrong, and even manually creating an exchange move won't solve
  that.

So, we absolutely need to warn users not to try to do that.

(We've been encountering lots of tickets lately in the tech-support
pipe because of users who tried this and then wonder why it doesn't
work.)
@antoine162 antoine162 force-pushed the 14.0-l10n_mx-warn-multicurrency-payment branch from adb73db to fb4c487 Compare May 4, 2022 07:31
@antoine162
Copy link
Contributor Author

@jcs-odoo all my apologies for my lateness in getting back to this PR, and thank you so much for educating me on good practices! I've changed the wording as you suggested, and put the warning at the end of the section on PUE payments, after the explanation of the normal flow. (The warning applies only to PUE payments, since these are the only payments that require a CFDI.)

Copy link
Contributor

@jcs-odoo jcs-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problem @antoine162 !

Can you just rename the commit message
[IMP] accounting: add a warning about invoices in USD in Mexico

I take the liberty of changing the name of the PR so the reviewer can merge directly and rename the commit based on the PR's title.

@jcs-odoo jcs-odoo changed the title [ADD] accounting/l10n_mx: Warn not to create separate payments for invoices in USD [IMP] accounting: add a warning about invoices in USD in Mexico May 4, 2022
@jcs-odoo jcs-odoo requested a review from a team May 4, 2022 15:21
Copy link
Collaborator

@AntoineVDV AntoineVDV left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@robodoo r+ squash

@robodoo
Copy link
Collaborator

robodoo commented May 4, 2022

Merge method set to squash

robodoo pushed a commit that referenced this pull request May 4, 2022
Mexican companies very commonly issue invoices in USD, to be fulfiled
in MXN, at the official exchange rate defined by the Banco de Mexico
on the day of payment.

(Presumably, this is to insure against the volatility of the Mexican
peso.)

Odoo supports this workflow, but only if the payment is registered
directly on the invoice using the 'Register Payment' button.

If the payment is created separately, and then reconciled manually
with the invoice, a whole host of problems occur:
- the payment typically can't be reconciled fully with the invoice,
  (even though that can usually be solved by manually creating
  an exchange move)
- but more problematically, the amounts on the payment CFDI will
  be wrong, and even manually creating an exchange move won't solve
  that.

So, we absolutely need to warn users not to try to do that.

(We've been encountering lots of tickets lately in the tech-support
pipe because of users who tried this and then wonder why it doesn't
work.)

This is currently an issue in 14.0, 15.0 and master.

closes #1728

Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
@robodoo robodoo closed this May 4, 2022
@robodoo robodoo temporarily deployed to merge May 4, 2022 17:14 Inactive
robodoo pushed a commit that referenced this pull request May 5, 2022
Mexican companies very commonly issue invoices in USD, to be fulfiled
in MXN, at the official exchange rate defined by the Banco de Mexico
on the day of payment.

(Presumably, this is to insure against the volatility of the Mexican
peso.)

Odoo supports this workflow, but only if the payment is registered
directly on the invoice using the 'Register Payment' button.

If the payment is created separately, and then reconciled manually
with the invoice, a whole host of problems occur:
- the payment typically can't be reconciled fully with the invoice,
  (even though that can usually be solved by manually creating
  an exchange move)
- but more problematically, the amounts on the payment CFDI will
  be wrong, and even manually creating an exchange move won't solve
  that.

So, we absolutely need to warn users not to try to do that.

(We've been encountering lots of tickets lately in the tech-support
pipe because of users who tried this and then wonder why it doesn't
work.)

This is currently an issue in 14.0, 15.0 and master.

closes #1917

Forward-port-of: #1728
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
robodoo pushed a commit that referenced this pull request May 5, 2022
Mexican companies very commonly issue invoices in USD, to be fulfiled
in MXN, at the official exchange rate defined by the Banco de Mexico
on the day of payment.

(Presumably, this is to insure against the volatility of the Mexican
peso.)

Odoo supports this workflow, but only if the payment is registered
directly on the invoice using the 'Register Payment' button.

If the payment is created separately, and then reconciled manually
with the invoice, a whole host of problems occur:
- the payment typically can't be reconciled fully with the invoice,
  (even though that can usually be solved by manually creating
  an exchange move)
- but more problematically, the amounts on the payment CFDI will
  be wrong, and even manually creating an exchange move won't solve
  that.

So, we absolutely need to warn users not to try to do that.

(We've been encountering lots of tickets lately in the tech-support
pipe because of users who tried this and then wonder why it doesn't
work.)

This is currently an issue in 14.0, 15.0 and master.

closes #1915

Forward-port-of: #1728
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
robodoo pushed a commit that referenced this pull request May 5, 2022
Mexican companies very commonly issue invoices in USD, to be fulfiled
in MXN, at the official exchange rate defined by the Banco de Mexico
on the day of payment.

(Presumably, this is to insure against the volatility of the Mexican
peso.)

Odoo supports this workflow, but only if the payment is registered
directly on the invoice using the 'Register Payment' button.

If the payment is created separately, and then reconciled manually
with the invoice, a whole host of problems occur:
- the payment typically can't be reconciled fully with the invoice,
  (even though that can usually be solved by manually creating
  an exchange move)
- but more problematically, the amounts on the payment CFDI will
  be wrong, and even manually creating an exchange move won't solve
  that.

So, we absolutely need to warn users not to try to do that.

(We've been encountering lots of tickets lately in the tech-support
pipe because of users who tried this and then wonder why it doesn't
work.)

This is currently an issue in 14.0, 15.0 and master.

closes #1914

Forward-port-of: #1728
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
robodoo pushed a commit that referenced this pull request May 5, 2022
Mexican companies very commonly issue invoices in USD, to be fulfiled
in MXN, at the official exchange rate defined by the Banco de Mexico
on the day of payment.

(Presumably, this is to insure against the volatility of the Mexican
peso.)

Odoo supports this workflow, but only if the payment is registered
directly on the invoice using the 'Register Payment' button.

If the payment is created separately, and then reconciled manually
with the invoice, a whole host of problems occur:
- the payment typically can't be reconciled fully with the invoice,
  (even though that can usually be solved by manually creating
  an exchange move)
- but more problematically, the amounts on the payment CFDI will
  be wrong, and even manually creating an exchange move won't solve
  that.

So, we absolutely need to warn users not to try to do that.

(We've been encountering lots of tickets lately in the tech-support
pipe because of users who tried this and then wonder why it doesn't
work.)

This is currently an issue in 14.0, 15.0 and master.

closes #1913

Forward-port-of: #1728
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
robodoo pushed a commit that referenced this pull request May 5, 2022
Mexican companies very commonly issue invoices in USD, to be fulfiled
in MXN, at the official exchange rate defined by the Banco de Mexico
on the day of payment.

(Presumably, this is to insure against the volatility of the Mexican
peso.)

Odoo supports this workflow, but only if the payment is registered
directly on the invoice using the 'Register Payment' button.

If the payment is created separately, and then reconciled manually
with the invoice, a whole host of problems occur:
- the payment typically can't be reconciled fully with the invoice,
  (even though that can usually be solved by manually creating
  an exchange move)
- but more problematically, the amounts on the payment CFDI will
  be wrong, and even manually creating an exchange move won't solve
  that.

So, we absolutely need to warn users not to try to do that.

(We've been encountering lots of tickets lately in the tech-support
pipe because of users who tried this and then wonder why it doesn't
work.)

This is currently an issue in 14.0, 15.0 and master.

closes #1916

Forward-port-of: #1728
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
@antoine162
Copy link
Contributor Author

Merci beaucoup @jcs-odoo @AntoineVDV

@fw-bot fw-bot deleted the 14.0-l10n_mx-warn-multicurrency-payment branch May 18, 2022 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants