Skip to main content
Question

Initial Last Cost

  • Nov 18, 2026 3:36 PM UTC
  • 4 replies
  • 14 views
  • Translate All

dalesimmerly58
Pro I
Forum|alt.badge.img+1

We have an internal request to update the Last Cost of items to Vendor Price if the value for Last Cost is zero

The idea is to have an initial Last Cost before there is a Receipt 

Seems wrong to me to override how this this field is updated but I can not come up with any specific issues doing this…

We are a manufacture and these would primarily be component part cost / prices that are visible to sales and engineering 

 

Thoughts?

 

4 replies

josborn02
Varsity III
Forum|alt.badge.img+3
  • Varsity III
  • Nov 18, 2026 3:58 PM UTC

I agree with your concern about overriding how Acumatica normally updates Last Cost, although initializing it with a vendor price isn't necessarily a bad idea. Last Cost is used in more places than just the Stock Items screen, including manufacturing BOM cost rollups, sales margin calculations, and as a fallback for costing certain inventory transactions. An inaccurate vendor price could therefore have unintended consequences.

Entering Last Cost for new items with no receipt history makes sense, provided the vendor price is accurate and the downstream impacts are understood. However, if the objective is to give Sales and Engineering visibility into estimated component costs, I'd consider displaying Vendor Price or a separate Estimated Cost field instead. That preserves the integrity of Last Cost while still providing the information those teams need.

Translate

Forum|alt.badge.img
  • Freshman I
  • Nov 18, 2026 4:04 PM UTC

My standard practice is to update Last Cost until a receipt transaction is done.  This helps in the BOM cost rollups, estimations, margins, etc….

Translate

josborn02
Varsity III
Forum|alt.badge.img+3
  • Varsity III
  • Nov 18, 2026 4:20 PM UTC

Once a receipt transaction takes place you no longer need to update last cost, but until that happens, Acumatica will need something to key off so updating last cost prior to the first receipt makes sense.

Translate

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

My replies are created in part with the help of proprietary AI, built with my AI skills, curated and maintained myself. Most replies are tested on local instances before they go up, and all are reviewed before posted.

@dalesimmerly58 it isn’t really an override. Entering the starting cost of a new purchased item in Last Cost is the normal setup, or in Pending Cost if the item uses standard costing. That’s the practice vwilson92 described.

It also stops on its own. The first receipt at a warehouse replaces that warehouse’s Last Cost with the receipt’s unit cost. Transfers in and positive adjustments do the same. Issues never change it.

Until that first receipt, several things read it. With nothing received, the BOM cost roll and new BOM material lines cost the part at Last Cost. A sales order line for that part uses it as the unit cost. If it’s zero, Est. Margin is blank on that line. Inventory receipts and adjustments you enter by hand take their default unit cost from it. If the item class allows negative quantity and the part is issued before it’s received, that issue is costed at Last Cost.

josborn02’s separate estimated cost field keeps Last Cost clean if all you need is visibility. The cost roll and sales order lines won’t read that field, though.

Two things to watch in the update. Stock Items (IN202500) only lets you edit Last Cost on Average and FIFO items. With Multiple Warehouses on, it stays locked until the item has a warehouse record. Last Cost is per base unit in your base currency, while a vendor price has its own UOM and currency, so convert before you copy it. Try it in a sandbox first.

Translate