Once your International Bank in Luxembourg statement is uploaded, what you get back depends on which export format you actually need next. Upload a statement document. The engine detects the issuing bank and its layout automatically; there is no template to configure, no field to map before the file even opens. The transaction table is extracted in full and the running balance is verified line by line against the statement's own printed closing figure. A row whose arithmetic does not add up is flagged for your review; the rest of the conversion proceeds.
Whichever order your International Bank in Luxembourg statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Each column in the extracted transaction table is mapped into the export in the right order and with the right data type. Date columns stay in the original format or are normalised to your preference, amounts keep their sign and decimal precision, and any transaction codes or reference numbers are preserved as text so they import cleanly without leading zeros dropped or long identifiers rounded. If the statement groups credits and debits into separate columns, they are split into a single signed amount column on export; if the statement already carries a signed amount, that structure is kept intact.
Should a description on your International Bank in Luxembourg statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When a transaction description runs long and wraps across multiple lines, the engine reads the full text as one record instead of slicing it into phantom rows. Line breaks inside a single transaction are collapsed into a single field in the export, so a multi-line merchant name or payment reference ends up in the right cell with nothing truncated or spilt into the row below. This keeps every transaction whole and prevents the kind of short-row artifact that would otherwise break a reconciliation.