Whichever order your Albaraka Türk Participation Bank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Column mapping lets you align the extracted data with your existing workflows. Every field the engine identifies is presented as a source column; you choose which to keep and where each one should land in the output file. Rename headings, reorder columns, and hide anything you do not need before the export is written. The mapping configuration is remembered for future statements from the same layout, so the next file follows the same structure without further setup. When you export to Excel, CSV or QBO, only the columns you have mapped appear, in the order you specified.
When your Albaraka Türk Participation Bank 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 is handled the same way as a digitally generated file. The engine reads the image with OCR, extracts the transaction table, and applies the same running-balance check it uses on every statement. Any character the scan misread that causes a line to fall out of balance is flagged for review rather than silently accepted. You can correct the flagged figure directly before the file moves to column mapping and export, so a paper-origin document still produces a verified, structured record.