https://netsuiteprofessionals.com logo
Join Slack
Powered by
So whats the big thing in 2023.1? I read the Relea...
# releases
e
So whats the big thing in 2023.1? I read the Release Notes every week but it seems very empty to my use cases. Meanwhile, I hope some day NS give us multi-subsidiary employees for OneWorld 😒
a
That would be nice! I didn't catch anything groundbreaking in the release notes that I can recall but hopefully there's something cool I missed.
k
gents, there is not much hope for that until the tax law changes 🙂
a
i suppose that makes sense, but it's not like i am prevented as an employee to only interact in one/certain subsidiaries- that's controlled at the role level
😁 1
k
on the groundbraking front - i have my christmas wish! Finally rev rec journal and reclass journal are part of Period Close/Month End list. It is such huge step that I cannot tell you how happy it makes me 🙂
stanley 1
a
Have you by chance heard anything about the roadmap for revrec allowing commingling of direct revenue posting and non-direct revenue posting items on the same transaction?
k
cannot happen 😞. right now invoice: DR AR CR Deferred Rev, rev rec - DR Deferred rev, CR Rev; direct rev (DR AR CR Rev) does not fit here 😞
source transaction must match rev arrangement, otherwise it falls apart
a
Right, oh well. Have constructed a bunch of workarounds that are working well, was just hopeful that they could eventually handle it
k
do you mind sharing a use case? I’d love to hear what other people are doing. Work around should not be happening, really, ARM module can make revenue human-less if configured properly
a
not at all - the biggest issue is selling serialized hardware (non-DRP) and recurring revenue software (DRP - a la maintenance contracts) on the same order
so, we have both items on a Quote
but when they go to create the order, there's an error - so we built custom scripted buttons to facilitate separating out the product from the service
we also have custom column fields on transactions that link the two - a "unique key" id for each line, and a sep column for the "connected hardware" which is the unique key of the product, tagged on the service line item
that helps us do a bunch of things the in the downwind processes
another major requirement is having both HW and service wind up on the same invoice, which we know we can get done w/ invoice groups - it's just that invoice groups is a pretty new / fledgling feature at the moment, without a lot of ability to customize or automate without scripts
sorry i had it backward above - obviously hardware IS DRP and services are non-DRP/recurring
k
ok; having inventory on SO with ARM does not prevent from recognizing rev as you need it. There are many cases like that, where software and hardware (serialized inventory serialized assembly builds,) are combine on the same SO. Sure, devil is in details, but hardware is recognized either on fulfillment or on sale with one rev rec and software (whatever it is - maintenance, DRP, XYZ, ABC LOL) uses ratable rev rec. Same SO, can recognize revenue daily, if that
is the goal
a
yes - you are reminding me that the revrec folks on our team did say that this was an option, but the client in this case didn't like the accounting impact of doing it that way
but i did forget about that option, and i wonder if they'd feel differently about it now having been live w/ rev rec for 6 months
k
i had more interesting case - guys were building a product (read: WO+Assembly), then would add software on the SO and then they would actually not sell it but rent it, that’s where it was fun
a
in this case both hw and service are set up to recognize on fulfillment, but hw is just not deferred
yikes - that does sound a lot more complex
k
yeah, someone did not explain ARM setup to your client correctly
and that’s how I get my clients…. 12 months after implementation LOL
a
no i think they explained it properly, but the client opted to keep it to direct revenue posting and non, forcing the split onto different SOs
their controller didn't like the sound of having hardware enter ARM at all
k
it is hard for controllers to deal with ARM if they are boxed in 😞. My hardest work goes into change management
a
boy ain't that the truth!
j
doesn't help that saved searches on recognised revenue are extremely limited, whereas on direct revenue posting you can do all kinds of cool stuff.
Open in Slack
PreviousNext
Powered by