Whichever order your Credito Emiliano statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Every column the engine identifies can be mapped to the field you need in the export. Date, description, debit amount, credit amount and running balance are each assigned to the matching column in your output file. If a statement contains extra columns, for example a transaction code or a branch identifier, those fields appear in the mapping list as well; you decide which ones to keep and which to leave behind. The mapping stays consistent from one statement to the next, so once it is set you can process a batch of files without re-confirming field placements.
If your Credito Emiliano statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statements that run several pages are handled as a single continuous record. The engine reads across page breaks and picks up column headers again only when they actually change, so the transaction table in your export is one unbroken list rather than a separate table per page. The running balance is verified across the full span of the document, from the first transaction on page one to the closing figure printed on the final page.
If the Credito Emiliano 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 extraction begins. The engine locates the transaction table in the image, then extracts rows and verifies them against the printed running balance. If a character is misread and a row no longer adds up, that row is flagged instead of being silently exported, so you can correct the single misread entry without reprocessing the whole statement.