When a Rietumu Banka 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 document runs several pages, the engine treats it as one continuous table, not as disconnected sections. It threads the transaction rows together and verifies the running balance from the first line of page one through the closing figure on the final page. A break mid-transaction or a page footer inserted between rows does not split what belongs together: the extraction holds the structure intact across page boundaries, exactly as it appears in the source.
When your Rietumu Banka statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. If the statement was scanned or photographed rather than exported as a clean file, the engine applies optical character recognition to pull the numbers and text from the image. A grainy scan, a crooked photo, or a low-resolution shot can cause a digit to misread, the same way a human eye might mistake a 6 for an 8 at a glance. The line-by-line balance check catches those misreads: every row that does not add up is flagged, so a single scan error does not taint the whole export.
Whichever order your Rietumu Banka statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Mapping each column into the right place in the export means lining up the date, the description, the amount, and any reference field with the columns your ledger or package expects. The engine identifies the transaction table's structure automatically, so there is no template to configure. You confirm the mapping once; every statement that shares that layout follows the same pattern, and the output lands in Excel, CSV, or QBO with the columns in the order you chose.