On 2017-08-07 13:16, Sergi Almacellas Abellana wrote: > El 07/08/17 a les 12:40, Cédric Krier ha escrit: > > On 2017-08-07 12:14, Sergi Almacellas Abellana wrote: > >> El 07/08/17 a les 12:00, Cédric Krier ha escrit: > >>> I do not understand. Could you give concrete example (not linked to > >>> module implementation). > >> The tax mapping it's used for two things: > >> > >> 1. Proposing a default operation key to the user depending on the taxes > >> selected on the invoice. > >> 2. Restricting the available operation keys. In Spain there are some > >> keys that are only available for "in" invoices and others for "out" > >> invoices. As each tax has the "sale" or "purchase" kind, we define the > >> available keys on it. All the taxes that are not related to > >> intracomunitary operations have an empty keys, so no operation key can > >> be selected for this invoices. > > But why do you need more than 1 key per tax? > No, only one. > > How do you select the key? Based on which criteria? > > We select the default key, based on which is most commonly used, but the > user can customize the key as it may be a different one.
Please be more specific. I do not understand how this key is selected. > But if we have to choose one key criteria it will be probably the tax, > so each tax will have it's own key. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/ -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/20170807112536.GH3697%40kei.
