When a Zagrebačka 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. Statement documents that run several pages long present a particular challenge for manual conversion, where copying and pasting risks missing rows or introducing duplicates at every page break. The engine reads multi-page statements as a single continuous table, stitching the transaction rows together so the running balance is verified across page boundaries without interruption. If a page has a subtotal or carried-forward line, the reconciliation logic accounts for it automatically, confirming that the closing figure on the final page matches the statement’s own printed balance. This keeps the full account history intact in one file, with no need to split, merge, or manually align separate sheets before starting.
However your Zagrebačka banka statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping is automatic. The engine identifies the date, description, debit, credit, and balance columns by their content and position, then places each one into the correct field in the export layout. You can review the mapping before download and adjust it if your workflow calls for a different column order, but rekeying values or manually aligning headers is never required. The export arrives with columns in a consistent, predictable arrangement that is ready for import into your accounting package.
If a transaction description on your Zagrebačka banka 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 in a statement document are often the source of split rows and scrambled figures when pasted into a spreadsheet. The engine reads multi-line descriptions as a single transaction record, keeping the narrative intact while the associated amounts stay in their correct debit or credit column. This prevents the common failure where a wrapped line is mistaken for a new row, preserving the accuracy of the extracted ledger without manual cleanup.