Just tried and got through now. Weird. Thanks for looking into it, will let you know if it happens again.

No, deletion leaves no trace. Your only clue is a gab in internal IDs, but you will never know who did it, there are NO logs for deletion. Which is why you want to make sure you give EDIT permissions to everyone rather than FULL.

Hi there, A Support contract with Netsuite is not mandatory. As you seem to be aware, you can chose between Silver, Gold and Platinum support, which are all a varying degree of % of your Netsuite bill, which your Netsuite Account Manager can explain to you in more detail. You can also renounce Support, but that stills…

I had similar, err, "phone enthusiasm" with the following recent cases 904733 904714 904324 It feels like the reps are following a policy though, so I wouldn't necessarely blame the reps.

Gold support isn't the highest level - Platinum is. You basically get a dedicated rep that understands your business. It is, of course, very expensive, but I know of several customers that are very satisfied with it. Another option is to get your support from one of us Partners. We have access to a special Partner Support…

Oh I hadn't understood you just wanted to move the subs in the hierarchy. Yes, you can just use the Modification tool for that. It will alter historical reporting, but otherwise I have never had problems using this tool.

There is no such thing as Advanced Multi-Book. There is only Multi-Book. We have done several implementation of these. The functionality within Netsuite is quite simple. The challenge comes with organizations needing to be able to think through all account mappings. The effort is really all on the business implementing the…

Great to hear!

Javier is correct - another sub is probably not needed. You can run the TB in consolidated but only showing the USD sub's transactions, which effectively converts them to CAD for reporting purposes as desired. However, if there is some sort of complexity preventing this from being viable, you do not need professional…

Yes, this is a standard Data Migration job. There are no shortcuts (save the ability to share customers and vendors to new subs). So, all the same challenges of a standard historical data migration.

Yes, this is actually quite common, particularly in the UK, where rates are updated once a month based on officially published rates. That being said, NS doesn't exactly support it. The FX Integration only has the option for nightly updates. So, if you want to do monthly, you will need to have someone go in and manually…

Yes. It's a manual effort. NetSuite has no mechanisms to auto-magically extract a sub and place it in a new instance. You will need to build a migration plan and shuffle all the data. Depending on your account size and budget, I had good results using integration to move the data. You can use like a Boomi type platform,…

It is not needed. You can have a single interco account shared with all your subs. During reporting, you can dynamically pivot to see which sub owes what slice of the pie.

Yes, with customization. Basically you can use scripting to chain up the series of interco transactions/GL impacts necessary to make this happen. If you dont want customization you can do it of couse, but you'll need to manually create the shuffle of GL Impacts to pass it back to Canada. Said differently - NetSuite has no…

Depends on the desired "documentation" of the transaction. Formal arm's length relationships would require nothing less than a Bill and an Invoice on either end. If the company is more wishy washy about the formality of transactions, yeah, you can probably get away with a single interco Journal, which really isn't so bad.…

That is impossible. The only way to achieve this would be for that sub to be 100% eliminated in an Elimination Subsidiary during consolidation. However, there are not means to do that - you'd have to manually post a 100% reversing Journal every month's end (or whenever you want to consolidate). A script could help do that,…

Multi-Book is free for all OneWorld users (or, said differently, you already paid for it). However, do plan some professional services fees for setup from a Partner. Note that only Partners who are certified are allowed to implement this for you - so specifically ask if the Partner has that certification before hiring…

Hmmm, that's a pickle. So the standard trick to load up historical transactions with specific historical rates when setting up a new implementation is to book the historical account way in the past, in its own period, so that you can define a rate there just for that transactions. In the case of a live, ongoing account,…

The After Submit script would trigger on the save of the Item Receipt The script would then do EXACTLY what you describe in your 4 points It just comes down to picking the right APIs to execute the right logic for each step. I can tell you SuiteScript can do all of this for sure.

So long as you created your Bill an dInvoice using as "represents subsidiary" customer and vendor and thus so long as you used a "To be eliminated" AP and AR account (and Income and Expense), then yes, no problem.

Sorry about that, we recently did some web site changes and some links got changed. Here is the link that works (for the time being, I thnk they are working to fix the old links) http://www.tribridge.com/blog/TribridgeConnections/post/01/13/2017/netsuite-product-spotlight-multi-book-accounting

As to you specific reporting question: no, it will not be possible to pull historical vs going forward. Once you make the subsidiary hierarchy change, NS will consider your sub was "always" where it it now. There is no concept of as-of date, and no ability to pull reporting from 2 different hierarchies. The closest way to…

Well "parsed += + prop" is not a good start... I think you mean "parsed += prop [...]" You also have "+ "\n""}" which is no good. So, basic syntax problems right now..

Sorry I got lost. Can you restate what your start point is and what your end goal is?

Oh ok, well this is simple. Just do an interco Journal Sub A DR Expense $500, Vendor "Sub B" Sub A CR Interco Clearing, Vendor "Sub B" Sub B DR Interco Clearing, Customer "Sub A" Sub B CR Income $500, Customer "Sub A" This will eliminate provided Vendor Sub B and Customer Sub A are properly configured as "Represents…

That is not how you call a Suitelet. Look, I'm gonna give you some tough love here: it is my professional opinion you do not yet have the expertise to tackle this script, and need more training than can be provided ad hoc via a user group. I would recommend you hire a consultant to complete this project, of if you can…

I'm not sure if this can be done with a Workflow. I would aim for a 'regular' script - User Event suitescript with After Submit trigger deployed on Item Receipt. You'll be able to do everything you need to from there.

You would place an After Submit script on the Item receipt. You would cycle through all line items, collecting internal IDs into an array. Then you'd call a search, passing in the internal ids, and retrieving all the info you need. Then you do the "warehouse distribution", though I'm not clear on what that is.

Yes. The Interco JE I used as example in post #11 is your template for making this happen. So long as you use properly configured "Represents Subsidiary" entities, NS will correctly auto-eliminate, which will affect consolidated totals, but not per-sub totals. You will achieve exactly what you illustrate here.

The option that a number of companies still use is to segereate subsidiaries via the use of Class, Location or Department. The idea is that you take, say Department, and create 1 department per subsidiary. Then, you tag all of your GL impacts with the appropriate Department/subsidiary. Pros: * Extremely inexpensive…