Learn about common errors and messages you might encounter when submitting license, appointment, or termination transactions.
Select the section below to jump to your action error list:
- Licensing
- Appointing / Terminations
- Address and Contact Change Requests
- Completing the Producer Detail Record
Status vs. Status Detail
When submitting transactions in AgentSync, there should be both a Status (2) and a Status Detail (1) on the record to indicate whether or not the transaction was successful. The status shows just that - the status of that particular transaction. The status detail provides additional information as to why the status is what it is.
This article only refers to the Status Detail (1) of a transaction. For information on what each status means, click here to learn more.
Licensing
AgentSync Tip: These are the errors most commonly found under the "NIPR status detail." To learn what the different AgentSync status messages mean, please click here.
| NIPR Status Detail Message | Meaning and Next Steps |
| Not Eligible: The NIPR response indicates that the agent is not eligible for this transaction. | This is NIPR's catch-all for any state rule related ineligibility. Please see here for the top 5 reasons you would see this message. |
| Action Required: After your license has been issued but PRIOR to representing a business entity, you must be affiliated. | This one is particularly baffling for customers, especially if you already did the steps detailed in this message. This is Washington's auto-response, meaning that you will receive this message no matter what. We recommend that you confirm that you completed the steps detailed in the message. If so, you are free to disregard. The transaction will show as approved once the license is renewed or issued. |
| Applicant.Owner.Title must not be blank (1) | This error indicates that one of the owners listed on your entity's producer detail record does not have a title. Navigate to the producer detail and updated the owner's title. |
| Fault occurred while processing. The date of birth invalid. | The date of birth for this producer is incorrect. Please confirm the producer's date of birth and fix the error on their agent record. |
| {messageTemplateData":null,"messageTeemplate":null,"message":"The following issues must be resolved prior to creating this batch:/n - FLORIDA RULE: Owner address is required for licensing transactions. One or more addresses is missing in one or more fields./n - FLORIDA RULE: Owner address is required for licensing transactions. One or more addresses is missing one or more fields."} | Are you applying for or renewing a FL entity license? You must ensure that you have an address for your owner. You can find how to add an address for Owners, Partners, and Directors here. |
| You have entered a phone or fax number that begins with '1'. This number is invalid. Please enter a valid phone or fax number. | The fax number on your producer detail record does not match what is in NIPR. It is common that a customer will put down a fake number for fax, but this is not universally accepted. Please update the fax number in your AgentSync org by following these instructions: https://help.agentsync.io/manage-producer-details |
| Not eligible: No matches were found in the NIPR response. |
|
| Eligibility Error: Authentication Failed | This is related to your NIPR credentials and you must reset your password. Follow the instructions detailed here and reach out to support@agentsync.io to get this taken care of. |
| <<State>> has not been implemented on NIPR for this transaction type | This state likely shut down their PDB gateway to make updates. Confirm with support@agentsync.io and we can let you know if there are any state based updates that resulted in this gateway being turned off. |
| 1.) Non_Uniform.Key_Value must not be blank (1) 2.) Non_Uniform_value must not be blank (1) 3.) Missing State Specific Question 1 (4) | This producer detail is missing the response to a background question. Check the producer's biographic information to confirm that it shows the correct agent types (ex: adjuster, producer, surplus). If not, please add the correct Agent type and ask the customer to submit any incomplete background questions. |
| NIPR is not responding with confirmation of receipt. Please submit at a later date or reach out to AgentSync support (support@agentsync.io) for review | This is related to an NIPR timeout or outage. Please close the transaction and try again when the timeout has passed. You may need to re-sync the NPN, which you can find instructions to here. |
| httpresponse status code 403 - forbidden | This is related to an NIPR timeout or outage. Please close the transaction and try again when the timeout has passed. You may need to re-sync the NPN, which you can find instructions to here. |
| 404 or 405 error | This is likely related to password changes with NIPR credentials. Please reach out to support@agentsync.io to have it taken care of. |
| TIMEOUT: Transaction submitted to NIPR. Response is pending. | This is related to an NIPR timeout or outage. Please close the transaction and try again when the timeout has passed. You may need to re-sync the NPN, which you can find instructions to here. |
| Address does not match records. Address type(s) that failed to match: 'Resident', 'Business', 'Mailing'. (35). | This can happen if the address in AgentSync does not match the address in NIPR. Simply click the "retrieve NIPR address" button and this will do a real-time call to NIPR for your producer's address. |
| 1.) Valid country code must be entered. In APPLICANT.EMPLOYMENT_HISTORY. (94852) | This can happen if a producer selects any other country besides USA in the employment history section of the Producer Detail record. If the producer worked in a US Territory (such as Guam, Puerto Rico and/or the Virgin Islands), USA should still be selected as the country code. |
| 1.) Country code must be valid. In APPLICANT.EMPLOYMENT_HISTORY. (85081) |
This can happen if a producer selects any other country besides USA in the employment history section of the Producer Detail record. If the producer worked in a US Territory (such as Guam, Puerto Rico and/or the Virgin Islands), USA should still be selected as the country code. |
| 1.) Only one Colorado licensed responsible producer must be listed on the application. |
Some states only allow for one Designated Responsible Producer (DRLP) to be listed on a license application. If there are multiple DRLPs for different states listed when the transaction is submitted to a state that only allows for one DRLP, it will error out. To resolve, close out the original license transaction, remove all DRLPs except the on needed for that state, submit a new license transaction, and add the other DRLPs back onto the record.
|
| 1.) Only one applicant is allowed per transaction (4) 2.) At least one Applicant Address is required (1) 3.) APPLICANT.ATTESTATION must not be blank (1) 4.) APPLICANT.COUNTRY_CODE must not be blank (1) 5.) Missing Business email address (4) 6.) APPLICANT.LICENSE_KEY.LICENSE_ID must not be blank (1) 7.) Invalid License ID submitted for APPLICANT.LICENSE_KEY.LICENSE_ID. License ID must not contain a forward slash '/' character. (1) 8.) APPLICANT.LICENSE_KEY.RES_STATE must not be blank (1) 9.) Missing Primary Name (4) 10.) Missing Business Phone Number (4) 11.) APPLICANT.TAX_NUM must not be blank (1) 12.) APPLICANT.TYPE must not be blank (1) 13.) AUTHORIZATION.PREPARER_CODE must not be blank (1) 14.) Only one license is allowed per transaction (4) 15.) LICENSE.LICENSE_CLASS must not be blank (1) 16.) At least one License LOA Code is required (1) |
This long list of errors indicates an NIPR timeout. This can be confirmed by looking at the information in the Audit Log section at the bottom of the transaction. The Status in the Audit Log section will read "Error" and will include a message that indicates the transaction was submitted to NIPR but we are pending a response. To resolve - close out the transaction and try to resubmit again in 10-15 minutes. |
Looking for a full dictionary of NIPR response codes? Click here to access.
Appointing / Terminations
AgentSync Tip: These are the errors most commonly found under the "NIPR status detail." To learn what the different AgentSync status messages mean, please click here.
| NIPR Status Detail Message | Message Meaning | Details & Next Steps |
| 1.) APPLICANT.TAX_NUM must not be blank (1) | This state requires a social security number to appoint. | This state requires a social security number to appoint. Reach out to the producer requesting their social security number (securely, of course), and add it to their contact record. Once you add their social security number, reapply for the appointment |
| 1.) Applicant SSN not on record. (86294) | ||
| 1.) Affiliated Producer needs appointment (999), 2) Passed business rule processing. (10007) | The state rules require that an affiliated producer is appointed before an entity can be appointed. | This message is likely from Michigan, which requires all entities to first appoint an affiliated producer. Both the agency and each individual affiliated producer must be appointed. The affiliated producer's individual appointment must be in place before submitting firm appointment. |
| "1.) Passed business rule processing. (10007) 2.) Active appointment was not found between license #XXXXXXX (Insurance Producer) and company NAIC #XXXXX (999)" |
The producer does not have the required active license. | This message surfaces when the producer does not have the required license for this appointment. Confirm that this producer holds an active license in the correct state and line(s) of authority. Reach out to the producer to ensure that they renew or reapply for their license. Once the new license is issued, reappoint. |
| "1.) Appointment requires an active License with either a future expiration date or no expiration date. (999) 2.) Passed business rule processing. (10007)" |
||
| Appointee's license expiration date is in the past. Please renew the license before applying for an appointment. (102519) | ||
| 1.) APPLICANT.ADDRESS.ADDR_LINE_1 must not be blank (1) 2.) APPLICANT.ADDRESS.CITY must not be blank (1) 3.) APPLICANT.ADDRESS.STATE_CODE must not be blank (1) 4.) APPLICANT.ADDRESS.ZIP_CODE must not be blank (1) |
This producer does not have an address on file with NIPR | NIPR does not have all 3 required addresses on file for this producer. In order to complete this appt/term, the producer will need to have all 3 addresses on file with NIPR. They can do this by reporting the address to NIPR and we will pick it up in our sync. If you license and appoint, you can submit a contact change request for this producer and the new address will be picked up once it is issued. |
| 1.) No appointment exists to terminate. (123029) | There is no appointment on file | This message surfaces when there is no appointment on file. Confirm with your team that this appointment has not already been terminated. If not, it may be related to changes in state rules - reach out to support@agentsync.io or check your emails from AgentSync to determine if you need to make some changes to your AgentSync org to accommodate state rule changes. |
| "1.) Reactivate/inactivate Appointment is missing its original record. (999) 2.) Passed business rule processing. (10007)" |
||
| Appointment does not exist for requested termination | ||
| 1.) There must be an active appointment between the appointer and appointee (13323) | ||
1.) Appointment does not exist for requested termination. (77392) |
||
| 1.) Appointment Already Canceled (999) 2.) Passed business rule processing. (10007) |
||
| Appointer not on record. License number (from state company id) 'XXXXX' not found for state code FL. (XXXXXX) | ||
| Appointment must exist. (XXXX) | ||
| Error CodError Code: 1 Description: Unable to process transactions at this time : System error. Gateway transaction id: Transaction ID not available. Customer id: XXXXX Customer transaction key: Cust Batch: GB-00029512; Cust Trans GT-00072935 Line number of transaction in XML: 1 Ordinal position of transaction in XML: 1 error id: e80ccda6-8376-4f26-b890-162b2a927d6f.e: 1 |
There is an issue with the NIPR gateway for this transaction. | There was a timeout with NIPR. We recommend resubmitting the transaction. |
| "Error Code: 201 Description: Transactions for this state and transaction type are not being admitted into the system because they are switched off. Gateway transaction id: Transaction ID not available. Customer id: XXXXXX Customer transaction key: Cust Batch: GB-00028718; Cust Trans GT-00069959 Line number of transaction in XML: 1 Ordinal position of transaction in XML: 15 From file: realtime_20220102220459745 From entity: XXXXXX" |
There is an issue with the NIPR gateway for this transaction. | This is when a state turns off transactions for a period of time due to maintenance or conversion to a new system. Look at the NIPR bi-weekly updates or support@agentsync.io to determine how long this outage will be. |
| 1.) Appointee does not have a record of an appointment with appointing firm. | Confirm that your FL appointment is appointed with the state before the county. | This is a tricky one! Florida requires that you apply for an appointment for the state first and the county. When appointing with Florida, a pop up will display asking which county. Select, select none for non-resident and all for resident appointment. For residents who are physically selling a policy in a specific Florida county, you can appoint by county. |
| Appointee Tax ID does not match. | Confirm that your producer's social security number is correct in AgentSync or in NIPR. | "TaxID" refers to the customer's social security number. The producer has a discrepancy between the social security number that they inputted and the social security number in NIPR. Please reach out to the producer to confirm their correct social security number. |
| 1.) Appointment already exists. (927) | This appointment is a duplicate | This message usually pops up when an appointment is a duplicate. First, confirm that you submitted the correct appointment for the correct state and correct lines of authority. Check the NIPR transactions for this producer to confirm whether the appointment was already submitted and confirm that this producer does not already have this appointment. If that looks good, check in with your team that the producer's appointment was not already submitted (in our out of AgentSync). |
| 1.) Appointment cannot be added because it already exists. (999) 2.) Passed business rule processing. (10007) | ||
| "1.) The appointment is already processed. (999) 2.) Passed business rule processing. (10007)" |
||
| 1.) A transaction has already been successfully submitted for this appointee and appointer. NIPR Trans: XXXXXXX (107567) | ||
| 1.) Appointment requires an approved Authorized Line for the company. (999) 2.) Passed business rule processing. (10007) | Reach out to AgentSync Support to help you with this issue. | "This error can occur if the appointment's metadata is turned off. Metadata is initially configured during implementation, but it is common that certain lines can be turned off by accident. Reach out to support@agentsync.io and we will resolve this issue immediately. |
| 1.) APPLICANT.LICENSE_KEY.LICENSE_CLASS - Invalid value '1007' (2) | The license class code is incorrect | This happens commonly when states change systems and update business rules. AgentSync audits changes frequently to ensure that our rules reflect the new rules. Very rarely, a state will change their rules prior to their announced launch date. Reach out to AgentSync to confirm when these rules will be changed. |
| 1.) APPLICANT.STATE_COMPANY_ID must not be blank (1) | The company state settings are missing a key datapoint | This state requires a company ID. Go to the company state settings on your company page and find the state that you seek to appoint. Make sure that the license ID field is filled out (you can find this informaiton through a carrier report in NIPR). Add iorad |
| 1.) APPOINTER.LICENSE_KEY.RES_STATE must not be blank (1) | Whenever you see the word "appointer," this is usually related to your company record and company state settings. If you see this message, confirm that your company record has a resident license listed. | |
| Appointer's License Number does not match records. No licenses found for license ID (XXXXXX) | Whenever you see the word "appointer," this is usually related to your company record and company state settings. If you do not see a license ID when looking up your company record (which you can look up here) input your company state ID credentials in the correct field. | |
|
1) Appointer and appointee do not share a common line. (5502) |
The producer does not have the correct lines of authority. | Please check your producer's license to confirm that they hold the correct lines of authority for your specific company. If they do, please update your company record to include the correct line of authority category. |
|
1.) The appointer and appointee must share a common authority (13293) |
||
| 1.) Applicant name does not match records. (45682) | The producer's name in AgentSync does not match the producer's name in NIPR. | AgentSync pulls the name of the applicant from the contact or account record. However, there can be some differences from what NIPR has on file (which can be found on the producer detail record). To fix this issue, change the name on the account or contact record to match the producer detail record. Click the link to view instructions on how to fix this error: https://ior.ad/7YC2 |
| Appointee name does not match records. (77370) | ||
| 1.) Only one applicant is allowed per transaction (4) 2.) APPLICANT.TYPE must not be blank (1) 3.) Only one appointer is allowed per transaction (4) 4.) APPOINTER.TYPE must not be blank (1) 5.) License class is required. (1) 6.) Appointee license number is required. (1) 7.) Applicant first and last names are required. (1) 8.) APPLICANT.TYPE must not be blank (1) 9.) Appointer's Co-Code is required. (1) 10.) Appointer's license ID is required. (1) 11.) Appointer's name is required. (1) 12.) Appointer's Tax Id is required. (1) 13.) ASSUMED_STATE_FEE must not be blank (1) 14.) AUTHORIZATION.FIRST_NAME must not be blank (1) 15.) AUTHORIZATION.LAST_NAME must not be blank (1) 16.) AUTHORIZATION.PHONE.PHONE_NUMBER must not be blank (1) 17.) AUTHORIZATION.TITLE must not be blank (1) 18.) LICENSE.LOA.LOA_CODE must not be blank (1) |
This long list of errors indicates an NIPR timeout. This can be confirmed by looking at the information in the Audit Log section at the bottom of the transaction. The Status in the Audit Log section will read "Error" and will include a message that indicates the transaction was submitted to NIPR but we are pending a response.
|
Close out the transaction and try to resubmit after 10-15 minutes. |
Still having issues? Email us at support@agentsync.io and we are happy to help troubleshoot!
Looking for a full dictionary of NIPR response codes? Click here to access.
Address and Contact Change Requests
| NIPR Status Detail Message | Meaning & Next Steps |
| Valid Business Address is Required | This error likely occurred due to a state requirement. We see this most frequently if a state does not allow a P.O box or a business address from a state that is different than the resident address. Please fix the error and submit a new contact change request. |
| There were errors syncing with NIPR. Fault occurred while processing. The "taxnum" element is invalid | "Taxnum" refers to the customer's social security number. The producer has a discrepancy between the social security number that they inputted and the social security number in NIPR. Please reach out to the producer to confirm their correct social security number. |
| null input to JSON parser (system code) | This may be related to a NIPR outage. Please email support@agentsync.io and we will respond with appropriate next steps. |
|
First name is required Last name is required Birth Date is required Resident License Number is Required Valid Resident Address is Required Valid Mailing Address is Required Valid Business Address is Required |
This may be related to a duplicate producer detail record. This can happen occasionally when the producer detail record flow was exited out of before completion. Simply search the producer's name and find the duplicate record. Then, delete the one with the least information. |
| There were errors syncing with NIPR. Fault occurred while processing. Could not send message. HTTP response '401 Unauthorized' when communicating with https://gateway-contact-change-service-direct.api.nipr.com/gateway-contact-change-service/api | This is due to a NIPR timeout. Click the "Retrieve NIPR Address" button in AgentSync under the "Contact Information" on your producer detail record. That should resolve the issue. If not, reach out to support@agentsync.io |
| Producer has pending NIPR transactions. Contact change cannot be submitted at this time. | This occurs when a contact change request is submitted when a license is pending state review. Please wait until the license is approved before submitting any contact change requests. |
| Address does not match records. Address type(s) that failed to match: Resident Address, Business Address | Select the "Retrieve NIPR Address" button in AgentSync under the "Contact Information" on your producer detail record. That may help resolve the issue. If not, reach out to support@agentsync.io |
|
There were errors when syncing with NIPR: Error for address code 3: Resident licensees must not change the state code of the address using this application. Please contact the state directly. |
When a resident license changes from one state to another, an address change must be submitted directly to the new resident license state. After this is complete, NIPR and AgentSync will both recognize the update and allow you to transact. |
Still having issues? Email us at support@agentsync.io and we are happy to help troubleshoot!
Looking for a full dictionary of NIPR response codes? Click here to access.
Completing the Producer Detail Record
| NIPR Status Detail Message | Message Meaning | Details & Next Steps |
| Applicant.Owner.Title must not be blank | This error indicates that one of the owners listed on your entity's producer detail record does not have a title. |
Want to see a visual step-by-step walkthrough of this process? Click here to login and see! Step 1: Navigate to your entity's Producer Detail record by typing the name in the Global Search Bar and clicking the producer detail record. Step 2: Click the name of your entity that has the label Producer Detail beneath the name AgentSync Tip: Don't see your producer's Contact or Account record in the preview? Try clicking "Show more results for" at the bottom of the preview. Step 3: On the Producer Detail record, scroll down to the section titled Owners, Partners, Officers and Directors Step 4: Click the arrow on the right side of the line next to the owner you would like to add the title for. Then, click the option to Edit. Step 4: Add your title to the Title field. Step 5: Click Save And you should be all set! Try to reapply for that license! Click here for a walkthrough of this process! |
| Valid Business Address is Required |
This error likely occurred due to a state requirement. We see this most frequently if a state does not allow a P.O box or a business address from a state that is different than the resident address. Please fix the error and submit a new contact change request. |
|
| There were errors syncing with NIPR. Fault occurred while processing. The "taxnum" element is invalid |
"Taxnum" refers to the customer's social security number. The producer has a discrepancy between the social security number that they inputted and the social security number in NIPR. Please reach out to the producer to confirm their correct social security number. |
|
| null input to JSON parser (system code) |
This may be related to a NIPR outage. Please email support@agentsync.io and we will respond with appropriate next steps. |
|
|
First name is required Last name is required Birth Date is required Resident License Number is Required Valid Resident Address is Required Valid Mailing Address is Required Valid Business Address is Required |
This may be related to a duplicate producer detail record. This can happen occasionally when the producer detail record flow was exited out of before completion. Simply search the producer's name and find the duplicate record. Then, delete the one with the least information. |
Looking for a full dictionary of NIPR response codes? Click here to access.
Still having issues? Email us at support@agentsync.io and we are happy to help troubleshoot!