Hi, I have a client that is looking to create a parent subsidiary with two child subsidiaries. Items would be associated with the parent, so that both children can sell the same items. They would like to disallow posting any transactions to the parent subsidiary. Any thoughts would be appreciated. So far all I've come up with is to script to prevent saving transactions in the parent.

That's probably best bet.

Bad experiences with "include children"?

No. Just that it's what's causing the behavior you are trying to prevent?

I think the goal is to configure items in the parent, and then include children so that there's one item configuration used in the two subs.

the subsidiary fields should be multiselect.

Yes, you're right. I was trying to figure out what the advantage to having this extra subsidiary might be. I think selecting two subs on an item is probably the better option.

even if the items are set up to only be used in the child subs, someone could still post a JE (or an expense line on a bill or something) to the parent sub. without a script, you can prevent probably 90% of instances of that by restricting items, accounts, and roles to exclude the parent sub. but there's still a chance of an admin being able to get around it, so if you want to be 100% certain you'd want a script deployed to all transactions to prevent entry to the parent sub.

What if employees permissions only have access to the two subsidiaries? Then they can’t make any entries like journals. customers they create would also only go into the subs.

To be honest, I'd just create a saved search that alerts any time a record (transaction) is created in parent sub, then go in and kill it (and have a word with the person making the transaction). Scripting and making stuff inactive seems like overkill, but that's just my 2 cents