Once your Rabita Bank statement is uploaded, what you get back depends on which export format you actually need next. Upload the statement document; the engine identifies the issuing bank and its layout automatically, so there is no template to configure. The transaction table is extracted and the running balance is verified line by line against the statement's own printed closing figure. A row that does not add up is flagged for review rather than rejecting the whole file.
If a transaction description on your Rabita Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. When the transactions are captured, you map the columns into the exact export format you need next. Choose Excel, CSV or QBO, and decide which columns appear and how they are labelled. The mapping persists for the next statement from the same layout, but you can still adjust it each time; the point is that the data lands where your ledger or tax prep workflow expects it, without manual column surgery after the fact.
If your Rabita Bank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. Transaction descriptions that run long and wrap across multiple lines in the original document are fully captured, not truncated mid-word. The engine recognises multi-line cells and keeps the description intact, which matters when the narration carries the payee, invoice number or reference the reconciliation depends on. For statements that run several pages long, all pages are processed together and the running-balance check continues across page breaks. The closing balance you typed in for verification must still match the very last figure on the final page, and any imbalance anywhere in the sequence is flagged at the row level, so a long file does not hide a small discrepancy.