When a Fibabanka 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. A statement document that runs several pages long is handled as one continuous record. The engine reads every page in order, stitches the transaction table together, and verifies the running balance across the full file. Any row that breaks the chain is flagged; the rest of the data remains intact and ready for review.
Once your Fibabanka statement is uploaded, what you get back depends on which export format you actually need next. Getting the file into the exact export format needed next is straightforward. The engine writes the extracted transaction table into Excel, CSV or QBO, preserving the column structure and detail that were verified during extraction. There is no template to build and no intermediate format to clean up.
Whichever order your Fibabanka 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 happens automatically. The engine identifies and labels every column in the statement document, then places each one into the corresponding field of the chosen output format. A column that carries a date, description, debit, credit or balance lands in the correct slot so the exported file opens ready to work with.