This reference covers the most common sync errors between Re-Leased and Oracle NetSuite, their causes, and how to resolve them.
Error Message | Cause and Resolution |
A contact with this name already exists — please use a different name | Cause: Re-Leased does not allow two contacts with the same name. This usually occurs when a Vendor and Customer in Oracle NetSuite share the same name. Resolution: Rename the duplicate contact in Oracle NetSuite — typically the Vendor contact. |
Invoice/contact is using multi-currency. This feature is not currently supported by Re-Leased | Cause: An invoice or contact in Oracle NetSuite is configured for multi-currency, which Re-Leased does not support. Resolution: Unlink the invoice or contact from Re-Leased. Make the contact inactive in Oracle NetSuite and create a new contact in your local currency. |
Payment has linked transaction(s) of type(s) 'Journal Entry' and is not currently supported by Re-Leased | Cause: Journal Entries do not sync from Oracle NetSuite to Re-Leased. Resolution: Unlink the payment. Once unlinked, add the payment to the invoice in Re-Leased — it will not sync back to Oracle NetSuite as the invoice is already paid there. |