How are Revenue Element Start/End Dates determined in Advanced Revenue Management (ARM)
Let’s say I create a Sales Order with header level start and end dates of, for example, 2019/1/1 and 2019/12/31, respectively, with ARM enabled.
Then I create two transaction line items with item level start and end dates of:
Item 1 – 2019/1/1 and 2019/6/30, respectively
Item 2 – 2019/7/1 and 2019/12/31, respectively
In this case I just have two items for which I want to recognize revenue in those distinct periods.
Once I go to update Revenue Arrangements and Revenue Elements, each of the Revenue Elements corresponding to Items 1 & 2 have a start and end date of 2019/1/1 and 2019/12/31, ignoring the item level dates I input.
I can work around this by going into the associated Revenue Arrangement and manually editing each Revenue Element’s date fields, but is there a way to have the Revenue Element source the values the way I want to begin with, natively?
KevinJ Of Kansas
Not a rev rec expert by any stretch – do you *have* to populate it at the header?
HL
The header Start Date is explicitly mandatory. The header End Date is not but adding an item will require it regardless before being allowed to be saved.
SO either way both header date fields are needed for the Contract Renewals Module.
KevinJ Of Kansas
Perhaps you should share your recognition rule setup here so that others who are more experienced can see it. It’s plausible there’s a setting wrong in the rule.
HL
It didn’t end up being a revenue recognition rule issue. I think it’s just a scenario in ARM (custom rev rec dates) that’s poorly documented.
For posterity, we were able to resolve this via configuring Transaction Line custom date fields and setting them up on the Setup-> Accounting -> Revenue Field Mapping page.
SuiteAnswers Id: 61890