This article references default installation paths and uses YY to reference the tax year in 20YY format. C: will always indicate the local drive and X: will always indicate the network drive.
This article will help you with the following errors:
In a small number of returns, sometimes the custom client letter can get corrupted and prevent proforma from happening. If we rename it, the program will create a new one the next time the client is accessed.
Make note of the client number on the file you want to proforma.
In the prior year program, go to Help and select Troubleshoot (or press F10).
Make note of the data path that is listed.
In Windows File Explorer, browse to that data path.
Select and open the Notes folder.
Rename the file. (format: ClientNumber.?iY)
Example: Let's say the client number is 1234. If the data path in step 2 is C:\Lacerte\19tax\IDATA, then browse to C:\Lacerte\19tax\IDATA\Notes, find 1234.ii9 and rename it. In TY20, a partnership file extension of .Pi0 will show.
This happens when a Proforma is initiated from the prior year. It may have been done accidentally by another user. It can go unnoticed until the current year for that tax type is accessed. If the bridging has completed and work has been overwritten, the only way to get it back is to restore from a backup. There is no undo feature.
If the Proforma bridge was caught in time or to prevent it from going further, you can delete the bridge files.
Follow these steps to delete the bridge files:
Close Lacerte.
Open the directory of the Data Path.
Example for 2019 Individual stand alone - C:\Lacerte\19tax\Idata
Within this ?data folder, delete any file that ends in .?PY (? = letter of tax type, Y = last digit of tax year)
Example for 2019 Individual file - client.IP9
Once these files are deleted in each tax type's Data Path, open the program.
If this issue repeats itself on a network, it may be helpful to disable a user's ability to Proforma in Trustee Rights.
This error is caused when there is minor damage to the database that the program is attempting to import the client to. Run a database repair to resolve the issue.