I've read the consequences of doing this and they ...
# general
c
I've read the consequences of doing this and they don't sound good, but I was curious if anyone has succesfully moved a subsidiary in a heirarchy and wondering if it didn't screw all the reporting and customizations up? I ask this because we are in the process of being acquired and this was something that was discussed, but I'm pushing for them not to do it because I know of all the spiraling effects from it. Rather just let the old one be and create a new one under the heirarchy we want it at.
d
Ha, I just got off a call on this topic. We have over 500 subs and will be doing a somewhat massive sub hierarchy change. As far as I can tell, the two biggest factors/things to consider when doing a sub hierarchy change are: 1) are you multi-currency and 2) have you run automated eliminations. I've had good and bad experiences changing the hierarchy. In the bad case, the multi-currency factor wasn't taken into consideration enough and it jacked up the consolidated exchange rates which jacked up the historical financials and cost us a ton to fix. In the good cases, nothing happens and it's scary but easy.
In neither case have I seen anything that affected customizations.
j
@Cole there are inherent risks but may be of value if the company is being acquired as well. Generally you can support this process with careful planning and summaries.
To @Dylan Fields point - this should not affect customizations since these can be maintained within their desired subsidiary structure regardless.
c
We are multi currency AUS, EU, GBP, INR, USA, and CAD
So wondering if we could get support from NetSuite directly on setting of the exchange rates so that heirarchy we want to move isn't jacked up historically and going forward?
k
You could either get help from NetSuite with it or you could get help from someone competent that has done it before. There's a difference.
c
I'm not a huge fan of working directly with NetSuite and would rather work with someone who has done it before
k
But the main thing that I have seen in the past is the consolidated exchange rates getting messed up, because those are inherited from grandparent to grandchildren, etc. So if you start messing around with parent/child relationships, you may need to correct them. Its nothing that can't be tested and verified in Sandbox first, so I wouldn't be afraid to do it if that's your concern.
j
@Cole definitely recommend a NetSuite Partner vs. NetSuite Professional Services for this type of engagement. DM if you have any additional questions.
r
I'd be more concerned about elims than consolidated exchange rates. In theory, the rates should be easy-ish as long as you're careful. Figure out what the rates should be, check to see what they are, then do a CSV import to fix the incorrect ones. Running the elims process seems like it could create a huge mess though.
p
Don't think elims would be an issue if you time it and make sure you post everything, close periods etc - but you can't have anything ongoing that would be a disaster
☝️ 1