What we shipped, in plain language.

• 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.

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.

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.

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.

• 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.

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.

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

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.

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.

The Unallocated Receipts KPI on the Receivables Dashboard was hard-coded to 0.00 regardless of how many on-account or partly-applied receipts a company actually held. It now sums the unapplied balance on open payment ledger rows.

The Payslip Template serializer’s read_only_fields were written after a method definition inside Meta, where Django never sees them, so id, created_at and updated_at were silently writable on save. They are now honoured.

New scripts covering recruitment pipeline, employment history, print forms, employee personnel detail, separation/exit, travel (setup, request/approval, advances, expense claims, desk booking), shift roster and time management (shift masters, roster publish, attendance/device integration, time evaluation, short permission, overtime and compensatory leave, ESS leave/permission, HR absence entry), organisation management (setup masters, positions/org chart, staffing access), performance (goals, check-ins, cycles/appraisals, competency calibration, 360° feedback, talent, training compliance, setup access), statutory filings (registrations, calendar readiness, carry-ins, Form 16, lifecycle prepare/approve, access control), and the HRM dashboard (overview/workforce, time/cost/compliance, actions/reports, setup/access).

New scripts covering AR setup, receipt entry and reversal, payment and mass allocation, customer reconciliation, dunning, direct invoices, debit/credit notes, the GST advance receipt voucher, GST recon and refund claims, netting reports, journal entries, the GL ledger and payments, bank operations, period close and FX, Schedule III, financial statements and consolidation/XBRL, and financial setup and reports access.

The Employee Master script moves to Master Data as UAT-MD-005 (it was UAT-HR-026) - the screen belongs with the other masters even though it still lives on the Human Resources menu.

Create Material from Reference only built variants when both colours and sizes were chosen, so a size-only material (size labels) or a colour-only one (fabrics) got no variants at all. It now runs over whichever axes are given; the both-axes codes and names are unchanged. Applies to the Material Variants page and the PO Import master-data step, which share the same service.

A released structure is changed only by a Change Order by design, but the BOM list, detail and form all still offered a plain Edit whose save could never succeed - a user who had already released a change order still hit the refusal and read it as the change order not working.

• Edit on a locked BOM in the list or detail page now opens a new Change Order pre-filled with that structure; the detail button reads “Raise Change Order”.
• Opening the BOM form directly on a locked BOM shows an info banner with the same action, and Update is disabled.
• The lock itself, and when it applies, is unchanged.

A new Change Management Settings page under Production Planning > Change Orders edits the BOM change-order configuration per company, with the tenant default as the fallback - including the switch that makes change orders optional for a company. A new company row is pre-filled from what the company resolves to today.

A line added to a new Purchase Order was stored with its Asset Class or Service picker flattened to a plain id, then flattened again when the order was saved - so an asset line reached the server with no asset class and was refused, and a service line lost its service the same way. The stored line now keeps the picker object.

The Sales Order field no longer shows as required on an asset line, matching what the server already allowed.

• An invoice could go into two payment runs at once, and executing both paid the vendor twice. An invoice is now held by the open run it is in, Due Invoices shows which run, and posting a run refuses an invoice that was settled since it was proposed. A run that is only proposed or approved can now be cancelled to release its invoices.
• Posting a payment run, generating its bank file, recording a UTR and reversing a payment ran on read-only access; they now require the proper AP approve / release / reverse permission, and the screens show only the actions a user may take.
• A payment reversal could itself be reversed, and a submitted or executed run could be deleted.
• The same vendor invoice number could be booked twice for a vendor in one financial year.
• An invoice that had consumed a down payment could never be reversed.
• A foreign-currency PO invoice with no exchange rate posted at 1:1; a rate of 1.000000 on a foreign invoice is now refused, as it already was for advances.
• The AP TDS Report and the Cash Forecast failed on every run; the TDS report also missed tax withheld at invoice posting and the PAN column, and the Cash Forecast put every invoice under NEFT.
• Outstanding Payables, Cash Forecast and the TDS Report asked for a typed company id; all three now use a picker.
• No RCM category could be created, and an RCM invoice posted without its liability, so no self-invoice, GST payment or ITC claim was possible.
• Vendor Reconciliation and the AP Dashboard answered any logged-in user; they now require AP access.

• Saving a new asset saved nothing.
• Posting a disposal, revaluation or CWIP capitalisation always failed.
• The Asset Movement report failed, and the Reports page listed nothing.
• An asset with no useful life on file was silently written off in one month; it is now left out of the depreciation run and reported, and the rest of the run still posts.
• The transfer picker stopped showing assets past the thousandth on the register, and the asset form had nowhere to set a work center.
• A partial capitalisation activated the whole asset and stranded the remaining cost in CWIP.
• An asset already under disposal could be disposed a second time, and a posted asset could be deleted.
• Every fi-aa screen now rounds amounts to the rupee consistently.

UAT-HR-026 records how the Employee Master screen behaves today: its API checks only that a user is logged in, not that they hold the Employee Master permission, so the sidebar hides the page but the URL does not; and an employee can have more than one address marked default or bank account marked primary, unlike the customer master.

Nine new scripts, UAT-FI-011 to UAT-FI-019: AP posting configuration and house banks, invoices against purchase orders, invoice differences and the over-billing debit note, non-PO invoices, invoice reversal, the payment run, bank payment files and UTR capture, manual payments, and advance payments and credit allocation.

Nine new scripts, UAT-FI-002 to UAT-FI-010: setup, the asset master, manual acquisitions, procurement with CWIP and capitalisation, depreciation, transfers, disposals, revaluations, and reports and access.