Once your United Bulgarian Bank statement is uploaded, what you get back depends on which export format you actually need next. The export delivers a clean workbook, a flat CSV or a QBO file matched to the target ledger’s column map. Transaction rows land in the order they appear on the statement, with dates kept as proper date types and amounts as numbers rather than text, so no further cleaning pass is needed before import.
If the United Bulgarian Bank statement you have is a scanned image or a phone photo instead of an exported file, that alone does not stop Convert·Into from reading the transaction table off it. OCR reads scanned pages and phone photos, pulling transaction rows from the image with the same table engine used for digital files. A misread digit in the amount or balance column breaks the running-balance check, which is the safeguard that flags the affected row instead of letting an error through unseen.
Should a description on your United Bulgarian Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When a transaction description wraps, the engine joins the continuation lines back to the same row before building the export. The running balance is evaluated only after that reassembly, so a split line that would otherwise look like an orphaned credit or debit is caught and kept whole.