Skip to main content
Question

Pending Cost not working for Non Stock Items

  • October 23, 2026
  • 4 replies
  • 24 views
  • Translate All

Forum|alt.badge.img

Hello all,

I have been facing issue after updating the Cost for Non Stock items. I have entered:

Pending Cost = 120

Pending Cost Date= 10/22/2026

Current Cost= 100

 

If I’m creating an PO for this item for the date of 22 or 23, it is still taking 100 and not 120. Shouldnt it be taking 120?

 

4 replies

Ed Goodman
Acumatica Employee
Forum|alt.badge.img+4
  • Acumatica Employee
  • October 23, 2026

​@Harry,

Good morning.

You indicate that you have a pending cost for this item.

Have you run the Update Cost function to update the cost?

Unfortunately, I am getting an error when attempting to copy / paste a screen shot in here to illustrate, but here is the help documentation from https://beacon.acumatica.com/ if needed.

https://beacon.acumatica.com/r/Form-Reference-Guide/Inventory-Forms/Non-Stock-Items

Hope this helps!

Ed

 

Translate

Eric Ratté
Jr Varsity I
Forum|alt.badge.img+4

Hi, the 120 $ is pending. Meaning that you have to run the action Update cost to make it effective.

Translate

Forum|alt.badge.img+1

Hi ​@Harry,

This usually happens when the pending cost has not been activated yet.

In Acumatica, entering a Pending Cost and Pending Cost Date does not automatically apply it to transactions. The system keeps it as a pending value until it is updated.

To make the new cost active:

  • Go to Non‑Stock Items (IN202000)
  • Open the item
  • Go to the Price/Cost tab
  • Enter the Pending Cost and Pending Cost Date
  • From the More (Other) menu, click Update Cost

After this step, the pending value becomes the Current Cost, and the system will use it for transactions such as purchase orders.

Translate

Steve Milner
Varsity III
Forum|alt.badge.img+6

@Harry Ed, Eric and Wasana have the first step right. The Pending Cost Date doesn't switch anything on by itself. Nothing changes until you run Update Cost. Then 120 becomes the Current Cost with 10/22 as its Effective Date, so POs dated 10/22 or later can use it.

There's a second thing that can keep you at 100 after that, and I reproduced it on 2026 R1. When a PO line fills in its unit cost, it checks the vendor before the item. It looks at Vendor Prices (AP202000) first, then the Last Vendor Price that vendor has on the item's Vendors tab, and only then the item's Current Cost.

That Last Vendor Price is recorded for you. With Vendor Price Update on AP Preferences (AP101000) set to On PO Entry, every PO you save writes its unit cost there. With On AP Bill Release, releasing the bill does it. So if this vendor already has 100 recorded from an earlier PO or bill, the next PO from them still comes in at 100. In my test, a second vendor with no history got 120 on the same day.

After Update Cost, open the item's Vendors tab. If that vendor shows a Last Vendor Price of 100, type 120 on the next PO line and it becomes the vendor's new last price the same way. Or add a 120 price for that vendor on Vendor Prices (AP202000) effective 10/22.

Translate