Once your Bank of Hawaii statement is uploaded, what you get back depends on which export format you actually need next. The statement document exports to the format that fits the next step in your workflow. Choose Excel when you need one clean table for filtering or pivot analysis. Export to CSV if the data is headed into another accounting tool that expects a plain, universally readable file. For import into QuickBooks Online, select the QBO format and the converted file lands in a structure the general ledger recognises, with no extra mapping pass required. The raw numbers are preserved exactly as they appear on the page, so the debit and credit columns retain their original sign and precision.
Whichever order your Bank of Hawaii statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. A long transaction description that wraps onto a second printed line can fool a simple extractor into splitting it into two phantom rows. The engine reads the statement layout as a whole, not line by line in isolation, and recognises when a text block belongs to the record above it. The running balance check then confirms that every amount row lands only once; a phantom row would immediately break the arithmetic and be flagged for correction before any data reaches your export.
Should a description on your Bank of Hawaii statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. Column mapping is applied during the conversion itself, so the output layout matches your working file. The engine identifies the statement columns automatically and presents them for review after extraction: date, description, debit, credit, balance, and any additional reference fields the statement includes. You confirm the mapping once, and the converter places every value into the correct column in the export, removing the need to rearrange columns or re-sort rows afterwards.