Openbravo Issue Tracking System - Modules | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0015432 | Modules | Intrastat | public | 2010-12-15 11:14 | 2011-07-20 18:10 |
| Reporter | networkb | ||||
| Assigned To | jonalegriaesarte | ||||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Regression date | |||||
| Regression introduced by commit | |||||
| Regression level | |||||
| Review Assigned To | |||||
| Support ticket | |||||
| OBNetwork customer | |||||
| Regression introduced in release | |||||
| Summary | 0015432: Intrastat must not take into account "Triangulations" (Operaciones Triangulares) | ||||
| Description | "Triangulations" scenarios (operación triangular in Spanish): Scenario 1 => A Spanish resident (Spanish company located in Spain) acquires goods and sell those goods out of Spain (but within the EU region). The exempt Intra Community sales must be included in the 349 report but must not be included in the Intrastat. Scenario 2 => An EU intermediary supplies goods to a Spanish company coming from another EU country. That supply is not considered an Intra Community transaction but a Reverse Charge scenario, therefore it does have to be included in the 349 report and Intrastat. Above Intra Community transactions of goods/items are out of scope as OB ERP do not allow: * to specify other “destination” country rather than organization country, in the case of purchase operations. * to specify other “origin” country rather than the organization country, in the case of sales operations. | ||||
| Steps To Reproduce | |||||
| Proposed Solution | Scenario 1: A company installed in Spain for example, can buy in France and sale in Italy, therefore the goods do not pass the spanish frontier, so this kind of transactions should not be taken into account for the intrastat report. In this moment, there exists a work around uncheking these transactions from the lines in Intrastat not to be considered. The problem is that if the company has many transactions of this type, it would result a really difficult action. We propose to have a check into purchase/sales invoices transactions to be able to indicate that this transaction is triangular so it shouldn´t be taken into account in Intrastat in an automatic way. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2010-12-15 11:14 | networkb | New Issue | |||
| 2010-12-15 11:14 | networkb | Assigned To | => psanjuan | ||
| 2011-04-12 12:26 | psanjuan | Summary | Not to take into account Triangular Operations in Intrastat => Intrastat must not take into account "Triangulations" (Operaciones Triangulares) | ||
| 2011-04-12 12:26 | psanjuan | Description Updated | bug_revision_view_page.php?rev_id=1818#r1818 | ||
| 2011-04-12 12:26 | psanjuan | Proposed Solution updated | |||
| 2011-06-03 11:10 | dalsasua | Assigned To | psanjuan => dalsasua | ||
| 2011-07-20 18:10 | dalsasua | Assigned To | dalsasua => jonalegriaesarte | ||
| There are no notes attached to this issue. |