MT940 → DATEV EXTF Buchungsstapel 700/13

MT940 to DATEV EXTF Buchungsstapel 700/13

Prepare DATEV EXTF journal postings from original MT940 bank statements after explicit accounting review.

Purpose

What this converter does

Upload the unchanged SWIFT MT940 bank statement (.mt940, .sta or .txt). Java inspects actual statement groups, :61: entries, :86: details, dates, balances and booked status; the browser neither interprets postings nor converts them through CSV. Provide genuine bank and counter-ledger accounts, DATEV adviser/client data, fiscal period and explicit tax confirmation. A free destination inspection must approve the native source and accounting plan before a separate eligible paid or trial conversion.

Workflow fit

When this route is useful

For bookkeeping teams importing vetted SWIFT MT940 bank entries into DATEV EXTF Buchungsstapel 700/13 journal batches, rather than DATEV bank feeds.

Implementation note

What to expect

The output is a DATEV EXTF .csv journal batch, not MT940, a bank-feed import or a guaranteed DATEV connection. Missing booking dates, multi-statement ambiguity, reversals, FX, insufficient balances or counterparties may be rejected. No ledger or VAT information is invented. Verify the batch in your DATEV installation.

DATEV EXTF 700/13 · Buchungsstapel (not a bank statement)

Before converting MT940 to DATEV EXTF

Select the original MT940 / STA / TXT statement file
Confirm its native source; Java reviews statement and financial semantics
Declare real accounts, counterparties, DATEV period and taxes; run free inspection
Convert, download the EXTF .csv and verify journal postings in DATEV

Do I need to convert MT940 to CSV first?

No. The Java backend reads the original MT940 bytes directly and validates the statement without an intermediate CSV or tabular mapping.

Can missing counter-accounts or booking dates be inferred?

No. You must provide real evidence. Entries without authentic dates or accounts may be refused rather than silently completed.

What about multiple statements, reversals and foreign currencies?

The backend determines whether each statement and posting can be represented. Ambiguous grouping, unbalanced entries or unsupported foreign-currency data may be rejected.