If the running balance on your Türk Ekonomi Bankası 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 transaction row extracted by Convert·Into is checked against the closing balance printed on the statement. The running total is verified line by line: if a figure does not add up, that row is flagged for review rather than silently accepted. You receive a reconciliation summary that shows exactly where the breakdown occurred, so you can correct a single misread digit instead of rechecking the entire file.
If the Türk Ekonomi Bankası 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. Statements that were scanned or photographed are read using optical character recognition. Because the same running-balance check applies, any character the scan misreads is caught when the numbers stop reconciling. You can upload a camera photo or a multi-page scan; the engine treats both the same way and flags only the rows that need attention.
If your Türk Ekonomi Bankası statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. A statement that runs several pages is handled as a single continuous document. The engine stitches the pages together, drops repeated headers, and delivers one clean transaction table. You do not need to split the file or convert it in batches: the export contains every row in sequence, with the same verification applied from the first page to the last.