DATEV Integration vs. CSV Export: Which Is More Stable in Practice?

What you export and why the method makes a difference 

This article is for finance managers and accounting teams who set up the export, run it every day or are weighing up a switch. It's also for tax advisors who want to give their clients well-founded advice.

Every export has one goal: to transfer invoices, credit notes, payables and documents so that they arrive cleanly in the DATEV system, are assigned correctly and don't cause any mysteries at month-end close.

What gets exported is the same with both methods. How it gets transferred determines how much effort it takes (and how much can go wrong).

Xentral offers three export routes:

1. CSV export (manual): Export accounting data as a CSV file in DATEV format and upload it to the DATEV system manually.

2. DATEV invoice data service 1.0: Automatic transfer directly via API. Authentication runs via DATEV SmartLogin or SmartCard and has to be renewed every 24 hours.

3. Digital document transfer (DATEV Unternehmen online): Documents are transferred directly, without local storage, in an audit-compliant way.

Here, we compare the manual transfer (route 1) with the direct integration (routes 2 and 3), because those are the two basic methods companies have to choose between in practice.

Direct DATEV integration: strengths, limits and pitfalls 

The direct DATEV integration is for companies that export regularly and in higher volumes. Once it's set up, the DATEV invoice data service transfers the data straight from the ERP.

There's no manual download, no upload, and so no risk of forgetting an export. That's an advantage especially during peak season around Black Friday and the holiday business. You make smaller, more frequent transfers without extra effort, and there's no limit on data volume.

The setup effort is higher at first. You have to configure SmartLogin, enter client and advisor numbers and set up number ranges. The integration is less flexible for special cases, for example if your tax advisor doesn't use DATEV.

3 pitfalls that keep coming up with the direct DATEV integration: 

1. Authentication expires after 24 hours 

The invoice data service 1.0 requires authentication via DATEV SmartLogin or SmartCard. It expires every 24 hours. If you forget to log in again, the automatic export stops. The problem: if several days pass without a transfer, you only notice the missing automatic export at month-end close.

Tip: Set up a calendar reminder for the daily authentication, or check the authentication status regularly.

2. Duplicate invoice numbers 

With duplicates, DATEV doesn't just reject the affected entry, it rejects the entire export. That means you have to find the error manually, correct it and then start a re-export. With a higher volume of documents, this can quickly become time-consuming.

Tip: Run a filter for duplicate invoice numbers before the export. It saves time when troubleshooting.

3. Currency codes for payables 

DATEV rejects currencies that were entered manually instead of being picked from the selection list. This affects payables to international suppliers.

Tip: Use the CSV export for diagnosis: temporarily disable CSV validation to find and correct the affected entries.

CSV export: easier to set up, but with hidden traps 

The CSV export is the pragmatic way in. For smaller companies, one-off transfers or setups with a tax advisor who doesn't use DATEV, it's often the right choice. The ongoing effort is manageable: depending on document volume, roughly 5 to 15 minutes per export.

4 pitfalls that often come up with the CSV export in accounting: 

1. Wrong DATEV format 

Xentral offers several DATEV export formats, including "New DATEV Format (from 2018)" and "Version 700". If you choose the wrong format, you'll get an error message when importing into DATEV.

Tip: Agree once with your tax advisor which format to use, and then don't change that setting again.

2. Forgetting the test booking flag (the most critical mistake) 

For the first export, the "Insert Test Booking" option has to be enabled. If you forget it, you finalize all bookings in DATEV immediately, with no easy way to undo them.

Tip: Create a short checklist for the first export and mark "Enable test booking" as a mandatory step.

3. Editing the CSV file manually 

Every manual change to the exported CSV file risks format errors on import into DATEV. That includes adding or removing columns, changing delimiters or saving in a different character set.

Tip: NEVER edit CSV files manually. Ideally, don't even open the CSV file after the export, and upload it directly.

4. Limited file volume in peak season 

The CSV export is limited to a maximum of 5,000 files per export. That's normally more than enough. But if you're still exporting monthly in November while your document volume is three times the usual, you can hit this limit. And you only notice at month-end close.

Tip: From October, plan weekly instead of monthly exports. That spreads the volume and reduces the risk of errors.

Direct comparison of DATEV and CSV: what works better in which scenario 

The difference between a DATEV export and CSV isn't just technical. It also affects the time your team invests every month and how error-prone the process stays. The following table summarizes the most important differences.

If you regularly export more than 50 documents per month, have a tax advisor who actively uses DATEV and want to scale in the long term, the higher setup effort of the direct integration pays off. The ongoing effort is minimal. The risk of errors from manual steps disappears.

For smaller companies, special cases or setups with a tax advisor without a DATEV connection, the CSV export is the pragmatic route. You should agree on the chart of accounts (SKR03 vs. SKR04) and tax codes with your tax advisor once; decisions with tax implications belong in the hands of experts.

5 practical tips for clean accounting – whatever the method 

These tips apply to both export methods. They aren't Xentral-specific recommendations but basic operating rules for anyone who regularly transfers accounting data, wants to avoid errors in the DATEV FiBu export and keep their CSV accounting clean.

1. Complete payment reconciliation before the export: Open items have to be matched with incoming payments before the export runs, otherwise you export incomplete data. The payment reconciliation agent in Xentral can automate this step: it matches bank payments with open items and closes invoices before the export starts. You can find out more on our overview page on Xentral's AI agents.

2. Check pre-assignment of accounts: DATEV only exports items with an account assignment; missing assignments don't come through. So before the export, check the "Missing Account Assignment" filter in payables.

3. Align the chart of accounts once, properly: You have to agree customer and supplier account numbers, the chart of accounts (SKR03 vs. SKR04) and tax codes with your tax advisor once. Later corrections are time-consuming (as a general rule, always align decisions with tax implications with your tax advisor).

4. Introduce a monthly reconciliation routine: Once a month, reconcile total figures between Xentral and DATEV: revenue, payables, income. Finding discrepancies early is far cheaper than discovering them at year-end close.

5. Check authentication status and export settings before every export: For the direct integration: check the auth status. For the CSV export: don't forget the test booking flag on the first export.