Summary: This guide explains how Tithely's QuickBooks Online integration creates customer records, detailing the mapping logic for mandatory fields like GivenName (First Name), FamilyName (Last Name), and the unique identifier added to the DisplayName field to automatically handle duplicate names.
Before You Begin
- At least one of the three fields (First Name, Last Name, or Email Address) is required to create a customer record.
- The integration ensures transactions are accurately recorded with the correct customer information.
How Customer Information is Handled
When syncing transactions, Tithely uses the following logic to map giver information to the required QuickBooks customer fields:
Example Mapping Scenarios
| Scenario | First Name (Tithely) | Last Name (Tithely) | Resulting GivenName (QB) | Resulting FamilyName (QB) |
| Complete Info | John | Doe | John | Doe |
| Missing First Name | (nil) | Doe | Doe | Doe |
| Missing Both Names | (nil) | (nil) | Email Address | (nil) |
Handling Duplicate Names
- Unique Identifier: To avoid the "Duplicate Name Exists" error in QuickBooks, the integration includes a unique identifier in the DisplayName field if a name match is found.
- Format Used: If a duplicate name is detected, the DisplayName will be set to: "first_name last_name (customer)
- Example: If "John Doe" already exists, the new record will be created as "John Doe (customer)".
Troubleshooting & FAQs
- What is the minimum requirement for customer creation? At least one of the three fields (First Name, Last Name, or Email Address) is required.
- Why does the name sometimes show up as the email address? This occurs when both the First Name and Last Name are missing, forcing the system to use the Email Address for the mandatory GivenName (First Name) field.
- How can I prevent duplicate customers? The integration automatically adds "(customer)" to the Display/name field for any detected duplicate names, ensuring a unique record is created and transactions are recorded.