What we shipped, in plain language.

The GL Tagging Workbench now offers the statement lines that belong to the entity’s chosen presentation frame, so a partnership is not asked to tag accounts into company-only Schedule III lines.

Financial statements are no longer locked to the company format. A presentation frame now decides how the pack is laid out — corporate (Schedule III under the Companies Act) or non-corporate for partnerships, LLPs and proprietary concerns, whose capital and equity are presented quite differently.

The frame flows through the whole pack: the Balance Sheet and Statement of Profit & Loss faces, the PDF, the notes and the XBRL output all follow the selected frame.

Non-corporate entities get their own capital statement: opening capital, introductions, drawings, share of profit and closing balance per owner or partner — the non-corporate counterpart of the Statement of Changes in Equity.

The valuation snapshot stored against a movement recorded the moving-average price as it stood before the movement was applied, so price-analysis and material-ledger views were one step behind. The snapshot now records the price that the movement actually used.

A goods receipt valued the incoming stock at the gross Purchase Order price and ignored the line discount, so stock — and therefore the inventory balance and later cost of sales — was overstated on every discounted purchase. Receipts are now valued at the net price after discount.

Every create, change and delete on a financial document — journal entries, customer and vendor invoices, payments, adjustment notes, credit notes and cash transactions — is now recorded in an immutable edit log as required by Rule 11(g) of the Companies (Audit and Auditors) Rules.

Each entry is cryptographically linked to the one before it, so removing or altering a record breaks the chain and is detected. The trail cannot be switched off.

A new Audit Trail page lets finance and auditors search the edit log by document type, action, user, record and date, and see exactly which fields changed.

An integrity check verifies the whole chain on demand and a statutory PDF report — integrity certificate plus edit log — can be produced for the auditor. The check can also be scheduled so the confirmation arrives by email.

A new read-only Statutory Auditor role grants access to the audit trail and its report without any ability to change data.

Action required: after deploy, assign the role to your auditors.

Issuing material directly to a cost centre has been tested end to end and the problems found along the way are fixed: the issue posts against the correct expense account and cost centre, the delivery-note print reflects what was actually issued, and the entry form no longer rejects valid combinations.

The garment costing screens have been reworked for everyday use: a clearer layout, better grouping of the cost blocks and quicker entry of the figures a costing sheet needs. This is the first part of a wider costing UI refresh.

The Sales Order status-journey views could fail to render, leaving the page blank. The underlying screen error has been corrected and the journey view opens reliably.

Help documentation pages can now include short how-to videos alongside the written guidance, so a user can watch the steps instead of reading them.

Views and viewer feedback are recorded per video, giving a simple picture of which topics people actually need help with.

A new Materials Variant Manager role covers the maintenance of material variants (colour, size and similar grids) on its own. Staff who only maintain variants no longer need broad materials-master permissions.

Action required: after deploy, assign the new role to the users who maintain variants.

Purchase Order line items now surface more of the inventory context behind each material, so a buyer can judge what to order without leaving the order screen.

When a company had no purchasing-specific numbering sequence configured, creating a Purchase Order failed to fall back to the default sequence and the order could not be numbered. The fallback now works, so new Purchase Orders are numbered correctly in every configuration.