How-toSYSPROWork In Progress / Job Close

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

Question

SYSPRO job will not close WIP variance job receipts

Also searched as

SYSPRO how to close a job
SYSPRO job close WIP balance not zero
SYSPRO job completed but still in WIP
SYSPRO job variance posting

Short answer

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.

Applies to: SYSPRO 7 and SYSPRO 8 Work In Progress with standard or actual costing; menu names vary slightly between releases and the new UI

Checklist before closing a job

1Open the job in the WIP job query and confirm the job status and the quantity to make versus the quantity received.
2Post any outstanding receipts of finished goods or by-products through the job receipts program, using the right warehouse, lot or serial details.
3Review the materials list for allocated but unissued components and either issue them or deallocate the remaining quantity.
4Check labour and machine time: confirm that all operations have run times posted, and that no unposted or held time entries remain for the job.
5Check for open purchase order lines or subcontract operations still tied to the job, and receive or cancel them.
6Review the job cost summary: material, labour and overhead issued versus the value received into stock, and read the difference.
7Run the job close program so the remaining balance is moved to job variance, then run the WIP and inventory reports to verify the job shows zero.
8Reconcile the WIP control account in the general ledger at period end.

What a WIP balance is made of

For each job SYSPRO accumulates the cost of material issued, labour and machine time, overheads and any subcontract cost. When finished goods are received, the receipt value relieves WIP. Anything left after the last receipt is the WIP balance. A job that cannot close has either not received all its output, or has charges that arrived after the last receipt.

Under standard costing, receipts relieve WIP at standard cost, so the remainder is by definition variance. Under actual costing the receipt picks up the actual cost accumulated to date, and later charges remain in WIP until you close.

Common causes by symptom

Quantity short of the order: the last few units were scrapped or never reported. Receive the good quantity and close the job short, or adjust the scrap through the proper scrap posting so yield variance is visible rather than buried.

Materials issued in excess of the bill: a larger issue than the bill of materials implies shows as a usage variance at close. That is the correct outcome, but check whether a bill of materials or backflush error caused it, since the same error will hit the next job.

Late labour or subcontract invoices: costs posted after the receipt leave a balance. Post the pending costs, then close.

Verifying with SQL

A read-only query against the WIP tables lists open jobs that are complete in quantity terms but still carry cost. Column names differ between releases, so confirm them in your data dictionary and treat the query as a starting template.

-- Template only: confirm table and column names for your release
SELECT Job, StockCode, QtyToMake, QtyManufactured, Complete
FROM WipMaster
WHERE Complete <> 'Y'
  AND QtyManufactured >= QtyToMake;

Variance accounting at close

Closing a job writes the remaining balance to the variance accounts defined in your WIP GL integration, split into material, labour and overhead variance where your configuration supports it. If the variance is large relative to job value, review it before closing, because closing is hard to reverse once the period moves on.

Common pitfalls

!Closing jobs in bulk without reviewing variances, which pushes real cost problems into a single variance account.
!Leaving allocated but unissued materials, which keep demand and allocation alive on stock after the job is finished.
!Receiving finished goods to the wrong warehouse and compensating with transfers rather than fixing the receipt.
!Forgetting subcontract purchase orders tied to operations, so a cost arrives after close.
!Closing a job in a period that is already locked for GL, forcing a reopen.

How an ERP-grounded AI assistant handles this

An assistant grounded in SYSPRO can list jobs that are quantity-complete but still carrying WIP, show per job which of the usual causes applies (unreceived output, unissued materials, unposted labour, open subcontract lines) and quantify the variance that closing would book. Closing the job is a write, so in Netray's approach it remains a human-approved action with the evidence shown beside it.

See ERPray

Frequently asked questions

Can I reopen a closed job in SYSPRO?

Depending on release and settings, you can reverse or reopen under controlled conditions, but it is not a casual step. Reopening affects WIP and variance postings, so involve finance and check the period status first. It is better to review the job thoroughly before closing.

What is the difference between completing and closing a job?

Completing means the quantity has been manufactured and received. Closing is the accounting step that clears any remaining cost to variance and stops further transactions against the job. A job can be physically complete but still open with cost on it.

Why is there WIP value left when all quantity was received?

Under standard costing the difference between actual issues and the standard value received remains until closing. Under actual costing late charges can also remain. Compare the job cost summary with the receipts to see which component, material, labour or overhead, accounts for the balance.

Does closing a job release allocated material?

You should issue or deallocate material before closing so the allocation does not linger. Check the job's material list and the stock allocation figures afterwards, since stale allocations reduce available stock and distort material requirements planning.

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

How to Run Requirements Planning (MRP) in SYSPRO

SYSPRO's MRP engine lives under Planning and Scheduling > Requirements Planning. Set planning parameters per warehouse, run the Requirements Calculation to net demand against supply, then review and release the resulting suggestions as purchase requisitions or work orders. A full regenerative run typically runs on a schedule, with net change runs in between to pick up new activity.

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

How to Create a Generic Inquiry in Acumatica

Generic Inquiries (GI) are Acumatica's no-code query builder for joining tables, adding filters, and exposing the result as an inquiry screen, dashboard data source, or API endpoint. Open System > Customization > Generic Inquiry, add your base table, define joins and conditions, then run and save. No SQL or customization project is required.

Error fix

Fix Odoo AccessError: You Are Not Allowed to Access Records

Odoo raises AccessError when a user's security groups do not grant a CRUD right on a model through ir.model.access.csv, or when an ir.rule record rule filters the specific record out for that user or company. Fix it by adding the user to the group named in the error, editing the model's access rights, or reviewing the record rule's domain under Settings > Technical > Security.

How-to

How to Void a Check in Sage 100

Sage 100 voids checks through Accounts Payable > Main > Check and Payment Voiding. Select the bank code, choose the check number, and Sage reverses the Cash Disbursements Journal entry and reopens the invoice it paid. A check that already cleared in Bank Reconciliation or falls in a closed period needs an extra step before it can be voided cleanly.

AI for ERP