Raghav Mittal
Menu
Approach →
Services
Shopify CRO Find and fix the friction between a visit and a completed checkout: product pages, collections, cart, checkout, speed, trust and tracking. Subscriptions Launch, fix or migrate Shopify subscriptions: offer design, app choice, customer portal, cancellation flows, failed-payment recovery and retention reporting. Shopify & Web Build or clean up websites that are fast, trackable, SEO-ready, and designed around how buyers actually decide. Shopify Automation Connect Shopify orders, customers, inventory, fulfilment, support, subscriptions, and reporting so your team spends less time moving the same information. SEO & UX Find the crawl, speed, mobile, UX, and conversion issues that stop good pages from ranking or turning traffic into leads. AI Workflows Use AI practically inside business workflows: Excel analysis, PPT reporting, SOPs, dashboards, content, and team documentation. Automation Replace manual follow-ups, spreadsheet relays, and status chasing with trigger-based systems that move work automatically. CRM Systems Turn your CRM from a contact database into an operating system for pipeline, ownership, follow-up, and reporting. Lead Systems Capture, qualify, assign, and follow up with leads across forms, CRM, WhatsApp, email, and sales teams. GST + Tally Connect the work between sales, invoices, GST review, Tally, reconciliation, and management reporting so finance operations have fewer blind spots. TallyPrime Integration Connect approved orders, invoices, inventory and customer records to TallyPrime with maintained mappings, confirmed results and reconciliation. Tally TDL Development Adapt the work inside TallyPrime with scoped TDL fields, validations, reports and document layouts, tested against your installed release. Shopify + Tally Connect Shopify orders, payments and refunds to Tally with clear stock ownership, approved accounting mappings and daily reconciliation. Distribution Software Connect buyer catalogues, tier pricing, purchase orders, warehouse tasks and stock movements in one distribution application. How we workScope, review and first-milestone payment View all servicesBrowse the complete delivery bench →
Blueprints → Work → Blog → Free Audit → Book a strategy call
Automation· Oct 18, 2026· 6 min read ·Updated

Job Work Automation: Track Material Sent, Received and Pending

Track outsourced job work with linked material movements, partial receipts, unused returns, scrap review and an accountable outstanding-material queue.

Editorial illustration: Job Work Automation: Track Material Sent, Received and Pending
Editorial illustration of the article’s workflow.

Key takeaways

  • Keep a job-work reference across dispatch, receipt and follow-up.
  • Separate physical movement from consumption and commercial closure.
  • Support partial receipts and unused returns without losing the open balance.
  • Assign an owner and next action to every unexplained difference.

Putting this workflow into practice? Explore Automation Systems Architecture for implementation scope, controls, and next steps.

Job work automation is useful when the factory can explain where its material is, which outside operation it belongs to and what must happen before the job closes. A register of dispatches alone cannot answer that. The system needs connected receipts, returns, consumption and unresolved differences.

This article proposes an operational tracking workflow for a principal manufacturer using outside processors. The examples are illustrative. Configure the accounting and statutory treatment with the responsible finance team; an operational balance should not be presented as a completed compliance determination.

A sample job-work outstanding register you can check

Download the synthetic job-work register and adapt the columns to your movement records. For JOB-DEMO-41, 100 kg is sent, 72 kg is physically received and 3 kg is an approved process loss. Outstanding material is 25 kg: 100 − 72 − 3. These are illustrative quantities, not client results.

Two kilograms of the received material remain on quality hold. They belong in the quality queue, but they have already returned physically, so they are not added to material still with the job worker. An unapproved loss remains an exception until the responsible reviewer accepts it. Keep every calculation in the same unit and reconcile conversion rules separately.

If an authorised correction changes the receipt to 70 kg, outstanding becomes 27 kg. Retain the source movement, correction reference and approver so the change is explainable. The TDL report specification example shows how the same reference and quantities should survive entry, alteration, printing and export when this workflow belongs inside Tally.

Review your job-work tracking process with one redacted outward document, return receipt and the current exception register. Those records help define the workflow before choosing software.

Establish the relationship before moving material

Record the outside processor, operation, expected output, planned input and agreed return date. Use stable item and order references rather than relying on free-text descriptions. Define how the factory distinguishes its own stock from material belonging to another party.

A single processor may handle several open jobs using the same material. The receipt team needs a way to allocate a delivery to the correct order. If the business allows one delivery to satisfy multiple jobs, the allocation should be visible rather than hidden in a narration field.

Tally's job-work setup guide covers job orders and Material Out and Material In configuration. The chosen consumption setup affects how receipts and material use are recorded. Confirm that setup before building an external reconciliation.

The workflow at a glance Follow material from issue to outstanding balance
  1. Link the job-work issue
  2. Record returned material
  3. Separate losses and adjustments
  4. Review the outstanding balance
100Issued (kg)
72Returned (kg)
3Recorded loss (kg)
25Still outstanding (kg)

Fictional example: 100 − 72 − 3 = 25 kg outstanding. A 2 kg quality hold within the returned material is part of the 72 kg, not an extra deduction.

Connect each movement to its source

Capture dispatch date, reference, item, quantity, unit, source location and the job-work order. Attach the operational evidence your team uses to acknowledge transfer. A transport document and a processor acknowledgement can have different purposes; keep their references distinct.

Record returns against the relevant dispatch or order allocation. Do not close an order just because a receipt exists. A processor can return only part of the expected output, return unused raw material or deliver a quantity that needs inspection before acceptance.

Event Quantity to record Question for the operator
Material sent Input by item and unit Which job and processor received it?
Finished output received Actual output by item Which order allocation does it satisfy?
Unused material returned Original material returned Is it available again or awaiting review?
Scrap or loss reported Quantity and reason in its own unit Who approved the treatment?
Difference unresolved Documented outstanding position What evidence or action is still needed?

Avoid subtracting unlike quantities

If material leaves in kilograms and returns as finished pieces, raw subtraction is meaningless. Define the approved conversion or material-consumption relationship and preserve the units in every comparison. Some processes have variable yield, so a standard quantity may be an estimate that requires actual confirmation.

For an illustrative machining job, a dispatch contains metal stock while the return contains components and offcuts. Track the output, unused stock and offcuts separately. A zero piece balance does not prove the input material has been fully reconciled.

Use the same principle when processors return output across several dates. Keep movement-level evidence and an order-level summary. The summary must be reproducible from those movements so a corrected receipt does not leave an unexplained manual adjustment behind.

Keep physical and commercial closure separate

A job may be physically complete while the service invoice still needs review. Another job may have an approved charge but an unresolved material difference. Model those states separately and show the next owner for each one.

Agree what evidence permits closure. It could include accepted output, resolved unused material, approved loss treatment and a reconciled cost reference. These are business-specific decisions; avoid automatically writing off an outstanding quantity because the expected return date has passed.

Build an outstanding-material action queue

Show processor, operation, job reference, first dispatch date, latest movement, expected return and the type of unresolved balance. Age the pending obligation from a defined date rather than resetting the clock whenever somebody adds a comment.

A useful follow-up identifies the missing action: confirm delivery, return unused stock, explain a yield difference or supply a corrected receipt. Record the response and next promised date. A reminder that simply repeats “job pending” creates activity without improving control.

Keep the decisions clear Three facts that need their own evidence
Material returned
Quality hold
Commercial settlement

Track these separately. Evidence for one does not automatically confirm the others; use the article’s review and ownership checks.

Implementation work to scope

  1. Map the job order and dispatch identifiers used by stores, production and finance.
  2. Decide the allocation rules for several dispatches and partial receipts.
  3. Establish unit conversions, actual consumption and loss review responsibilities.
  4. Build the outstanding view with ageing, reasons and next-action dates.
  5. Reconcile the operational movements with the selected accounting records before closing a pilot job.

Where a connector is needed, use supported interfaces described in Tally's integration methods. The implementation should distinguish an accepted request from a confirmed business result.

Test the difficult returns

Rehearse a partial delivery, a receipt against the wrong order, excess reported output, returned raw material and a loss awaiting approval. Correct a previously entered movement and confirm the summary changes without losing the earlier evidence.

Include one opening outstanding job in the pilot. Historical balances often lack the detail available for new transactions. Mark estimated opening allocations clearly and get approval before treating them as reconciled facts. This makes the first production report more useful than a clean screen built from incomplete history.

For quantity discipline, also review multiple-godown inventory. Explore automation systems, GST and Tally integration, or share one job-work cycle to scope the handoffs and exception owners.

Frequently asked questions

How should partial job-work receipts be tracked?

Link each receipt and allocation to its job and original material movements. Record accepted output, unused material, scrap and unresolved differences separately so one receipt does not prematurely close the job.

Can kilograms sent be subtracted directly from pieces received?

No. Preserve the units and use an approved conversion or actual consumption relationship. Finished output, offcuts and unused raw material need separate evidence before the input balance can be explained.

Related implementation guides

Automation Systems Architecture

For teams where leads, orders, operations, or reporting still depend on memory, WhatsApp nudges, and manual sheet updates.

Explore the service →
Turn the idea into a working system

Which handoff is slowing your team down?

Describe the process, its tools and one exception your team handles manually. We can define a focused workflow pilot.

Prefer a conversation? Book a call →
Keep reading
View the full archive →