Whichever order your Bank Degroof Petercam statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The engine identifies every column in the transaction table: the date, the narrative description, the amount in, the amount out, and the running balance. You do not need to label fields or draw boxes around the data. Each column is then mapped into the correct slot in the export template, and you can adjust that mapping once before you export. If a statement splits credits and debits into separate columns, the engine recognises that convention and merges them into a single signed amount column in the output, so your ledgers stay clean. You review the mapping, confirm the column destinations, and the file is ready.
If your Bank Degroof Petercam statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. When a statement spans several pages, the engine reads the document as one continuous table. Page headers, footers, and repeated column titles are identified and stripped out automatically, so the transaction list remains unbroken. The running-balance check continues across the page boundaries; a discrepancy on page three is caught with the same rigour as one on page one. The full statement is treated as a single source of truth, not as separate fragments.
If a transaction description on your Bank Degroof Petercam statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across two or three lines inside a table cell are reconstructed into a single text field. The engine preserves the full narrative, including any reference codes that span the line break, and places it cleanly into one export column. No text is concatenated with the next row's data, and the amounts stay in their own columns. The export matches the original statement layout, just in a usable spreadsheet format.