If a transaction description on your National Bank of Kuwait 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 wraps, the engine reads it as one logical row, not as several independent entries. It groups the continuation lines with their parent transaction so that the narration stays whole and no phantom rows appear in the output.
Once your National Bank of Kuwait statement is uploaded, what you get back depends on which export format you actually need next. Mapping columns into the final export gives you control over what lands where. The engine identifies the statement’s own headers and assigns them to the fields your downstream tool expects: date, description, debit, credit and running balance. You can review and adjust that mapping before export so the column order and field names match your ledger or import template exactly, which eliminates reformatting after conversion. Once you are satisfied, export the result to Excel, CSV or QBO in a single step.
When a National Bank of Kuwait 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. Multi-page statements are processed in one pass. The engine reads every page continuously, joins the transaction table across page breaks and reconstructs a single running balance that spans the entire document. When the closing figure on the final page is reached, it is verified against the statement’s own printed total; any line that does not add up is flagged for review rather than letting the whole file fail silently.