How-toSYSPROInventory Control / Bill of Materials costing

SYSPRO Cost Multiplier and How to Update an Item's Standard Cost

Question
cost multiplier syspro

Also searched as

  • syspro item cost update
  • syspro update standard cost
  • syspro cost rollup wip inventory valuation

Short answer

In SYSPRO the cost multiplier is a factor held with the stock code's cost data that scales the cost SYSPRO uses, so check the field help (F1) in your release for its exact rule. To update an item's cost, change it through stock code maintenance or a cost rollup, understand which costing method (standard, average or last cost) the item uses, and expect a standard cost change to revalue on-hand stock and affect WIP and the GL.

Applies to: SYSPRO 7 and 8; behaviour depends on the stock code's cost basis (standard, average, FIFO or last cost) and the company's inventory and GL setup.

How to update an item cost in SYSPRO safely

  1. 1Check the stock code's costing method in stock code maintenance. Standard cost items keep a fixed cost until you change it; average and FIFO items move with receipts.
  2. 2Note the current material, labour, fixed and variable overhead and subcontract components, plus the cost multiplier value, before changing anything.
  3. 3For manufactured items, update component costs first, then run the Bill of Materials cost rollup so the parent's standard reflects the new components and routing.
  4. 4Record on-hand quantity by warehouse, because the cost change revalues that stock and creates a revaluation entry.
  5. 5Apply the change in a test company or on a small set of stock codes first, and review the cost change journal in the General Ledger integration.
  6. 6Check open jobs afterwards. Jobs already in progress keep the issues they have booked, and variance appears when the job is closed against the new standard.

What the cost multiplier is for

Cost multipliers exist so a cost entered in one basis can be converted to the cost SYSPRO carries for the stock unit, for example a cost quoted per hundred or per thousand, or an uplift factor. Because exact behaviour has been adjusted across releases, treat the field help and your release notes as the authority, and test with a single stock code before applying it widely.

The practical risk is entering a value that is silently multiplied. If a unit cost looks ten, hundred or thousand times wrong after a receipt or cost change, check the multiplier and the unit of measure conversion first, before suspecting the transaction.

Standard cost changes and valuation

When a standard cost changes, inventory on hand is revalued at the new cost, and the difference is posted as a cost revaluation through the General Ledger integration. That is a real accounting event: a large increase across thousands of stock codes can move the inventory balance significantly in one period, so finance should approve the timing.

WIP behaves differently. Work already issued to a job is held at the cost it was issued at, and job variances against the standard show up when the job is completed or closed. Doing a mass cost update with many open jobs means the variance report for that month will contain cost-change noise as well as genuine usage variance.

Verifying the result

After any cost update, reconcile the inventory valuation report to the GL inventory control account for the period. If they differ, look for stock codes with a changed cost but no revaluation journal, or a GL period closed at the time.

A read-only comparison of costs before and after is cheap insurance. Export the cost fields to a spreadsheet before the update and again afterwards so you can explain any line to an auditor.

-- Read-only: list cost columns on the stock master (confirm names in your database)
SELECT TABLE_NAME, COLUMN_NAME
FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'InvMaster' AND COLUMN_NAME LIKE '%Cost%';

Try it here, free

SYSPRO BOM Material Cost Rollup Worksheet

Open full tool

Editable bill of material costing sheet with scrap allowance per component, to sanity check the rolled up cost SYSPRO holds for a parent stock code.

Common pitfalls

  • !Changing standard cost mid-month with many open jobs, which mixes cost-change effects into job variances.
  • !Updating a parent's cost before its components are updated and rolled up.
  • !Not exporting the before values, making it impossible to explain differences later.
  • !Ignoring unit of measure conversions, which can look like a wrong multiplier.
  • !Running the update in production without checking which GL period is open.

How an ERP-grounded AI assistant handles this

Netray adds a private AI layer to the SYSPRO you already run, including on-prem installs where the SQL Server and application server never leave your network. ERPray answers questions over live SYSPRO data with read-only SQL or e.net queries it shows you, under the operator's own SYSPRO security, so a planner or accountant can ask the question in plain language and see exactly which tables or business objects produced the answer. Any write-back, such as posting a transaction, goes through a human approval step. The model is open-weight and runs on your own GPUs, so company data is not sent to a public AI service.

See ERPray

Frequently asked questions

What is the cost multiplier in SYSPRO?

It is a factor kept with an item's cost data that scales the cost SYSPRO uses. The exact rule is in the field help for your release, so confirm it on one stock code before applying it broadly, particularly where costs are quoted per hundred or per thousand units.

How do I update the standard cost of a stock code?

Change it in stock code maintenance, or for manufactured items update the components and run the bill of material cost rollup. Review the revaluation journal and reconcile inventory to the GL control account afterwards. Do the first run in a test company.

Does a standard cost change affect WIP?

Costs already issued to open jobs are not restated. The difference between actual issued cost and the new standard appears as variance when the job is completed. Plan cost updates around job closure to keep variance reports clean.

Why is the cost wrong by a factor of ten or a hundred?

The usual causes are a multiplier applied unexpectedly or a mismatch between the stocking and purchasing unit of measure. Check both on the stock code before correcting the transaction itself.

Related

How-to

SYSPRO Job Will Not Close or Leaves a WIP Balance: What to Check

A SYSPRO job leaves a WIP balance or refuses to close when material, labour or overhead is still sitting on the job without a matching receipt of finished goods. Check that the full quantity has been received through job receipts, that all allocated materials are issued or deallocated, and that outstanding labour is posted. Then close the job so SYSPRO transfers the remaining difference to variance.

How-to

How to Find and Fix Negative Quantity on Hand in SYSPRO

Negative on hand in SYSPRO means more stock was issued, shipped or consumed than was ever received into that warehouse. It is almost always a timing or receiving problem, not corrupt data. Find the movements that drove the balance below zero, fix the receiving or unit-of-measure root cause, and then correct the quantity with a proper inventory adjustment so costs stay consistent.

How-to

SYSPRO Landed Cost Tracking: Freight, Duty and Allocation

Landed cost tracking adds freight, duty, insurance, brokerage and other import charges to the cost of received stock so that inventory carries the true cost to your door. In SYSPRO you define cost types, collect the charges against a shipment or purchase order, allocate them to the received lines by value, quantity, weight or volume, and the stock cost and GL valuation update accordingly.

Advanced

SYSPRO SQL Query for Inventory On Hand by Warehouse

SYSPRO runs on SQL Server with one database per company, typically named like SysproCompanyA, and inventory is split between InvMaster for part-level data and InvWarehouse for quantities per warehouse. Join them on StockCode, filter, and read the quantity columns. Use a read-only login, never write to SYSPRO tables directly, and prefer e.net business objects for any change.

How-to

SYSPRO reporting API: e.net, SRS server-side reporting, Crystal Reports and SRS preview problems

SYSPRO gives you three reporting routes: the e.net Solutions business object API (XML in, XML out) for programmatic data, SYSPRO Reporting Services (SRS) for designed reports run on the server, and Crystal-based or SQL-based custom reports. If the SRS preview does not work, check the services, the runtime and bitness, the SQL permissions and the client and server versions in that order.

Error fix

Error validating SYSPRO online profile: what it means and how to fix it

A profile validation error means the SYSPRO client or service could not confirm the operator, company, licence or database connection it was handed at logon. Check the service and licence first, then the operator and company, then the database and disk, in that order. Storage errors are usually full disks, a locked SQL file or a tempdb problem rather than a SYSPRO bug.

AI for ERP

AI for SYSPRO production and job costing

How AI reads SYSPRO WIP jobs, labor and material postings to explain job cost variances and late work orders, with read-only access and on-prem hosting.

AI for ERP

AI for SYSPRO Manufacturing Operations: From Work Centers to Answers

SYSPRO Manufacturing Operations generates data on work centers, routings, and WIP - see how private AI turns it into shop floor answers on-prem.

Stuck on SYSPRO?

Talk to engineers who work inside SYSPRO every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Software

TermsInventory Valuation Methods (FIFO, Average, Standard)