Lacerte export troubleshooting

Alerts and notices
Leave feedback

Contact information (optional):

Leave this blank:

Please tell us how we can make this information more helpful.


Characters left:

In addition to using tax codes to integrate with UltraTax CS, licensed users of Workpapers CS can export account numbers, account descriptions and balances to Lacerte.

This topic provides troubleshooting information for common integration issues between Workpapers CS and Lacerte.

You may find after completing the export to Lacerte that the the Diagnostics window within Lacerte contains nothing. Review the following areas before exporting again.

Note: When creating the export file, accounts with blank tax codes are listed in the diagnostic screen.

Note: If the client ID’s are different between the two applications, a new client will be created in Lacerte during the export process.

Naming convention for export file: ClientID.?By

? = entity y = year
C = Corporation 6 = 2016
P = Partnership 7 = 2017
R = Non-profit 8 = 2018
S = S Corporation etc.

Workpapers CS will create the subfolders for each type of entity during the export process. The export file is placed in the appropriate folder based on entity type. The following entity type subfolders are automatically created when the Export Data tab in Setup > File locations for Lacerte is set to C:\Lacerte\17Tax\.

C:\Lacerte\17Tax\CDATA = Corporation\1120

C:\Lacerte\17Tax\PDATA = Partnership\1065

C:\Lacerte\17Tax\RDATA = Non-Profit\990/990PF

C:\Lacerte\17Tax\SDATA = S Corporation\1120

Related topics

Tax export to Lacerte (Export Client Data Wizard)

Setting up file locations

Internal notes


Another option: Browse out to the export directory (C:\Lacerte\yyTax\?Data folder, ? is the entity type). Open the exported file with NotePad. If all you see is a single header row, one of the above items listed in this articles was skipped or overlooked.

Here is an example of an empty file:

Client ID: ARAPDEPT

Location: C:\Lacerte\16Tax\PDATA\ARAPDEPT.P86

Contents of file: <?xml version="1.0" encoding="utf-8"?><LSCBridgeFile />

Share This