How-toSYSPROInventory / Costing

SYSPRO costing methods: standard, average, FIFO and last cost

Question
syspro costing method

Also searched as

  • syspro standard cost vs average cost
  • syspro fifo costing
  • syspro last cost

Short answer

SYSPRO sets the costing method on each stock code, so one company can mix methods. Standard cost holds a fixed cost and posts variances, average cost blends receipts into a moving cost, FIFO values stock at the cost of the oldest layers, and last cost uses the latest purchase cost. The method drives inventory value, WIP and variance postings.

Applies to: SYSPRO 7 and 8. Field names and available options can differ by release and by version of the inventory module, so confirm in Inventory setup and the help for your build.

Check and understand the method on a stock code

  1. 1Open the stock code maintenance program in Inventory and find the costing method on the stock code.
  2. 2Check the cost fields: material, labour, overhead for standard, and the current unit cost for the others.
  3. 3Review the cost related setup options, including how receipts and variances are posted to the GL.
  4. 4Run an inventory valuation report to see the extended value under the current methods.
  5. 5If you plan to change method, test on a copy company first and review the effect on the GL control accounts.
  6. 6Agree the change with finance, because it alters inventory value and the way variances arise.
  7. 7Document the date and reason for audit.

How the four methods behave

Standard cost fixes the unit cost until you roll it. Receipts and production at a different actual cost post purchase price and production variances, which makes performance visible but needs a disciplined cost roll. Average cost recomputes after every receipt, so value follows reality and variances are small.

FIFO consumes the oldest layers first and suits items where cost changes quickly and layers matter, at the price of more data to carry. Last cost values stock at the latest purchase cost and is simple but can swing value sharply, so it is rarely right for finance reporting on its own.

Effect on WIP and variances

For manufactured items, the issue of materials to a job and the receipt of the finished good use the method of each stock code. With standard costing, the job accumulates actual cost and the receipt relieves WIP at standard, leaving a variance when the job closes. See the page on jobs that will not close for how that variance behaves.

With average or FIFO, the finished good is received at the actual accumulated cost, so there is little or no variance, but cost changes flow straight into margin on the next sale.

Changing the method

Changing the method on a stock code that has on-hand stock or open jobs needs care. The system must revalue or reclassify the stock, and the GL effect can be large. Make the change in a controlled window with stock counted and open jobs reviewed, and rehearse it on a copy.

Never change methods casually to fix a variance. Find the cause first, such as a stale standard, a bad receipt cost or a wrong unit of measure.

Try it here, free

SYSPRO Job Costing Worksheet

Open full tool

Enter estimated and actual material and labour for each WIP job and see cost variance per job and in total. Exports to Excel.

Common pitfalls

  • !Mixing methods across components of one assembly without understanding the variance flow.
  • !Letting standards go stale, so variances become noise.
  • !Changing method with open jobs and stock on hand without a rehearsal.
  • !Relying on last cost for financial valuation.
  • !Not telling finance, so the valuation moves without explanation.

How an ERP-grounded AI assistant handles this

An assistant over your SYSPRO data can list stock codes by costing method, show where standard cost differs from recent receipt cost, and explain a variance in plain language, in read-only mode. Netray deploys it on-prem so cost data stays private.

Frequently asked questions

Can different stock codes use different methods?

Yes. The method is held at stock code level, so a company can mix them. Just be sure finance understands the GL effect of each.

Which method is best for manufacturing?

Standard costing is common in stable repetitive manufacturing because it exposes variances. Average cost suits volatile materials. The right answer depends on how finance reviews performance.

Where do variances post?

To variance accounts defined in the GL integration setup. Check the mapping so purchase price and production variances reach the accounts finance expects.

Will changing the method revalue stock?

It can, depending on the method and setup. Test on a copy and review the journal that results before you do it in production.

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.

Error fix

SYSPRO GL interface error: how to diagnose and fix it

A GL interface error means a subledger transaction could not build or post its journal to the General Ledger. The usual causes are missing or invalid GL account mapping, a closed or invalid period, journals left unposted, or an out-of-balance entry. Find the failing transaction, fix the mapping or period, then post the pending journals.

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.

How-to

How to update SYSPRO (and how to check the latest version)

SYSPRO 8 ships as named releases (for example 2022 R1 style names) plus later updates, and the current release is listed on the SYSPRO partner and customer portals, not on a fixed public page. To update, back up, test the new build on a copy of your data, then update the server, services and clients in a planned window.

AI for ERP

AI for SYSPRO, Grounded in Your Own Manufacturing Data

Add AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.

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.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Software