QuickBooks Error C=47: Can't Find Transaction, Causes and Fixes

Last reviewed 2026-09-14

Error C=47 means QuickBooks went to look up a transaction and could not find it. A pointer inside the company file still references the transaction, but the record itself is missing, unreadable, or was never fully written. In many cases, a Verify and Rebuild clears it without drama.

What does error C=47 mean?

C=47 is one of QuickBooks' internal data errors. The message behind it is plain: can't find transaction. Somewhere in the file, a link points to a transaction that is not there. QuickBooks follows that link, finds nothing, and stops to report the code.

This is not a Windows problem and not a network error like H202. It is damage inside the company file itself. You will usually meet it when you open, edit, save, delete or void a particular transaction. Reports that include the missing record can trigger it too, and so can a Verify run or a backup that walks the whole file.

C=43, C=51 and C=88 are close cousins. All of them point to the same underlying fault, which is data damage. Our QuickBooks error code repair service handles the whole family, and the steps below are where most cases start.

Common causes

In our repair work, the same handful of causes show up again and again.

• An interrupted save. A power cut, a frozen computer, or a forced shutdown while QuickBooks was writing leaves half a transaction behind: the summary exists, the detail does not.
• A transaction that was deleted while other records still pointed to it.
• A dropped connection. When the file lives on a shared folder on the host computer or a mapped network drive, losing the network mid-save can cut a write in half.
• A damaged transaction log that was applied when the file reopened.
• A full disk. When the drive ran out of room, the write never finished.

Before you touch anything

Two checks take five minutes and save a lot of guesswork.

• Check free disk space on your own computer and on the machine that hosts the file.
• Copy the company file to your local desktop and open the copy. If the error vanishes, the network path is the suspect. If it follows the copy, the damage is in the file.
• Make a backup, or at minimum a plain copy of the file, and run every step that follows on that copy. Never repair the only version you have.

Steps to clear the error

1. Confirm you are on the latest release of your QuickBooks version, then reopen the file and try the same action again.
2. Run Verify Data from the File menu: choose Utilities, then Verify Data, and let it run to the end.
3. If Verify reports a problem, run Rebuild Data from the same menu. QuickBooks will ask for a backup first, so let it take one. Then leave the rebuild alone until it finishes, even if the progress bar looks stuck for a while.
4. Run Verify again once the rebuild completes. A clean result is your confirmation that the repair took.
5. If the error was tied to one transaction, delete it and enter it again. The audit trail and a transaction detail report will show you what went missing.
6. If Rebuild cannot clear the code, restore the most recent backup that verifies clean, then re-enter the transactions posted since that backup date.

Most cases stop at the second Verify. The ones that do not are what the next section is for.

If the error keeps coming back

A returning C=47 means the damage sits deeper than Rebuild can reach, or the record the link points to is gone entirely. Rebuild can repair structures it understands. It cannot recreate a transaction that no longer exists.

The manual route is to run a transaction detail report for the period, compare it against your bank and sales records, and re-enter the gaps. That is reasonable when a few entries are missing. When hundreds are involved, it becomes days of careful work, and every re-entry is a chance for a new mistake.

When should you hand the file to us?

Send the file to our team if Verify crashes partway through, or if Rebuild fails or leaves things worse. The same goes for a company file that will not open at all, or a C=47 that returns after every fix. These are signs of structural damage, not surface noise.

We do this work every day. Our engineers recover transactions QuickBooks can no longer find and hand back a file that opens, verifies clean, and balances. Start with our QuickBooks Rebuild and Verification service, which exists for files that fail Verify or Rebuild.

Whichever route you take, keep the damaged copy until the repaired file has verified clean and your key reports match. Then take a fresh backup and store it somewhere other than the computer that holds the live file. That habit turns the next error like this into a five-minute restore instead of a repair job.