If the running balance on your Bank of India 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. The running balance is verified line by line against the statement’s own printed closing figure. The engine reads the deposit and withdrawal columns and recomputes the balance after every transaction, comparing the result to what the statement shows for that row. When a mismatch appears, that specific row is flagged for review rather than the whole file being rejected. A flagged row commonly points to a misread digit caused by a broken character or a light watermark cutting through a number. The check acts as a safety net, confirming that what was extracted matches the arithmetic the issuing bank already performed.
If the Bank of India 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. If a statement document was scanned or photographed, the engine reads it with OCR and treats the result like any other file. Smudges, skewed pages and uneven lighting can produce misreads, but the running-balance check catches them when they break the arithmetic. A column that is faded into the paper background might read as an empty cell, and the verification flags it so the figure can be corrected before export.
However your Bank of India statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Each column is mapped into the right place in the export layout: date, description, debit, credit, balance, and any additional fields the destination format expects. The mapping is applied automatically, drawing on the layout identification that happened at upload, so there is no template to build or column header to pair by hand. The same mapping logic feeds every supported output. Whether the export goes to Excel, CSV or QBO, the same verified transaction data lands in the correct fields.