If a transaction description on your MagNet 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 across several lines, the text can bleed into the date or amount columns, making the table impossible to parse by a simple script. The engine reads the full block of text as one record, then aligns every field back to its correct column. Running balances and totals are checked after the alignment, so a wrapped line does not lead to a miscategorised entry or a balance that suddenly drifts.
Once your MagNet Bank statement is uploaded, what you get back depends on which export format you actually need next. Once the statement is mapped and verified, you choose the output that fits your workflow: Excel, CSV, or a QBO file formatted for direct import. Columns are arranged to match the export target, not the source document's original order. The file is ready to drop into your ledger or reconciliation tool without reordering, renaming, or reformatting.
If the MagNet 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. Scanned and photographed statements introduce noise: speckled backgrounds, skewed text, digits that blur together. The engine applies OCR to pull the text, then runs the same running-balance check it uses on a clean electronic file. A row that does not reconcile is flagged individually, so one misread character does not invalidate the whole statement. You can review the flagged row, correct it, and proceed with the rest of the data intact.