What we shipped, in plain language.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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

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

Additional UI pages added to the Production module.

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.

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.

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

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.

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

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.

Accounts Receivable receipts now record which house bank account the funds landed in, keeping the Bank Book and AR ledger consistent.

A running day book of every posting against a house bank account, giving finance a single ledger view of bank movements without pulling the full General Ledger.

Bank charges, interest, and inter-bank transfers can now be posted directly against a house bank account, without routing through a customer or vendor sub-ledger.

Reversing a statutory payment reopens the accrual it cleared and nets the payment’s own posting against the reversal, so a reversed challan no longer leaves a phantom balance on the liability account.

GST payable, TDS/TCS, PF, ESI, professional tax and advance tax accounts can be flagged as open-item managed. Every posted journal line on a flagged account becomes a clearable open item, matching Schedule III’s treatment of these as Other current liabilities → Statutory dues rather than trade payables.

Record a statutory challan as a single-account payment, select the accrued open items it clears, and post interest or penalty as separate expense lines that don’t distort the liability account.

New /financial/gl-open-items worklist with per-account cards and a “Pay Selected” action, plus manual clearing for items that already net to zero.

Full purchase-return workflow against a goods receipt: physical return, a GST-compliant debit note with ITC reversal (Route A), and an outward tax invoice with e-Invoice and e-Way Bill for cases that must move as an outward supply (Route B). A route engine selects the correct path, covering reverse charge, SEZ, composition and import vendors.

Quality Management inspection results can now split a goods receipt line and auto-raise a partial rejection return, instead of rejecting the entire receipt.

Purchase returns now feed the GST register and GSTR-3B contributions, reconcile against GSTR-2B, surface pending credit notes, and roll up into a vendor return scorecard.

Contract Management’s signing-certificate encryption no longer derives its key from SECRET_KEY, removing a hidden coupling between application secret rotation and signed document integrity.

A pass-through usage meter (/admin/gst-usage) records how many e-Invoice, e-Way Bill and return calls each tenant consumes, so government service provider usage is visible and attributable.

GST returns can be prepared, submitted and filed from the new GST Compliance workspace, reusing the existing GST reconciliation data rather than a second set of figures.

The lifecycle is maker-checker: the person who prepares a return is not the person who files it.

An e-Way Bill is raised from the invoice's existing IRN, so transport details do not have to be re-keyed. The delivery dispatch can trigger it, and the e-Way Bill number and validity are held against the invoice.

A sales invoice can now be registered with the government Invoice Registration Portal directly from the invoice screen, returning the IRN, acknowledgement number and the signed QR code.

• New e-Invoice panel on the invoice detail page with a live status chip and Generate / Retry / Cancel actions
• The IRN and QR code are printed on the invoice PDF, as required for a valid tax invoice
• Export invoices and credit / debit notes are supported with their own payload rules
• Every call to the portal is logged and can be inspected from the panel via View API Log, so a rejection can be explained rather than guessed at

A single workspace (/financial/gst-compliance) shows e-Invoice status, e-Way Bills, returns and the credentials / masters behind them. Eligibility rules decide which documents actually require an IRN, so exempt documents are not pushed to the portal.

Portal credentials (user name, password, client keys) are held in encrypted fields and are never returned by the API. Access to the GST compliance screens is controlled by dedicated gst.* permissions.