Once your BanBajío statement is uploaded, what you get back depends on which export format you actually need next. The engine writes out the transactions in the format your workflow needs. Choose Excel for a standard spreadsheet, CSV for a plain-text import into another tool, or QBO for a direct upload into QuickBooks. Column order and date formatting are standardised, so the exported file lands in a predictable shape every time. There is no extra mapping step; the columns you see on screen are the columns written to the export. All three formats are available for every statement.
If the BanBajío 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. A photographed or scanned statement works the same way as a clean digital file. The engine reads the image with OCR, identifies the transaction table, and extracts every row it finds. The running-balance verification then steps through each line and checks the arithmetic. Any character the scan misread is caught when the balance no longer ties, flagging the row for review instead of silently carrying an error into the export.
If your BanBajío statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Statements that span several pages are handled as one continuous table; you do not need to split the file or process it in parts. The engine follows the columns across page breaks, picks up the running balance where it left off, and outputs a single set of transactions. The verification still runs end to end, using the statement's own printed closing figure, so the full month reconciles in one pass.