If a transaction description on your Nubank 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 runs long and wraps across multiple lines, a naive parser treats every new line as if it were a new row. That splits a single purchase or payment into fragments that must be reassembled by hand before the data is usable. Convert·Into reads each transaction as one complete record. It follows the column structure of the statement document, not the line breaks on the page, so a wrapped description stays attached to its date, amount and running balance in a single row. No column is skipped because a line happened to wrap; the extracted table lands in your export exactly as the statement displays it, with every multi-line entry intact and in the correct cell.
If your Nubank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Long statement runs add a second risk: a running balance that drifts across pages can hide a missing row. Convert·Into treats a multi-page file as one continuous ledger. It extracts all pages into a single transaction table and verifies the running balance against the printed closing figure on the final page. A discrepancy anywhere in the chain, even one buried ten pages in, is flagged at the affected row rather than silently accepted. The full list of transactions exports as one sheet, keeping the audit trail whole from the first page to the last.