If a transaction description on your ICBC Turkey Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions can run long, stretching across several lines on the page. When a single entry wraps like this, a copy-and-paste workflow often splits it into multiple rows, breaking the table structure. Convert·Into reads the full statement layout and recognises a wrapped description as one logical row. The entire text stays together: no fragments, no orphaned amounts, no extra blank lines. The transaction table lands in the export as the bank printed it, with every field in the correct column.
Once your ICBC Turkey Bank statement is uploaded, what you get back depends on which export format you actually need next. Export formats are not one-size-fits-all. Convert·Into maps each extracted column into a clean, predictable structure and lets you choose the output that fits your workflow: Excel, CSV or QBO. The same statement data lands in the same columns every time. No reformatting, no manual column alignment before you can start working.
If the ICBC Turkey Bank 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. A scanned statement or a photograph of a page is still a statement document: the numbers are there, but they are pixels, not a table. Convert·Into reads them with OCR, extracts the transaction rows and runs the full running-balance check against the statement's own printed closing figure. If a misread digit causes a row to go out of balance, that row is flagged. The rest of the file remains intact and usable, so you review only the exception.