ANS-0682 · PURCHASE & VENDOR MANAGEMENT
Why Does Last Purchase Price on NetSuite POs Seem Inaccurate with Units of Measure?
NetSuite's Last Purchase Price on Purchase Orders may appear inconsistent when using Units of Measure; understand the calculation and accurate viewing strategy.
Short answer
When Multiple Units of Measure are enabled, NetSuite calculates the Last Purchase Price on Purchase Orders using purchase units, which may lead to perceived inaccuracies. Custom fields sourcing this value also reflect this behavior. The most reliable method to view the accurate Last Purchase Price is directly on the Item Record.
Scenario
Users often observe that the Last Purchase Price field displayed on Purchase Orders appears inconsistent or inaccurate when Multiple Units of Measure are in use. This behavior occurs because NetSuite calculates the Last Purchase Price based on the item's purchase units. Attempting to source this value into a custom field on the Purchase Order will also reflect the same calculation, leading to similar perceived discrepancies.
Solution
When Multiple Units of Measure are enabled, the Last Purchase Price field on Purchase Orders is calculated by NetSuite using the item's purchase units. This defined calculation method may result in a value that differs from expectations if other units are anticipated. The Last Purchase Price displayed directly on the item record, however, provides the accurate and current value. If a custom field is created on the Purchase Order to source the Last Purchase Price, it will reflect the same calculation based on purchase units, thus showing the same perceived discrepancy. The recommended approach to obtain the accurate Last Purchase Price is to view it directly on the Item Record.
Expert NetSuite Support
Need help with this NetSuite issue?
Purchase & Vendor Management consulting and configuration support