May 2025   ​|   ​Finance & Accounting

DATEV & Odoo – sounds like the perfect combination. But as is so often the case when two systems come together, it turns out that technology can do a lot, but not everything.

Odoo already comes with a DATEV interface as standard - export of booking lines in ASCII format, document images in XML format. Sounds good? It is - in theory. In practice, however, it turns out that more finesse is needed in the details than the standard can provide.

A brief review: From XML export to the BEDI link

Up to version 18, Odoo exported postings including receipts in “extended XML format”.

Since version 18, Odoo has taken a different approach: the so-called BEDI link has been introduced.

This link connects invoices and documents via a hash value that appears in the ASCII export as a cryptic character string in the “Document link” column. This hash is essential for DATEV - it ensures that the correct link works during import.

A smart step - but only a first one.

Where the standard interface reaches its limits

Despite many good approaches, the daily application shows: The interface needs tutoring. Here is an overview of the typical weaknesses:

1. Export from the general ledger

•  Any user with accounting rights can export at any time

•  No central overview or tracking

•  This can quickly become confusing in larger teams

2. Automatic number assignment

• Odoo assigns customer and vendor numbers automatically

• There is no option to define your own number ranges

•  For all those who love structured numbers - rather impractical

3. Hidden setting options

• Consultant number, client number, automatic key – hidden in the system

•  Hard to find without technical know-how

•  Flexibility? Not a chance.

4. No DATEV check

• No automatic check of the exported fields for DATEV conformity

•  Consequence: Manual corrections - and loss of time

5. No export status for “fixed” bookings

•  ASCII exports cannot be transferred as “hard-coded”

•  But this is a must for many tax firms

6. Problems with 0 accounts

• Odoo exports 0 accounts with leading zero

• DATEV does not understand this – Error message during import

7. Additional information missing during export

• KOST1 / KOST2 are not transferred

• Service date missing

• Terms of payment remain undefined

8. BEDI Links - no refresh possible

• Currently no possibility to assign new BEDI links

•  A real gap for corrections or changes

9. No ASCII reimport possible

•  Exported once = one-way street

• DATEV ASCII files cannot be imported back into Odoo

10. No grouping of booking lines

•  Each line stands for itself

•  No clear export with summarized positions
  
  

Conclusion: A good foundation with optimization potential

Odoo's DATEV interface is a step in the right direction - especially with the introduction of the BEDI link.

But:

If you want to work professionally with DATEV, you need more. More control. More flexibility. More insight.

The details are crucial - especially in financial accounting. And here it is clear that the standard can be improved.

What now?

For all those who don't want to settle for half solutions:

• We show you how to take DATEV integration to a new level with syscoon

• We develop advanced exports, intelligent checks and user-friendly settings

•  And we don't think of DATEV as a restriction - but as an opportunity to make processes smart and secure

Because one thing is certain: accounting can be complex - but never complicated.