What we shipped, in plain language.

• The Hire-to-Retire Pay stage uses the standard House Rent and Conveyance Allowance wage types every tenant has.
• The demo connects to local tenants on Windows machines that cannot resolve *.localhost.

• The grid no longer stays blank after loading or after choosing another account until the page is changed.
• When an account is flagged for open items but has none yet, the page says so and offers Build from history.

• Registering an attendance agent failed with a server error on every tenant. It now works.
• Creating a shift swap request no longer fails.
• A plant time zone must be a name such as Asia/Kolkata; offsets such as "GMT+5:30" are refused, and existing ones are converted to Asia/Kolkata.

The Vendor and Customer Balance Lists show the control account by name only, for a shorter, more readable column.

The Human Resources menu has been regrouped so related screens sit together.

The Reference column on GL Open Items used to read "Line 1 Tax" or "Line 2" for vendor invoice items. It now shows the supplier's Bill No, the payment's Cheque No / UTR, the supplier credit note number or the customer invoice number, whichever applies. Existing items are corrected without any data repair.

Creating or editing a purchase requisition now opens in the page in place of the list, instead of a pop-up dialog.

Creating or editing an employee now opens a full page (/hrm/employees/new and /hrm/employees/<id>/edit) instead of a dialog over the list.

Presenters can run the guided demo walkthroughs without the source code. A small demo shell downloads a signed bundle of walkthroughs, verifies it and runs it; new demos arrive as a new bundle with no reinstall. The bundle is published automatically after a production deploy.

A journal that had been posted to another company's GL account could not be reversed. A reversal now hits exactly the accounts its original hit, so it always cancels it.

Customer receivables, invoice revenue, tax codes and AP round off name one GL account, so one company's sales invoices could post into another company's ledger.

• The account is now resolved to the posting company's own account on the same chart of accounts node, or the posting is refused with the account named.
• Journals to another company's or a deleted GL account are refused at entry and on Post.
• AP Posting Configuration refuses another company's accounts.

A GL account could show one balance on the GL Ledger and a different one on the Balance Sheet. Several causes are fixed:

• Older foreign-currency receipt journals that already held rupee amounts were being converted a second time. They are restated by a repair command.
• A GL account with postings can no longer be deleted, and a second live account cannot be created on the same chart of accounts node. Existing duplicates are merged.
• Both balance sheets now carry Surplus brought forward for earlier years that have not been closed.

The GL repair commands can be re-run safely: an already repaired journal is skipped quietly, deleted accounts with postings and no live twin can be restored, and reversed pairs are left alone. A production run book is documented.

Receipts re-done under the same number no longer leave an unlinked, fully open entry behind in the customer ledger, and direct-invoice reversals are settled by an allocation record. Repair commands are provided for existing data.

The Issues & Changes tab now has a New Change Request button that creates a draft. The message for a circular activity dependency now names the two activities in the right order.

• The Overdue card now counts what its drill-down lists.
• The dead bulk "Assign" and "Export Selected" items are removed.
• The Template form marks Task Source as required.
• Recurrence labels read "Every N days".
• New Task Report Labels page and a sample workbook for Tasks Upload.

• Voiding a loaded piece's only scan no longer resets it to "Created".
• The DHU report now uses the same definition as the board, and reports coded and uncoded defects separately.
• A void now reaches the hourly rollups immediately.
• Rework recording validates before writing the scan.
• Loaded and WIP counts come from pieces, not load scans.
• Stale-WIP with 0 hours no longer falls back to 72.
• Quality Analytics default end time uses local time.

The Payment Allocation screen now allocates by side, not by document type.

• Credit notes and credit journals can be cleared against invoices alone or together with a receipt.
• Debit journals are now treated as receivables and can be settled.
• Manual, automatic and mass allocation share one write path, so repeating a pair no longer fails.
• The 100-row cap on open items and unmatched payments is removed.

The GL Open Items screen loads about five times faster and its summary is near-instant.

• Now a Syncfusion grid with filtering, grouping, export, column chooser and saved layouts.
• New columns: Document Date, Reference and Vendor / Customer. The party is left blank when it cannot be determined, never guessed.

Eight UAT scripts (UAT-TM-001 to 008) cover templates, projects, task create / edit, dashboard, recurring tasks, time tracking, worksheet / upload and capacity / chat access.

Two new reports under Finance → Reports show opening balance, debits, credits and closing balance for every vendor and customer, with the control account.

• Read from the sub-ledgers, so each row equals that party's own statement.
• A foreign-currency customer with no exchange rate is flagged, never silently converted at 1.0.
• Access is controlled by the new View AR Reports permission.

Six UAT scripts (UAT-PS-001 to 006) cover projects and WBS, network scheduling, people and timesheets, cost governance, meetings and chat, and dashboard access.

Five UAT scripts (UAT-PT-001 to 005) cover setup and profiles, pieces and labels, scanning, rework and analytics, and the board, cost and access.

Creating, changing and deleting tasks, projects, templates, definitions and recurring tasks (including bulk update and delete) no longer rides on the read permission. They now require the add / change task permissions.

• Creating a service order failed with a server error because a date field defaulted to a date-and-time.
• The dashboard counted statuses that do not exist (Open anomalies, In-Repair breakdowns).
• Completing a maintenance schedule never moved the plan's next due date.
• Work-order labour and parts actions were unusable, task number was wrongly required, and labour hours did not roll up.
• Missing validation on several PM forms is now enforced by the serializers.

A new Change Requests list, a Production Order cost page and cost-reference freezing, clearer BOM and routing editing, plant configuration for stock posting, and corrections to MRP planned-order conversion, variant matrices, SO BOM and pre-packs found while scripting the Production UAT.

Confirming a production operation can now back-flush the components and receive the finished good into stock. It is opt-in per plant and off by default. Confirmation, stock and GL postings are one block: a shortage or a missing account refuses the whole confirmation rather than half-posting. Operations can also be put On Hold.

New reliability (MTBF, shown as not available rather than 0 when there is no failure history) and maintenance compliance reports, plus a 37-step Plant Maintenance walkthrough and training guide.

New acceptance test scripts covering BOMs, routing, MRP, scheduling, production orders, shop floor, prepacks and style intent (Production Planning), and UAT-CR-001 to 005 for markers, cutting jobs and notes, lay slips, bundles and QC, down-sizing and reports.

Production Planning endpoints and screens now check module permissions, with the buttons hidden where a user lacks them. A new test fails the build if a write action is added without being listed. Run setup_rbac per tenant after deployment to seed the new codenames.

Order lines count only sent invoices, but the line figures were refreshed only when an invoice line was saved, so a sent invoice left the order at “Not invoiced”. They now refresh when the invoice status changes. Dispatching a delivery by status also now records the dispatch date.

• Revenue (MTD) summed every order ever raised, unconverted; it is now month-to-date and in company currency.
• Overdue invoices counted CRM invoices, which a receipt never marks paid, so paid invoices stayed overdue (8.2 cr against 0.89 cr). The ledger is now the source, on both the CRM and Receivables dashboards.
• Late and blocked values added dollars to rupees.
• The Sales Order dashboard cache was never refreshed when an order changed and summed native-currency amounts; it is now refreshed and in company currency.

• Date fields on leads, quotations, orders, deliveries, invoices and receipts defaulted to a date-and-time; when omitted by an API caller, creating a lead failed with a server error after the record was already saved. They now default to the local date.
• Lead activities could not be edited; they can again.
• Naive date-times were shifted by 5 h 53 m (historical local mean time) instead of 5 h 30 m.
• The Lead Add Activity dialog defaulted its date to UTC; it now uses local time.
• Creating an opportunity now returns its id and number; a delivery-note item over-delivery returns a clear message instead of an HTML error page.

A guided 42-step walkthrough from lead through customer, opportunity, quotation (with revision), order (credit block, release and cancel), delivery, invoice and receipt to dashboards reconciled to the registers, with a matching training guide.

Approving or rejecting a credit block, and listing the pending credit approvals, had no permission check, so any signed-in user could release any credit block. They now require credit.release_credit and credit.view_credit. The pending-approvals route, which returned 404, is also reachable.

Saving only some fields of a material wrote empty values for every field that was not sent, wiping its code and hierarchy classifications. Fields not sent are now left untouched. A same-day change of cost group, which failed with a server error, is also fixed.

• A hand-raised inspection lot dropped its supplier; it now keeps it, and the lot form has a picker.
• Cost of Quality counted the headline figure instead of the usage-decision splits.
• A measurement CSV with ragged rows could not be parsed; it now is.

An inspection lot can now be raised against a specific goods-receipt line, with a lookup of the receipt lines on the Inspection Lots page. This is what makes Return to Vendor available on the lot. Scrap falls back cleanly for a cost group that has no consumption account.

A guided 72-step run through Quality Management - plans, lots, results, usage decisions with stock postings, Return to Vendor and analytics - with a matching training guide.

• Converting an accepted offer into an employee failed because foreign keys were passed by the wrong field name; marking a candidate Hired also closed the application before moving it to the Hired stage.
• Overlapping roster periods on a plant were accepted and then failed with a server error on generate; they are now refused with a clear message.
• Creating a performance cycle scoped to a department failed with a server error.

Corrections found while writing the Procurement and Material Management UAT scripts: permission-aware buttons on the Purchase Requisition and Goods Receipt pages, the Material Variants and Service form screens, and variant attribute handling.

The Sales Order update logic was defined twice, and the live copy shadowed the one that recorded amendments, so changes to an approved order were never snapshotted. The two are merged: header and line changes on an issued order are now captured in its version history, and a draft still edits in place.

A new /demo page starts, stops and watches the walkthrough from the browser. It needs the special permission test.run_walkthrough (administrators are not exempt) and is available only on demo, QA or local hosts.

A guided, step-by-step demonstration of the whole employee life: hire, time, assets, pay, loans, performance, employee relations and retire. Each click on Next performs one step and saves one real record.

It runs only against a local, demo (bizworks) or QA tenant, and never against a live tenant.

New acceptance test scripts UAT-PR-001 to 004 (Procurement) and UAT-MM-001 to 004 (Material Management).

Send, record quote, award and convert-to-PO on a Request for Quotation changed the RFQ but were gated only by the view permission, so a view-only user could drive the whole workflow with a direct request. They now require srm.change_rfq, matching the buttons the screen already hid.

A transfer is first parked - validated and numbered, with its items earmarked but no journal - and then posted by a different person; the person who parked it can never post it, administrators included. A parked transfer can be edited or discarded with a reason, and a parked vendor invoice is held out of payment runs.

Advances can now be the source too: vendor advance payments and down payment requests, and customer unapplied receipts. A customer credit lands so it can still be applied later in Payment Allocation.

A new screen, Balance Transfer, moves a balance between accounts in five directions: vendor to customer, vendor to vendor, vendor to GL, customer to customer and customer to GL.

• The source gives up its open items, fully or partly; the target receives the amount. One journal and both sub-ledgers are written in one transaction.
• A cleared vendor invoice can never be paid again by a payment run.
• Simulate shows every refusal and the journal before anything is posted; reversing contra-posts the journal and re-opens every item.
• Control, receivable, payable and advance accounts are refused as GL targets.

A posted cash journal transaction can now be reversed: it posts a contra journal on the original posting date, so the GL cash account and the cash book - which only counts posted entries - stay in agreement day by day. A reason is required, and the reversal is refused by name on a closed cash day, a locked period, a transaction with no GL journal, a second reversal, or an inflow reversal that would overdraw the till.

Delete now covers every never-posted status (Draft, Rejected, Cancelled); a posted transaction is refused with a message pointing to Reverse instead. Both actions are on the grid and the detail page.

Three defects in the saved-layout behaviour shared by every Syncfusion grid, found while piloting automated UAT on the Customers screen:

• A sorted grid never remembered its layout - saving the sort order copied Syncfusion objects that point back at their own parent, which made the save silently fail across 74 grids. It now saves a plain sort record.
• A column hidden and saved was not re-hidden on reload, because the restore matched on the column's display text instead of its field name, across 60 grids.
• A grid's Excel export named its file with a UTC date, which could read a day ahead of the user's local date near midnight; it now uses the local date.

New help articles covering the Additional Motivation Payment (AMP) module - the un-account overtime stream, how an approved OT day is split into payroll and AMP hours against the plant ceiling, and how it is paid.

A UAT script can now be run automatically: Playwright drives the real screens through each step and files the verdict on the UAT Testing screen as an AUTOMATED result with a screenshot. A failed step records FAIL and blocks the rest of its case; a step the harness cannot perform is left Not run for a tester. An automated run never signs off - a person still does that.

Automation runs only against the demo tenant bizworks, a QA tenant whose identifier starts with “qa”, or a dev database, judged from the database the request lands on. UAT-MD-001 (Customers) is the pilot script.

New acceptance test scripts covering Quotations (including revision/versioning), Sales Orders, the Merchandising Dashboard and the Sales Order Summary with Photos.

The automated end-to-end test setup carried an admin username and password in plain text in tracked files. Those values now load from a git-ignored .env file (with the keys documented in .env.example), and an environment variable set by CI takes precedence. A missing value stops the test run and names the missing key rather than falling back to a default.