Once your Bpifrance statement is uploaded, what you get back depends on which export format you actually need next. Once the transaction table has been extracted and verified, the export step maps every column into the format the next tool expects. Choose Excel for a clean workbook with date, description, debit, credit and balance columns already separated. Choose CSV when a bare data exchange format is required, with all fields consistently quoted and delimited so nothing shifts on import. Choose QBO to send the data straight into QuickBooks Online, with the transaction descriptions, amounts and dates aligned to the ledger fields that reconciliation depends on. The export preserves the column ordering and data types from the statement, so there is no re-sorting or reformatting to perform after the download completes.
If a transaction description on your Bpifrance statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Statements that carry long transaction descriptions often wrap the text across two or more lines inside the original document, which can split a single entry into what looks like multiple rows during extraction. The engine recognises these continuation lines and re-joins them into one coherent record, keeping the full merchant name, reference number and any terminal or location details together. When a description spans more lines than the layout detection expects, the running-balance check on the following row catches any misalignment and flags it, so a wrapped line is never silently trimmed or dropped from the export.