When your Union Bank of Nigeria statement arrives as a scan or a photo of the page rather than a clean export, the numbers on it are just pixels until they are extracted. Even a scanned or photographed statement is not a dead end. The engine reads the images with OCR, line by line, then verifies the extracted running balance against the balance printed on the statement itself. A 3 misread as an 8 or a smudged decimal point breaks that check, so the row is flagged instantly. You review only the few lines that need attention, not the entire document. The original image stays visible beside the extracted data, which makes it quick to confirm the correct figure and move on.
If a transaction description on your Union Bank of Nigeria statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions in statement documents often wrap across two or three lines, especially when they include reference codes or merchant details. The layout detector recognises a continuation line and stitches the text back into a single record rather than treating every line break as a new row. What you see in the preview is a clean table: one row per transaction, no fragmented descriptions, no manual merging required before export.
Once your Union Bank of Nigeria statement is uploaded, what you get back depends on which export format you actually need next. Once the statement is verified, you choose the export format that fits your workflow. The columns map cleanly into Excel for pivot analysis, CSV for system imports, or QBO for direct reconciliation. There is no template to build and no macro to maintain; the engine repeats the same column mapping for every statement document from the same issuer, so subsequent conversions take only the time required to upload the file and confirm the balance.