If your bookkeeper just disappeared.

1. Go to each of your banks’ online portals and download the last 3–12 months of statements as PDF. Most banks expose a “Documents” or “Statements” tab in the online-banking UI.
2. If you have any old files exported from Bench/Botkeeper (CSVs, PDFs, monthly summaries), download those too. They’re useful for the next bookkeeper’s context, even if ProofRows only needs the PDFs.
3. Sort the PDFs into one folder per bank account. You don’t need to rename them — ProofRows uses the bank name and account mask from the PDF itself.

1. Sign in to ProofRows and create one client workspace per former client (or one workspace for your own books, if you’re the business owner). The free trial gives you 150 pages over 14 days.
2. Match the client name and (if you have it) industry to whatever you had in Bench/Botkeeper. The contact field is optional.
3. Set the retention window. The default is 30 days; if your data-retention policy is shorter (common for healthcare or financial-services-adjacent businesses), set it explicitly. The PDF auto-purges after that, but the transactions and the export-log audit trail stay forever.

1. Open the client workspace and drag the folder of PDFs into the uploader. The first statement opens in the review screen as soon as the worker finishes; the rest catch up in the background.
2. If a PDF fails preflight (encrypted or oversized), the row turns red with a reason. Drag the original back in once the cause is fixed.
3. PDFs that are images of statements (e.g. a paper statement you scanned yourself) are read with built-in OCR. Rough scans get lower per-row confidence and land in the review queue rather than slipping through.

1. The review screen shows the source PDF on one side, the extracted transactions on the other. Click any row, the source line highlights in the PDF.
2. Every row has a confidence score. Anything under 90% is flagged; under 70% is a hard “review” tag. The validation page lists every flag and how to fix it.
3. The balance check at the bottom of the validation page tells you whether beginning + Σ debits + Σ credits = ending. To the cent. If it’s off, the page says so before you ever export.
4. For a Bench-style catch-up, you’ll spend most of your time here, on the validation page, accepting the duplicates and low-confidence rows. That’s the work — ProofRows doesn’t pretend to do it for you.

The export modal now shows where each format drops:

• QuickBooks-ready CSV — for clients staying on QuickBooks Online. See the QBO import guide.
• .qbo (OFX) file — for clients on QuickBooks Desktop who need a Web Connect import. One click in the bank feeds center.
• Xero-ready CSV — for clients staying on Xero. See the Xero import guide.
• XLSX workbook — for the human-in-the-loop case where the next bookkeeper wants to see the math in Excel first.

Every export is logged with format, options, and row count. Hand the audit-log row to your next bookkeeper as proof of the cleanup.

• Review-first, never autonomous. Both Botkeeper and Bench pitched “fully automated” AI bookkeeping. The category is bruised — buyers don’t trust it. ProofRows shows you every row, every confidence score, and the source line. The bookkeeper decides when a statement is ready.
• No proprietary lock-in. Bench customers lost access to their own data when the platform shut down. ProofRows exports the standard file formats your accountant already accepts. The CSV is yours.
• Math has to add up. Every statement reconciles to the printed balance, or the export button stays disabled. The Botkeeper collapse was partly driven by invisible math errors (wrong-signed transactions, double-counted invoices). We make those impossible to ship.

• No QBO or Xero OAuth import. You re-upload the PDFs. We’d rather give you a clean working surface than a half-broken connector.
• No automatic QBO push yet. Direct API push is on the roadmap. Today, the export file is the wire — five clicks in QBO or Xero.
• Scans go through review. Built-in OCR reads scanned statements; rough scans get lower per-row confidence and are flagged before export.

Email our team with the subject “Bench migration” and a rough count of clients and statements. We’ll extend your trial and run a one-time discount on the first three months of the Firm plan.