Troubleshooting

Xentral DATEV Export Troubleshooting - The Most Common Errors

DATEV export from Xentral not working? The 10 most common problems and their solutions. From 'Successful but no data' to validation errors.

Fabian22. Jänner 2026Updated: 27. Jänner 202616 min read
datevaccountingexporttroubleshootingtax advisor
DATEV export from Xentral: accounting documents next to a laptop on a desk

DATEV Export Not Working? The Short Answer

The 3 most common causes of failed DATEV exports from Xentral:

  1. Duplicate document numbers → Check invoices for duplicates
  2. Missing account mappings → Enter revenue and tax accounts in Xentral
  3. Wrong export period → DATEV expects completed periods

Quick fix: Accounting → Invoices → Filter by period → Search for duplicates → Retry export.

ProblemSolution
"Successful" but no dataCheck for duplicate document numbers
"bindTo() on null" errorAccount mapping is missing
Amounts are incorrectVerify tax rates

It's the 15th of the month. Your tax advisor is waiting for the DATEV data. You click "Export" and... nothing happens. Or a cryptic error message appears. Or Xentral reports "Successful" — but nothing shows up in DATEV.

Welcome to the club. The DATEV export is one of the most common pain points in the Xentral community. In my consulting practice, I see these problems weekly — sometimes daily. The good news: most issues can be resolved on your own once you know where to look.

In this article, I'll walk you through the ten most common DATEV problems in Xentral and how to fix them. You'll also learn how to set up the integration correctly from the start to prevent many of these issues altogether.

Why the DATEV Integration Matters

Before diving into troubleshooting, a brief background for context. DATEV is the standard system for working with tax advisors in Germany and Austria. More than 40,000 tax firms use DATEV, and if your tax advisor is one of them, there's no way around the integration.

Without a working DATEV integration, that means: manually exporting data, preparing it, sending it to your tax advisor, answering follow-up questions, incorporating corrections. That costs time — yours and your tax advisor's, who will naturally bill for it.

With a working integration: click Export, data flows automatically into DATEV Unternehmen Online, and your tax advisor can start working immediately. This not only saves time but also reduces the errors that occur during manual data transfer.

That's why it's worth investing time in troubleshooting. A working DATEV integration pays off every month. You can find the official documentation in the Xentral Help Center.

Expert insight: "90% of all DATEV problems in Xentral come down to one of three causes: duplicate document numbers, missing account mappings, or an incorrect export period. The fix is usually done in 15 minutes." — Fabian, XentralExperte.at


Why Does Xentral Show "Successful" but DATEV Has No Data?

This is the most frustrating problem of all, because Xentral claims everything is fine — but nothing arrives at the tax advisor's end.

What you see: Xentral displays "Export successful." You breathe a sigh of relief. Then your tax advisor calls: "I don't see any postings for this month."

The most common cause: Duplicate document numbers within the export period. If two invoices share the same number, DATEV rejects the import — but Xentral's new DATEV interface unfortunately doesn't display this as an error. This is a known issue that Xentral will hopefully fix soon.

How to resolve it: Open the Accounting section in Xentral and navigate to Invoices. Filter by the period you were trying to export. Sort by invoice number and look for duplicates. If you find any, you'll need to cancel one of them and reissue it with a unique number.

Then run the export again. This time, it should actually arrive in DATEV.

Why does this happen? Duplicate invoice numbers often arise from manual interventions, cancellations that weren't processed correctly, or system errors. Running a regular duplicate check before each export prevents this problem.


Problem 2: Technical Error Message "bindTo() on null"

Sometimes Xentral displays a technical error instead of a readable message. One of the most common is: "Call to a member function bindTo() on null".

What it means: This is a PHP error pointing to an issue in Xentral's code — not a configuration error on your part.

The cause: This error occurred in certain older Xentral versions and has since been fixed. If you're seeing it, your Xentral version is out of date.

The solution: Update Xentral to the current version. This error should be resolved since version 23.0.32. If you can't or don't want to update yourself, contact Xentral support.

After the update, the export should work. If the error persists after updating, open a support ticket with the exact error message.


Problem 3: CSV Validation Errors

You attempt a CSV export and Xentral shows "Validation error" — without revealing which record is causing the problem. Frustrating, but solvable.

What's happening: The CSV validation checks whether all exported data meets DATEV's requirements. If there's a problem, the export is aborted, but the error message is often too vague to be useful.

Common causes of validation errors: Invalid IBAN or BIC length, incorrectly formatted tax numbers, special characters in fields that only accept ASCII, missing required fields such as posting text or account.

The troubleshooting approach: Go to the DATEV export settings and temporarily enable the option "Disable CSV validation." Run the export and save the CSV file locally. Open the file in Excel and look for suspicious entries: empty IBAN fields, values that are too short or too long, special characters.

Once you've found the culprit, correct the master data in Xentral. This could be customer data, supplier data, or account settings. After making the corrections, re-enable validation and run the export again.

This process is time-consuming, but it helps you improve the long-term data quality in your system.


Problem 4: Export Button Does Not Respond

You click the export button and absolutely nothing happens. No error, no file, no reaction. As if the button is broken.

The cause: Almost always a browser issue. Either the cache is stale, JavaScript is blocked, or a browser extension is interfering.

How to proceed: First, clear your browser cache. In most browsers, this is done with Ctrl + Shift + Delete. Select "Cached images and files" and delete them.

If that doesn't help, try an incognito or private browsing window. All extensions are disabled there and the cache is empty. If it works there, one of your extensions is the culprit — ad blockers or script blockers are common offenders.

As a final test, try a different browser. If it doesn't work in Chrome, try Firefox or Edge. This helps you determine whether the problem is browser-specific.


Problem 5: Documents and Postings Not Linked

The postings arrive in DATEV, but the associated documents (PDFs) are missing or aren't linked to the postings. Your tax advisor sees the figures but not the corresponding invoices.

Why this happens: The classic CSV export only transfers posting data — no documents. The PDFs must be uploaded separately and assigned manually or via a different process.

The better solution: Use the XML + PDF export instead of CSV. This method is more modern and transfers postings and documents together in a single package.

How to switch: Go to the DATEV export settings and select "DATEV XML" as the export format. Enable the option "Include document images." The export will now generate a package that you upload to DATEV Unternehmen Online. Documents are automatically assigned to the correct postings.

This method requires that your tax advisor uses DATEV Unternehmen Online. If they're still using classic DATEV software, discuss an upgrade with them — it's worthwhile for both sides.


Problem 6: Period Overlaps and Duplicate Postings

During the import into DATEV, you see messages like "Posting already exists," or you find duplicate postings for the same period.

The cause: You exported overlapping periods. For example, January 1–15, and then January 10–31. The postings from January 10–15 are now duplicated.

The simple rule: Always export complete months, never overlapping periods. And keep a simple log of what you've exported and when.

Best practice for monthly exports: On the fifth of the following month, export the previous month in full. So on February 5, you export January (01/01–01/31); on March 5, February (02/01–02/28); and so on. This system is simple and prevents overlaps.

Why the fifth? That gives you time to capture any late-arriving invoices that trickle in at the beginning of the month.


Problem 7: Amazon Fees Are Missing or Incorrect

If you sell through Amazon, you may know this problem: Amazon revenues appear in the export, but the fees are missing or incorrect.

Why this happens: Amazon uses its own billing model. Fees are not deducted per order but are collected and netted against the payout. This doesn't align with Xentral's order model, where each order is a self-contained unit.

Two possible solutions:

The first option is the clean approach: you post Amazon fees separately based on the Settlement Report. Amazon provides you with a detailed biweekly report that precisely breaks down which fees were incurred for which transactions. You post these fees as a lump-sum entry to a dedicated expense account "Amazon selling fees." This requires a bit more work but is bookkeeping-compliant.

The second option is an estimation approach: calculate the average fee per order and post it directly. For most Amazon categories, fees range between 15 and 20 percent of the selling price. You define an average and post it per order as an expense. Quarterly, you reconcile the difference against the actual amount.

Which method is better depends on your volume and your tax advisor's preferences. Discuss it with them before committing to an approach.


Problem 8: Foreign Currencies Displayed Incorrectly

EUR amounts suddenly appear as a foreign currency, or conversely: CHF amounts are exported as EUR. This naturally distorts the entire accounting record.

The cause: In some Xentral versions there were bugs in the new DATEV interface that handled currencies incorrectly. The problem occurred especially in mixed setups — i.e., when processing both EUR and other currencies.

The solution: First check whether you're using the current Xentral version. Many currency issues have been resolved in newer releases. If the problem persists after updating, open a support ticket with Xentral and include concrete examples.

As a workaround, support can sometimes temporarily enable the legacy export method, which has more stable currency handling. This is not a permanent solution, but it bridges the gap until the next fix.


Problem 9: Cost Centers Are Not Transferred

You've set up and maintained cost centers in Xentral, but they don't arrive at the tax advisor's end. The postings are there, but without cost center assignments.

The cause: Cost centers are not exported automatically. You need to explicitly configure them to be included in the export.

How to enable cost center export: Navigate to Accounting, then Settings, then DATEV. There you'll find an option "Export cost centers." Enable it. Also make sure the cost center numbers in Xentral match those in DATEV. If you have cost center "100" in Xentral, there must also be a cost center "100" in DATEV.

After enabling this, run a test export and confirm with your tax advisor that the cost centers are coming through.


Problem 10: Advisor Number or Client Number Invalid

When connecting to DATEV Unternehmen Online, an error message appears stating that the advisor number or client number is invalid.

The cause: Incorrect credentials or missing permissions on the DATEV side.

The multi-step solution: First, verify the advisor number with your tax advisor. It is five digits and identifies the firm. Then check the client number — also five digits, identifying your company within the firm.

If both numbers are correct, the problem is likely due to missing permissions. Your tax advisor needs to grant authorization for data exchange in DATEV Unternehmen Online. Ask them to check and activate this if necessary.


Setting Up the DATEV Export Correctly: Prevention over Repair

Many of the problems described above can be avoided if the DATEV integration is set up correctly from the start. Here are the most important points for a clean setup.

Check the Basic Configuration

Before running your first export, go through this checklist:

Is the DATEV export enabled? In some Xentral setups, the feature must be activated first.

Are the advisor number and client number stored? Without this data, the connection to DATEV Unternehmen Online won't work.

Is the correct export format selected? I recommend XML + PDF for most setups, because it automatically links documents.

Align the Chart of Accounts

Xentral and DATEV must use the same chart of accounts. In Germany, this is typically SKR03 or SKR04. Check with your tax advisor which one they use, and configure Xentral accordingly.

If the charts of accounts don't match, postings will be booked to incorrect accounts, which requires costly corrections.

Ensure Master Data Quality

Most validation errors stem from poor master data. Invest time in data maintenance:

All customers should have complete addresses. DATEV requires correct postal addresses for the postings.

IBAN and BIC must be in the correct format. German IBANs have 22 characters; Austrian IBANs have 20.

Tax numbers and VAT IDs should be correctly formatted. German VAT IDs begin with "DE" followed by 9 digits.

Perform Regular Test Exports

Don't wait until month-end to discover the export isn't working. Run small test exports regularly to catch issues early. A weekly test export with a few postings will confirm whether the system is fundamentally working.


Real-World Example: A Typical Troubleshooting Case

To illustrate what troubleshooting looks like in practice, here's an anonymized case from my consulting work.

The situation: A mid-sized online retailer processing around 2,000 invoices per month. The DATEV export had been running smoothly for months, then suddenly stopped working. The message: "Export successful," but nothing arrived at the tax advisor's end.

The analysis: I first checked the obvious causes: version up to date? Yes. Credentials correct? Yes. Period clean? Yes.

Then I looked at the invoice numbers and found the problem: due to a system error during a cancellation, two invoices had been created with the same number. They were two weeks apart and each appeared correct in isolation — but together within the same month, they triggered a silent import rejection in DATEV.

The resolution: One of the two invoices was cancelled and reissued with a corrected number. The export ran through immediately afterward.

What we learned: We introduced a monthly check for duplicate invoice numbers — a simple SQL query that runs before every export. The problem has not recurred since.

Time required: Analysis and resolution took about two hours. The monthly preventive check now takes five minutes.


Checklist Before Every DATEV Export

Run through this list before every export:

  • Is the period a complete month?
  • Is there no overlap with previous exports?
  • Do all invoices have unique numbers?
  • Are all postings correctly assigned to accounts?
  • Are the tax keys correct?
  • Is Xentral up to date?
  • Have you reviewed the last export logs for warnings?

If you can check off all items, the export should run without issues.


Frequently Asked Questions (FAQ)

How often should I run the DATEV export?

For most businesses, a monthly export is sufficient. Run it in the first week of the following month so that all late-arriving documents are captured.

CSV or XML — which is better?

XML + PDF is the more modern and superior option. Documents are automatically linked, and the import into DATEV is cleaner. CSV is now only relevant for specific legacy setups.

My tax advisor doesn't use DATEV Unternehmen Online. What should I do?

In that case, only a file export (CSV or XML) is possible. You export the file from Xentral and send it by email or cloud storage to your tax advisor, who then imports it manually.

Can I export months retroactively?

Yes, but be careful about overlaps. If a month has already been exported and you export it again, duplicates will appear in DATEV.

What do I do when I encounter a technical error I don't understand?

Take a screenshot of the exact error message and open a support ticket with Xentral. Include your Xentral version, the browser you're using, and a description of what you were doing when the error occurred.

Are cancellations automatically transferred?

Yes, but the handling depends on your configuration. In general, cancellation invoices are exported as negative postings.

How long do I need to keep the export files?

You don't need to keep the files themselves, but you do need to retain the underlying documents — ten years under German commercial law. The data is stored in the system, meaning in both Xentral and DATEV.

Can I automate the export?

In principle, yes — via Xentral Flows or cron jobs. However, I recommend keeping a manual review step before the final export is sent to your tax advisor.


When to Contact Xentral Support

Xentral support can help when:

  • The error message is technical in nature (PHP error, database error, etc.)
  • The problem appeared after an update
  • You've tried all the solutions described here
  • It's a demonstrable bug

Create a ticket including: the exact error message as a screenshot, your Xentral version, the browser you're using, and a description of what you've already tried.


Conclusion: Most Problems Are Solvable

The DATEV export in Xentral can be stubborn at times, but most problems can be resolved on your own with the right information. The key takeaways:

Check for duplicate document numbers — this is the most common cause of "successful" exports that don't actually arrive.

Always export complete months with no overlaps.

Use XML + PDF instead of CSV for automatic document linking.

Keep Xentral up to date — many bugs are fixed in new versions.

Work closely with your tax advisor — they know the DATEV side better than you do.

If you're still stuck despite everything, reach out to me. Resolving DATEV issues is one of my most frequent support requests, and I'm happy to help.


Further Resources

Next Steps

Fabian

Fabian

Xentral Consultant & E-Commerce Expert

After building my own logistics business with €3.5M annual revenue, I now consult SMEs on Xentral implementation. Practitioner knowledge, not theory.

Xentral user for 6 years8+ years of e-commerce experience
More about me

Questions about this topic? I'm happy to help — free of charge and without obligation.

Book a free consultation

Questions about this topic?

I'm happy to help — free of charge and without obligation. Let's find out in a short call how I can assist you.