[Subscription Billing] Overview of Revenue and expense deferrals in Microsoft dynamics 365 finance and operations: Part-3

Views (7)

saurabh bharti

15,039 Moderator

Like(0)

Report

This blog is the next part of subscription billing series where we are going to talk about Revenue and expense deferrals. Objective of this blog is to set the base about overall process and get an idea what this feature does. After that I will write next few blogs to drill down to each critical scenario.

If you have not visited the previous blogs, please do visit then only this will make sense for you: Part-1 and Part-2

Revenue and expense deferrals let you to control revenue recognition at the line-level. Revenue and expense recognition processes are managed through deferral schedules to eliminate manual recognition processes.

What is deferral? Deferral in account is something which we defer posting to actual Ledgers at the time of original transactions and later recognise to actual ledger posting.

Why we do? This is done so that we can have accounting of transaction in actual periods rather than having in one single period.

Example: Lets say we buy Netflix subscription of worth 1200 for an year in the month of Jan, now when Netflix generates the invoice for this subscription, should it post revenue of 1200 in Jan month?? No, it shouldn’t, because this revenue is for next 12 month. So at this point of time when we post invoice in Jan , revenue gets deferred to the deferral ledger instead actual revenue then later ever month we transfer from deferral account to respective month which which is called as recognition.

Now in this blog we are going to discuss the end-to-end high-level process and then in upcoming blogs we will drill down to different scenarios and concepts.

Here is the overall process: