If the running balance on your Cater Allen 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 engine reads the statement's own printed closing figure and checks it against every line of the running balance. It does not trust the raw extraction. Each row's balance is verified sequentially; if one row does not add up to the next, that row is flagged for review rather than rejecting the whole file. The check catches both misread digits and missing lines, so you do not discover a mismatch only after export.
Whichever order your Cater Allen statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is handled by the layout detection engine, not by manual templates. Transaction dates land in the date column, descriptions stay whole, and amounts preserve their signs. You can review the alignment before export, but the engine places each field in the correct slot automatically. There is no column to drag, no lookup to configure.
If your Cater Allen 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 a single continuous table. Page breaks, repeated headers and carry-forward balances are recognised and stripped, so the transaction list stays whole from the first line through to the closing balance. The running-balance check runs across the full span, not page by page, which prevents a break in the middle from hiding a mismatch.