Skip to main content

Error Messages Returned from Sage Intacct upon Export

Identify and resolve export errors between Lightyear and Sage Intacct

J
Written by Jessica Callaly

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. Export errors between Lightyear and Sage Intacct can occur due to configuration issues or integration problems.

If an export fails and Lightyear displays the reason for the error, you will see a warning message with information like the following, directing you to view the document's Activity History.


Common Export Issues

When exporting invoices from Lightyear to Sage Intacct, you may encounter errors such as:

  • Rejected exports

  • Exports that appear to do nothing without showing specific error messages

These issues are often related to configuration settings or integration connectivity.

Configuration Settings in Sage Intacct

One common cause of export errors is incorrect configuration of the 1099 flag in Sage Intacct. To resolve this:

  1. Navigate to Accounts Payable in Sage Intacct.

  2. Select Configure Accounts Payable.

  3. Scroll to the 1099 section.

  4. Enable the option to override the 1099 flag on an AP line item.

  5. Save your changes.

This setting ensures that transactions involving 1099 handling are processed correctly, reducing the likelihood of export errors.

Integration Verification Steps

Another common issue arises when the integration between Lightyear and Sage Intacct is disrupted. To verify and re-establish the connection:

  1. Check if your Lightyear account is still connected to Sage Intacct.

  2. If the connection is broken, disconnect and then reconnect the integration.

  3. Ensure that the user performing this action has admin privileges in both Lightyear and Sage Intacct.

Reconnecting the integration often resolves issues where exports are rejected or fail silently.

Troubleshooting Tips

  • Always ensure that both Lightyear and Sage Intacct are updated to their latest versions.

  • Verify that all required fields in the invoice data are correctly populated before exporting.

  • Consult the Lightyear and Sage Intacct support teams if issues persist.


Error messages

Enter either all positive or all negative amounts, and try again.

Sage Intacct does not allow invoices/credit notes to have a mixture of positive and negative lines, e.g. Credit Notes can't have positive lines. Invoices can't have negative lines. You will need to send the document back to Approvals and adjust the line items to remove the appropriate positive/negative line.

This can be adjusted by changing a value on another line to include the extra amount. Or, in the case of an invoice with a negative line, you can create a separate credit note to make the adjustment.

Date must be on or after 01/01/2019

The period in Sage Intacct has been closed. The invoice date must be changed to a date after 01/01/2019, or you can reopen the period in Sage Intacct. Send the document back to Approvals to make the adjustment.

Failed to export invoice [' You must select a department for all your line items; transaction department value approval requires a department. Please modify the line items or save your transactions in draft mode.]

Check the department is available for use with the rounding Account Code. Even if all the line items have a department if the invoice/bill requires rounding within Sage Intacct this will require a department.

Failed to export invoice [' You do not have permission for API operation X on objects of type X']

This occurs when the Web Services user doesn't have the necessary permissions to access the object. The solution for this is to have an Intacct Administrator ensure that the Web Services role has the required permissions or subscriptions to access the object.

java.io.IOException: Connection reset by peer

The API connection between Lightyear and Sage Intacct has dropped. You will need to go to Accountancy Software and Disconnect/Reconnect to Sage Intacct.


Did this answer your question?