If a transaction description on your HSBC Turkey 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 reads every line, even when a transaction description runs long and wraps across multiple rows on the page. A human can glance at the printout and see that the second line belongs to the same entry; the engine does the same, reassembling the split text into a single row so the payee, reference or narration is complete before any amount is attached to it. You get a clean table with one transaction per row, no orphaned fragments.
If the running balance on your HSBC Turkey 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. The running balance is then verified line by line against the statement's own printed closing figure, not against an expected total you supply. Each row's arithmetic is checked: the prior balance plus the row's credit or minus its debit must equal the printed balance on the same line. If a single digit was misread, the row is flagged and you are shown exactly where the sum broke, so you can correct that one field and carry on. The rest of the file stays intact; nothing is rejected wholesale.
If the HSBC Turkey statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. Scanned and photographed statements are read with OCR, and the same verification protects you from whatever the image introduces. A smudge that turns a 6 into an 8, a glare that clips the last column, a skew that shifts a number into the wrong line: the running-balance check catches the discrepancy before the figure reaches your ledger. Upload the scan, review the flagged rows, correct anything the light or the lens distorted, then export a reconciled file to Excel, CSV or QBO.