generally speaking how have people been managing e...
# arm
l
generally speaking how have people been managing existing contracts that are currently in-play and have been partially recognized and a client implements ARM? are you entering orders and starting new from a point in time or is there a conversion process that one can do?
j
We created zero value invoices for all of these items, but set them not to go to the customer. The positive items were all of the open deferred revenue items, set to amortize over the remaining life of the contracts. The negative items which offset this total were set to amortize into a "manual" deferred revenue account, so would have zero impact on the P&L in future months. Ours was a full migration onto Netsuite rather than just switching on ARM but the principle would work in the same way. 1. ITEM A. $1100 01/02/2019 - 31/12/2019 2. ITEM B. -$1100 31/01/2019 - 31/01/2019 Where item A goes to a revenue account, Item B goes to a deferred revenue account (assumes you switch on ARM for the February period, but keep Jan open to recognise the 31st Jan transactions). Our contracts are really basic though, with well-defined recognition rules
k
We migrated ~2500 sales orders. Largely developed internally. I had done a migration with the assistance of NetSuite PS previously, so we modeled it after that migration path. Helps if you have a strong NS Developer and some runway.
l
thanks, i was hoping we didn’t need to go there. my first instinct was the zero dollar invoices and /or S/O’s with billing schedules put in. Thought i’d ask in case someone had thought of a magic want approach 😉
s
another approach i am working on with the client is (and the scenario might differ for you a little here) we are migrating client to NS. They have been recognizing their revenue in NS since before this migration with imported JE’s and invocing from their legacy system. as we migrate the full contracts we set the charges to not bill also in revenue plan on the lines there is a small checkbox called IS RECOGNIZED which means it will not try to post that JE as it reads it as already recognized. We wrote a script to do that on the revenue plan lines for all those entries from before the migration date so those JE’s dont post and the rest will continue as planned