What we shipped, in plain language.

Two Point of Sale cash-sale blockers fixed: product search no longer errors out (it now searches on the correct material code and unit fields and returns a valid base unit for checkout), and the general-ledger journal entry now records its posting period so the posting no longer violates a required-field constraint.

The row-level data-authorization engine gains three new dimensions: Warehouse, Storage Location, and Sales Point. Once a tenant is set up and users are assigned, each user only sees the storage locations, sales points, goods movements, and cash sales for the org units they are authorised for.

The rollout is non-breaking by default — unassigned users remain unrestricted until you assign them under /admin/data-access. Run setup_authorization per tenant to register the new dimensions.

A new Accounts Payable dashboard brings the key payables metrics together on one page — outstanding and due amounts, aging, and recent payment activity — so the AP team can see the overall payables position at a glance.

The final Point of Sale general-ledger posting issue is resolved: journal lines now link to their journal header using the correct field, and a missing cost centre no longer blocks the posting. Cash-sale accounting entries now post end to end.

Point of Sale now supports per-outlet pricing with sales tax:

• Sales Point Pricing screen (/pos/sales-point-pricing) — maintain selling prices per sales point, with a material picker, duplicate protection, and its own permissions (POS Pricing Manager role).
• Pricing hierarchy — the terminal resolves the selling price through Customer → Sales Point → material standard price, so the right per-outlet price applies automatically.
• Output tax per price — attach a sales-tax configuration to each price; the terminal cart then shows a Tax column and GST summary, and totals include tax with the correct CGST/SGST/IGST split.

Refinements to the Point of Sale terminal and the cash-sale detail screen, including a dedicated cash-sale items grid view and improvements to how cash-sale lines are captured and displayed.

Enhancements to the Material Requirement Planning (MRP) engine, improving the accuracy of its planning calculations, with expanded test coverage and documented known issues.

Copying an opportunity to create a repeat order from the Textile Costing workspace has been refined so the copied opportunity and its costing details carry over correctly from the Repeat Order dialog.

The Accounts Payable payment programs have been reworked to make paying suppliers faster and less error-prone:

• Due Invoices worklist — a new screen lists all due payables, grouped by supplier and due date. Tick the invoices to pay and create a payment proposal in one step.
• Real dropdowns instead of raw IDs — the manual and advance payment forms now use proper supplier, payment-method, and bank selectors rather than asking for internal IDs.
• Manager → CFO approval — payment runs route through a two-step approval; final CFO approval automatically posts the run (with a manual Execute fallback on the run detail page).
• Improvements to the payment run detail and list pages.

Editing fields on a CRM Opportunity had a noticeable typing lag, where characters appeared slowly while the form re-rendered on each keystroke. The opportunity form and grid have been reworked so text fields now respond immediately.

The Dispute Management list now respects the items-per-page setting, so the disputes grid paginates as expected.

Fixes in Plant Maintenance, including the Failure Prediction and Work Order Part forms, so these screens save and display their data correctly.

Enhancements to Logistics Invoice Verification, strengthening how vendor invoices are matched to procurement documents:

• Vendor invoice lines can now be tied to their originating goods receipt items, enabling goods-receipt–based billing and tighter three-way matching against the purchase order.
• Improvements to the vendor invoice entry screen and the related purchase order and goods-receipt views.
• More accurate vendor ledger postings flowing from verified 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.