QuickBooks Error C=387: What It Means and How to Fix It
Last reviewed 2026-11-09
Error C=387 means QuickBooks hit a transaction or linked record inside your company file that it cannot read or finish working with. It usually appears when you open a saved transaction, save a new one, or run a data check. The cause sits inside the file itself, and it is fixable; there is a sensible order to work through.
What does error C=387 mean?
QuickBooks uses the C= family of codes for internal data errors, and the number points to where the program gave up. With C=387, the program cannot find or complete an operation on a transaction, usually because a link between records is broken or the underlying data is damaged. Links of that kind connect an invoice to the payment that settled it, or a bill to the cheque that paid it. When a link points at data that is damaged or missing, QuickBooks stops and reports the code rather than guessing.
The exact number matters less than the fact it describes: data inside the company file is damaged, and the file needs attention.
Why does QuickBooks show error C=387?
Files rarely damage themselves; something usually happens to them. The common triggers we see are:
- An abrupt end to a session: a power cut, a forced restart, or a laptop closed while the file was open.
- A network drop in multi-user mode, most often when the file lives on one machine and is opened across the network from another.
- The file being opened straight from a cloud-synced folder or a removable drive, where sync activity can interrupt a write.
- A company file that has grown large and tired over many years of use.
- An earlier condense or rebuild that was interrupted partway through.
Back up the file before anything else
Before you run any fix, copy the company file somewhere safe, along with the transaction log that sits beside it in the same folder. Keep that copy untouched no matter what the later steps suggest. Rebuild changes the file it works on, and if it misfires you will want the original exactly as it was. If a recent backup exists, confirm its date before you count on it.
Fixes to try, in order
- Run Verify, then Rebuild. From the File menu, under Utilities, choose Verify Data. If it reports problems, run Rebuild Data from the same place and let it finish, including the backup it asks you to save first. One pass often is not enough. Repeat the pair until Verify comes back clean or two rounds in a row change nothing.
- Note where the error appears. If one transaction or one report triggers it every time, that tells you where the damage sits. Try reaching the same transaction a different way, through a report rather than a register. If the file will not open at all, the damage is broader and the built-in tools will not reach it.
- Work on a local copy in multi-user setups. If the file is hosted on one machine and shared, copy it to the machine you are fixing it from, then verify and rebuild there. A rebuild across a network connection can fail in ways that look exactly like damage.
If Verify and Rebuild will not clear the error, the file needs more than the built-in tools. Our service for files that fail QuickBooks Verify or Rebuild exists for exactly this point.
Should you restore a backup instead?
A backup that predates the trouble is often the cleanest fix, if the gap is small. Anything entered since that backup will be missing, so weigh the re-entry cost honestly. Test the restore before you rely on it; a backup can carry the same damage if the trouble started days before you noticed.
When the newest good backup is too old, the transaction log beside the company file may still hold the missing entries. QuickBooks cannot read that log on its own, but recovering transactions from the QuickBooks transaction log is a routine job for our team.
Checks to make after the fix
Run Verify one final time and let it finish, even if Rebuild reported success. Then test the exact spot that failed: open that transaction, save it, run the report that tripped the error. Keep an eye on the file through the next few days of normal use. A C= code that returns after a clean verify means deeper damage, and catching that early protects more of your data.
When does this need a professional repair?
Hand the file over when the built-in tools stop improving things: Verify keeps failing, Rebuild loops, the good backups are too old, or the error returns within days of a clean pass. Repeated rebuilds on an already fragile file can make recovery harder, so stop rather than push. Our engineers repair company files at the data level, and our QuickBooks error code repair service covers the C= family directly.
Before you decide either way, write down exactly when the error appears and which transaction, report, or action triggers it. That single detail speeds up any repair considerably, and it takes five minutes to capture.