When your Bank Windhoek 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. A statement document that was scanned or photographed arrives as an image, not as a table. The engine applies OCR to read every character from the page, even when the scan is angled, shadowed or of modest resolution. Each transaction row is rebuilt from the recognised text, and the figures are tested against the statement's own printed closing balance. A 3 misread as an 8 or a comma swallowed by a fold in the paper knocks the running total out of alignment, so the row is flagged at once rather than buried in a clean-looking export. You can review only the rows that need a second look, which keeps a photographed statement just as usable as a digitally issued file.
Whichever order your Bank Windhoek statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping decides where every extracted field lands in the output. The engine presents the recognised columns as they appear on the statement: date, description, debit, credit, balance. You confirm which source column corresponds to which field in Excel, CSV or QBO, and the export respects that mapping on every row. Because the mapping is set once per layout and remembered, a second statement from the same source can skip that step entirely. The export carries exactly the columns your ledger expects, with no extra fields to delete and no gaps where a figure should have been.