If a transaction description on your Urbo bankas statement is long enough to wrap across two or three lines, it still needs to land in a single row once converted. Multi-line transaction descriptions are handled without splitting. When a single entry wraps across several rows in the statement document, the engine groups those rows together before extracting the figures. That keeps each transaction whole: the date, amount and narrative stay linked. No manual rejoining is needed, even when a description runs long enough to look like a separate entry at first glance.
Once your Urbo bankas statement is uploaded, what you get back depends on which export format you actually need next. The converted data is mapped into clean columns and delivered in the format you require. Export to Excel, CSV or QBO directly; the mapping step organises every field so the output fits your ledger or import template immediately. You control column order and inclusion, so the file arrives with the right structure for your next workflow. No reformatting is necessary once the file is saved.