Accounting CS: Common conversion diagnostic messages

Alerts and notices

Conversion diagnostics are displayed when CSA information does not transfer to Accounting CS for various reasons. These diagnostics can be prevented in many cases by completing the appropriate pre-conversion steps, such as running the Accounting CS Conversion Report and running the Repair Case of Descriptions utility.

Note: The application displays a conversion import diagnostic report when the CSA to ACS conversion completes. Once this window is closed, it cannot be reopened with Accounting CS. However, a copy can be found on your local computer:

Browse to:  C:\Users\"user name"\AppData\Local\Creative Solutions\Accounting CS

  • The name of the file will be similar to: ImportFromCSA_20160602113424.txt or ImportFromCSA_YYYYMMDD######.txt
  • The first 8 numeric characters will be the date of the conversion in YYYYMMDD format. The last 6 characters are the time the conversion was completed in HHMMSS format.
  • If you are working in the Virtual Office or Saas environment, you can contact the Support Department to get a copy of the conversion diagnostics report.

Here are some common conversion diagnostics and how to resolve them.

It is important that both Accounting CS and CSA are updated to the most recent versions.

See also: Transitioning from CSA to Accounting CS services

Address-related diagnostics

During the conversion process, Accounting CS reads and attempts to verify all employee and client addresses. If the Client and Employee Address Mapping screen is skipped during conversion or the address could not be verified, you may see one of the following diagnostics and encounter errors when processing payroll in Accounting CS.

CSA to Accounting CS Conversion address mapping screen
  • Unable to use work location for the address of '[address here]' - (If no zip is provided, then there must be a city and state). The address of '[city, state]' will be used instead.

    The work location for the address of 'City, State' could not be validated to street level accuracy. This diagnostic is usually displayed in conjunction with the above diagnostic message.

    If the client being converted does not have a complete address entered in CSA, this diagnostic may be displayed. Use one of the following methods to resolve the diagnostic.

    In Accounting CS, choose Setup > Clients and then modify the address on the Main tab.

    Or,

    In CSA, choose File > Client Properties and update the client address. Then, delete the client in Accounting CS and perform the conversion from CSA again.

  • Unable to determine/validate county for the address of 'City, State'

    If the address referenced is the work location (client) address:

    In Accounting CS, choose Setup > Clients and then modify the address on the Main tab.

    Or,

    In CSA, choose File > Client Properties and update the client address. Then, delete the client in Accounting CS and perform the conversion from CSA again.

    If the address referenced is an employee address:

    In Accounting CS, choose Setup > Employees and then modify the address on the Main tab for the appropriate employee.

    Or,

    In CSA, choose Setup > Employees and then modify the address on the General tab for the appropriate employee. Then, delete the client in Accounting CS and perform the conversion from CSA again.

  • [Employee ID, Employee name]> was not validated to street level accuracy. Please verify the street address information is correct before processing payroll for this employee.

    This is an FYI (For Your Information) diagnostic informing you that the employee address was not verified. Before you process payroll in Accounting CS, all addresses need to be verified in order for the application to correctly determine which taxes to calculate. Use the following steps to resolve the diagnostic before you begin processing payroll.

    1. In Accounting CS, choose Setup > Employees and edit the appropriate employee record.
    2. Use the Address Verification dialog to update and verify the employee address.
  • Employee [ID] - [Employee name] has an invalid address

    This is an FYI (For Your Information) diagnostic informing you that the employee address was not verified. Before you process payroll in Accounting CS, all addresses need to be verified in order for the application to correctly determine which taxes to calculate. Use the following steps to resolve the diagnostic before you begin processing payroll.

    1. In Accounting CS, choose Setup > Employees and edit the appropriate employee record.
    2. Use the Address Verification dialog to update and verify the employee address.
  • Unable to add determine/validate county for employee [Employee name].

    This is an FYI (For Your Information) diagnostic informing you that the employee address was not verified. Before you process payroll in Accounting CS, all addresses need to be verified in order for the application to correctly determine which taxes to calculate. Use the following steps to resolve the diagnostic before you begin processing payroll.

    1. In Accounting CS, choose Setup > Employees and edit the appropriate employee record.
    2. In the County field, select the appropriate county for the address. If not available, use the Address verification feature to verify the address and determine the correct county.

See also: Entering historical payroll data

Earnings not converted

Diagnostics related to earnings are displayed when a pay, deduction, or withholding item is found in the global CSA database, but is not found on the employee. For earnings to convert, you will need to add the withholding item to the employee in CSA and re-convert the client.

Alternatively, the employee may need to be added to a new or different location during the conversion; or the address was not verified correctly on the Client and Employee Address Mapping screen.

Payroll item diagnostics

These diagnostics are typically FYI (for your information) diagnostics that can be resolved in Accounting CS after conversion. To prevent these diagnostics, use the Accounting CS Conversion Report in the Utilities menu prior to conversion.

Accounting diagnostics

Typically, these diagnostics are avoided by completing the pre-conversion steps in the conversion walkthrough topic.

  • [Importing transaction]: Journal _Entry: Program error: Journal Entry missing associated GL Transaction
    There are a few different causes of this diagnostic.
    • There may be a transaction in CSA that has dates in a period after today's date.
    • The Current Processing Period in CSA is too far in the past.
    • One or more payroll items is missing a GL account in CSA.
  • [Importing client information]: GL_Account: A GL account number must not have more characters than the Chart of Account's mask.

    This diagnostic is caused by two things:

    • There are accounts the truly do not fit the mask. In CSA, choose Setup > Chart of Accounts and then choose Edit > Verify accounts. Adjust any account numbers that do not fit the mask and then reconvert the client.
    • Less commonly, if there are fewer than 3 character slots in the first part of the mask before the first separator, the client will not convert because the Undistributed 999 account cannot be created. Edit the mask in CSA to have 3 or more slots in the first part of the mask and reconvert the client.
  • [Importing transaction]: Bank_Transaction_Accounting_Source_Override_Bank_Transaction_Distribution (bank_transaction_distribution_KEY):Value already exists

    This diagnostic may be accompanied with "Database Messages: GL Transactions row errors: bank_transaction_distribution_KEY:Value already exists. Column values: bank_transaction_KEY. Bank_transaction_distribution_KEY"

    This diagnostic is displayed when there is a balancing entry in CSA using a GL account that is not set up as a checkbook. To prevent the diagnostic, use these steps:

    1. Preview a Transaction Listing report in CSA with a selected range by the reference so you only see transactions with a reference of 1.
    2. Review the list, and verify that there are only checkbook accounts assigned to the transactions.
    3. If there are any transactions that are not using checkbook accounts, either set those accounts up as checkbooks or change the reference to something other than 1.
    4. Delete the client out of Accounting CS and re-convert the client data.

Internal notes


Less common diagnostics (such as those that say "contact Support"): See IT 382252 / TFS 812258

  • The Accounting CS Conversion report may say "Employee specific information could not be matched to an existing employee. Please contact Support for further assistance." In this case, you will need to get the CSA client data and open the "employee" table in Access. Look for Employee SysID 0 and delete those records from the table. Send the CSA client back to the firm and the conversion should go through successfully. If you are not comfortable with or do not have access to the underlying tables, contact the CF.
  • See also: Internal: Fixing duplicate vendor names in CSA data

Dynamic SQL diagnostics: If you have a diagnostic that looks like "*** <dynamic SQL>, line X, errno XXX: [message here]" search in TFS for the resolution. You'll see the most success if you search "errno XXX" in TFS to see all of the relevant instances of the diagnostic.

Address-related diagnostics: During conversion (at the very end, when it is actually converting data and not mapping data), Accounting CS checks the addresses against the database that Symmetry maintains. If Symmetry does not find the address information, that is when a diagnostic will be displayed.