|View Issue Details|
|Type||Category||Severity||Reproducibility||Date Submitted||Last Update|
|feature request||[Openbravo ERP] 09. Financial management||minor||always||2008-01-30 02:36||2008-12-17 11:09|
|Priority||normal||Resolution||open||Fixed in Version|
|Status||acknowledged||Fix in branch||Fixed in SCM revision|
|Projection||minor fix||ETA||none||Target Version||pi|
|OS Version||Database version||Ant version|
|Product Version||SCM revision|
|Review Assigned To|
|Regression introduced in release|
|Regression introduced by commit|
|Triggers an Emergency Pack||No|
0003453: Implement SAF-T export capabilities
|Description||SAF-T (Standard Audit File for Tax Purposes) is an file format to export accounting data from software. It is part of an OECD recommendation for business and accounting software (http://www.oecd.org/document/57/0,2340,en_2649_34897_34910329_1_1_1_1,00.html [^]).|
In Portugal, since the start of 2008, the capability of exporting a SAF-T file is required from all accounting software. The specific file format for Portugal is SAFT-PT (http://www.assoft.pt/saft-pt/ [^]).
It would be important to have this export capability in OpenBravo as it is likely that other European countries will adopt the SAF-T standard.
edited on: 2008-06-12 09:26
Logged In: YES
This export capability is already an imperative requirement in Portugal and will be a requirement in many other European countries soon.
I am open to develop this functionality, since I would like to use the OpenBravo software in my companies, but I need some guidance from the project developers. I am not interested in analysing the whole project to find out the correct way to implement this. The other way around would be a quicker way to produce the expected results.
So I am requesting the attention of one of the project developers to advice me of the correct way to start and implement such functionality of exporting this type of XML document from the OpenBravo database, and also to analyse the possibility of this feature to be integrated in the trunk.
This is important because this functionality can be implemented outside of the project, but I think that it will be needed in the near future for many other countries and we can save development time if we start implementing it embedded in the product.
Please submit your advices to prcolaco [at] gmail [dot] com
edited on: 2008-06-12 09:44
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.
You can see the original bug report in:
|2008-06-29 23:52||pjuvara||Tag Attached: ReleaseCandidate|
|2008-06-29 23:52||pjuvara||Status||new => acknowledged|
|2008-07-02 19:29||pjuvara||Status||acknowledged => scheduled|
|2008-07-02 19:29||pjuvara||Assigned To||user71 => eduardo_Argal|
|2008-07-02 19:29||pjuvara||fix_in_branch||=> trunk|
|2008-07-02 19:30||pjuvara||Projection||none => minor fix|
|2008-07-02 19:30||pjuvara||Target Version||=> 2.60|
|2008-07-02 19:30||pjuvara||fix_in_branch||trunk =>|
|2008-07-02 19:30||pjuvara||Description Updated|
|2008-11-21 16:45||pjuvara||Status||scheduled => acknowledged|
|2008-11-21 17:05||pjuvara||Target Version||2.60 => trunk|
|2008-11-22 11:54||tbaptista||Issue Monitored: tbaptista|
|2008-12-17 11:09||pjuvara||Assigned To||eduardo_Argal => rmorley|
|Copyright © 2000 - 2009 MantisBT Group|