DKB Statement to Excel Converter

Partly. The DKB app itself speaks English: DKB's help page says the app supports German and English, and takes the first supported language from your phone's settings — on an iPhone you can switch it under Settings › DKB app › Language, on Android 13 and later under System › Languages & input › App languages. The menus, buttons and the Postfach then read in English.

The documents are another matter. DKB states on the same page that even if you change the app's language, the contract language with DKB remains German, and its help pages on statements, older statements and confirmations describe no English-language Kontoauszug or English bank confirmation. In practice that means the statement you download from the Postfach is in German, whichever language your app shows.

If you need the content in English — for a landlord abroad, a visa file or an accountant outside Germany — the useful move is to keep the German PDF as the document and hand over a converted version alongside it. FlowParse reads the German statement and returns plain columns: the date, the description and one signed amount, with the opening and closing balance checked. Whether an institution accepts a German statement with such an export is its decision; ask it before you send anything.

DKB issues documents on a fixed rhythm, and knowing it tells you when a month is complete enough to convert. The Girokonto statement comes monthly, after the 5th. The Tagesgeld statement follows the same rhythm. The credit card statement comes monthly after the 22nd, so its period never lines up with the calendar month of the Girokonto. A Kreditkonto gets one statement a year, at the start of the year, and every securities trade or distribution gets its own Abrechnung straight away.

For bookkeeping that means two things. A calendar-month close for the Girokonto can be done in the first week of the next month. The card is better reconciled on its own cycle, 22nd to 22nd, and then matched to the single Girokonto booking that settles it. FlowParse converts both; Smart Merge can put them in one workbook with a source column, so the card's individual purchases and the Girokonto's settlement booking sit side by side.

Most of the German on a DKB Kontoauszug comes down to a short list of banking terms. Kontoauszug: account statement. Datum: date. Erläuterung: description or details of the booking. Betrag Soll: debit, money out. Betrag Haben: credit, money in. Kontostand: balance; alter and neuer Kontostand: the old and new balance, meaning the opening and closing balance for the period. Verwendungszweck: payment reference. Lastschrift: direct debit. Überweisung: bank transfer. Gutschrift: incoming credit. Gläubiger-ID and Mandatsreferenz: the creditor ID and mandate reference that come with a SEPA direct debit.

German number formatting is the other trap for an English reader: 1.250,00 means one thousand two hundred and fifty euros, with a dot for thousands and a comma for the cents. Dates run day, month, year. FlowParse reads both as numbers and dates, so the converted sheet sums correctly in Excel set to any language.

A Kontoauszug is not generated on request — DKB creates it on fixed dates: the Girokonto and the Tagesgeld monthly after the 5th, the credit card monthly after the 22nd, the Kreditkonto once a year. If you need a statement for the middle of a month, there are three things DKB does let you produce yourself, and one you ask for.

First, a transaction list: in the banking, filter the Umsatzübersicht to the dates or account you need and choose Exportieren — DKB's help says the list exports as a PDF. Second, a Bankbestätigung, which shows your name and IBAN but no balances: in the Postfach choose Weitere Dokumente anfordern › Bankbestätigung, and DKB provides it as a PDF free of charge in the web banking (not in the app). Third, the Entgeltaufstellung, an overview of the previous year's fees and interest: request it under Kontodetails, and it arrives in the Postfach within a few hours.

What you ask for is a Saldenbestätigung, a confirmation of balances on all your DKB accounts at a date you choose: write to DKB through the contact form with your IBAN and the cut-off date. It is chargeable and comes by post. DKB itself notes that a statement or a transaction overview from the banking is often enough — free and faster.

DKB's help page on statements describes one export for account transactions: the filtered Umsatzübersicht exported as a PDF. We found no DKB help page describing a CSV or Excel export of Girokonto transactions in the current banking, so this page does not tell you to look for one.

The route that works with what DKB documents is PDF to CSV. Take the monthly Kontoauszug from the Postfach — or the exported transaction list — and convert it. FlowParse merges Soll and Haben into one signed amount, keeps the whole Erläuterung, and checks the month against its old and new balance before you download Excel, CSV or the DATEV-ready file. The free plan covers 10 pages a month, which is enough to see a few months of DKB statements come out as rows.

Most DKB business and freelance customers do not keep the books themselves in Excel; they hand them to a Steuerberater working in DATEV, or keep them in Lexware or sevDesk. FlowParse exports the converted statement as a DATEV-ready CSV — date, amount, debit/credit indicator, booking text — which the Steuerberater can import without re-keying, and as a plain CSV for any software that reads one.

For QuickBooks or Xero users, the same statement exports as a .QBO bank-feed file or a Xero-ready CSV. Whichever format you pick, the Erläuterung travels with each booking, so a Lastschrift can still be matched to its contract and a card payment to its receipt.

DKB moved to a new Postfach in early 2025. Documents from before the switch are under Archivierte Dokumente, and DKB keeps those available without a time limit. Newer documents follow the deletion-date rule above. If a statement has already been deleted, DKB cannot put it back into the Postfach, but it can send a replacement statement by post while the ten-year legal retention period is still running; you request it through the contact form in the banking with your IBAN (or the last four digits of the card) and the period you need, and DKB charges for it according to its price list.

A replacement on paper converts the same way as a downloaded PDF: photograph or scan it, upload it, and FlowParse reads the text first and then the table. For a German business, where account records are generally kept for ten years, converting each month into your own spreadsheet archive is cheaper than ordering replacements later.

The best input is the statement exactly as DKB filed it: open the Postfach, filter to the account and the year, and download each Kontoauszug as its own PDF. A downloaded PDF carries real text, so FlowParse reads it directly, without OCR, and every digit is the digit DKB printed. Avoid printing the statement and scanning it back in, and avoid screenshots of the banking app — both turn text into pixels and add a step where a 3 can become an 8.

If you are collecting a year for a Steuerberater, download all twelve months in one sitting and upload them together. Keep the original file names; FlowParse writes the source file on every row of a merged workbook, so a name that already says the month makes the result easier to read. A statement that prints across several pages is still one file — upload the whole PDF rather than single pages, so the balance proof can run from the first page's old balance to the last page's new one.

Three things go wrong most often when a DKB Kontoauszug is copied by hand. The first is the sign: an amount in the Haben column pasted as a debit. FlowParse takes the sign from the column the amount sits in, so that mistake cannot happen. The second is the Erläuterung: a Lastschrift's text runs over three or four lines, and pasting it splits one booking into several rows with no amount. FlowParse joins the lines of one booking into one cell.

The third is the page break. A booking whose text starts at the foot of one page and continues at the top of the next is easy to count twice or to lose. Here the balance proof does the work: if the old balance plus the bookings that were read does not land on the new balance, the export is not marked reconciled, and the preview shows exactly where the difference sits. For the card statement, the usual confusion is the cycle — purchases from the 22nd of one month to the 22nd of the next — which is why it is kept as its own sheet rather than folded into the Girokonto month.

Take a freelancer's Girokonto for March, downloaded from the Postfach after the 5th of April. The statement shows an old balance, a handful of Haben bookings — client payments with an invoice number in the Verwendungszweck — and a longer list of Soll bookings: rent by Dauerauftrag, insurance and phone by SEPA-Lastschrift, a few Visa payments, and the transfer that settles the credit card. These figures are an illustration, not a real customer's.

Uploaded to FlowParse, every booking becomes a row with the date, the full Erläuterung and a signed euro amount. The old balance plus the rows lands exactly on the new balance, so the month is marked reconciled. The freelancer exports the DATEV-ready CSV, and the Steuerberater imports it; because each client payment still carries its invoice number and each Lastschrift its mandate reference, matching them to invoices and contracts takes minutes instead of an afternoon. The same file, opened in Excel, gives the freelancer a quick check of income for the Umsatzsteuer-Voranmeldung.