Inspecting DATEV EXTF files and mapping generic CSV and Excel
Accounting teams exporting payment systems or e-commerce reports into German tax software often fight encoding errors, signed negative numbers, and stripped date digits. This browser utility runs locally inside a Web Worker on files up to 25 MB, either auditing existing EXTF batches or mapping generic spreadsheets per the DATEV Accounting EXTF Interface documentation.
| Processing mode | Trigger condition | Header & column mapping | Numeric & date conversion | Output readiness |
|---|---|---|---|---|
| EXTF inspection | Row 1 col 0 equals EXTF or DTVF |
Checks 31 header fields and row 2 columns | Pads 3-digit DDMM; warns on negative Umsatz |
Highlights UTF8_NOT_CP1252 warnings |
| Generic CSV/TXT | Auto-detects ,, ;, \t, or | |
Regex maps Date, Amount, Konto, Text |
Converts ISO/DD.MM.YYYY dates to DDMM |
Builds fresh EXTF v700 header |
| Generic Excel | .xlsx first non-empty worksheet |
Reads up to 250,000 rows (180 MB unzip cap) | Turns negative numbers into positive + H |
Rejects legacy binary .xls files |
| Sample EXTF | Load sample EXTF file button | ISO-8859-1 / Windows-1252 Buchungsstapel |
Validated EXTF_Buchungsstapel_Sample.csv |
Shows immediate PASS baseline |
| Sample generic | Load generic CSV button | UTF-8 table with signed amounts | Defaults SKR03 length 4, 1200 counter-acct |
Demonstrates clean EXTF synthesis |
In generic conversion mode, missing Konto values default to 8400, missing Gegenkonto values fall back to your sidebar setting (initially 1200), and currency codes default to EUR. Negative signed amounts automatically flip to unsigned positive comma-decimal numbers paired with Haben (H) rather than Soll (S).
Header matching recognizes common German and English column names such as Datum, Buchungsdatum, Betrag, Amount, Brutto, Belegfeld 1, Buchungstext, and WKZ across comma, semicolon, tab, or pipe CSV delimiters.
International finance groups maintaining accounting batches across both Germany and France frequently pair DATEV format checks with our tool to validate French DGFiP FEC accounting ledgers. Standardizing both interfaces locally removes manual CSV cleanup before monthly closings.
How are Beraternummer, SKR03/SKR04 lengths, and DDMM dates validated?
Exported booking tables frequently fail DATEV import gateways over subtle metadata rules rather than bad account balances. Every upload validates firm identifiers, chart-of-accounts digit lengths, and four-character calendar dates before producing download bytes.
31-field EXTF v700 header, Beraternummer, and Mandantennummer
Row 1 of an EXTF v700 Buchungsstapel (format category 21, format version 12) contains 31 semicolon-separated metadata fields. Our checker validates Beraternummer (4 to 7 numeric digits, 1001 or higher), Mandantennummer (1 to 5 digits from 1 to 99999), and fiscal year start WJ-Beginn (YYYYMMDD), while warning if UTF-8 bytes appear instead of Windows-1252 per the Unicode Consortium Windows-1252 code page table.
Sidebar controls let you override Beraternummer, Mandantennummer, WJ-Beginn, SKR03 or SKR04, and Sachkontenlänge interactively before exporting. Generic inputs receive clean starting defaults (1001, client 1, SKR03, length 4) so tax staff can drop in consultant numbers right before download.
EXTF inspection also extracts posting date ranges (datumVon and datumBis) and batch descriptions (Bezeichnung) from the 31-field header so reviewers confirm fiscal quarter boundaries before loading files into DATEV.
Account lengths under SKR03/SKR04 and Excel-padded DDMM dates
Both Konto and Gegenkonto must contain purely numeric digits matching your configured Sachkontenlänge (4 to 8 digits for general ledger Sachkonten) or Sachkontenlänge + 1 digits for customer/vendor Personenkonten. Optional BU-Schlüssel VAT keys allow 1 to 4 digits only.
Spreadsheets often damage Belegdatum (DDMM) by removing leading zeros (converting 0511 into 511), so three-digit inputs pad automatically before calendar verification including February 29 leap dates. Companies billing B2B buyers before posting revenue batches can generate German XRechnung and ZUGFeRD invoice templates alongside clean SKR bookings.
Windows-1252 EXTF export, Excel workbooks, and UTF-8 CSV output
After inspecting up to 300 previewed rows and confirming separate Sum Soll (S) and Sum Haben (H) EUR totals in the sidebar, choose the output format matching your downstream workflow.
Byte-accurate CP1252 encoding and 22 Buchungsstapel columns
Selecting DATEV EXTF (Windows-1252 .csv) downloads EXTF_<stem>.csv using CRLF line endings, semicolon delimiters, double-quoted strings, comma-decimal positive Umsatz, and zero BOM bytes. Our encoder maps € (U+20AC) directly to byte 0x80 alongside full German umlauts (äöüß) and safely substitutes ? (0x3F) for unsupported Unicode characters.
Each exported booking row spans 22 standard DATEV headers from Umsatz (ohne Soll/Haben-Kz) and Soll/Haben-Kennzeichen through Kostendatum and KOST2 - Kostenstelle. Stripping stray semicolons and line breaks inside text fields prevents column shifting during automated imports.
Unsigned positive Umsatz figures prevent DATEV import errors caused by minus signs inside currency fields, while separate Sum Soll (S) and Sum Haben (H) counters let accountants confirm gross batch totals.
Three-sheet Excel review workbooks and formula-safe UTF-8 CSV
- Excel review workbook (.xlsx): Builds three worksheets (
Buchungsstapel,EXTF Header, andValidation) with numericUmsatzcells so reviewers can inspect sums without altering sourceDDMMtext. - Standard UTF-8 CSV (.csv): Writes
12readable columns (Belegdatum (DDMM)toKOST2) with a UTF-8 BOM, quoting rules aligned with the IETF RFC 4180 CSV format specification, andsanitizeCsvTableformula protection against leading=,+,-,@, or|prefixes.
Groups rolling German subsidiary trial exports into annual European parent statements can inspect financial ESEF iXBRL filings offline without server uploads after exporting workbook summaries.
Troubleshooting encoding warnings, 25 MB limits, and GoBD scope
Diagnostic banners highlight whether an input passed strict EXTF v700 checks, mapped from generic columns, or hit syntax warnings that need correction prior to import.
Truncated 60-char Buchungstext, BU keys, and 25 MB upload caps
Because DATEV truncates or rejects long invoice references and posting descriptions, generic mapping slices Belegfeld 1 to 36 characters and Buchungstext to 60 characters (TEXT_TOO_LONG warning on EXTF inputs exceeding 60 chars). Single uploads cap at 25 MB (.xlsx decompression stays bounded inside sheet-tools.ts), and legacy binary .xls files must first be re-saved as .xlsx or .csv.
Statutory bookkeeping records in Germany remain governed by GoBD and retention duties of up to 10 years under the German Fiscal Code Section 147 AO retention rules. Clean pre-import formatting reduces rework when archiving monthly journal batches.
Validation warnings pinpoint exact issue codes such as BERATERNR, MANDANTENNR, WJ_BEGINN, ACCOUNT_LENGTH, and BELEGDATUM alongside row numbers so bookkeepers correct source templates quickly.
Client-side Web Worker processing and tax advisor review scope
Every inspection, conversion, and CP1252 byte write executes 100% locally inside src/workers/everyday.worker.ts with zero network file uploads. Multinational payables teams also pair German accounting batches with our BACS file checker for UK GBP disbursements.
Tip: Click Load sample EXTF file or Load generic CSV before uploading real client ledgers. Comparing
EXTF_Buchungsstapel_Sample.csvwithgeneric-bookings-sample.csvshows exactly how signed numbers map into positiveUmsatzwithS/Hindicators.
Converted EXTF files, Excel workbooks, and validation alerts are provided for informational purposes only and do not constitute legal, tax, accounting, or financial advice. Always verify VAT BU-Schlüssel tax codes, SKR03/SKR04 mappings, and GoBD archive compliance inside DATEV software and with a qualified Steuerberater, tax advisor, or chartered accountant.