Byte-Order-Mark missing on CSV export for Datev

accounting csv format CSV Datev

1 Beantwoorden

140 Weergaven

Daniel Huying

Using Odoo 18.4.

In the Accounting App, I can go to Reporting->Audit Reports->General Ledger and then via the gear symbol make a DATEV Data export. This creates a zip file named general_ledger_data.zip which contains 3 CSV files EXTF_accounting_entries.csv etc.

The CSV files are created with UTF-8 encoding, but without a ByteOrderMark.

In the official definition of the DATEV format (on https://developer.datev.de/de/file-format/details/datev-format/character-set) it is stated:

Der Default-Zeichensatz für den Import nach DATEV Rechnungswesen ist der Standard ISO-8859-1 bzw. CodePage 1252. Zusätzlich kann DATEV Rechnungswesen auch die Unicode-Standards (UTF-8, -16, -32) interpretieren, sofern die ByteOrderMark (BOM, gilt auch für UTF-8) mitgeliefert wird.

Translation:

The default character set for importing into DATEV Accounting is the ISO-8859-1 standard, code page 1252. Additionally, DATEV Accounting can also interpret the Unicode standards (UTF-8, -16, -32) if the ByteOrderMark (BOM, also applicable to UTF-8) is included.

It seems that the output is not in conformance with the DATEV format definition, since it is UTF-8, but without the ByteOrderMark.

Is there a fix to get the CSV files to be created WITH the ByteOrderMark?

This is not only relevant for DATEV, but also to simply open the CSV files in Microsoft Excel, which will only interpret the characters in UTF-8 files correctly if there is a ByteOrderMark.

Zehntech Technologies Inc.

Hello Daniel,

Yes, you are correct in your observation.

Odoo currently generates the DATEV export CSV files using UTF-8 encoding without a Byte Order Mark (BOM). While many systems can interpret UTF-8 without BOM, DATEV and Microsoft Excel often rely on the BOM to correctly detect the encoding, especially for special characters.

Out of the box, Odoo does not provide a setting to include the BOM in these exports. The typical approach is to slightly override the export generation logic via a custom module so that the CSV files are written using UTF-8 with BOM (utf-8-sig) before being added to the ZIP archive.

This is a relatively small customization in the reporting/export code and ensures full compatibility with DATEV’s format requirements and Excel imports.

Hope this works for you! Feel free to reach out for further discussion.

Regards,

Zehntech Technologies Inc.

santosh.sekwadia@zehntech.com

Geniet je van het gesprek? Blijf niet alleen lezen, doe ook mee!

Maak vandaag nog een account aan om te profiteren van exclusieve functies en deel uit te maken van onze geweldige community!

Aanmelden

Gerelateerde posts	Antwoorden	Weergaven
How to change date format in odoo14 accounting format odoo	1 jun. 23	3954
How to save a csv file to download it later by clicking another button? filestore csv CSV v14	1 okt. 21	3262
Fetch list of all created Invoices data for the user, do some calculations and write to csv file accounting invoice tax csv	0 aug. 17	4377
How can we export accounting data for external audits? accounting export format datev	1 okt. 16	6713
'NoneType' object has no attribute 'group' while validating accounting import csv nonetype	1 mrt. 15	7154

Deze vraag is gerapporteerd

Geniet je van het gesprek? Blijf niet alleen lezen, doe ook mee!