DATEV interface

A good DATEV handover not only saves recording time. It creates a common, verifiable cycle between operational X-ERP and accounting.

Translate a set of rules into a safe process

The DATEV CSV header contains central context values such as consultant and client number, financial year, ledger account length and data period. The posting lines must fit this context and the coordinated account/tax logic.

This is how X-ERP works in the process

1. Agree on the account framework, account length, advisor/client number, financial year and export period.
2. Check general ledger accounts, personal accounts, tax codes, document dates, document numbers and cost centers.
3. Generate the DATEV export from a defined, documented period of time.
4. Validate headers and lines; compare debits/credits, taxes and totals.
5. First import into test/batch processing and resolve protocol errors.
6. Archive export, log and release to the X-ERP period.

Check before submitting or shipping

• Header values match the recipient system.
• Accounts and tax codes are valid.
• Debit/credit and tax controls are correct.
• No period is passed on twice or incompletely.

Limits and obligation to check

• Account length does not match the financial year.
• posting text replaces missing structured reference.
• A corrected export is imported additionally instead of replacing it.

This is what you take with you

The transition to financial accounting is period-accurate, auditable and coordinated together.

Further information / source

Related topics

1. For country specialists – National requirements and special features › ELSTER export
2. For country specialists – National requirements and special features › GoBD

Frequently asked questions