When a Daycoval statement you need to convert spans more than one page, Convert·Into merges every page into a single transaction table rather than treating each page as its own file. A statement document that runs several pages long does not need to be split or processed in sections. Upload the whole file at once. The engine reads across page breaks without interruption, treating the entire document as a single transaction table. Line items that begin on one page and finish on the next are stitched together automatically. The extracted data arrives as one continuous list, ready for export. No manual assembly is required, regardless of how many pages the original statement spans.
If the running balance on your Daycoval 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 against the statement's own printed closing figure. Every row is checked, line by line, from the opening balance through to the end. If a single transaction does not add up, only that row is flagged for review. The rest of the file remains intact and exportable. You keep the data that is correct, fix the one line that is not, and move forward, instead of having the whole conversion blocked.
If the Daycoval 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. A scanned or photographed statement is read with optical character recognition. The same running-balance check that applies to clean digital files also applies here. If the scan misreads a digit, the arithmetic will not reconcile, and that row is flagged. You can correct the misread value against the original image and continue. The export options remain the same: Excel, CSV, or QBO, from any source format.