How to deal with contract revisions without using version number field
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.