QuickBooks Error 47 (C=47): Fix the Can't Find Transaction Error
Last reviewed 2026-09-21
QuickBooks Error 47, shown in messages and reports as C=47, means the program cannot find a transaction that your company file says should exist. It is a data damage code, and it points to broken internal links in the file rather than to anything you did wrong in the program.
Most people meet it in one of two moments. Verify Data lists C=47 among its results, or the message appears while you open, save, or print a specific transaction or report.
What does C=47 actually mean?
QuickBooks stores every transaction as a set of linked records. An invoice points to the customer, the items, and the payment that settled it. A bill payment points to the bills it cleared. When one record in that chain goes missing, the file can no longer trace the connection, and QuickBooks reports C=47 instead of showing numbers it cannot prove.
That is also why the message feels vague. The code tells you a link is broken, but not which transaction broke it. The steps below narrow that down.
Why does a transaction go missing?
The record almost never disappears on its own. In our experience the damage traces back to an interruption while the file was being written:
- a power cut or forced shutdown while QuickBooks was saving
- a network drop between a workstation and the computer hosting the file, mid-save
- a damaged transaction log that QuickBooks replayed after a crash
- a backup restored over the file partway, or a restore that stopped before it finished
- failing storage on the drive that holds the file
Multi-user files kept in a shared folder on the host computer are the most common setting. Larger files take longer to write, so they spend more time exposed to exactly these interruptions.
Fix error 47 in this order
1. Copy the file first. Put a copy of the company file, together with its transaction log file, in a safe folder on the local drive. Every step after this one changes data, so protect a copy taken before you change anything. Never work on the only version of the file.
2. Update QuickBooks, then log everyone out. Install the latest maintenance release for your version and close the program on every machine. The repair utilities work best when the host computer has the file to itself.
3. Run Verify Data. Open the File menu, choose Utilities, then Verify Data. Verify reads the whole file, writes a report of what it finds, and changes nothing. Note every entry it lists.
4. Run Rebuild Data. Open the File menu, choose Utilities, then Rebuild Data, and let it run. Rebuild repairs what it can and removes what it cannot, which is exactly why step 1 matters. When it finishes, open the rebuild report and look for entries that repeat the same code.
5. Verify again. Keep running Verify until it reports the file clean. If the code returns after a successful rebuild, move to step 6.
6. Restore a backup that passes Verify. Take your most recent backup, verify it before you overwrite anything, then restore it and re-enter the transactions dated after that backup. Keep the damaged file, because it is the only record of those transactions.
7. Test where the file lives. Keep the file on the local drive of one computer while you repair it. If it passes locally but fails again on the shared folder, the trouble sits in the connection or the hosting setup, and that needs fixing before the file moves back.
After the rebuild, confirm the file is clean
Open the transaction or run the report that first raised the message. Then check the numbers you know: the bank register, the accounts receivable aging, and a balance sheet compared against a date before the trouble started. Rebuild removes records it cannot repair, so a small gap in history is possible. Find that gap now rather than during a rushed close. Finally, run Verify once more. A clean result means the repair held, and you can return the file to its usual home.
When to hand the file to us
Rebuild clears many of these breaks, but not all of them. Call in our team when the code returns right after a clean rebuild, or when Verify fails again immediately. The same applies if the file will not open at all, if every backup you own fails Verify or refuses to restore, or if the message keeps appearing in everyday use despite clean Verify results.
Our engineers repair damaged QuickBooks company files every working day. For files that fail Verify or Rebuild, see our QuickBooks Verify and Rebuild repair service; we rebuild the missing links by hand and return a file that passes. If you have no usable backup at all, our emergency QuickBooks data recovery covers files rescued from crashed drives and backups that will not restore.
Whatever route you take, do not delete the damaged copy once a backup is restored. It holds the transactions Rebuild removed, and it is often the difference between a complete recovery and months of re-entry.