Bruno Mota
12/20/2024, 2:28 PMCeligo AI
12/20/2024, 2:28 PMAI generated answer (using internal Slack threads):Based on the conversations, it appears that changing the Recognition Account in a revenue element is not directly possible because it's linked to the item record sales account on the sales order. The only way to do this would be to delete the revenue arrangement, update the rev rec rule on the item record (which is tied to your SO) and then regenerate the revenue arrangement/elements. However, this is only possible if the Revenue Plan has not yet posted any rev rec JEs. If that has happened, your only option is post reclass entries. If the item was set up with the wrong GL account number and you have updated it to the correct account number, you would have to delete the Revenue Arrangement associated to the Sales Order for it to take the new item configuration. If the revenue arrangement/Plan has already been processed you won't be able to delete it without deleting the JE. At that point, if you want this to be clean and it's only one transaction, it would make sense to fully bill and credit the original SO (creating a revenue stream that will REVERSE the incorrect order along the same time-span/schedule) and then create a new SO to post correctly. As for automatically updating revenue arrangement when editing the transaction source, it was mentioned that this was scripted in a project. A saved search for the Revenue Element was used to join both the revenue plan and the sales order. Lastly, to confirm if your Revenue is set up to be recognized from the sales order and not the invoice, you can check the GL impact of a sales order. If it shows "Posting" = NO, it means a Sales Order is a non posting transaction and revenue is not recognized on a Sales order. Revenue is only recognized when Money is collected unless it is recorded as Cash Sale where you record Cash collection at time of sale. ****** 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
12/20/2024, 2:28 PMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.852064669
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.832401037
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.828272402
Celigo AI
12/20/2024, 2:28 PM