If the running balance on your Lloyds Bank 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 converter verifies the printed closing balance against the running total it computes row by row. Any line where the arithmetic does not add up is flagged, so you catch a misread digit or a shifted decimal before it reaches the ledger. The statement is never rejected wholesale; only the broken row needs attention.
If a transaction description on your Lloyds Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions wrap across multiple lines, the extraction engine treats them as a single record rather than splitting them into phantom entries. It recognises that the narrative text belongs to the transaction above it and merges the content into one clean row, so you do not open the export to find a description cut in half.
If your Lloyds Bank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Multi-page statements are read as one continuous table; page breaks, repeated headers and carry-forward totals are stripped automatically. Columns are mapped into a consistent set of fields, and you download the full dataset as a single Excel workbook, a CSV file or a QBO file ready for import. No rows are lost at the boundary between pages, and the same running-balance check spans the entire statement.