Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0049233 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
feature request | [Openbravo Localizations] Localization Portugal | major | have not tried | 2022-05-05 13:42 | 2022-05-18 15:45 | |||||||
Reporter | psanjuan | View Status | public | |||||||||
Assigned To | psanjuan | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Linux 64 bit | Database | PostgreSQL | Java version | 7.x | |||||||
OS Version | Openbravo Appliance 14.04 | Database version | 9.3.x | Ant version | 1.9.x | |||||||
Product Version | SCM revision | |||||||||||
Regression date | ||||||||||||
Regression introduced by commit | ||||||||||||
Regression level | ||||||||||||
Regression introduced in release | ||||||||||||
Summary | 0049233: New GDPR laws in PT required that there is not need to identify the customer, unless the costumer wants it. | |||||||||||
Description | This means that for normal and simplified invoices, there is no need to identify the customer, unless the costumer wants it. If the customer is taxable person, the invoices must identify him, but only if he wants to deduce the VAT amount stated in the invoices. In any case, simplified invoices must comply with the limits for it issuance (100 in the case of taxable persons and 1000 in the case of not taxable persons or individuals). | |||||||||||
Steps To Reproduce | N/A | |||||||||||
Proposed Solution | A new pop-up needs to be shown before completing a sales transaction, therefore the seller can ask the buyer if he/she wants to be identified. * if the answer is yes, and the customer of the sale is already identified in the OB DB (Name, Location and Tax ID (NÂș del contribuyente). That information will be then taken and included in the corresponding template (simplified invoice, full invoice or nota de credito). * if the answer is yes, and the customer is already identified in the OB DB (Name, Location), "Tax ID" pop up will be shown for the seller to enter the tax id of the customer. That information will be taken and included in the corresponding template (simplified invoice, full invoice or nota de credito), and saved (Tax ID) in the OB DB. * if the answer is yes, and the customer is an anonymous one, it will have to be identified. * if the answer is no, no matter if the customer is identified or not in the OB DB, customer data if any will not be printed in the corresponding template (simplified invoice, full invoice or nota de credito) and no tax id pop up will be shown. A preference could be added to force and therefore make mandatory, that the Tax ID is given for "Companies" business partner type, at the time of issuing a Full Invoice. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0137433) psanjuan (manager) 2022-05-18 14:05 |
Related to Jira https://openbravo.atlassian.net/browse/RM-564 [^] [^] |
(0137436) psanjuan (manager) 2022-05-18 15:44 edited on: 2022-05-18 15:45 |
This feature has been discussed internally high level. Functional Specification (Business requirement that explain the big picture/approach, and after that define the level of detail) needs to be created (together David B.) to be reviewed and estimated by sw team. |
Issue History | |||
Date Modified | Username | Field | Change |
2022-05-05 13:42 | psanjuan | New Issue | |
2022-05-05 13:42 | psanjuan | Assigned To | => psanjuan |
2022-05-10 12:10 | psanjuan | Proposed Solution updated | |
2022-05-10 12:11 | psanjuan | Proposed Solution updated | |
2022-05-10 15:32 | psanjuan | Proposed Solution updated | |
2022-05-10 15:38 | psanjuan | Proposed Solution updated | |
2022-05-10 16:15 | psanjuan | Summary | New GDPR laws in PT required that there is not need to inform about the Tax ID of "Individuals" while issuing a Fatura. => New GDPR laws in PT required that there is not need to there is no need to identify the customer, unless the costumer wants it. |
2022-05-10 16:15 | psanjuan | Description Updated | View Revisions |
2022-05-10 16:15 | psanjuan | Proposed Solution updated | |
2022-05-10 16:16 | psanjuan | Description Updated | View Revisions |
2022-05-10 16:20 | psanjuan | Description Updated | View Revisions |
2022-05-10 16:21 | psanjuan | Summary | New GDPR laws in PT required that there is not need to there is no need to identify the customer, unless the costumer wants it. => New GDPR laws in PT required that there is not need to identify the customer, unless the costumer wants it. |
2022-05-10 16:25 | psanjuan | Description Updated | View Revisions |
2022-05-10 16:25 | psanjuan | Proposed Solution updated | |
2022-05-12 13:29 | psanjuan | Proposed Solution updated | |
2022-05-18 14:05 | psanjuan | Note Added: 0137433 | |
2022-05-18 15:44 | psanjuan | Note Added: 0137436 | |
2022-05-18 15:45 | psanjuan | Note Edited: 0137436 | View Revisions |
2022-05-18 15:45 | psanjuan | Type | design defect => feature request |
Copyright © 2000 - 2009 MantisBT Group |