USE CASE

Subcontract jobs

Send material out for processing and always know what the job worker holds.

The problem

Plating, machining or painting goes to an outside vendor. Material leaves on a gate pass, comes back weeks later in different quantities, and the stock register never matches what the job worker actually holds.

The flow in Sundial

1. Set up the subcontracted item. Define the bill of materials for the service: what you supply and what comes back.

2. Raise the subcontracting order. Create the order against the job worker with the service charge and finished quantity.

3. Send the raw material. Transfer the supplied material to the supplier’s warehouse with a stock entry. It stays your stock, held at the job worker.

4. Receive finished goods. Record the subcontracting receipt. Sundial consumes the supplied material against it and values the finished goods at material plus service cost.

5. Settle the job worker. Book the job worker’s bill against the order and return any unused material.

What the team sees

Buying sees each open job with sent, consumed and pending quantities. Stores sees material held at every job worker. Finance sees finished goods valued with their processing cost included.

Why it holds up

Material at a job worker is held in a warehouse of its own, so it appears in stock reports instead of disappearing on a gate pass. Consumption is calculated from the bill of materials on receipt, which makes over-use or loss at the job worker visible. The service cost lands in the finished goods’ value, so margins include it.

With AI (coming to Sundial)

Coming to Sundial: ask “how much of our material is sitting with job workers right now?” in plain language.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us