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.
Fulfilment posting to GL on created date, not shipped stage date
Hi,
We are still doing some testing, but we have come across an issue where if you use the '3 stage - pick/pack/ship' fulfilment process instead of the single fulfill step - the G/L impact can get backdated into a closed period.
The example for our business is that we do some customizing of a product and attach some labour, but don't use assembly builds for it, what we had done was fulfill the order to Picked stage - go do the QA/Upfit work on it - then return it to the despatch area and mark is as Packed. When it is physically shipped, it is marked as shipped, and that is when the G/L should be posted (that date/that period). The problem appears to be that the inventory is debited correctly (on the shipping stage), but the G/L COGS hit occurs