This message was deleted.

Can someone provide input on the above?

well there are a lot of 'it depends' in this - but in general, you have to itemize, meaning each resource or type of resource would have its own item. The items in turn will carry the rules for recognition as well as the triggers (could be fulfillment-based also, like booking number of hours) The forecast rule is the budget-part of this but it is optional so reporting could replace. Adding a resource at a later stage is not a problem since you can have start/end date on each line - if you do not add it at start you would need to add an order and merge the arrangements (you can keep them separate, merging is mainly if there are multi-year recognitions after the addition.) Not sure if you were asking if ARM could do it - it can and probably the non-advanced version could as well, the main thing ARM brings is the detachment of invoicing from recognition.

The problem with creating separate items for each resource will be a challenge itself. A project can have 100s of resources tagged to it. Secondly, adding a resource in future is not a problem, complication is we do not have the resource allocated as of yet, and since we don't have one allocated the efforts are less compared to what it's supposed to be and such recognition and forecasted amount will differ then what is expected.

It does not need to be a separate (different) item but you have to have a line-level structure that is similar to what the customer would see on the invoice (same item re-used with diff text, resource name etc.) The resource allocation is not really an ARM issue that is more about what that process looks like, if you use projects etc.

honestly ARM is the least of the issues here. you set up your all your items (that you assign to each resource) with Percent Complete rule and Create Revenue On as Project Progress. When you create your billing rules use Milestones on Billing and As Charged on Revenue.

I am still trying to wrap my head around how to implement this use case. This is one of the 4 use case that we will have to implement. (Have dedicate resource for ARM setup, but trying to learn). I have previously worked on a completely custom revenue recognition module, that I have developed and enhanced with a group of individuals. I am familiar with the business logic but this is still Slightly complicated to setup.

are you saying you are not familiar with ARM module at all?

Exactly. I am familiar with revenue recognition but not ARM. First time trying to implement it.

I strongly suggest taking the ARM class and preferably hiring an ARM expert (with the understanding of projects). You can create a lot of unrecoverable damage very very quicky

Agreed - the eLearning course is a good primer if you have access to learning pass content (you can get a demo env also then), you may be able to find a couple of walkthroughs on youtube as well.

I am not trying to implement it alone. We have an experienced resource for it to implement. I only know the business use cases. And I am trying to see if it will be possible to certain use cases in ARM. I am just eager to learn it bit better. As I know even once implemented there will be too many things we will have to handle. The company is switching from their inhouse budgeting and revenue recognition module to ARM. Budgeting, ARM is slightly less and more advanced at the same time vs what we had...

so go and take the class. It will lay the groundwork for you. ARM is a complex module, and configuration is the key to success

I have to agree, trying not to sound like a broken record here but you cannot possibly decide on uses cases unless you know the module

Business use case I know. And the company will not switch modules that they have been running for 8+ years. Unless they can give a similar output if not the exact same. Custom module could even give employee wise P&L and used to do recognition as well as forecast at employee level. ARM will give at sales order / project level at Max at department level. I got very slight idea I know. And I was just looking for directions to move forward on how to properly learn it.