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: |
|
What happened? |
Your request timed out. |
Why did it happen? |
There’s an error with the Yodlee (third-party banking service provider) component that connects your bank’s website with Zoho Books. |
What should you do? |
Please try again. |
What happened? |
There’s an error with the values you’ve entered in Zoho Books. |
Why did it happen? |
We could not link your account as the username and/or password are incorrect according to your bank. |
What should you do? |
|
What happened? |
We couldn’t update your account due to an error with the Yodlee (third-party banking service provider) component that connects your bank’s website with Zoho Books. |
Why did it happen? |
There’s a technical issue with Yodlee’s component. |
What should you do? |
|
What happened? |
We couldn’t update your account due to an error with the Yodlee (third-party banking service provider) component that connects your bank’s website with Zoho Books. |
Why did it happen? |
There’s a technical issue with Yodlee’s component. |
What should you do? |
Please try again after 30 minutes. |
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the request was canceled. |
Possible workaround: |
|
Suggested Action: |
|
What happened? |
We could not update your account as you need to perform some actions. |
Why did it happen? |
Your bank’s website needs you to perform some additional actions at the bank’s website. |
What should you do? |
Log in to your bank’s website and see if you’re prompted for any actions. Once you make changes, try again. If you’ve updated the credentials, ensure that you update them in Zoho Books. |
What happened? |
We could not update your account as your account might have been locked. |
Why did it happen? |
This usually happens when there are too many unsuccessful login attempts in a short period. |
What should you do? |
Please visit the bank’s website to resolve this issue. Once you resolve it, please try again. |
Type of Error: |
Agent |
Description: |
There were no accounts found at the site. |
Possible workaround: |
|
Suggested Action: |
|
What happened? |
We could not update your account due to an error with the bank’s website. |
Why did it happen? |
The bank’s website could be down or inaccessible. |
What should you do? |
Please write to support at support.usa@zohobooks.com. |
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: |
|
What happened? |
We could not update your account due to an error with the bank’s website. |
Why did it happen? |
The bank’s website could be having technical issues. |
What should you do? |
Please write to support at support.usa@zohobooks.com. |
What happened? |
We couldn't update your account due to an error with the Yodlee (third-party banking service provider) component that connects your bank’s website with Zoho Books. |
Why did it happen? |
There’s a technical issue with Yodlee’s component. |
What should you do? |
Please write to support at support.usa@zohobooks.com and we will check this with Yodlee, our third-party service provider. |
What happened? |
We could not find your account at the bank’s website. |
Why did it happen? |
You may have selected a similar bank name under a different category or it could be due to a change in your bank’s website URL. |
What should you do? |
To confirm that it’s the correct bank:
|
What happened? |
We could not update your account due to an error with the bank’s website. |
Why did it happen? |
The bank’s website could be having technical issues. |
What should you do? |
Please write to support at support.usa@zohobooks.com. |
What happened? |
We attempted to update your account but it failed. |
Why did it happen? |
It seems like you have an active bank session in one of your devices. |
What should you do? |
Please log out from those sessions and try again. |
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: |
|
What happened? |
We could not update your account due to an error with the bank’s website. |
Why did it happen? |
The bank’s website could be having technical issues. |
What should you do? |
Please write to support at support.usa@zohobooks.com. |
What happened? |
We couldn't update your account due to a technical issue at the bank’s website. |
Why did it happen? |
There were unexpected variations on the bank's website. |
What should you do? |
please write to support at support.usa@zohobooks.com and we will check this with Yodlee, our third-party service provider. |
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: |
|
What happened? |
The bank’s website has an unsupported language. |
Why did it happen? |
The language setting in your bank’s website is not supported by the Yodlee (third-party banking service provider) component. |
What should you do? |
Please write to support at support.usa@zohobooks.com so that we can check this with Yodlee, our third-party service provider. |
Type of Error: |
User Action Required |
Description: |
The request cannot be completed because the account has been closed or cancelled. |
Possible workaround: |
|
Suggested Action: |
|
What happened? |
We could not access your account at your bank’s website. |
Why did it happen? |
Your account might not be active at the bank’s website. |
What should you do? |
Please verify at your bank’s website. If it is active, please write to support at support.usa@zohobooks.com. |
What happened? |
We were unable to update your account due to an error at your bank’s website. |
Why did it happen? |
Your bank’s website is temporarily down for maintenance. |
What should you do? |
The bank’s website should be up and running in a few hours. Please try again later. |
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: |
|
What happened? |
We could not update your account due to an issue at the bank’s website. |
Why did it happen? |
The bank’s website requires you to view a new promotion. |
What should you do? |
Please log in to the bank’s website and click through to your account overview page to update the account. Once you’ve done that, please try again. |
What happened? |
We could not update your account due to an issue at the bank’s website. |
Why did it happen? |
Your bank's website requires you to accept a new Terms & Conditions. |
What should you do? |
Please log in to the bank's website, read and accept the Terms & Conditions. Once you’ve done that, please try again. |
What happened? |
We could not update your account due to an issue at the bank’s website. |
Why did it happen? |
Your bank's website requires you to verify your personal information. |
What should you do? |
Please log in to the bank's website and update the required fields. Once you’ve done that, please try again. |
What happened? |
We are unable to connect with your bank’s website. |
Why did it happen? |
Your bank’s website is not supported for data updates anymore. |
What should you do? |
Please write to support at support.usa@zohobooks.com, we will check this with our service provider |
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 Books payment method has already been established with the biller, and it is not possible for Zoho Books 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: |
|
What happened? |
We are unable to connect with the bank’s website. |
Why did it happen? |
We’re sorry. Currently, the Yodlee component does not support the security system used by the bank’s website. |
What should you do? |
Please try again later to see if the situation has changed. |
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because new log in information is required. |
Possible workaround: |
|
Suggested Action: |
|
What happened? |
There’s an issue with the Yodlee (third-party banking service provider) component that connects your bank’s website with Zoho Books. |
Why did it happen? |
We have just started providing data updates for this website, and it may take some time to be successful as we get started. |
What should you do? |
Please wait till the website is fully developed. We’ll notify you once the website is ready. |
What happened? |
Your request timed out. |
Why did it happen? |
There’s a technical issue with the Yodlee (third-party banking service provider) component that connects your bank’s website with Zoho Books. |
What should you do? |
Please try again. |
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: |
|
What happened? |
We could not update your account due to an issue at the bank’s website. |
Why did it happen? |
The required additional authentication information was unavailable. |
What should you do? |
Please refresh the feeds and provide the authentication details. |
What happened? |
We could not update your account due to an issue at the bank’s website. |
Why did it happen? |
Your account was not updated as the authentication information like security questions and answers were unavailable or incomplete. |
What should you do? |
Please refresh the feeds and provide this information. |
What happened? |
We’re unable to connect with the bank’s website. |
Why did it happen? |
Your bank's website indicates that the additional authentication information provided is incorrect. |
What should you do? |
Please refresh feeds and provide these details. |
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: |
|
What happened? |
Your request has timed out. |
Why did it happen? |
The required security information was unavailable or was not provided within the expected time. |
What should you do? |
Please try again. |
What happened? |
We’re unable to connect with the bank’s website. |
Why did it happen? |
The authentication information provided is incorrect. |
What should you do? |
Please refresh the feeds and provide these details. |
Type of Error: |
User Action Required |
Description: |
Your request cannot be completed because the additional security information provided has expired. |
Possible workaround: |
|
Suggested Action: |
|
What happened? |
We couldn’t update your account. |
Why did it happen? |
There’s a technical issue with the Yodlee (third-party banking service provider) component that connects your bank’s website with Zoho Books. |
What should you do? |
please write to support at support.usa@zohobooks.com and we will check this with Yodlee, our third-party service provider. |
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: |
|