// THE MOST IMPORTANT POINTS AT A GLANCE
What You'll Take Away from This Article
- Standard export (ASCII) plus BEDI Link (available since v18) for document linking.
- Ten vulnerabilities, including a lack of compliance checks, a lack of formalization, and issues with zero-balance accounts.
- Conclusion: It's a good approach, but for professional use, you'll need Syscoon extensions.
// BACKGROUND
Background and Context
DATEV & Odoo—it 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 yet.
Odoo comes with a DATEV interface out of the box—exporting journal entries in ASCII format and document images in XML format. Sounds good? It is—in theory. In practice, however, it becomes clear that, especially when it comes to the details, more finesse is needed than the standard interface can provide.
// BEDI-LINK
A Brief Look Back: From XML Export to BEDI Link
Up through version 18, Odoo exported entries along with their supporting documents in “extended XML format.”
Starting with version 18, Odoo has taken a different approach: the so-called BEDI Link has been introduced.
This link connects invoices and receipts via a hash value, which appears in the ASCII export as a cryptic string in the “Receipt Link” column. This hash is essential for DATEV—it ensures that the correct link is established during import.
A smart move—but just the first step.
// WEAKNESSES
Where the Standard Interface Reaches Its Limits
Despite many good ideas, daily use reveals that the interface needs some work. Here is an overview of its typical weaknesses:
- Export from the General Ledger
Any user with accounting permissions can export data at any time
No centralized overview or tracking
This can quickly become confusing in larger teams - Automatic Number Assignment
- Odoo automatically assigns customer and vendor numbers
- There is no way to define your own number ranges
- For anyone who loves structured numbers—it's kind of impractical
- Hidden Settings
- Consultant ID, client ID, auto-generate key—hidden in the system
- Hard to find without technical expertise
- Flexibility? Not a chance.
- No DATEV Check
- No automatic check of exported fields for DATEV compliance
- Consequence: Manual corrections—and wasted time
- No export status for “fixed” entries
- ASCII exports cannot be passed as “fixed”
- For many tax firms, however, this is exactly what's required
- Problems with zero-balance accounts
- Odoo exports zero accounts with a leading zero
- DATEV doesn't understand this – error message during import
- Additional information is missing during export
- KOST1 / KOST2 are not transferred
- Payment date missing
- BEDI Links – Refresh Not Possible
- Currently, it is not possible to assign new BEDI links
- A real gap when it comes to corrections or changes
- ASCII reimport not possible
- Once exported = no turning back
- DATEV-ASCII files cannot be imported back into Odoo
- No grouping of posting lines
- Each line stands on its own
- No clear export with consolidated items
// CONCLUSION
CONCLUSION
Conclusion: A solid foundation with room for improvement
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 clarity.
It's the details that matter—especially in financial accounting. And this is where it becomes clear: The standard has room for improvement.
// OUTLOOK
OUTLOOK
What now?
For anyone who isn't willing to settle for half-measures:
We'll show you how to take your DATEV integration with syscoon to the next level
We develop advanced export features, smart checks, and user-friendly settings
And we don't see DATEV as a limitation—but rather as an opportunity to design processes in a smart and secure way
Because one thing is certain: Accounting can be complex—but it should never be complicated.