Once your Kotak Mahindra Bank statement is uploaded, what you get back depends on which export format you actually need next. Upload a statement document, and the service maps the transaction table into the export format you select. The output keeps every column aligned: date in one column, description in the next, amounts each in their own fields. If your workflow requires Excel for pivot tables and further analysis, CSV for import into ERP tools, or QBO for direct ledger posting, the same extraction feeds all three. You choose the format at the point of download; no intermediate transformation step is needed.
If the Kotak Mahindra Bank 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. Scanned or photographed statements are read with optical character recognition before the extraction runs. The image is treated as a bank statement, not as a general document, so the engine expects repeating rows of dates, descriptions and amounts. After the text is lifted, the running balance is checked against the closing figure printed on the statement. If a smudge or low contrast misreads a digit, the mismatch is flagged on the affected row rather than forcing you to restart the whole upload.
Should a description on your Kotak Mahindra Bank statement break across multiple lines of the printed page, that line break is not the same thing as a new transaction. When a transaction description sprawls over two or three lines, the row is stitched back together before mapping begins. The layout engine looks for the pattern of a date, a multi-line block of text, and the paired debit and credit amounts that follow it. Those blocks are joined into a single description cell in the final table. The result is one clean row per transaction, ready to drop into your spreadsheet or accounting package without manual splicing.