Openbravo Issue Tracking System - Localization Pack: Spain
View Issue Details
0028553Localization Pack: SpainAEAT 340public2015-01-09 14:172015-02-26 12:30
maite 
vmromanos 
urgentmajoralways
closedinvalid 
5
 
 
vmromanos
0028553: ISO Country Code is taken from Business Partner's Location instead of directly from Business Partner's Tax ID defined, using NOI
In some cases, location defined for a business partner could not be in same country as business partner's tax id defined. In that cases, business patner's tax id should be proper information instead of business partner's location country.

We should directly take information from Business Partner TAX ID field instead of from location's information, previously ensuring that NOI format is correct (in the same way that we validate NIF information)
1. Define your BP as NOI and tax id= SI11111111 (which corresponds to Eslovenia)
2. Define Location for that BP in France
3. Register Sales Invoice for that business partner
4. Configure and execute Invoice Register Book having that invoice into account
5. Run "Modelo 340" based on previous book and realize that identifier set for your bp is FR11111111 (instead of SI11111111)
Develop a module similar to NIF Validator module but for NOI identification
No tags attached.
related to feature request 0028904 new psanjuan Create NOI field inside Business Partner window 
Issue History
2015-01-09 14:17maiteNew Issue
2015-01-09 14:17maiteAssigned To => vmromanos
2015-01-12 14:46jonalegriaesarteRegression date => 2015-02-09
2015-01-12 14:47jonalegriaesarteRegression date2015-02-09 =>
2015-01-12 14:47jonalegriaesarteResolution time => 1423436400
2015-02-10 11:28vmromanosNote Added: 0074319
2015-02-10 11:29vmromanosRelationship addedrelated to 0028904
2015-02-26 12:30vmromanosReview Assigned To => vmromanos
2015-02-26 12:30vmromanosStatusnew => closed
2015-02-26 12:30vmromanosResolutionopen => invalid

Notes
(0074319)
vmromanos   
2015-02-10 11:28   
The Tax ID field in Business Partner window should be filled with the tax id, not with the NOI, so this is issue is being rejected.

However, we think it could make sense to define a new separate field to fill the NOI, and take it into account in the reports where the NOI is used. Besides, a NOI validation could be applied to this field too.
Reported as a feature request 0028904