Re-entering Missing Transactions After a QuickBooks Repair and Condense

When Verify/Rebuild or structural repair deletes transactions, this playbook walks through identifying the gaps, reconstructing them, and reconciling against your last clean trial balance.

When a QuickBooks Desktop company file suffers structural damage, the repair process itself can remove transactions that were causing target chaining errors or list corruption. The result is a file that opens cleanly and passes Verify, but is missing bills, invoices, payments, or journal entries that belong in the period. This playbook covers how to identify what was deleted, reconstruct it from backups and paper records, and confirm the rebuilt file ties to a known-good trial balance.

Phase 1: Establish the Baseline Before You Touch the Repaired File

Before re-entering anything, isolate the repaired file and create a read-only copy. Run a standard trial balance and a general ledger detail report for the full fiscal year in both the repaired file and the most recent pre-damage backup. Export both to Excel and diff them by account and by transaction date range. This tells you exactly how many transactions are missing and which accounts are affected. Do not skip this step — without a baseline comparison, you cannot confirm later that the file is whole.

Phase 2: Identify Every Missing Transaction

Our engineers typically see two categories of loss after a repair. The first is transactions that the repair utility explicitly deleted because they were structurally damaged. The second is transactions that vanished silently during Rebuild when the utility encountered a broken link chain and dropped the record without logging it.

To catch both, generate a Transaction List by Date for the affected period in the repaired file and in the backup. Sort by date and transaction type, then compare the two lists row by row in Excel. Flag every transaction ID present in the backup but absent from the repaired file. Record the transaction type, date, amount, accounts affected, customer or vendor name, and any memo text for each gap.

Phase 3: Gather Source Documents for Each Gap

For every flagged transaction, locate the supporting documentation. Pull from whichever sources you have: paper invoices and bills, bank and credit card statements, payroll reports, electronic receipts, email confirmations, or third-party integrations that logged the original entry. If a backup file is readable, you can open it in single-user mode and export the full transaction detail directly — this is faster and more accurate than reconstructing from paper alone.

Organize the documents by date before proceeding. Re-entering transactions out of chronological order increases the chance of posting errors and makes reconciliation harder.

Phase 4: Re-enter Transactions in Date Order

Work in single-user mode inside the repaired file. Enter each missing transaction using the same form type as the original — a bill stays a bill, an invoice stays an invoice, a journal entry stays a journal entry. Match the original date, account splits, customer or vendor, class, and memo fields exactly.

If the file was condensed to a cutoff date as part of the recovery, only re-enter transactions dated on or after that cutoff. Transactions before the cutoff have been replaced by opening balance adjustments and should not be re-entered individually.

Save each transaction and note it on your tracking sheet immediately after posting. This creates an audit trail of what was re-entered, when, and from what source.

Phase 5: Reconcile Against the Last Clean Trial Balance

Once all flagged transactions are re-entered, run a fresh trial balance as of the same date used in Phase 1. Compare it line by line against the backup trial balance. Every account must match to the cent.

If an account is off, the most common causes are a transposed digit, a wrong account split, a transaction posted to the wrong date, or a transaction that was duplicated. Pull a general ledger detail for the problem account and compare it against the backup version to isolate the discrepancy.

Rollback Points

Keep the repaired file untouched until Phase 1 is complete. After Phase 4, create a backup before running reconciliation. If Phase 5 reveals widespread mismatches, restore that backup and restart Phase 4 rather than layering corrections on top of errors.

Clean Outcome

A clean outcome is a file that passes Verify with no errors, ties exactly to the pre-damage trial balance on every account, and contains source documentation for every re-entered transaction in your tracking sheet.