Convert DKB CSV to MT940Upload an existing CSV or XLSX transaction export, verify amounts and columns, and convert it for accounting.
DKB explicitly lists CSV exports for securities transactions as unavailable. That does not establish the availability or absence of CSV exports for current-account transactions. Check the export options of the specific DKB product.
Official provider documentationDrop your CSV or XLSX file here
Upload a CSV or XLSX file with booking date, amount and description. MT940/CAMT.053 additionally require an account identifier, currency and a reliable balance basis.
1 credit per started block of 50 transactions
1–50 transactions = 1 credit, 51–100 = 2 credits, and so on. CSV input is billed by transaction count rather than PDF pages.
For bank transactions, review account scope, internal transfers, payment references and amount signs. Transaction lists do not always provide full statement balances.
DKB giro and card statements prepared for CSV/Excel.
MT940 requires coherent account statement and transaction data. Account reference, currency and opening and closing balances may be needed for reconciliation.
Use a transaction or statement CSV exported by your bank or card issuer. A PDF statement requires a separate workflow.
Dates, debit/credit signs, currencies, fees and account identifiers vary by report. Check unmatched columns and missing statement balances.
DKB giro and card statements prepared for CSV/Excel.
Open the matching PDF page