If the running balance on your Donner & Reuschel statement does not add up row by row, that is exactly the kind of mismatch Convert·Into is built to catch rather than pass through silently. Every line in the transaction table is checked against the statement’s own printed closing balance. The engine works through the running-balance column row by row, flagging any entry that does not add up to the declared figure. If a single line fails the check, it is marked for review rather than rejecting the entire document, so one questionable row never blocks a whole month of clean data.
If the Donner & Reuschel 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. The engine reads scanned and photographed statement documents with the same running-balance verification applied to clean digital files. OCR picks up the figures from the image, and the line-by-line check provides a reliable signal for whether the scan misread any digit. A flagged row lets you correct a single amount instead of re-entering the full statement by hand.
However your Donner & Reuschel statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping organises the extracted transactions to match your export template. Date columns, descriptions, debit and credit amounts are assigned to the fields your accounting software expects, so the layout is consistent across every export. The mapped data can then be saved as an Excel workbook, a CSV file, or a QBO file ready for import.