If a transaction description on your Bank Mandiri 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 can split what is meant to be a single entry into several rows. The engine identifies the start of each transaction by a date stamp or a running balance figure rather than by a hard row break. When a description continues onto a second line, it is joined back into the same row so that every narration stays with its correct amount, date and reference. That way a long payee name, a structured reference or a multi-line free-text note arrives in the export as one continuous field, not as three broken fragments scattered down the column.
Once your Bank Mandiri statement is uploaded, what you get back depends on which export format you actually need next. The export step converts the verified table into whichever format your ledger or tax-filing software requires next. Choose Excel for a plain spreadsheet, CSV for direct import into a bookkeeping package, or QBO for QuickBooks Online. The file renders the same table you reviewed on screen, with every column present and no hidden rows.
Whichever order your Bank Mandiri statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping puts each data field into the slot your downstream system expects. The date column lands on the date header, the debit and credit amounts split into two columns or stay in one, and the running balance ends up where a reconciliation check can pick it up immediately. If your import template needs the narrative in a column labelled Memo rather than Description, that swap happens before the file downloads.