Once your Caixa statement is uploaded, what you get back depends on which export format you actually need next. When the extraction is complete, choose exactly the format your downstream system expects. Export to Excel for manual review and adjustment, or select CSV for a lightweight, universal interchange format that loads into almost any spreadsheet or database tool. If the ledger is bound for QuickBooks, select QBO export; the file arrives with columns already mapped so that dates, descriptions, debits, credits and the running balance land in the fields QuickBooks expects without further rearrangement.
If a transaction description on your Caixa statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Some transactions carry descriptions that cross several printed lines on the page: a payee name on one line, a reference number on the next and a narrative detail on the line after that. The engine groups these multi-line entries into a single transaction row, treating the whole block as one description field rather than splitting it into fragmented, unrelated records. That grouping prevents the scenario where a partial description drifts into an adjacent column and breaks the layout further downstream.
If your Caixa statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. A statement that runs to five or ten pages is no different to the engine than one that fits on a single sheet. Every page is read sequentially, the running balance is verified across page breaks and the full transaction history is assembled into one continuous table. There is no need to split the file yourself, convert pages individually and stitch them back together later, or worry that a balance carried forward will be misread as a new opening figure.