Whichever order your Banque cantonale vaudoise statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The columns the engine extracts are mapped to the fields in the export automatically. Transaction date, description, debit, credit and running balance each land in the column an accountant expects to see, so there is no manual dragging or renaming. The mapped layout is consistent across every file from the same issuer, which means a statement you convert today will organise its columns the same way as one you convert next month.
If your Banque cantonale vaudoise statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Long statements that run across several pages are handled as a single continuous table. The engine joins the pages together, deduplicates any repeated header rows and verifies the running balance across the break. A closing figure on page three that does not flow into the opening figure on page four is flagged, so a missing page or a misread carry-forward never passes unnoticed.
If the Banque cantonale vaudoise 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 or photographed statements are read with OCR before the same checks apply. The engine identifies the numbers, dates and text blocks in the image, rebuilds the transaction table and then verifies every row against the printed running balance. A smudge that turns a 5 into a 6 will break the arithmetic, and that row is surfaced for review while the rest of the file remains intact and ready for export.