If a transaction description on your Bank of Greenland 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, it often spills onto a second or even third line in the statement. The engine reads these wrapped lines as one continuous record, not as separate rows. It recognises where the description ends and the next data column begins, so the amount and date stay with their proper entry. Every multi-line row rebuilds into a single, clean transaction in the output file; nothing gets orphaned.
If your Bank of Greenland 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 to several pages introduces its own risk: a page break can split a transaction in half, separating the description from the amount or cutting a running balance mid-column. The tool reassembles rows that span page boundaries, treating the document as one continuous ledger. The same line-by-line balance check that runs on a one-page statement applies here too, across every page break, so the final closing figure is verified against what the document itself prints.
If the Bank of Greenland 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 add a layer of uncertainty because a smudge, fold or shadow can turn a digit into something it is not. The engine uses OCR to lift the text and numbers from the image, then runs the same balance verification it applies to a clean digital file. If a misread digit breaks the running balance, that row is flagged for review rather than silently accepted. You can correct the contested figure and proceed, with the rest of the statement already mapped and ready for export.