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.
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
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?