Melvin Pastores
10/11/2024, 6:36 PMCeligo AI
10/11/2024, 6:36 PMAI generated answer (using internal Slack threads):The error "Invalid subsidiary reference key Y" or "Invalid subsidiary reference key 521 for accountingbook1" typically occurs when there is a mismatch between the subsidiary reference key provided and the actual subsidiary in the system. This could be due to a number of reasons: 1. The subsidiary reference key provided does not exist in the system. Make sure that the subsidiary reference key you are using is correct and exists in the system. 2. The subsidiary is not active or not available for use. Check the status of the subsidiary and ensure it is active and available for use. 3. The GL account you are posting to is not tagged to the subsidiary. If you are posting to a GL account, ensure that the account is tagged to the subsidiary. If you are posting to a bank account, remember that you can only tag one subsidiary to that account. 4. If the subsidiary is a parent for multiple subsidiaries, ensure that the "include children" box is checked on the GL account form. 5. If you are using multi-subsidiaries and have more than one subsidiary working with a client, ensure that the correct subsidiary is being used for the transaction. It seems that you cannot use a workflow or prevent the automatic sourcing of the subsidiary from the entity record. Remember to always double-check the subsidiary reference key and the subsidiary settings in the system to avoid these errors. ****** 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
10/11/2024, 6:36 PMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.82104063
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.820933163
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.820734918
Celigo AI
10/11/2024, 6:36 PM