OdooWiki OCA HUB

Datev Export DTVF

datev_export_dtvf folder_open OCA/l10n-germany open_in_new
Accounting License: AGPL-3

This module implements DATEV exports in the dtvf format.

auto_awesome What this module does

AI-generated from the code · Odoo 19.0

Create DATEV DTVF export files (ZIP with CSV) from posted journal entries for a chosen fiscal year and periods, and optionally send them automatically by email every month.

This module adds a DATEV DTVF export screen under Accounting > Reporting. Users create an export record, choose a fiscal year, one or more periods and optionally journals, then click Generate. Odoo collects all posted journal entries in those periods and produces a ZIP file containing the booking batch, partner master data and account descriptions in DATEV format. The generated file is stored on the record and can be downloaded.

Settings in the invoicing configuration control the DATEV account code length and how business partners are numbered (none, Enterprises Edition, or a sequence). When sequence numbering is used, DATEV customer and supplier numbers appear on the partner form in the Accounting tab, with Generate buttons that assign the next number from the configured sequences.

On each account you can set an alternative DATEV code and a flag that suppresses automatic calculations in DATEV for entries on that account.

A scheduled job (disabled by default) can run monthly: it finds the previous month and its fiscal year, creates an export, generates the file and emails it using the DATEV export template.

Depends on

Menus it adds

menu_datev_export_dtvf
Models and fields (5)
  • res.company · extends an existing modeldatev_partner_numbering (DATEV Partner numbering), datev_account_code_length (DATEV account code length), datev_customer_sequence_id, datev_supplier_sequence_id
  • res.partner · extends an existing modell10n_de_datev_export_show, l10n_de_datev_export_identifier_customer (DATEV number (customer)), l10n_de_datev_export_identifier_supplier (DATEV number (supplier))
  • account.account · extends an existing modeldatev_code, datev_export_nonautomatic (Suppress automatic calculations in DATEV)
  • res.config.settings · extends an existing modeldatev_partner_numbering, datev_account_code_length, datev_customer_sequence_id, datev_supplier_sequence_id
  • datev_export_dtvf.export · new modelname, state, file_data (Data), file_name (Filename), company_id, period_ids (Periods), journal_ids (Journals), fiscalyear_id (Fiscal year), date_generated (Generated at), fiscalyear_end, fiscalyear_start

Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 3 confirmed, 6 with no information of 9 versions.

Sources · Odoo 15.0

Confirmed on 2026-11-03 in branch 15.0 of OCA/l10n-germany.

terminal Installation and usage

OCA documentation · Odoo 19.0

To configure this module, you need to:

  • Go to Settings -> Invoicing
  • Fill in the fields in the DATEV section
  • For accounts where you want to suppress automatic calculations (for ie taxes), set the according flag

The module also contains an inactive cronjob and a mail template allowing you to send period DATEV export somewhere via email. It relies on finding exactly one date range for the previous month and one for the year of the previous month, otherwise you'll see an error message in your log when running the cronjob. Note that the data transmitted via email is not encrypted.

To use this module, you need to:

  • Go to Invoicing / Reporting / DATEV export
  • Create an export, choose a date range to use as fiscal year, and ranges to export
  • Click Generate

No verified information in OCA: Installation.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.