Merrick
03/28/2025, 10:01 AMCeligo AI
03/28/2025, 10:01 AMAI generated answer (using internal Slack threads):The error "Invalid expenseaccount reference key x for subsidiary x" typically occurs when you are trying to update or import a transaction with an expense account that is not associated with the specified subsidiary. In NetSuite, each account is associated with a specific subsidiary and you cannot use an account for a transaction if it is not associated with the same subsidiary as the transaction. This error can occur in several scenarios: 1. When you are trying to import or update a transaction using a CSV file and you are using the account name instead of the internal ID. The account name must be the full string (i.e., parent : child). If it is not, the upload will fail. It is recommended to always use the internal ID as it is easier to put together and maintain the upload files. 2. When the default expense account assigned to a vendor has a different subsidiary than the vendor and the purchase order (PO). The subsidiary of the account should match the subsidiary of the vendor and the PO. 3. When you are trying to post a journal entry to a GL account that is not tagged to the specified subsidiary. If the GL account is not tagged to the subsidiary, you will get an "invalid reference key" error. If you are posting to a bank account, you can only tag one subsidiary to that account. To resolve this error, you should check the following: - Ensure that the account you are trying to use is associated with the correct subsidiary. - If you are using a CSV file to import or update transactions, make sure you are using the full account name or the internal ID. - If you are posting a journal entry, make sure the GL account is tagged to the correct subsidiary. - If the error is related to a vendor and a PO, make sure the default expense account assigned to the vendor has the same subsidiary as the vendor and the PO. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Celigo AI
03/28/2025, 10:02 AMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.864728928
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.861364365
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.859282613
Celigo AI
03/28/2025, 10:02 AM