Revenue should not be recognize for Migrated Subscription — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Revenue should not be recognize for Migrated Subscription

Summary:

Revenue should not be recognize for Migrated Subscription

Content (please ensure you mask any confidential information):

We are migration subscription of Older year 2024 or may be 2023 and We observed that if the older the period subscription is migrated but when a contract creates it will also book the revenue for older period in the current period

we want that after migration of subscription the revenue for the older period should not recognized, is there a way to achieve this requirement


Version (include the version you are using, if applicable):

25A Fusion


Code Snippet (add any code snippets that support your topic, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!