Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003453Openbravo ERP09. Financial managementpublic2008-01-30 02:362008-12-17 11:09
Reporteruser71 
Assigned Tormorley 
PrioritynormalSeverityminorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionpiFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0003453: Implement SAF-T export capabilities
DescriptionSAF-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.
Steps To Reproduce
Proposed Solution
Additional Information
TagsReleaseCandidate
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-06-29 23:52pjuvaraTag Attached: ReleaseCandidate
2008-06-29 23:52pjuvaraStatusnew => acknowledged
2008-07-02 19:29pjuvaraStatusacknowledged => scheduled
2008-07-02 19:29pjuvaraAssigned Touser71 => eduardo_Argal
2008-07-02 19:29pjuvarafix_in_branch => trunk
2008-07-02 19:30pjuvaraOBNetwork customer => No
2008-07-02 19:30pjuvaraProjectionnone => minor fix
2008-07-02 19:30pjuvaraTarget Version => 2.60
2008-07-02 19:30pjuvarafix_in_branchtrunk =>
2008-07-02 19:30pjuvaraDescription Updated
2008-11-21 16:45pjuvaraStatusscheduled => acknowledged
2008-11-21 17:05pjuvaraTarget Version2.60 => trunk
2008-11-22 11:54tbaptistaIssue Monitored: tbaptista
2008-12-17 11:09pjuvaraAssigned Toeduardo_Argal => rmorley

Notes
(0007042)
user71   
2005-06-01 00:00   
(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:
https://sourceforge.net/support/tracker.php?aid=1882280 [^]
(0003936)
user71   
2008-06-07 12:37   
(edited on: 2008-06-12 09:26)
Logged In: YES
user_id=1516468
Originator: NO

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