QuickBooks C-Series Error Guide
How to Fix QuickBooks Error C=47
QuickBooks stopped what you were doing and displayed: "An error has occurred in QuickBooks. Please restart QuickBooks and try again. C=47"
Error C=47 means QuickBooks tried to locate a specific transaction and could not find it — the index in your company file is pointing to a transaction that has moved, been partially deleted, or is in a disordered list. At QuickFix Bookkeeping, the first thing we do is re-sort the QuickBooks lists — it resolves a significant portion of C=47 cases in under two minutes, before any data repair is needed.
The QuickFix Bookkeeping Distinction
C=47 is not always deep file corruption. The most common cause is a disordered name list — and re-sorting lists takes 2 minutes. Verify/Rebuild comes second, not first.
What C=47 means
QuickBooks searched the company file's transaction index and the transaction the index points to was not found. Could be a sorted list issue or genuine file damage.
Fix 1 — 2 minutes
Re-sort lists. A disordered Chart of Accounts, Customer list, or Vendor list causes the index to point to the wrong position. Re-sorting restores correct order and resolves many C=47 cases immediately.
Fix 2 — if lists are fine
Verify and Rebuild the company file. If re-sorting did not help, the data file itself has corruption that needs QuickBooks' built-in repair tools.
C-series errors explained: QuickBooks uses C= codes to signal internal runtime failures — unexpected conditions the application cannot handle gracefully. C=47 specifically means "cannot locate transaction." Other common C-series errors: C=272 (cannot write), C=343 (memory), C=184 (list damage). Each has a distinct fix path.
What Is QuickBooks Error C=47?
Error code
C=47
C-Series · Runtime Error
Related: C=272 · C=343 · C=184
What it means
Error C=47 is QuickBooks' internal signal for "cannot locate transaction" — a runtime failure that occurs when the company file's internal index references a transaction that QuickBooks cannot find at the expected location. This can happen because the list order has been disrupted (the fastest fix), or because the file has genuine data corruption that needs repair tools.
C=47 typically surfaces when editing a transaction, deleting a deposit from a report, posting payments, or running reports that traverse the transaction index.
When Does C=47 Appear?
01
Posting payments to customers
The most commonly reported trigger — applying a payment to a customer invoice causes C=47 because the payment process traverses the customer list index.
02
Editing or deleting a transaction
Any edit — changing a date, amount, or description — triggers C=47 when the save process cannot re-locate the transaction in the index.
03
Deleting a deposit from a report
Attempting to remove a deposit directly from a report or report-like screen causes C=47 when QuickBooks cannot locate the underlying transaction to delete.
04
Emailing a payment receipt
Generating and emailing a payment receipt document can trigger C=47 — the receipt generation process reads from the transaction index to populate the document.
05
Running reports with many transactions
Large reports that traverse many transactions across the company file expose index inconsistencies — C=47 appears when the report engine hits the broken pointer.
06
Opening the company file
In severe cases, C=47 fires immediately on opening the company file — the startup scan encounters the broken index before any user action is taken.
How to Fix QuickBooks Error C=47 — Step by Step
Start with Method 1 — re-sorting lists resolves a significant portion of C=47 cases and takes under 2 minutes.
METHOD 1
Re-Sort QuickBooks Lists
Do this first — resolves most C=47 cases in 2 minutes
QuickBooks stores its Chart of Accounts, Customers, Vendors, Items, and other lists in a specific order that the transaction index depends on. If that order becomes disrupted — from a display settings change, a sorting click, or certain data events — the index points to the wrong positions, producing C=47. Re-sorting restores the default order.
Chart of Accounts:
1
Go to Lists → Chart of Accounts. Click View → Re-sort List. Click OK on the confirmation. Close the Chart of Accounts.
Customer list:
2
Go to Customer Center. Click the Customers & Jobs tab. Click View → Re-sort List → OK. Close the Customer Center.
Other lists (Vendors, Items, Employees):
3
Repeat the same process for Lists → Vendor List → View → Re-sort List, Lists → Item List → View → Re-sort List, and any other lists relevant to the area where C=47 is appearing.
4
Close QuickBooks completely and restart the computer. Reopen the company file and test the action that was triggering C=47.
QuickFix tip: The "Include Inactive" checkbox in each list view matters — check it before re-sorting so that inactive customers, vendors, and items are included in the sort. An inactive record with a broken index position can cause C=47 even though it never appears in the active list view. Re-sorting without including inactive records can miss the broken entry.
METHOD 2
Verify and Rebuild Company File Data
If re-sorting did not resolve C=47
If re-sorting lists did not clear C=47, the company file has genuine data corruption. QuickBooks' built-in Verify and Rebuild utilities scan the file for inconsistencies and repair what they can find. Always run Verify first to assess damage before running Rebuild.
Before proceeding: Create a manual backup of your company file — File → Back Up Company → Create Local Backup. Rebuild modifies the file and if interrupted mid-process, you need a restore point.
1
Run Verify Data: Go to File → Utilities → Verify Data. QuickBooks will scan the company file. If it reports "QuickBooks detected no problem with your data" — the file is clean and C=47 has a different cause. If it reports issues or prompts Rebuild — proceed to step 2.
2
Run Rebuild Data: Go to File → Utilities → Rebuild Data. Click OK on the information window. QuickBooks will prompt you to save a backup — do it. The rebuild scan can take several minutes for large files. Do not interrupt it.
3
When Rebuild completes, run Verify Data again to confirm the corruption was repaired. Rebuild does not always fix every issue in one pass — if Verify still finds problems, run Rebuild a second time.
4
After a clean Verify result — close QuickBooks, restart the computer, reopen the company file, and test the action that was triggering C=47.
QuickFix tip: Verify Data writes a detailed log to QBWin.log — located in the QuickBooks installation folder or in C:\Users\Public\Documents\Intuit\QuickBooks. After running Verify, open this log and search for "LVL_ERROR" entries. These pinpoint the exact transactions or list items that are damaged — useful for manually identifying and removing or rebuilding specific broken records when Rebuild cannot fix them automatically.
METHOD 3
Suppress QuickBooks to Test Program vs File
Diagnose whether the fault is in QB or the company file
Before committing to a full Verify/Rebuild cycle, suppressing QuickBooks tells you within 2 minutes whether C=47 is caused by the QuickBooks installation itself or by the company file. If it disappears with a sample file — the company file is the problem. If it appears even with a sample file — the QuickBooks program is damaged.
1
Close QuickBooks. Right-click the QuickBooks Desktop icon on your desktop. Hold the Ctrl key while clicking Open. Keep holding Ctrl until the No Company Open window appears — do not release Ctrl early.
2
In the No Company Open window, click Open a sample file and choose any sample company. Attempt the action that triggered C=47.
3
If C=47 appears on the sample file — the QuickBooks program installation is damaged. Proceed to Method 4 (Repair QuickBooks). If C=47 does not appear — the program is fine and the corruption is in your company file. Return to Method 2 (Verify/Rebuild).
METHOD 4
Repair or Reinstall QuickBooks
If C=47 appears on sample file — program is damaged
If Method 3 confirmed the program installation is the source — not the company file — run a QuickBooks repair or Tool Hub diagnostic before attempting a full reinstall.
1
Open QuickBooks Tool Hub → Program Problems → Quick Fix My Program. Let it run. Retest.
2
If Quick Fix did not resolve it — go to Control Panel → Programs → QuickBooks → Uninstall/Change → Repair. Follow the repair prompts and restart.
3
After the repair, update QuickBooks fully (Help → Update QuickBooks Desktop → Reset Update → Get Updates) and retest with both the sample file and your company file.
METHOD 5
Restore from a Pre-Error Backup
If Rebuild cannot repair the damage
If Verify/Rebuild runs successfully but C=47 persists on the same transactions — the damage is beyond what the Rebuild utility can repair automatically. Restoring from a backup predating the error and re-entering any transactions created after the backup is the cleanest resolution.
1
Identify the most recent backup from before C=47 first appeared. Go to File → Open or Restore Company → Restore a Backup Copy → Local Backup. Restore to a different file name to preserve the current (damaged) version.
2
Test the restored file — attempt the action that was triggering C=47. If it completes without error, the backup is clean. Re-enter transactions that occurred between the backup date and now.
3
If no clean backup is available — or if the gap between backup and present is too large to re-enter — contact QuickFix Bookkeeping. Intuit Data Services can also perform deep file repair on severely damaged files, though turnaround time can be several business days.
Quick Reference — Which Fix For Your Situation?
| Your situation |
Most likely cause |
Start with |
| C=47 on any single action (payments, editing) |
Disordered list index |
Method 1 — re-sort lists |
| Persists after re-sorting, on multiple actions |
Company file corruption |
Method 2 — Verify/Rebuild |
| Unsure if it's QB or company file |
Unknown |
Method 3 — suppress test first |
| Appears on sample file too |
QB program damaged |
Method 4 — repair QB installation |
| Rebuild ran clean but C=47 persists |
Damage beyond Rebuild's scope |
Method 5 or call us |
Frequently Asked Questions About Error C=47
What does "C=" mean in QuickBooks error codes?
C= is QuickBooks' internal runtime error code prefix. These codes are generated by QuickBooks' own error handling system and correspond to specific unexpected conditions the application encountered. They are not Windows error codes. C=47 means "cannot locate transaction." C=272 means "cannot write to record." C=343 is a memory handling error. C=184 indicates a list damage condition. Each C= code points to a specific internal failure, which is why the fix for C=47 (list re-sort → Verify/Rebuild) is different from the fix for C=272 (file write permissions).
Will Rebuild Data fix everything, or can it miss some issues?
Rebuild Data fixes many types of corruption but not all. It handles list inconsistencies, transaction pointer errors, and certain index problems. It cannot repair physically damaged file sectors, recover transactions that have been partially overwritten, or fix corruption that occurred after the file's internal checksum was last updated. After running Rebuild, always run Verify Data again to confirm the file is clean. If Verify still reports errors after two Rebuild passes, the corruption is beyond what the utility can repair automatically and professional data services are needed.
C=47 appeared after I changed my display settings. Is that related?
Yes — this is a known trigger. Changing display settings, particularly switching which monitor QuickBooks opens on or changing resolution, can disrupt the list sort order in certain QuickBooks versions. Users in the Intuit community have reported C=47 appearing specifically after changing which screen QuickBooks displays on. The fix in this case is Method 1 (re-sort lists) — the list order change that the display event caused is what produced the C=47, and re-sorting restores the correct order.
How do I prevent C=47 from occurring again?
Three practices reduce C=47 recurrence significantly. Maintain a regular backup schedule — daily automated backups mean that if corruption appears, the restore point is never more than 24 hours old. Run Verify Data monthly as a maintenance check — catching corruption early, before it triggers errors, means smaller and faster repairs. Keep QuickBooks updated — many C= series errors are caused by bugs that Intuit fixes in maintenance releases. And store the company file on a reliable local drive or server rather than on a network share with intermittent connectivity — network interruptions during file writes are a common source of the corruption that produces C=47.
Related QuickBooks C-Series and File Errors
Company File Damaged? Data at Risk?
C=47 Still Appearing After Rebuild?
Let's Repair Your Company File Today.
Certified Intuit ProAdvisors · QuickBooks Data Repair Specialists
When Verify/Rebuild cannot fix the corruption, the company file needs hands-on data repair. At QuickFix Bookkeeping, our certified ProAdvisors assess the QBWin.log, identify the specific damaged records, and repair or reconstruct them — without data loss and without the multi-day Intuit Data Services wait.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Company file repaired fast.
