If a transaction description on your Banco de Chile statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When a transaction description wraps across multiple lines, the extraction engine reads the full text block rather than cutting it off at a line break. The layout is analysed row by row, and multiline entries are reassembled into a single transaction so no detail is lost. The reconstructed description keeps the original wording and formatting, and the running-balance check confirms the figures still add up after the merge.
When your Banco de Chile statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. When a statement document has been scanned or photographed, optical character recognition is applied to convert the image into machine-readable text. The engine then identifies the table structure within the recognised text, extracts the transaction rows, and verifies the running balance against the printed closing figure. A row that fails the check is flagged for review, so a single misread digit does not invalidate the rest of the file.
Whichever order your Banco de Chile statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping is handled automatically after extraction. The engine identifies the date, description, debit, credit and balance fields and places each one into the correct column for the chosen export format. You can review the mapping before export, and the same column layout is preserved whether you save the file as Excel, CSV or QBO.