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.
Intelligent Payment Automation, powered by BILL (aka 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.
Reducing Planned Standard Cost & Inventory Revaluation Records
We are currently in implementation of NS, and I have a question about best practices for updating Standard Costs.
We currently have 15 locations setup for tracking inventory when we transfer inventory to various contract manufacturers. When we do a standard cost update, if we create Standard Cost Versions applying to all 15 locations and then run Planned Standard Cost Rollups and Inventory Revaluations, it creates a rather large number of records for each (15 locations x Number of Items & Assemblies Affected).
In the future, when we actually begin using NS and need to update standard costs, we can probably not include all locations, which should help reduce the number of records generated. However, for the initial establishment of standard costs for all of our items/assemblies, it may be too difficult to create multiple SC Versions to reduce the number of records generated.