If the running balance on your Credit Agricole Group statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Every line total is checked against the statement’s own printed closing figure. The system does not assume the extracted numbers are correct: it compares the calculated running balance at each row to the number printed on the original document. A mismatch flags that row for review without stopping the rest of the conversion, so the file is never rejected wholesale over a single discrepancy.
If a transaction description on your Credit Agricole Group 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 are reassembled before extraction. The engine reads the block as one entry, preserving the full narrative even when a description occupies three or four rows on the page. This prevents a single payment from being split into multiple phantom transactions inside the output table.
Once your Credit Agricole Group statement is uploaded, what you get back depends on which export format you actually need next. The converted data is mapped into the export format you choose. Columns are arranged to match the target layout for Excel, CSV or QBO, with transaction dates, descriptions, amounts and running balances aligned into the correct fields. You set the output format once; the engine handles the rest.