If a transaction description on your L-Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Upload a statement document; the engine identifies its layout automatically and begins extracting the transaction table. When descriptions are long enough to spill across multiple lines, each block of wrapped text is reassembled into a single row before any column mapping takes place. The process preserves the original description text in full, so nothing is lost: a multi-line narrative about a transfer or a fee lands in one cell, not scattered across several. The extraction runs the same way regardless of how many rows a single transaction originally occupied in the printed layout.
If the running balance on your L-Bank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Every statement is verified against its own printed closing balance. The engine checks the running balance column line by line, starting from the opening figure and stepping through each transaction, and compares the computed final balance against the closing figure printed on the statement document. If a single row does not add up, that row is flagged for review; the rest of the file stays intact. You review only the flagged row, fix it, and move on. There is no mass rejection and no manual recheck of the entire statement.
Whether you need your L-Bank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. Export the verified data to Excel, CSV or QBO in one step. Column mapping is handled during the extraction, and the output matches the structure you need for your next process.