If a transaction description on your Banco Safra statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When transaction descriptions run long and wrap across multiple lines, the engine recognises the continuation and reassembles the text into a single cell. Inline line breaks are preserved, so multi-part references such as payment identifiers stay intact. If a wrapped line is mistakenly split into separate rows, the reconstructed running balance flags the irregularity for review.
When your Banco Safra 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. Scanned and photographed statement documents are processed with OCR, and the same row-by-row verification applies as for any other file. The extraction engine checks each line’s calculated running balance against the figure printed on the original page; any character that was misread is exposed at the point where the numbers stop adding up. When the balance verifies cleanly, the transaction table is ready to map to your export layout. Columns can be reordered, renamed or omitted, and the result is delivered as a single-sheet Excel file, a CSV or a QBO file that mirrors the ledger structure you expect.