What we shipped, in plain language.

Eight near-identical mail routines across the application were consolidated into a single dispatch service, so every message honours the configured channel and every send is recorded in one Send Log. If no channel is configured, mail goes out exactly as it did before — configuring channels can never stop mail from being sent.

A new Email Channels workspace lets you register your own sending accounts — SMTP or an email API — and assign one per category of message (finance, procurement, HR, support, and so on), with a tenant default behind them. Notices, statements and dunning letters then reach your customers and vendors from your own domain rather than a shared platform address.

SMTP passwords and API keys are stored encrypted and are never returned by the API — a channel reports only whether a secret is set. Leaving the field blank on an edit keeps the existing secret rather than erasing it.

Vendor invoice GL posting was refined alongside the HSN/SAC work, so tax determination on an invoice line follows the material’s maintained code.

The material master now selects its HSN/SAC code from the master through a searchable picker, so the code and its GST rate are consistent across every material rather than retyped per record. A backfill command maps existing free-text codes onto the new master.

HSN (goods) and SAC (services) codes are now a maintained master with description, chapter and default GST rate, seeded with the standard code set and available through its own API and Django admin.

The HSN/SAC seed data file was excluded by a blanket rule that ignored JSON files, so the migration that loads it failed for every tenant during deployment. The file is now tracked and the seeding completes.

Reading the tax (GST) code master required the CRM Leads module, so an Accounts Payable user saw an empty GST dropdown on a vendor invoice line — the failure was silent and looked like missing master data. Any module that legitimately consumes tax codes can now read them; maintaining the master is unchanged.

Purchase Orders, RFQ and RFI menu items carried no permission gating at all and were shown to users who could not open them. The Procurement menu now shows only what the user is authorized for.

Purchase Requisitions were gated on the vendor master permission for both reading and writing, so any role that could see a vendor could also create, edit and delete requisitions. Requisitions now have dedicated view and manage permissions, line-level actions are no longer writable by viewers, and raising a Purchase Order from a requisition requires the Purchase Order permission. Existing procurement roles keep the access they had.

Viewing and maintaining a vendor were gated on the same permission, so anyone who needed to see a vendor’s bank details, GSTIN or payment terms also received create, edit and delete rights on the vendor master. Vendor maintenance now requires its own permission, letting Accounts Payable and Finance be given read access without maintenance rights. The Add and Edit actions on the vendor list follow the same permission.

The RCM liability worklist, category manager, account configuration and reports now use the same grid, so filtering and exporting behave consistently across the GST screens.

The GST Compliance workspace and GST Reconciliation page were rebuilt on the standard high-performance grid, adding column grouping, advanced filtering and Excel export to the reconciliation worklists.

Purchase Order line items were not displayed correctly in the administration view; the listing has been corrected.

The Sales Order status service reported the wrong stage for certain order states. The computation is corrected, and the Status Report and Status Workbench now format quantities and values consistently.

The Purchase Order page and grid expose the amendment flow directly, including line-level editing and the resulting version history.

The PF, ESI, Professional Tax and TDS calculators were aligned with the rules the returns are filed under, including PF wage determination, ESI contribution-period membership and ESI dispensary/IP number capture on the employee record.

If no layout is assigned, no tenant default exists, or a configured layout fails to render, printing falls back to the built-in template and reports a warning on the result. Configuring layouts can never stop a document from being printed. Issued tax documents are archived, so a reprint serves the exact PDF the customer received even after the layout changes.

A new Print Forms workspace manages forms, assignments, themes and components, previews a layout against real document data, and answers “which layout would this customer get?” before anything is issued. Statutory documents (e-Invoice, e-Way Bill, GSTR, Payslip, Form 16, Schedule III) are shown as locked, since their formats are prescribed.

Print layouts are now configuration rather than code. A Print Form can be assigned per customer, customer group, company or country/language, with a tenant default behind it, so one customer’s Packing List or Invoice can differ from another’s. Layouts, themes and reusable components are maintained separately, so a rebrand does not mean duplicating every layout, and most variations are handled by declared options (column selection, section toggles) rather than a new form.

Amending an approved Purchase Order previously allowed header changes only, so lines could not be corrected at all once the order was issued. An amendment can now add, change and remove line items together with header fields, all recorded as a single version. The vendor capacity check is re-run on the amended order and the whole amendment is rolled back if it cannot be honoured.

A new Statutory Payroll Filings module prepares the returns that follow a payroll run: PF Electronic Challan cum Return (ECR), ESI monthly contribution, Professional Tax, quarterly TDS 24Q and Form 16. Each filing is a document with its own lines, validation and status, generated from posted payroll results rather than re-keyed.

A filing calendar lays out statutory due dates per registration and period, and a readiness check lists exactly what is missing — unregistered employees, absent UAN/ESI/PAN identifiers, incomplete contribution periods — before a return is generated, instead of failing at submission time.

Professional Tax slabs are maintained per state with a seeding command, and the payroll area now carries its work state so the correct slab applies. Prior-period carry-ins let earnings, contributions and TDS from a previous system or employer be recorded, so a mid-year go-live still produces a complete return and Form 16.

Foreign-currency Sales Order exposure was being divided by the order exchange rate instead of multiplied, understating exposure against the customer credit limit.

Creating or approving a second Original budget document against the same Sales Order, fiscal year and period is now blocked. Because the budget ledger is additive, a duplicate approved Original previously doubled the available budget.

Importing purchase orders no longer mismatches a line to the wrong product or the wrong colour variant of the right product.

Credit limit checks now read the limit in the currency configured on the customer record, instead of assuming the company’s base currency.

Consolidated multiple screens onto the standard Syncfusion Grid + PivotView pattern for consistent filtering, grouping and Excel export.

The budget document header and a new KPI card now derive and display the value committed by open purchase orders against the budget, instead of a stored field that always read zero.

Usability and workflow improvements to the Sales Order page.

Usability and workflow improvements to the Goods Receipt page.

A single vendor invoice can now reference and bill against more than one purchase order.

Verifying a goods-receipt-based vendor invoice against the vendor’s own billed amount now surfaces typed differences instead of silently absorbing them: price and quantity differences reallocate against the receiving material’s stock account (with a matching stock revaluation), while round-off and unplanned delivery costs post to their configured GL accounts. The invoice cannot be approved or posted while it doesn’t balance to the vendor’s billed total.

Style Intent entries can now be searched and filtered by colour and size.

Early beta of AI-assisted Bill of Materials creation: a material code minter, a size-decision step for size-grid items, blocking lints that catch invalid configurations before they reach the BOM, and a resolver that maps an approved style intent straight into a generated BOM.

House Bank Accounts can now be created and maintained from a dedicated UI page instead of Django Admin.

A Sales Order budget is no longer a single money bucket — each line now names a material, operation, or service with a quantity and rate, and the line amount is engine-computed from them. Purchase orders can be controlled at the SO pot, per-material, or per-operation level, and later changes to a dimensioned budget emit a matching supplement/return pair so nothing is stranded in a sub-budget.

Additional UI pages added to Quality Management and its master data screens.

Additional UI pages added to the Production module.

The SAVE/SUBMIT/FILE/GET call sequence now matches the GSTN spec, with proceed-to-file made best-effort and an unconfirmed GSP contract blocking SUBMIT/FILE until verified. Destination of supply for B2C invoices is now computed from the real place of supply rather than assumed.

GST Master, GST Usage, and the new Returns workspace are now grouped together under a single GST menu in Accounting.

GST reconciliation output is wired to the GSTN return builder through the confirmed WhiteBooks GSP contract, adding an HSN summary split and a dedicated Returns product surface for preparing, saving, and filing returns.

New help articles covering e-Invoicing, e-Way Bill, the Customer Portal, Vendor Capacity & Capability, Purchase Returns, Customer-to-Vendor conversion, and GSTR-1/GSTR-3B filing.

Introduces a Business Partner link layer so an existing customer can be linked to a vendor record (and vice versa) without duplicating master data. This is Phase 1 of a multi-phase rollout covering the shared partner identity.