Recovering a QuickBooks Desktop Company File When the .TLG Transaction Log Is Corrupt or

When the .TLG file is damaged or deleted after discontinuation, you can still recover uncommitted transactions by restoring your last backup and applying structured verification and rebuild steps.

When QuickBooks Desktop opens a company file, it pairs the .QBW working database with a .TLG transaction log that records every entry since the last backup. If QuickBooks crashes or the workstation loses power, that log is what lets the database recover uncommitted transactions. When the .TLG is missing or corrupt, QuickBooks opens the .QBW without that safety net — and if the .QBW itself has damage, there is no fallback. After discontinuation, the recovery path still exists; it just requires discipline and a working backup.

What the .TLG File Actually Does

Every time you post an invoice, write a check, or make a deposit, QuickBooks writes the transaction to the .TLG before it commits the change to the .QBW. When you create a .QBB backup, QuickBooks rolls the log into the backup and starts a fresh .TLG. This is why a .QBB plus its matching .TLG can bring you current even if the .QBW is destroyed. Without the .TLG, the best you can recover is the state of the file at the moment that backup was made — any transactions entered afterward are gone unless they exist in a secondary record.

Assessing the Damage

Before attempting recovery, determine what you have. Look for three files sharing the same base name — for example, Company.QBW, Company.QBB, and Company.TLG. If the .TLG is present but zero bytes, it is effectively empty. If it is present but far smaller than expected, it may be partially written and corrupt. If the .QBW opens normally and balances to your last backup, the missing log may not matter — you simply lost the ability to auto-recover from a future crash until the next backup cycle. The real problem arises when the .QBW will not open or throws verification errors and the .TLG is unavailable.

Step 1 — Isolate Your Files Before Anything Else

Copy the .QBW, the .QBB, and any .TLG files to a separate recovery folder on a different drive. Work only on copies. Never run rebuild or verification on your sole remaining copy of the company file.

Step 2 — Restore the Last Known Good Backup

Restore the most recent .QBB to a new location using a fresh file name so it does not overwrite anything. If QuickBooks prompts to create a new .TLG, allow it. This restored file becomes your baseline. Confirm the total account balances against a bank statement or printed trial balance dated as close to the backup as possible.

Step 3 — Run Verify and Rebuild on the Restored File

Open the restored company file in single-user mode as the Admin. From the File menu, choose Utilities, then Verify Data. If verification reports problems, run Rebuild Data from the same menu. Rebuild may need to run more than once — repeat until Verify completes cleanly. If Verify continues to report structural damage after multiple rebuild cycles, the file likely has target chain or structural corruption that the built-in tools cannot resolve.

Step 4 — Reconstruct Uncommitted Transactions

Any transaction entered after the backup was created but before the incident lives only in external records: printed reports, bank feeds, email confirmations, paper registers, or third-party integrations that retain export history. Work methodically by date range. Re-enter each transaction with its original date, document number, and amounts. Prioritize bank and credit-card accounts first, then payroll, then accounts receivable and payable. After reconstruction, run Verify again to confirm the file remains structurally sound.

Step 5 — Establish a New Backup and Log Cycle

Once the file is whole and verified, create a fresh full backup immediately. This resets the .TLG and gives you a clean recovery point. Going forward, maintain a rotating backup schedule — daily local backups plus an off-machine copy — so that no single hardware failure can leave you without either the database or the log.

When the .QBW Itself Is Damaged and No Log Exists

If the .QBW will not open and the .TLG is gone, the .QBB restore is your primary recovery path. But if the .QBB is old or the rebuilt file still fails verification, deeper data extraction from the damaged .QBW may be the only route to recovering list data and transaction history that the backup does not contain.

Preventing a Repeat

Set QuickBooks to remind you to back up on close, store backups on physically separate media, and periodically run Verify on the working file even when nothing appears wrong. A clean Verify result is the cheapest insurance you have.