When a Goldman Sachs 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 that runs several pages long creates one persistent annoyance: the column headers appear once on the first page, then vanish. Every subsequent page begins with raw rows of numbers and no column labels. A human reader flips back to page one to confirm which column holds the debit and which holds the credit. Convert·Into reads the full document as one continuous table. The engine identifies the header row on the first page and carries that mapping through every page that follows, so a six-page statement produces one clean transaction register with no orphaned rows and no repeated headers to strip out.
If the running balance on your Goldman Sachs 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. Every statement carries its own closing balance printed as the final figure on the document. Convert·Into verifies that the extracted transactions add up to that exact number before the export runs. The engine sums every credit and debit line, computes the running balance row by row, and compares the result against the printed closing balance. If a misread digit or a skipped row causes a mismatch, the offending line is flagged for review. The rest of the file remains intact and ready for export. You correct the flagged row once, re-verify, and move on, knowing the numbers reconcile to the penny.