What we shipped, in plain language.

Print and Download on a GST receipt voucher opened a new tab that landed on an authorisation error. The voucher is now fetched through the signed-in session, as every other printed document is, and a failure is shown on the panel instead of in a dead tab.

A lay slip now records the spreader it is issued to.

The cutting QC inspection screen can now send some of a bundle’s pieces to rework rather than the whole bundle; the pieces sent are recorded on the bundle.

A cutting note can be previewed and printed from the cutting-notes list, with its bundle table and page totals. The layout is a print form, so a tenant can have its own.

A new Down-Size screen records re-cutting pieces of a larger size into a smaller one between cutting and bundling. Pieces are conserved one for one, only downwards, and only from pieces not yet bundled. A size position table shows, per size, what was cut, what is required and what has been re-cut.

Only one approved marker was allowed per production order. A style is regularly cut from several — a different size set, a different lay length, a re-cut — so any number of markers may now be approved for the same order and colourway. The lay slip screen also shows more of the marker it was cut from.

Every short permission was refused where the company had not published a shift roster. The employee’s work schedule can now carry a default shift, used when no published roster covers the day; a published off day is still the roster’s answer. Which of the two answered is recorded on the permission and shown in the register.

A permission type can now be unpaid. The hours are priced once, when the permission is recorded, as a fraction of a day against the shift’s paid hours, and payroll deducts that stored figure — so a later change to the shift does not re-price a deduction already settled.

Every ledger row was dated the moment it was keyed, so a back-dated goods movement sat in the month it was entered rather than the month it belongs to. Each row now carries its posting date, and the Material Ledger reads periods by it.

Rows also carry the fine movement code (so a cancelled purchase receipt is no longer counted as an issue) and the company. A location transfer is now recorded as an out/in pair instead of a single issue.

A new report at Materials → Stock Abstract shows, for any date range, opening stock, receipts and issues by column, and closing stock — per material group, in quantity and value. Closing = opening + receipts − issues holds on every row by construction: a movement no column claims lands in Other Receipts or Other Issues rather than disappearing.

The column set is configurable per company, and a layout can be split into blocks (for example Yarn → Knitting WIP → Fabric), so the same transfer to a sub-contractor is an issue in one block and a receipt in the next. Groups drill down level by level to the material and on into the Material Ledger, and each block exports to Excel.

Material sent to a job-worker could be issued but never brought home. A new Returns from Vendor tab on the Sub-contracting page records what comes back — left over after conversion, a full return because the delivery date cannot be met, or a partial return after the order was cut — against the vendor’s delivery challan, with the reason recorded.

A return is refused if it exceeds what is still at the vendor on the order, or what the vendor location actually holds. It moves stock and the Material Ledger only; no journal is posted, since the material was ours at the vendor too. Vendor Stock gains a Returned column.

A bundle line removed from a cutting note reappeared on the next read, was counted in the note’s totals, and was even turned into a bundle and a label on confirm. Removed lines are now excluded everywhere.

Adding a bundle to a note that had ever had a line removed failed with “Failed to add bundle”; it now takes the next free bundle number.

The size on a cutting-note bundle is now picked from the sizes the production order is committed to make, for the note’s colour, falling back to the marker’s size ratio. A size the order does not make is refused by name. An order that carries no size variants still lets the size be typed.

A new Holidays page under My Workspace lists the year’s national and festival holidays, read straight from the Production Planning calendar — the same calendar the plant already schedules against, so there is no second list to keep in step.

A project’s company decides its chart of accounts, its posting periods and every settlement, billing and labour journal raised under it — and neither the API nor the Overview screen had ever set it.

Naming a sales order now derives the company and the customer from it, and a company that disagrees with the order is refused by name. Where there is no order — capital expenditure, internal work — the company is chosen on the Overview tab. Changing an established company is refused once journal lines exist under it, or once the cost plan names accounts outside the new company’s chart.

Reported as “there are many columns in the tasks report but some are missing in the Pivot analysis”. The two tabs are the same rows, so a reader expects the same columns — but the pivot built its own projection of about twenty fields while the grid renders fifty-one. A field absent from the data is not merely unplaced in the pivot: it cannot be dragged in at all.

Department, Assigned Role, All Assignees, WBS, Task Definition, Verified By, Critical Path and every actual, revised, float and weight figure are now there. The built-in layout is unchanged and the new fields wait in the field list, so a layout anyone has already saved still loads.

Three details make them behave: a tenant’s own column caption now reaches the pivot as well as the grid, so one caption renames the column on both tabs; a date reaches the pivot as the day it names rather than a timestamp, which otherwise makes one member per row; and a measure with no answer is blank rather than zero, which would have read as a real zero.

Order Quantity is now offered, defaulting to Max rather than Sum — an order’s quantity repeats on every task of that order, so a Sum multiplies it by the task count. Withholding the field entirely was the earlier answer, and it read as a missing column.

Project cost plan lines, change-request lines, activity rates, timesheet lines and budget document lines now name an expense account from the chart of accounts instead of a separate cost element.

Nothing in this product ever posted by cost element — actuals key on the account — so the element was a second master with no screen and no interface, kept in step with the chart by hand, which could only ever lose resolution against the ledger. One place now decides which accounts may be planned on: postable expense leaves of the project company’s own chart, refusing a heading, an inactive account, another company’s account or a non-expense account by name.

Plan against actual now keys on the same account on both sides. Existing plan lines are carried forward where the element named an account.

The automatic debit note on an over-billed purchase invoice is now documented in the in-app help: when it triggers, what it posts, why under-billing raises nothing, and how to turn it on.

Opening balance plus open receivables less unapplied credits is opening balance plus debits less credits. Four things were breaking that identity:

• The outstanding list was filtered to the fiscal year while the balance counted every open invoice ever raised.
• An unapplied receipt is a term of the identity that can appear in no list of invoices, and was being left out of the reconciliation entirely.
• Allocating a receipt wrote back only the invoice half, so every receipt reported its whole value as still unapplied.
• The cached allocated figure was nudged by a difference rather than rebuilt, which left 38 invoices allocated past their own debit amount.

The allocation rows are the record and those cached columns are a summary of them, so they are now recomputed, never adjusted by a delta. The customer’s balance is the net balance rather than the aging total — which ignored every on-account receipt, in the balance and in the credit check alike.

Administrators: reconcile_customer_ledger_allocations repairs existing data. It reports before it writes.

Converting a sales order BOM into a budget now counts the multi-level explosion correctly — top-level structures only, so a garment is not charged again under its own panel and fabric — and the budget delta reads the same way.

All three wrote their rows in bulk, which skips the step that stamps the created and updated columns — so taking the first baseline failed on a missing timestamp. All three now stamp every column.

Taking a baseline and approving a cost plan were also wrapped in a transaction opened on the wrong connection, which on a tenant means effectively no transaction at all. Both are now bound to the tenant’s own connection, so each either completes in full or leaves nothing behind.