Error Messages Returned from iFinance Upon Export
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the bill and information to iFinance. However, there are occasions when the export fails and Lightyear displays the reason for the error - you will see a warning message with information like the below, directing you to view the document's Activity History.
Here are some of the most common errors Lightyear receives, presented in [brackets]:
Failed to export invoice [Line 1 TAX_CODE_IS_NULL]
A Tax Code needs to be set on each line on the bill.
Return the bill to Approvals, and select a Tax Code for the line giving the error message.
You should now be able to export to iFinance.
Failed to export invoice [The specified stock GL account code does not exist or is not a Posting account. Please create it first before attempting to use it.]
The chosen GL code in Lightyear either does not exist in iFinance, or is set to a Control account in the General Ledger.
If it does not exist, it will need to be created.
If it is set to a Control account, you can either change it to Posting, or select another GL code in Lightyear.
Failed to export invoice [No Service Item found. Please select a service item from the dropdown in Accountancy Software Settings]
You have not selected a Default Service Item during the account setup. Go to Accountancy Software > Accountancy Software Settings, and under Default Service Item, select from the dropdown.
Check out our
to stay up to date
Related Articles
Error Messages Returned from iplicit Upon Export
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the bill and information to iplicit. However, there are occasions when the export fails and Lightyear displays the reason for the error ...Error Messages Returned from accountsIQ Upon Export
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the bill and information to accountsIQ. However, there are occasions when the export fails and Lightyear displays the reason for the ...Error Messages Returned from Sage Business Cloud upon Export
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the bill and information to Sage Business Cloud. However, there are occasions when the export fails and Lightyear displays the reason ...Error Messages Returned from Microsoft Dynamics Business Central upon Export
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the Bill and information to Business Central. However, there are occasions when the Export fails and Lightyear displays the reason for ...Error Messages Returned from Sage Intacct upon Export
Lightyear has a ton of built in validation checks to ensure the data is correct in Lightyear before trying to send the bill and information to Sage Intacct. However, there are occasions when the export fails and Lightyear displays the reason for the ...