QuickBooks Error 3140 – Damaged Transaction in the Company File

Error 3140 means QuickBooks found a transaction it cannot read cleanly. We explain the causes and the steps that get the file opening and verifying again.

Error 3140 appears when QuickBooks Desktop tries to read a transaction and finds the record damaged. It surfaces most often while Verify or Rebuild is running, and it points at the company file itself rather than at your installation, your license, or your network. On this page we explain what the code means, what damages the data, and the repairs we apply, in the order that works most often.

The message on screen

The dialog carries the heading Error 3140, and the text beneath it names a transaction QuickBooks cannot read. The wording shifts a little between releases, so treat the transaction named in your own message as the useful part. When the code appears during a data check, the Verify Results window usually ends with a line reporting that the data has lost integrity. Some readers first meet the code on a normal working day, when an invoice, bill, or journal entry refuses to open or save.

The mechanics behind the code

QuickBooks stores every transaction as a chain of linked records: the document itself, its lines, its links to the ledger, and its links to the customer, vendor, or item lists. When Verify walks that chain and finds a link that points nowhere, or a line whose totals no longer match its header, it raises 3140 against the transaction. Nothing about your Windows setup or your subscription is at fault. The bytes on disk no longer describe a transaction QuickBooks can trust, so the program stops rather than post numbers it cannot confirm to your ledger.

Common triggers

Almost every case we open traces back to an interrupted write. QuickBooks writes to the file continuously as you post, and a transaction caught half-written leaves the chain broken. The causes we see most:

• A power cut, crash, or forced shutdown while QuickBooks was saving
• A network drop between a workstation and the computer hosting the file
• Failing sectors on the drive that holds the company file
• A large multi-year file that has never been condensed
• An earlier Rebuild that was cancelled before it finished

Any single event can leave one bad transaction behind. Verify is usually the first thing to notice, which is why the code tends to appear during a check rather than during daily work.

How do you clear error 3140?

Work through the scenarios below in order and stop as soon as Verify comes back clean. Always keep the damaged file; it is your only source for the most recent entries.

If you have a recent clean backup:

1. Copy the damaged company file to a separate folder so nothing writes to it.
2. Restore your most recent backup into a working folder.
3. Open the restored file and run Verify (File > Utilities > Verify Data).
4. Re-enter the transactions posted since that backup, using the damaged copy as your reference.

If you have no backup to fall back on:

1. Make a copy of the file first; a rebuild can remove records it cannot repair.
2. Go to File > Utilities > Rebuild Data and let QuickBooks create the pre-rebuild backup it asks for.
3. Let the rebuild run to completion, then run Verify again on the same file.
4. Check your reports for the period around the error and re-enter anything the rebuild could not save.

If only one transaction triggers it:

1. Note the document named in the message or in the Verify log.
2. Back the file up.
3. Void or delete that transaction, then re-enter it from the source paperwork.
4. Run Verify to confirm the file is clean.

If the damage survives a rebuild:

1. Copy the file to the local Documents folder of the host machine and run Verify on the copy, to rule out the drive or the network as the source.
2. If Verify still reports the same transaction, the damage is beyond the built-in tools. Our engineers repair damaged company files from a copy you upload and return a file that opens and verifies, with transactions intact wherever the data allows.

Keeping the damage from coming back

Damage of this kind is mostly preventable:

• Take a backup before any long batch of entry work, and keep copies off the machine that hosts the file.
• Close QuickBooks properly before shutting the computer down, and fit a UPS if the office loses power now and then.
• Keep the company file on a stable local disk. Files on a share with an unreliable connection collect damage quietly over months.
• Run Verify once a month on a quiet afternoon. A bad transaction caught early costs you one bill, not a quarter of books.
• Condense an aging file. Our team handles a supercondense for files the built-in condense cannot finish.