CSV → DATEV EXTF Buchungsstapel 700/13
Prepare a DATEV EXTF Buchungsstapel CSV for manual accounting import, using genuine client, adviser and fiscal-period details.
Purpose
Upload the original CSV and inspect canonical columns or map actual fields. Provide the real DATEV adviser/client numbers, fiscal year, posting period, account length, booking options and bank/counter-accounts. Confirm tax treatment without estimation. Java checks representability in a free destination inspection before a separate paid or eligible trial conversion.
Workflow fit
For accountants who need reviewed bank transaction data as a DATEV EXTF 700/13 Buchungsstapel journal batch, not as a DATEV bank statement.
Implementation note
Output is a .csv EXTF Buchungsstapel whose filename and encoding come from the server. It is NOT a bank-feed import, tax calculator, DATEV API connection or certified DATEV import. Save a backup and verify the batch in the target DATEV environment.
DATEV EXTF 700/13 · Buchungsstapel (not a bank statement)
No. It is a DATEV EXTF 700/13 Buchungsstapel for journal postings, not a bank-feed or account-statement import.
No. You must provide and verify actual accounts, counterparties, posting dates and tax treatment. Incomplete or inconsistent evidence is rejected.
Yes, if Java accepts the original source and complete mapping; missing fields and unrepresentable transactions are not silently discarded.
No. Source and destination inspections consume neither prepaid credits nor trial conversions. A separate conversion uses the published pricing and eligibility limits.
No. A technically valid EXTF batch is not proof that your DATEV configuration accepts it. Review period, chart of accounts and batch after import.
Related converters
Explore other production-ready routes connected to this format.