If a transaction description on your Arab Tunisian Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description runs long and wraps across multiple lines inside the statement table, generic converters often split that single row into several, leaving you with orphaned amount cells and a running balance that no longer adds up. Convert·Into reads the table structure the same way a person would: each new transaction record begins on its own distinct row, and continuation lines are gathered back into the description cell where they belong. The engine does not guess where one entry ends and the next begins; it follows the column boundaries and the printed line ordering that the statement itself defines, so a six-line merchant name or a long payment reference stays in one row all the way through to the export.
When your Arab Tunisian Bank statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. Scanned and photographed statements introduce a different problem: the numbers are pixels, not characters, and any misread digit can silently change a transaction amount or break the closing balance. Convert·Into applies optical character recognition to the image, then runs the same line-by-line balance check it would run on a born-digital file. If a 3 was read as an 8 or a decimal point was missed, the maths will flag the row, and the row is presented for review rather than quietly accepted. This lets you correct a single reading error while trusting that every other line, and the final balance, survived the scan intact.