Whichever order your KeyBank statement prints its columns in, each one still has to land in the right place once it reaches a spreadsheet. Start by uploading the statement document. The engine identifies the layout automatically, so there is no template to configure. It extracts every transaction row and checks the running balance line by line against the printed closing figure, flagging only the rows that do not add up rather than rejecting the whole file.
When your KeyBank 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. From there, you control where each column lands in the export. Drag a column header onto the field name you need: date to date, description to memo, amount to debit or credit. The mapping is yours to set, not an opinionated default you are forced to accept. If the statement splits debits and credits into two columns, the export preserves that split; if the statement shows a single signed amount column, the sign carries through cleanly. The goal is a file that slots straight into your existing workflow without a second round of cleanup.
Whether you need your KeyBank statement in Excel, CSV or QBO, the underlying extracted table stays the same; only the export step differs. The same mapping logic holds for statements that were scanned or photographed rather than downloaded as a clean file. OCR reads the numbers and text from the image, and the running-balance check catches anything the scan misread: a 3 that optical recognition turned into an 8, a row total that no longer ties to the bank's own closing figure. You review only the flagged lines, not the entire statement.