If a transaction description on your mBank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across several lines in a statement document can break a basic extraction routine: one purchase may be read as two unrelated rows, and the detail that follows the wrapped line can end up misaligned in the wrong column. Convert·Into reads the full multi-line block as one record and reassembles it before the transaction table is populated, so a long merchant name or reference that spans three lines on the page still occupies one row in the output.
Once your mBank statement is uploaded, what you get back depends on which export format you actually need next. The export engine maps each column into the format needed next, whether that is Excel, CSV or QBO. A bookkeeper can reorder columns, rename headers and drop irrelevant fields without touching the source data, then save a reusable profile so every statement from the same issuer lands in exactly the right shape for the general ledger or tax-prep software that follows.