Whichever order your Saham Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. The export mapping step organises each column from the statement into the format your accounting tool expects. The extracted date, description, debit, credit and balance columns are aligned automatically, so a payment amount lands in the debit slot and a deposit in the credit slot every time. If a column carries an internal code or a reference number you prefer to suppress, you can exclude it and the export respects that choice without reordering the other columns.
If your Saham Bank statement runs to several pages, uploading it starts the same layout detection Convert·Into applies to any statement document, page by page. When a statement spans several pages, the engine processes every sheet as one continuous record, not as separate documents. Headers and footers that repeat on each page are recognised and discarded, so the transaction table stitches together without duplicate header rows or blank gaps where a page break fell. The running-balance check carries across the page boundary uninterrupted, verifying the closing figure the bank printed at the end of the final page.
If a transaction description on your Saham Bank statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across multiple lines in the statement are collapsed into a single cell per row. The engine identifies where a description continues and joins those fragments, so a single transaction is never split into two partial entries. This keeps the transaction count accurate and the export clean, even when a narration line runs long enough to fill several lines in the original document.