If the running balance on your Union Bank statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. The running balance printed on a statement document is a built-in audit trail: every row either adds up or it does not. Convert·Into reads that column line by line and recomputes it from the individual debit and credit amounts, comparing its own arithmetic against the figure printed beside each transaction. If a row does not balance, that single row is flagged for review rather than rejecting the entire file, so you know exactly where to look and can correct one misread digit instead of rechecking the whole statement.
If a transaction description on your Union Bank 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 run long and wrap across multiple lines are the norm in many statement layouts: a merchant name on one line, a city and reference code on the next, and a booking date tucked beneath. Convert·Into groups those wrapped lines back into a single row automatically when it detects the row boundaries, instead of treating each fragment as a separate transaction and breaking the running total. The result is one clean record per transaction, matching the document as you see it.
However your Union Bank statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Every exported file has to land with the right data in the right column: date in the date field, amount in the amount field, description where your ledger expects it, with no stray punctuation or merged cells. Convert·Into maps the detected columns into a standardised structure and lets you review the mapping before export. If a statement prints separate debit and credit columns, the engine factors them into a single signed amount column for Excel and CSV, preserving the sign convention your accounting software needs; the QBO export applies the same mapping silently so the transactions import directly into the correct register without manual column shuffling.