What we shipped, in plain language.

The priority-tasks data feed, the CSV/Excel export and the task analytics dashboard table now load correctly instead of failing or showing an empty table.

Cost versions and cost comparisons created through the costing service are now stamped with the user who made them.

Automatic tracking of sales order status changes now records the order's own user when no one is logged in, such as in background jobs. A failure there no longer breaks the rest of the save.

A per-unit surcharge condition used to be silently ignored for companies without a configured pricing procedure. It is now included in the calculated price.

Average template duration is now calculated in a way the database supports, so the template-performance figures display and the analytics export completes.

In line with the DPDP review, date of birth and birth year columns are now redacted in Table Explorer on all tables, including any added in future. HR users still see them on the HR screens.

If the goods issue for a POS cash sale cannot be posted, the sale is now refused with an error. Before, it could complete with a placeholder goods-issue number and no stock deducted.

Changing a customer service ticket's status or assignee outside a normal user request, such as from a scheduled job, now saves correctly. The activity entry for the change is recorded against the ticket's last updater.

Valuing forward contracts in a batch no longer fails when exchange rates are submitted. Rates are now handled to 6 decimal places, and rates for export contracts are inverted accurately.

The Vendor Master grid previously offered 11 columns. The Column Chooser now adds about 70 more, hidden by default. They cover general details, tax and GST, GST registry, MSME, accounting and TDS, default address, primary contact, payable bank account, record counts, and audit information. Your saved layouts are unchanged.

The pivot field list now includes payment term, GST registration type, GSTIN registry status, MSME category, RCM, TDS, payables account, city, state/region, country and bank.

The bank account number column shows only the last four digits, because the grid can be exported in bulk. The full number is still on the vendor form.

The stock transport order verification, previously available only from the server shell, can now be run from the Operations Console. It also creates documents and rolls them back, so nothing is kept.

The Operations Console now lists verification programs for quality management (sampling, incoming inspection, non-conformance, audits, release, calibration, document control, planning and KPIs), procure-to-pay controls and KPIs, job-work orders and movements, and the fabric roll register. Each one creates test documents on your own tenant and rolls them back, so nothing is kept. It holds row locks while it runs, so use a quiet hour on production.

The previous salary drawn on employee and candidate records, and the bank account number on bonus lines, are no longer shown in the table explorer. Other columns, such as dates of birth and the net-pay split threshold, stay visible.

Employees' payslips now open and download correctly in My Workspace. Previously the PDF link failed with a not-found error.

On the Payslip Templates page you can limit a layout to certain employee types, mark one as the default, and load the standard layout as a starting point. You can also preview the layout as a PDF. A layout with errors is now rejected when you save it, so a mistake no longer changes payslips on posting day.

Employees now see a payslip in My Workspace only after the payroll run is posted, which is when it is e-mailed. Before, it appeared as soon as it was approved.

HR can open a Payslips dialog on a payroll run to see each employee's e-mail delivery status. They can also print one merged PDF of the run's payslips, filtered by employee type, department or plant.

When a payroll run is posted, each employee receives an e-mail with their payslip as a PDF and a short summary in the body. E-mailing can be switched on or off for each payroll area. Every send attempt is recorded, and HR can resend payslips.

Each sub-contract order line has a specification based on its process. Mandatory fields are checked when the order is submitted and approved. The specification prints on the purchase order and on a new job-work challan. You can copy it from an earlier order, and after issue it can only change by amendment.

The BOM now sets the process-loss norm for each component, and the order shows the expected output. The norm is frozen once the order leaves draft.

Closed lots are reconciled against the norm. Loss is recognised only for closed lots, excess and weight gain are shown per component, and material still at the job worker is written off as loss. Each loss is valued at the recovery rate for its material group, or at the issued valuation if no rate is set.

A recovery proposal is created fortnightly for each job worker. The Fabric Head reviews it with reasons, and management approves it in My Approvals. The person who submitted it cannot approve it. Accounts then posts an AP debit note, and the MD can write off any part that is not recovered. A recovery working can be printed.

Record each job worker's approved processes, with an expiry date worked out from the approval. You can also record machines and capacity, and buyer nominations. Warnings about these need a reason, and an advisory finder suggests suitable job workers.

Rate cards propose a rate by process, fabric, shade and lot size band, and apply a minimum lot charge. Deviations from the card and extras need the Fabric Head's approval as part of the order approval. Approved orders keep the rate they were approved at. Extras are recorded and approved but are not yet added to the PO line value.

A new Job Work screen covers lots, recovery, rate cards, job worker approvals, capability and nominations. New reports show loss against norm, the recovery register and rate deviations. Reminders go out for the fortnightly recovery digest and for approvals that are about to expire.

Supplier codes such as SUP00123 and SUP00124 used to get the same job-worker stock location. The second job worker's first transfer then took over the first one's location. Each job worker now gets its own location. Locations that were already assigned wrongly are not repaired.

A stage's output can be received at job worker A and sent straight on to job worker B against B's approved order component, in one step. The challan is issued in B's name, the batch carries over, and no journal is posted. A chain movement register lists these movements.

A supply purchase order line can name the job worker and the order component it feeds. The goods are received into the job worker's location for the acknowledged quantity, which needs the receipt note, its date, the quantity and the attached file. Any billed quantity above that appears as the invoice's normal quantity difference.

Every goods transfer to a job worker now gets a challan number from a series per process. The challan print shows the actual from and to premises, line values and the e-Way Bill. You can generate an e-Way Bill for issue, chain and company-issued return challans. The screen says when one is required but doesn't force it, and cancelling is allowed only within 24 hours.

A goods transfer to a job worker can now be reversed. A challan whose e-Way Bill is still active cannot be reversed until that e-Way Bill is cancelled.

You can build ITC-04 tables 4, 5A, 5B and 5C for each GSTIN and period from your job-work documents. Validation names the failing document, and export to the portal template is refused while any row fails. Marking a period filed freezes it, and a late document goes into the next period.

Open challan quantity is worked out by matching receipts and returns to challans oldest first. Alerts are raised once each at 9 and 11 months and at 33 and 35 months. Lines past the limit go on a deemed-supply list showing value and tax. Nothing is posted. Stock-at-job-workers and chain-register reports are also added.

A new Job-work Movements page brings these functions together. Existing open challans can be loaded from the legacy system, with a test run before applying.

A receipt or issue is refused when the roll weights do not add up to the kg posted, within 0.5% or 1 kg, whichever is larger. A partial quality usage-decision split on a lot held as rolls is refused with a message.

New permissions control who can view, manage and print rolls, issue them to cutting, and grade them. A new Cutting Roll Issuer role is available. Administrators need to assign these permissions or the role to the right users.

New reports show roll stock, shade band by lot, and lot-to-roll traceability, from upstream lots to rolls to cut lots.

Each fabric roll is recorded at receipt with gross, tare and net kg, GSM, width or dia, length, shade and shade band. A new Fabric Rolls screen under Materials has tabs for the register, scanning and moving rolls, capture at receipt, inspection and grading, reports and set-up. Materials only become roll-managed when you configure them, so nothing changes for tenants that don't.

Key in the rolls of a receipt by pasting the packing list, or quick-enter a count of rolls at a given kg each. Rolls can be captured against purchase-order lines and sub-contract receipts. Roll IDs come from the plant's numbering series and are never reused.

Print roll labels at 100 × 50 mm, on A4, or as ZPL for label printers. A reprinted label is marked COPY and every print is logged. A per-lot roll list can also be printed.

Scan rolls onto job-work challans, returns from the job worker, store transfers, issues to cutting and scrap. A roll's status follows its location, and every roll event is recorded in its history. A roll at the wrong store, or in a state that cannot move, is refused with a reason. The roll receipt on a job-work chain passes on exactly the rolls received.

Inspection grades each roll as A, B, seconds or rags from points per 100 sq. yd, with thresholds you can set per buyer. Grades come only from the inspection. Seconds and rags rolls stay blocked until a posted usage decision on their lot releases them.