When an OTP Bank statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. When a statement continues from one page to the next, the table can split mid-row or leave a running balance dangling. Convert·Into treats the whole document as a single continuous ledger, joins page breaks back into complete rows, and confirms that the printed closing figure on the final page still ties out. A break across pages is treated as a layout artefact, not a data boundary, so no transaction is cut in half or double-counted in the export.
Once your OTP Bank statement is uploaded, what you get back depends on which export format you actually need next. The export step maps the statement’s native columns into the format you actually need next, whether that is Excel, CSV or QBO. The transaction table is preserved with its original structure: separate columns for date, description, debit, credit and running balance, each one populated from the matching field in the source. Because the mapping is deterministic and column-aware rather than a free-text scrape, the same export profile produces the same column alignment every time you run it. If two statements from the same issuer ever shift a column heading by a character, the engine still places the figures in the right field, so your import into QuickBooks Online lands with debits against debits and credits against credits.
If a transaction description on your OTP Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Long transaction descriptions that wrap across several lines inside a single row are one of the commonest causes of broken conversions, because a naive parser reads each line as a separate record and scatters dollar amounts into the wrong cells. Convert·Into reads a multi-line description as a single logical field, so the amount, date and balance stay locked to their parent row. The running-balance check catches any case where a wrapped line has been misread as a split row, flags that row for review, and leaves the rest of the statement intact rather than rejecting the whole file.