When your Kent Reliance 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. Upload a scanned or photographed statement the same way you would a digital file. The engine applies OCR to read the image, then extracts the transaction table automatically. Every row’s running balance is checked against the statement’s own printed closing figure; if the image was blurred or a digit was misread, the mismatch is flagged for review. You can correct individual cells rather than redo the whole capture, so a faint 3 mistaken for an 8 does not force a restart.
If a transaction description on your Kent Reliance statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Transaction descriptions that wrap across several lines are reassembled into a single row during extraction. The engine recognises multi-line text blocks by their formatting and grouping, rather than splitting every line break into a separate transaction. The result is one clean row per entry, with the full description, amounts and date kept together, ready for export.
However your Kent Reliance statement lays out its columns, that layout is only useful to you once it is mapped correctly into the export. Column mapping matches the extracted data to the export fields you choose, whether that is the date, description, credit, debit or balance column. The same mapping dialog lets you reorder, rename or omit columns, so the exported file matches your ledger or tool’s expected layout. Export to Excel, CSV or QBO is a single step once the mapping is confirmed.