Resolving Proforma errors in Lacerte
by Intuit•2• Updated 1 week ago
This article explains how to fix common problems and errors when you transfer client files to the current year using Proforma in Lacerte. It covers failed transfers, a Bridge Exception Log that shows R under Message, Proforma starting when you open Lacerte or switch modules, and Range Check errors after a Proforma.
Before you start
How to fix common problems and errors with Proforma
There are a few possible reasons why this error message may present itself, and we'll be going over each below.
Step 1: Make sure the current year tax program and the prior year tax program are both updated
- Open Lacerte 2026.
- From the Tools menu, select Lacerte Updates.
- Open Lacerte 2026.
- From the Tools menu, select Lacerte Updates.
- Attempt to Transfer Clients (Proforma) the client. If it fails, continue to the next step.
Step 2: Make a copy of the prior year tax return
- Select the Clients tab to view the list of your clients.
- Highlight the client that needs to be copied.
- Select the client, then select Copy (or press Ctrl+C).
- Enter the client number for the copy in the Copy Client window.
- Select OK.
- Attempt to Transfer Clients (Proforma) the client once more. If it fails, continue to the next step.
Step 3: Check input screens in return for any non-ASCII characters
- Open the prior year return that you transferred the client from with Proforma.
- Within the Detail tab, press Ctrl+W to enter Batch Mode.
- Review the input screens that show in bold.
- Look for any non-ASCII (American Standard Code for Information Interchange) characters. Examples: Ä Ë Ï Ö Ü Ÿ Ḧ Ẅ Ẍ ẗ ẞ ß Æ æ § ® ©. These tend to appear more commonly in the Foreign Address input fields.
- Search the Description field for any erroneous characters:
- Look for a line "|", extra text, or empty spaces.
- Clicking the input field will show the correct text.
- Delete any erroneous characters and re-enter the correct data.
- To exit Batch Mode, select the Detail menu once more and choose Switch to Interactive.
- Attempt the Proforma once more.
Step 4: Rename the Custom Client Letter file for the client
In a small number of returns, the custom client letter can get corrupted and prevent Proforma from happening. If you rename it, the program creates a new one the next time the client is accessed.
- Make note of the client number on the file you want to transfer with 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 using the format ClientNumber.?iY.
Example: Let's say the client number is 1234. If the data path in step 2 is C:\Lacerte\23tax\IDATA, then browse to C:\Lacerte\23tax\IDATA\Notes, find 1234.ii9 and rename it. In TY20, a partnership file extension of .Pi3 will show.
The Bridge Exception Log is showing R under Message

This usually means you have a REP Lock on an existing client.
- Open the current year of Lacerte to the Client list.
- Right-click on the client.
- Select Remove REP Lock.
- Go back to the prior year program and start the Proforma process once more.
When opening Lacerte or switching modules, Proforma starts
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.
Delete the bridge files
- Close Lacerte.
- Open the directory of the Data Path for the year the files are being transferred to with Proforma.
- Example for 2023 Individual standalone: C:\Lacerte\23tax\Idata
- Within this ?data folder, delete any file that ends in .?PY (? = letter of tax type, Y = last digit of tax year)
- Example for 2023 Individual file: client.IP3
- 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.
When opening Lacerte after a Proforma, Range Check errors show
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.
Related topics
More like this
- Troubleshooting the Lacerte error: Error while updating Tax Service Databy Intuit
- Failure during proforma processing or "failed to transfer" when attempting to proforma clientby Intuit
- Understanding why some client data did not proforma in Lacerteby Intuit
- Resolving Access Violation errors when opening Lacerteby Intuit