Odoo Changelog — 2024-10-24

Thursday, October 24, 2024

1 change · 17.0

Improvements(1)

Enhancements to existing features

[IMP] l10n_ar_edi: manage 10016 afip error.

Enterprise17.0l10n_ar_ediMedium

This update improves how users in Argentina are informed about AFIP error 10016 during invoice validation. Instead of a generic error message, users now receive specific guidance based on the actual cause—whether it's a date issue, numbering mismatch, or date range requirements. This helps users quickly resolve validation problems without contacting support.

Original PR description

This pr is created to help de user to know the origin of the afip error 10016. The error 10016 can be caused by different origins, so here we give the user more precision about the origin. The…

This pr is created to help de user to know the origin of the afip error 10016.

The error 10016 can be caused by different origins, so here we give the user more precision about the origin. The objective of this pr is to be able to differentiate what is the origin of error 10016 and to be able to give a more precise message to the client.

1) If the last afip invoice validated has a higher date than the date of the invoice that is being validated then the message shown to the user is '10016-1': 'The invoice date cannot be after the last invoice validated in AFIP.'

2) If the last afip invoice number is higher than the current invoice number being validated in Odoo, then the message shown to the user is '10016-2': 'There may have been a mismatch in the numbering of this type of document between Odoo and AFIP.'

3) If any other reason cause the error '10016' then the message shown to the user is:
    * Please note that if you are trying to validate an invoice with a date other than today, you must verify if it falls within the date range according to the AFIP concept or document type:

    a) If it is Product: N+5 or N-5 with N being today's date.
    b) If it is Services or Products and services: N+10 or N-10 with N being today's date.
    c) If it is a MiPyme Invoice: N-5 0 N+1 with N being today's date. For Debit Note or Credit Note only N-5"

Task Adhoc side: 37771
Task latam side: 1194

This pr replaces https://github.com/odoo/enterprise/pull/65675

#Argentina#AFIP#error handling#user experience#invoice validation

This pr is created to help de user to know the origin of the afip error 10016. The error 10016 can be caused by different origins, so here we give the user more precision about the origin. The objective of this pr is to be able to differentiate what is the origin of error 10016 and to be able to give a more precise message to the client. 1) If the last afip invoice validated has a higher date than the date of the invoice that is being validated then the message shown to the user is '10016-1': 'The invoice date cannot be after the last invoice validated in AFIP.' 2) If the last afip invoice number is higher than the current invoice number being validated in Odoo, then the message shown to the user is '10016-2': 'There may have been a mismatch in the numbering of this type of document between Odoo and AFIP.' 3) If any other reason cause the error '10016' then the message shown to the user is: * Please note that if you are trying to validate an invoice with a date other than today, you must verify if it falls within the date range according to the AFIP concept or document type: a) If it is Product: N+5 or N-5 with N being today's date. b) If it is Services or Products and services: N+10 or N-10 with N being today's date. c) If it is a MiPyme Invoice: N-5 0 N+1 with N being today's date. For Debit Note or Credit Note only N-5" Task Adhoc side: 37771 Task latam side: 1194 This pr replaces https://github.com/odoo/enterprise/pull/65675