Learn about Redwood and be one of the first to join the conversation

Visit Redwood Community
How to deal with contract revisions without using version number field — 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

How to deal with contract revisions without using version number field

Question
2
Views
0
Comments

Summary:Revenue basis data import: source system does not have version number for contract revisions


Content (required):We are sending contract creation events and termination events separately from the source system.

So, instead of sending line version 2 for a contract termination as in the white paper (2626663.1), we are planning on sending a second contract with a negative transaction amount and modified dates to offset the revenue that is getting recognized on the first contract.

The downside we see to this is the additional "Performance Obligation Satisfied" journal entries, both for the full term of the initial contract, and the offsetting entries on the modified term of the second contract.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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