Once your Crédit populaire d'Algérie statement is uploaded, what you get back depends on which export format you actually need next. The export step gives you a choice of formats without extra configuration. Whether you need an Excel workbook for analysis, a CSV file for upload into accounting software, or a QBO file for direct import into QuickBooks, select the format from the export menu and download it. The file contains every transaction from the statement, with columns mapped sensibly and ready to use. Nothing is flattened into a single cell or split across odd delimiters; the structure is a clean table from the first row to the last.
If a transaction description on your Crédit populaire d'Algérie statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across several lines on the original page are reassembled into one cell per row. The engine recognises that a payment reference or narrative continuing onto a second or third line belongs to the transaction above it, not to a new row. The result is a single description cell per entry, with no orphaned text fragments that would throw off filters or lookups downstream. That single-cell guarantee holds even when the wrapped lines include numbers that a simpler parser might mistake for a new transaction.
However your Crédit populaire d'Algérie statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping matches the statement's fields to the export's columns without guesswork. Date, description, debit, credit and balance each land in their own column, and the order is consistent from file to file. You can review the mapping before export and adjust it if your workflow uses a different column arrangement. Once mapped, the same layout repeats for every statement you process, so a format that works for one client or period works for the next without further setup.