If a transaction description on your Quintet Private Bank 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, the true record is not a single row that happens to split, but two rows that belong together. The engine reads the statement grid structurally instead of line by line. It recognises that the currency amount fills only one cell, that the joint second row carries the rest of the description, and that those two rows must be merged into one complete record before any export happens. The result in the converted table is a single transaction with the full description intact, ready for categorisation.
Once your Quintet Private Bank statement is uploaded, what you get back depends on which export format you actually need next. The export step is not a single one-size option. After the statement table is extracted and verified, you map the columns you need into the output format your next tool expects. Choose Excel if you are cleaning or reviewing in a spreadsheet, CSV when a plain-text data feed is what your import requires, or QBO when the file is heading straight into QuickBooks. The mapping stage lets you line up the statement's date, description and amount columns with the target's own field names, so the file that leaves Convert·Into fits your workflow without further reshaping.
If the Quintet Private Bank statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. A photographed or scanned statement arrives as an image of paper, not a machine-readable file. The engine runs OCR to recover the transaction grid from that image, then applies the same structural checks it uses on born-digital files. Every row is tested against the statement's own printed closing balance. If a smudged digit or a lighting artefact causes a misread, the running-balance check flags that row for a second look. The rest of the statement is left intact, so you review only the one anomaly instead of rekeying the whole month.