Type of Error: |
Agent |
Description: |
Your request cannot be completed due to technical reasons. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
The request timed out before completing due to delays beyond our control. We apologize for the inconvenience. Please try again. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
A 402 error indicates that your credentials need to be reverified. You must log in to the bank site, verify the credentials and ensure that the same credentials are submitted to Zoho Expense. There is no workaround for this issue if you have submitted the wrong credentials. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Represents a general script failure. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Temporary technical difficulties are causing the problem. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the request was canceled. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The member's password has expired. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
A script tried to log in, but your account is locked. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
There were no accounts found at the site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
Indicates that a site has reported that its service is temporarily unavailable. 4x applications have support only for error codes from 401to 409. Code 412maps to code 409in the 4x environment. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because of technical difficulties. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
Request cannot be completed because the bank's site no longer provides online services to its customers. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The bank's site displays an application error message ("Out of Memory", "Java Servlet Errors", "VB Script Error") |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed due to unexpected variations at the bank site. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the requested account was not found at the site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed due to technical difficulties at the bank's site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed as another session was already established at the same time. Note this error can appear in the following scenarios:
|
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because this type of account is not currently supported. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because of technical difficulties at the bank's site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
The request cannot be completed because of unexpected variations at the site. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the bank's site has merged with another site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the language setting for the account is not English. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the account has been closed or cancelled. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because the information for your account was unavailable. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
Your request cannot be completed as the sites are temporarily down for maintenance. This problem is typically resolved in a few hours. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because of technical difficulties at the bank's site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because of technical difficulties. This problem is typically resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed as the site requires you to view a new promotion. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the bank's site requires that you accept new terms and conditions. 4x applications have support only for error codes from 401 to 409. Code 412 maps to code 406 in 4x environment. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the site is no longer supported for data updates. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
THe request cannot be completed because the site is no longer supported for data updates. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because of technical difficulties at the site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed due to technical difficulties. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed as the attempt to AutoReg to the site was only partially successful. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
UAR |
Description: |
The request cannot be completed because the auto-registration was not completed. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the auto-registration was not completed. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the account being registered is already registered at the bank's site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed as the site limits the number of payments made with a certain time period. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because there is no balance to be paid. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
The request cannot be completed due to technical difficulties. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because some additional setup is required.. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because you are currently enrolled in automatic payments and the bank does not allow one-time payments. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because some of the payee information was not accepted at the site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because some of the payment account information provided was not accepted at the site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
The request cannot be completed due to a technical issue. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because there is an outstanding balance that needs to be paid before automatic payments can be set up. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because of an existing one-time payment enrollment at the site.. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed due to technical difficulties at the source site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because of technical difficulties at the source site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
The request cannot be completed due to technical difficulties. This error is usually resolved in a few hours. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
The request cannot be completed because the actual amount paid did not match the amount that was asked to be paid. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the payment information that was provided was not accepted at the site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the address on record for the payment account does not match the address stored at the site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
The request cannot be completed because of technical difficulties. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because this service is no longer supported for this site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because this service is no longer supported for this bank site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
The request cannot be completed because this service is no longer supported for this bank site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Site |
Description: |
Your request cannot be completed as this service is no longer supported for this site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because a similar payment was made recently. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the email address is invalid. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the amount entered was not accepted. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the card was not accepted. This error occurs when the security code (a unique 3 or 4-digit number printed on the back of the credit card) does not match the credit card number. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the bank site does not accept the submitted credit card type (Visa, Mastercard, Amex) in the geographic region. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request to enroll in automatic payments cannot be completed. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request to unenroll in automatic payments cannot be completed.. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the site does not accept direct payments in this geographic region. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the site does not accept online payments for certain account types. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the bank site does not support enrollment in recurring payments in a particular region. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the site does not support enrollment in automatic payments for certain account types. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because of insufficient funds in the payment account. This error occurs when a debit card is used instead of a credit card. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the payee site requires you to contact customer support. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because permission to make payments has not been granted. This error occurs because another individual is listed as the primary account holder. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the account cannot be automatically registered online. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the account was only partially automatically registered. This error occurs if the account was auto-registered without specifying either a username or password. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the account was partially auto-registered. This error occurs if your auto-registration to your mobile phone was incomplete. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed because of an unexpected variations at the site. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed because of unexpected variations at the site. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed because of unexpected variations at the site. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed because of unexpected variations at the site. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed because of internal technical difficulties. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the account is past due date. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed due to security reasons. There is a limit on the number of unsuccessful attempts to register in a day. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the billing telephone number was not entered. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed as the telephone number added is already taken. This error occurs for this specific Verizon use case, which itself is due to the data feed with Verizon. Once you successfully add a Verizon member item (using BTN a), you are given the option to add another BTN to the member item (BTN b). Yet the number entered is already registered under (BTN a). |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed as the account is being handled by a third party corporation. This error applies to all situations where a non-Zoho Expense payment method has already been established with the biller, and it is not possible for Zoho Expense to replace that method. This error applies to all agent activity types. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed as the online accounts in your region are not supported. Verizon has transferred control of Verizon Hawaii to Hawaiian Telecom. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed as the account type is not supported. The Verizon "residential" website does not allow other known account types like business, wholesale, enterprise, or federal. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the security system used by the bank site is not supported. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because new log in information is required. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed because of the problem in updating the account. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed because the required security information could not be retrieved within the given time. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed as the device information provided is no longer valid at the site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the site is unable to find the property information. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed as the site is unable to provide the home value for your property. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed as no payees were found in your account. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request could not be completed because payees could not be retrieved. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed because payee details could not be retrieved. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the payment account was not found. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed due to technical difficulties. This error is usually resolved in a few days. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed due to incomplete or incorrect additional security information. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed as security credentials are required to log in to the site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
UAR |
Description: |
Your request cannot be completed due to incorrect security credentials. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed as the required information is missing in the security authentication site. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the request timed out. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because of incorrectly added security information. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the additional security information provided has expired. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
User Action Required |
Description: |
The user name/password or the additional security credentials provided are incorrect. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed because the response data is insufficient. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
A validation error is thrown when data format/range is invalid for the fields in the data model. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Represents a general script failure. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Represents a general script failure. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
Agent |
Description: |
Your request cannot be completed as the account has never been updated. |
Possible workaround: |
|
Suggested Action: |
|
Type of Error: |
None |
Description: |
Your request cannot be completed because the refresh has not been completed even after the credentials of this item were updated. |
Possible workaround: |
|
Suggested Action: |
|