Issue 8243

Include ar_dni as a new tax identifier
Nosy list
ced, lukio, mariomop, pokoli, reviewbot
Assigned to
easy, review

Created on 2019-04-01.14:38:52 by lukio, last changed 22 months ago by ced.


Author: [hidden] (ced) Tryton committer Tryton translator
Date: 2019-06-30.09:45:51
I do not see neither in documentation provide that the requirement corresponds to the tax identifier.

For me, it is clear that this requirement is NOT a tax identifier because:

* it depends on the amount
* it is not said that it must be printed on invoice
* it is not said when and how this identifier must be reported
* it is too late to request it on invoice, it mus be on the sale in most case
* it is pointless to store a unique identifier on every document linked to the party, well because it is UNIQUE.
* In Tryton it is enough to identify the party of a document with well the party (as long as he has the proper identifiers).

So for me, it is wrong and not complete to just add DNI as tax identifier.
The Argentina localization must create a workflow where it checks that the system knows for the related party the DNI when it is needed and as earlier as needed. For example when confirming a sale order but also when posting an invoice.
Author: [hidden] (pokoli) Tryton committer Tryton translator
Date: 2019-06-29.12:11:56
@lukio could you explain what defines a *final customer* for Argentina? 
Is something that may be interesting for other contries? 

Does it make sense to allow only ar_cuit for tax identifiers, and when reporting to the tax authority include the ar_dni of the party for invoices with amount greather than 1000$?
Author: [hidden] (lukio)
Date: 2019-06-28.23:28:44
Hi cedk, the requirement of having an identity number (dni) for customer is when the invoice reviews the character of final consumer. If the invoice amount is greater than <defined> amount, the identity number is mandatory, if not the party_tax_identifier is not necesary to be setted.

It will be mandatory to enter the Unique Tax Identification Code (C.U.I.T.) in
all cases, except in the event that the recipient of the receipt reviews the
character of final consumer

The character of *final consumer* is something that is not of a tryton core module, is something that is added from contrib modules party_ar and account_invoice_ar.

So, if we could have a module that can set the party_tax_identifier for example matching the invoice amount at core, I think we could added a new contrib module that add a patterns to set the identity number on the character of final consumer.
Author: [hidden] (ced) Tryton committer Tryton translator
Date: 2019-06-13.11:41:07

I think the requirements of having an identity number for customer when the amount of an invoice is greater than <defined> amount, does not match with the design of the tax identifier. Especially because many kinds of identity number are valid.
For me such requirements are not linked to tax reporting but to money laundering. So I think it will be better to implement it with a new module that actually check the requirements based on the amount.
Author: [hidden] (lukio)
Date: 2019-04-01.15:10:53
Author: [hidden] (pokoli) Tryton committer Tryton translator
Date: 2019-04-01.14:51:45
It will be great if you can contribute a patch (

You will need to increase the required stdnum on and include the new identifier on the list of available ones.
Author: [hidden] (lukio)
Date: 2019-04-01.14:38:50
Hi! ar_dni was included into python-stdnum v1.11.

AR_DNI is is validating the Argentinian national identity. The other one, ar_cuit, was added with the issue7906.

Date User Action Args
2019-06-30 09:45:52cedsetmessages: + msg50474
2019-06-29 12:11:57pokolisetmessages: + msg50473
2019-06-28 23:28:45lukiosetnosy: + mariomop
messages: + msg50469
2019-06-13 11:41:07cedsetnosy: + ced
messages: + msg50222
2019-05-07 09:31:22reviewbotsetmessages: + msg49657
2019-04-25 08:59:26pokolisetpriority: wish -> feature
type: behavior -> feature request
2019-04-01 15:20:24reviewbotsetnosy: + reviewbot
messages: + msg48296
2019-04-01 15:20:23reviewbotsetreviews: 283141002
keyword: + review
2019-04-01 15:10:54lukiosetstatus: in-progress -> testing
messages: + msg48294
2019-04-01 15:02:22lukiosetstatus: chatting -> in-progress
assignedto: lukio

Showing 10 items. Show all history (warning: this could be VERY long)