Skip to main content
All CollectionsMember ManagementTroubleshooting
Error Message: Employee has the Same Name as a Customer
Error Message: Employee has the Same Name as a Customer

How to resolve conflicts between member record (customer) names and employee names.

Pete Zimek, CAE avatar
Written by Pete Zimek, CAE
Updated over 2 months ago

Why This Happens

QuickBooks Online does not allow duplicate names across customers, vendors, and employees. This rule applies both inside QuickBooks and when syncing with Novi AMS.

If a record in Novi has the same Display Name as an employee in QuickBooks Online, a sync conflict will occur, preventing data from being transferred properly. While this error can affect any customer/member record, it is most commonly seen with admin records.

How Novi Handles This Conflict

To allow the sync to proceed, the Onboarding Specialist manually appends "(C)" to the Display Name of the conflicting record in Novi. However, this is only a temporary fix, and the issue should be properly resolved before launch to avoid displaying "(C)" in places like directories, committees, or event contacts.

Steps to Resolve the Conflict

To permanently fix this issue, follow these steps:

  1. Update the employee name in QuickBooks Online.

    • First, please note: Before modifying an employee’s name in QuickBooks, consult with your accounting or payroll team. Changes to employee names can impact payroll reports or third-party integrations.

    • Modify the employee’s Display Name so that it no longer matches the customer/member record in Novi. Options include:

      • Adding a middle initial to the employee’s name.

      • Slightly modifying the spelling of the name.

  2. After updating in QuickBooks, remove "(C)" from the Display Name in Novi.

    • Once the conflict is resolved in QuickBooks, go to the affected record in Novi AMS and restore the original Display Name.

By following these steps, you can ensure smooth synchronization between Novi AMS and QuickBooks Online while keeping your records accurate and properly formatted.

Did this answer your question?