Unable to read a file to be included in the accountant's copy" in Sage 50
Sage 50 cannot read one of the files it needs while creating an accountant's copy, usually because of damage or a locked file.
When Sage 50 shows “Unable to read a file to be included in the accountant’s copy.”, it means the program was in the middle of assembling the accountant’s copy and hit a file it could not open or parse. Despite the wording, the problem is almost never the accountant’s copy itself. It is a symptom that something in your company data, or one of the supporting files alongside it, is unreadable.
What the message actually means
An accountant’s copy is a snapshot built from your live company data. To build it, Sage 50 has to read every piece of data in scope for the dividing date you chose. If any one of those components is damaged, truncated, or locked by another process, the build stops and you get this message. Think of it as a read failure somewhere in the chain, not a verdict on your whole file.
Common causes
- Damage or corruption inside the company database, often from a crash, power loss, or a network hiccup while the file was open.
- The file being open or locked by another user, a backup job, a sync tool, or a second instance of Sage 50 on the same machine.
- Antivirus or cloud-sync software interfering with the files while the accountant’s copy is being written.
- A company file stored on an unreliable network share or removable drive that dropped mid-write.
- A very large or fragmented data set that fails partway through the read.
What to try first, safest options first
- Close everything and retry. Make sure no other user has the company open, pause any backup, sync, or antivirus scanning of the data folder, and try creating the accountant’s copy again on the local machine rather than over the network.
- Restore from a known-good backup. If you have a backup from before the problem started, restore it to a new location and try the accountant’s copy from there. This confirms whether the damage is in the current file or the environment.
- Run Sage 50’s built-in data checks. Depending on your edition, Sage 50 includes integrity checking and backup verification tools. Run them against the company and note anything they report, even if they claim to complete successfully.
- Try a shorter dividing date. If the failure is tied to a specific damaged transaction, narrowing the accountant’s copy window sometimes avoids it. This is a diagnostic, not a fix.
When the file needs professional attention
If the message repeats after a clean restore and a retry on a quiet machine, the underlying data is likely damaged, and no amount of retrying will produce a valid accountant’s copy. Continuing to force it risks a snapshot that looks fine but is missing or misstating data, which is worse than no copy at all. This is the point where the file should be looked at by a repair service rather than pushed further. Our engineers repair damaged Sage 50 and Simply Accounting databases, and we also handle Sage 50 to QuickBooks conversions if the accountant’s copy is part of a bigger move.
A useful next step
Before doing anything else, make a manual copy of the entire company data folder and work only on the copy. That preserves the file exactly as it is now, which matters both for retrying safely and for any later recovery. If the error persists, send us the file for a free evaluation and we will tell you what is unreadable and what can be recovered.