Is datev-exporter affiliated with DATEV?

No. This is an independent open-source project with no affiliation to, endorsement by or support from DATEV. DATEV is a trademark of DATEV eG.

Does the library guarantee that DATEV accepts the generated file?

No. Passing library validation does not prove accounting correctness or acceptance by a specific DATEV product, tenant or configuration. Generated files are import candidates and acceptance must be verified in the licensed, configured target environment.

Which EXTF Buchungsstapel versions are supported?

The fixed v13 schema with 125 columns and the legacy v12 schema with 124 columns, each with its matching EXTF management record.

Does it map SKR03 or SKR04 accounts or determine tax treatment?

No. The library is a format exporter, not an accounting engine. Your application resolves the chart of accounts, tax treatment and master data before calling it.

What encoding and line endings do generated files use?

Windows-1252 encoded bytes with CRLF record separators, matching the DATEV import contract. A later UTF-8 text step must not rewrite them.

How many booking rows fit into one Buchungsstapel file?

A maximum of 99,999 booking rows per file. A reproducible JMH benchmark covers that full-size scenario.

What does the library need at runtime?

Java 17 or newer. The plain and advanced exporters have no third-party runtime dependencies; Univocity interoperability is an explicitly separate module.

Java 17 · Apache-2.0 · release 0.2.0

Own your booking data. Reuse the format layer.

Turn already-mapped booking data into deterministic DATEV Buchungsstapel / EXTF files—with fixed v13/v12 schemas, typed metadata, technical validation and forward-only streaming.

v13 · 125 columns v12 · 124 columns Windows-1252 · CRLF plain runtime · JDK only

Build your first export Inspect the evidence

Why it exists

The hard part is not joining values with semicolons.

A complete Buchungsstapel file combines a differently shaped management record, an exact versioned heading and tightly formatted booking rows. Small drift in width, order, quoting, line endings or encoding can make an otherwise valid export unusable.

Keep the schema canonical

Use one ordered definition for all 125 v13 fields and the 124-field legacy v12 shape instead of maintaining a private spreadsheet or array.

Fail before bytes drift

Reject structural, Windows-1252 and optional semantic violations before a booking row is committed to the destination.

Choose the memory model

Retain rows when they must be inspected or replayed; stream them forward once when export volume makes retention unnecessary.

What ships

A narrow API around a precise output contract.

The common path stays dependency-light. Optional modules are explicit, so a Univocity dependency or semantic validator appears only when you choose it.

2fixed schema versions

99,999maximum booking rows per file

0third-party runtime dependencies in plain + advanced

3records: management, heading, bookings

Recommended default

Plain fixed-schema exporter

Complete v13/v12 EXTF output, retained DatevFile and the forward-only DatevStreamWriter. Choose this unless the receiving contract intentionally differs from the official heading.

Start with plain →

Custom downstream CSV

Advanced exporter

Rename, reorder or replace headings and select validation mode per file. Custom headings cannot be combined with EXTF metadata because they are no longer the fixed DATEV schema.

Compare exporters →

Existing pipeline only

Univocity adapter

Route heading-and-row output through an existing Univocity CsvWriter. It cannot emit the differently shaped management record and quotes official text headings differently.

Understand the boundary →

A deliberate boundary

Your domain in. An import candidate out.

Map in your application

Resolve chart of accounts, tax treatment, master data and client-specific rules before calling the exporter.

Assemble and validate

Attach typed metadata, write named or typed columns, and select metadata-aware technical validation.

Verify in the target

Move the generated file through your controlled transfer process and verify acceptance in the licensed, configured DATEV environment.

No import guarantee

Passing library validation—or matching the checked v13 schema and sample contract—does not prove accounting correctness or acceptance by a specific DATEV product, tenant or configuration.

Evidence, not adjectives

Compatibility claims are graded.

For v13, an opt-in contract test pins DATEV’s official checker schema and official sample archive, compares the 125 field definitions and validates all 54 sample booking rows. It does not turn a Windows GUI launch into a pass/fail import result.

For v12, the library supports the 124-column prefix and matching management record, but currently has no independent official v12 fixture or recorded real-import acceptance evidence.

See the compatibility matrix