Rows from import files will appear as an error when there are problems with customer fields, payment account fields, payment transaction fields, and recurring payment transaction fields. Some of these errors will cause the entire row to be discarded, and others will allow a new Customer Record to be added and cause only the payment or payment schedule entry to fail.
There are many possible errors that can occur in import files. The Error Messages section of the Import Details screen provides a detailed explanation for each failed row. The following are some of the most common errors that occur for each Import type:
Customer with a User ID (User Name) that already exists in the system.
The entire row will fail and the Customer Record will not be added.
Invalid U.S. state abbreviation or zip code.
The entire row will fail and the Customer Record will not be added.
Invalid bank routing number.
The Customer Record will be added, but the bank account will not.
Invalid credit card number or credit card type.
The Customer Record will be added, but the credit card account will not.
Invalid credit card expiration date.
The entire row will fail, and the Customer Record will not be added.
Invalid value '{value}' given for drop-down custom field '{Field Name}'. Provide a valid value (not display label) as defined in the custom field setup.
The entire row will fail, and the Customer Record will not be added.
NOTE: Values in custom drop-down fields are cases sensitive, so if you see this error double check your data. For example, if you have a custom field configured with a display text of “Large” and a value of “L” and you enter “l” for the field in your import file, the import row will fail. It will also fail if you enter “Large” in the field. The only valid import value is a capital “L.”
“Insufficient customer information. Customer Identifier or Full customer information must be provided.”
The entire row will fail and the Customer Record will not be added.
NOTE: This error can occur if you do not a First Name and/or a Last Name for a Customer Record, or if you include only part of a billing address (i.e. including zip code but not the rest of the address.) (See Customer Import Requirements.)
This error also occurs when you have a stray row at the end of your file in which one cell contains a space. To eliminate this error, delete all rows after your last row of data prior to saving the file.
“Current user does not have enough rights to execute this operation”
This occurs if the Role assigned to the User attempting the import does not have sufficient permission to complete all components of a new customer import.
NOTE: To eliminate this error, assign the User the “Admin” role. Or make sure that the role assigned to the User contains the “Collect Payments & Send Invoices,” “Modify Payments & Invoices,” and “Manage Customers” permission. If any of those three are missing, this error may occur. (See Role Components for details on permissions.)
“Customer ID does not match any Customers of this Client.”
The Customer ID provided in the row does not belong to any of your customers. The payment is not processed.
“Invalid value for item: PaymentSubType.”
This error is only applicable to Echeck (ACH) payments. It means that you did not enter a valid ACH Type for the payment. Valid ACH Types are PPD, CCD, WEB, and TEL. The payment is not processed. If this row contained data for adding a new customer, and this was the only error, the new Customer Record will be created.
The Payment Amount is 0 or negative.
The payment is not processed. If this row contained data for adding a new customer, and this was the only error, the new Customer Record will be created.
Insufficient customer information.
This error occurs when data is not provided for all fields required for the Customer Record. (See Customer Import Requirements.) The payment is not processed and the Customer Record is not added.
Invalid bank routing number.
The entire row fails. The payment is not processed and the Customer Record is not created.
Invalid credit card number or credit card type.
The entire row fails. The payment is not processed and the Customer Record is not created.
Invalid credit card expiration date.
The entire row fails. The Customer Record is not added and the payment is not processed.
Company Name is required for all CCD transactions.
This error occurs when you enter “CCD” as the ACH Type and do not include a value for company name. The entire row fails. The Customer Record is not added and the payment is not processed.
Invalid value '{value}' given for drop-down custom field '{Field Name}'. Provide a valid value (not display label) as defined in the custom field setup.
The entire row fails. They payment is not processed and the Customer Record is not created.
NOTE: Values in custom drop-down fields are cases sensitive. If you see this error re-check your data.
“The given key was not present in the dictionary.”
This error appears for a row without data. It often occurs when you have a stray row at the end of your import file in which one cell contains a space.
NOTE: To eliminate this error, delete all rows after your last row of data prior to saving the file.
“Current user does not have enough rights to execute this operation”
This occurs if the Role assigned to the User attempting the import does not have sufficient permission to complete all components of a new payment import.
NOTE: To eliminate this error, assign the User the “Admin” role. Or make sure that the role assigned to the User contains the “Collect Payments & Send Invoices,” “Modify Payments & Invoices,” and “Manage Customers” permission. If any of those three are missing, this error may occur. (See Role Components for details on permissions.)
“Customer ID does not match any Customers of this Client.”
The Customer ID provided in the row does not belong to any of your customers. The schedule is not entered.
“Invalid value for item: 'PaymentSubType.”
This error is only applicable to schedules with an Echeck (ACH) payment method. It means that you did not enter a valid ACH Type for the payment. Valid ACH Types are PPD, CCD, and WEB. The schedule is not entered. If this row contained data for adding a new customer, and this was the only error, the new Customer Record will be created.
Recurring Amount is 0 or negative.
The schedule is not entered. If this row contained data for adding a new customer, and this was the only error, the new Customer Record will be created.
Invalid schedule start date.
The start date is not provided, or it is in the past. The schedule is not entered. If this row contained data for adding a new customer, and this was the only error, the new Customer Record will be created.
Invalid custom first payment date.
The custom first payment date is not provided, or is in the past. The schedule is not entered. If this row contained data for adding a new customer, and this was the only error, the new Customer Record will be created.
Insufficient customer information.
This error occurs when data is not provided for all fields required as part of the Customer Record. The schedule is not entered and the Customer Record is not created.
Invalid bank routing number.
The entire row fails. The schedule is not created and the Customer Record is not added.
Invalid credit card number or credit card type.
The entire row fails. The schedule is not created and the Customer Record is not added.
Invalid credit card expiration date.
The entire row fails. The schedule is not created and the Customer Record is not added.
Company Name is required for all CCD transactions.
This error occurs when you enter “CCD” as the ACH Type and do not include a value for company name. The entire row fails. The Customer Record is not added and the schedule is not created.
Invalid value '{value}' given for drop-down custom field '{Field Name}'. Provide a valid value (not display label) as defined in the custom field setup.
The entire row fails. The schedule is not created and the Customer Record is not added.
NOTE: Values in custom drop-down fields are cases sensitive. If you see this error re-check your data.
“The given key was not present in the dictionary.”
This error appears for a row with out data. It typically occurs when you have a stray row at the end of your import file in which one cell contains a space.
NOTE: To eliminate this error, delete all rows after your last row of data prior to saving the file.
“Current user does not have enough rights to execute this operation”
This occurs if the Role assigned to the User attempting the import does not have sufficient permission to complete all components of a new recurring payment import.
NOTE: To eliminate this error, assign the User the “Admin” role. Or make sure that the role assigned to the User contains the “Collect Payments & Send Invoices,” “Modify Payments & Invoices,” and “Manage Customers” permission. If any of those three are missing, this error may occur. (See Role Components for details on permissions.)
“Line item with “{item name}” already exists.”
This error appears if you attempt to import an item that has the same “Item Name” as an existing item. All Item Names must be unique.
“Item 'Price' is not in valid format. Must be a NON-negative monetary value in U.S. Dollars ('3.00')”
This error appears if you enter anything but a positive or negative number, or 0 (or leave the field blank) in the Item Price field.