Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Assembly Build posting to COGS?
I am seeing a curious G/L impact on one of our assembly build transactions.
In addition to debiting the parent asset account and crediting the components' asset accounts, the assembly build transaction also debited COGS and credited the parent asset account for the amount of the build.
I.e. the following transactions occurred:
DR Parent Inventory Asset Account
CR Component Inventory Asset Account(s)
DR COGS
CR Parent Inventory Asset Account
This only happened on one instance of an assembly build (other assembly builds did not have the COGS transaction).
Is there a reason why this might have happened? Was it the way the assembly build itself was transacted, or was it due to the way the parent assembly part was set up? How do I prevent it from happening again?