Hopefully quick question: finance team wanted a way to track "Non-GAAP" items for external reporting purposes. They wanted a project ID but it needed to be multi-sub so it wouldn't work. It seems like creating a Location would work the best because it auto-populates on amortization JEs unlike custom segments and fields. We have been testing it and it seems to solve the issue. I checked with NetSuite and they don't seem to have a reason why we couldn't use it like that considering we do not have inventory.

as long as it is non-mandatory you should be good. Mandatory fields may create issues during period close management steps (IC, reval, etc.)

considering we do not have inventory.

What are the chance you ever get inventory? If it's more than like 1%, I'd use a custom segment instead and use scripting to auto-set it if possible. I can tell you from experience that if you start using locations on multiple subs because you assume you'll never have to use them for inventory and then you later do have to use them for inventory, it's a huge headache to deal with.

@RJMNS totally agree with you. In my previous company, it was almost impossible to use locations for inventory purposes that were previously shared across multiple subsidiaries because of historical transactions

@RJMNS That was my main concern since I was thinking there may be something else we don't currently use and then when we start using location it will be a problem. We are a SAAS company so I don't think we will ever have inventory, but I will let finance team know. Maybe I can convince them to use Custom Segment. There aren't many entries that fall into that category so if we could figure out the amortization issue I think they would work. Thanks all