Whichever order your Bank im Bistum Essen statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The engine maps each column into the right place in the export for you. When a statement document opens, the software recognises the columns it contains: date, description, money in, money out, and the running balance. It does not force you to drag fields around or pair labels by hand. Every column the statement displays is assigned to a matching field in the output file. If the statement lists the amounts in a single column with a debit or credit marker, the engine splits them into two columns for you. This mapping step runs silently, but you can review the result before you download anything: the preview shows exactly which source column landed in which export column, so you can spot a mismatch before it reaches your ledger. The mapping logic is designed to handle the quirks of the document in front of you without manual setup.
Once your Bank im Bistum Essen statement is uploaded, what you get back depends on which export format you actually need next. Getting the file into the exact format needed next is straightforward. Choose Excel, CSV or QBO from the export options; the mapped data is written into the chosen format in one step. The export carries over every transaction row that passed the running-balance check, and any row that was flagged for review stays visible in the file with a note so you can resolve it in your accounting software rather than hunt for a missing entry later. The download is ready as soon as the conversion finishes, and every export uses the same column layout every time: the same ordering, the same headers, the same number formatting. That consistency matters when you are importing statements from multiple issuers into a single ledger or repeating the workflow each month.