Xero is retiring Hubdoc on May 8, 2026.

1. Open the Xero Hubdoc app (in Xero, go to Accounting → Hubdoc).
2. For each organisation, export the document list as CSV (Hubdoc → Settings → Export). This gives you a list of filenames, dates, and the supplier name you mapped.
3. Download the PDFs themselves via Xero Files (the new storage). One folder per client is the cleanest layout.
4. If you have any Hubdoc-only rules or supplier mappings you care about, screenshot them now. The replacement tool (ProofRows or otherwise) will not inherit them.

1. Sign in to ProofRows and create one client workspace per former Hubdoc organisation. The free trial gives you 150 pages over 14 days — enough for a real catch-up of one client.
2. Match the client name and (if you have it) industry to the Hubdoc record. The contact field is optional; leave it blank if you’re bringing the books in cold.
3. Set the retention window on each client. The default is 30 days; if your client’s data-retention policy is shorter, set it explicitly. The PDF auto-purges after that, but the transactions and the export-log audit trail stay.

1. Open the client workspace and use the drag-and-drop uploader. You can drop a whole folder at once; ProofRows tags every PDF to the client and queues them as a batch.
2. The first statement opens in the review screen as soon as the worker finishes. If you have a long batch, the rest catch up in the background.
3. If a PDF fails preflight (scanned, encrypted, oversized), the row turns red with a reason. Drag the original back in once the cause is fixed.

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 Hubdoc-style cleanup, 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 — pick the one that matches the client’s tool:

• Xero-ready CSV — for clients staying on Xero. See the Xero import guide.
• QuickBooks-ready CSV — for clients who’ve already moved to 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.

Every export is logged with format, options, and row count. That audit row is your record that the cleanup was reviewed and shipped.

• Per-row confidence. Hubdoc never told you which rows it was guessing on. ProofRows flags every low-confidence row before export.
• Side-by-side review. The source PDF and the extracted table are visible at the same time. You see the line that produced each row.
• Balance check. Every statement reconciles to the printed balance, or the export button stays disabled. Hubdoc didn’t catch that class of error.
• Audit log per export. Format, row count, options, and timestamp. A reviewer can defend every number.

• No Hubdoc OAuth import. You re-upload the PDFs. Hubdoc doesn’t expose a public export API, and we’d rather give you a clean working surface than a half-broken connector.
• No automatic Xero push yet. Direct API push is on the roadmap; for now you export a file and upload it through Xero’s bank import wizard. Five clicks.
• No scanned-PDF OCR. Text-based statements extract cleanly. Scans are flagged for manual review. OCR is on the post-beta roadmap.

Email our team with the subject “Hubdoc 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.