What we shipped, in plain language.

A new Vendor Down Payments capability in Accounts Payable lets you manage advances paid to vendors end to end:

• PO-linked and non-PO advances — raise an advance against a purchase order or as a standalone payment, as a percentage or a fixed amount (defaulting from the payment term's advance percentage). Multiple advances per PO are supported.
• Maker–checker approval — requests are created, approved, and then paid through a controlled workflow.
• TDS at source — tax is deducted on the advance using the configured TDS section.
• Automatic adjustment — advances are automatically applied against the vendor's invoices when those invoices post to the general ledger, with residual clearing.
• Reporting — an advances aging report and a per-vendor advance statement.

Available under /fi-ap/down-payments and gated by new down-payment permissions and roles (Requestor, Approver, Accountant).

A batch of fixes and refinements across the Payroll module, including employee compensation, statutory components, GL configuration, bank file generation, payslip templates, posting logs, and retro-calculation screens. These improve data validation and the reliability of the payroll maintenance pages.

Added in-app help documentation walking through the Vendor Down Payment process — from raising and approving an advance to its payment and automatic adjustment against vendor invoices.

Deleting a delivery note used to leave stale delivered quantities behind on the related sales order, which then carried through to invoicing. This is now corrected:

• Deleting a delivery note recomputes each affected sales order line's delivered quantity and delivery status from the remaining delivery note items, and refreshes the parent order's status.
• Invoice preparation now reads the live delivered total from the delivery note items instead of a cached field, so the remaining-to-invoice quantity reflects deleted or adjusted deliveries.

The Management by Exception (MBE) exception scan previously sent one email for every exception, for every recipient. A single scan can raise thousands of exceptions, so recipients were flooded — in one case a user received over 2,500 emails overnight. The notification flow has been reworked:

• The scan now creates only the in-app notification for each exception and no longer emails them individually.
• A new routine sweeps the un-emailed notifications, groups them by recipient, and sends one consolidated summary email with all of that user's exceptions.
• The daily scan moved from 02:30 to 09:00 IST so the digest lands during working hours.

The Sales Order Bill of Materials can now be converted directly into a budget in the Budget Control System:

• Generate a budget document from an SO BoM in a single action, carrying its planned material requirements and costs across.
• Keeps the committed sales order, its bill of materials, and the budget aligned without re-keying line items.
• Feeds the resulting budget into the existing Budget Control availability and consumption checks.

A new User Defaults framework lets administrators define reusable parameters (such as default Currency, Warehouse, or Company) that automatically pre-fill fields across the application, reducing repetitive data entry:

• Layered resolution — each parameter is resolved for a user through a clear priority chain: User → Role (by priority) → Department → Company → System, with an authorization-assignment fallback.
• Manage at every level — dedicated screens under /user-defaults for Parameter Definitions, My Defaults, Role Defaults, and Department / Company / System Defaults.
• Resolution Viewer — trace exactly which level a user's effective value came from.
• Pilot wiring — the POS Cash Sale screen now defaults Currency, Warehouse, and Company from a user's parameters.

Gated by new defaults.* permissions and a User Defaults Admin role.

Refinements to the Sales Order BoM to Budget flow, improving the budgeting experience and the accuracy of the figures carried from the bill of materials into the budget.

The "Load a batch" / "Select a batch" pickers on the Batch Traceability pages started out empty and only populated after typing a character, so clicking the list showed nothing.

• The pickers now preload the 20 most recent batches the moment they open, on the genealogy, history, recalls, quality, and documents pages.
• The list opens on focus and still searches as you type.

Added in-app help documentation for the new User Defaults framework.

Further usability enhancements and bug fixes across the Real Estate Management module.

A new Sales Order Status report tracks Make-to-Order (MTO) orders through their full lifecycle:

• Pipeline strip showing each order's position across the fulfilment stages at a glance.
• Journey drawer with a detailed, stage-by-stage breakdown of how an individual order has progressed — from order confirmation through production and delivery.
• Consolidated status view across the linked CRM, production, and fulfilment milestones.