What we shipped, in plain language.

Saving an invoice or other audit-tracked document occasionally froze the whole request, and every subsequent write queued up behind it. The cause was the audit log being written on a different database connection than the record it was recording — two separate connections to the same database ended up waiting on each other's lock. The audit event now always uses the exact same connection as the save it belongs to.

Three new roles: Warehouse Operator (scan + build sessions), Warehouse Supervisor (+ post + print labels), Warehouse Manager (full access).

A new Mobile Warehouse page lets a warehouse operator scan barcodes/QR codes on a phone or handheld to drive five core flows: Goods Receipt, Put-away, Transfer, Picking and Cycle Count.

• Works with a keyboard-wedge handheld scanner or the phone camera
• Recognises material, batch, bin, storage location, warehouse, purchase order, delivery note and production order codes, including GS1-128/DataMatrix labels
• Offline-safe: a dropped connection cannot double-post the same session
• Blind cycle counts never reveal the system quantity to the counter

Print QR code labels for materials, batches, handling units, bins and warehouses directly to an A4 sheet (24 labels per sheet).

The audit entry for a saved record could be written over a different database connection than the save itself, so the two waited on each other and the save never completed. The audit entry now always uses the same connection as the record it is recording.

At year end, a single closing entry zeroes every profit and loss account into the configured retained earnings account. The run can be previewed before it posts and reversed if needed.

Action required: set each company’s retained-earnings account in the Period Close configuration, then lock the historic periods.

A standard close checklist walks through the month-end tasks, with several items checked automatically — draft journals, unposted customer and vendor invoices, open cash days. Blocking items must be completed (or marked not applicable) before the period can be closed.

Accounting periods can now be locked so nothing further posts into a closed month. Locking works per module — payables, receivables, materials, production, payroll, cash and the rest — so operations can be closed while finance still posts its adjustments, or the whole period can be sealed at once.

An approved payment run can now be exported as a bank payment file in the bank’s upload format, so payments are handed to the bank as a single file instead of being keyed into net banking one by one.

The bank’s response file is read back in, matching each payment to its UTR reference and status. Payment records therefore carry proof of remittance without anyone transcribing reference numbers.

Open foreign-currency items — customer invoices, vendor invoices and foreign-currency bank and loan accounts — can now be revalued at the month-end closing rate as required by AS-11 / Ind AS 21.

The run is previewed first, showing every open item with its booking rate, closing rate and the resulting unrealised gain or loss, before a single adjustment entry is posted. A missing closing rate is reported as a blocker naming the currency — never guessed.

By default the entry auto-reverses on the following day, so the next month-end revalues afresh and settlement-time differences are untouched. A completed run can also be reversed outright.

Action required: configure the gain, loss and receivable/payable adjustment accounts per company, and maintain closing rates before each run.

The tamper-evident audit chain was being applied to every record saved anywhere in the system, which made unrelated saves queue behind one another and left the application unresponsive under load.

The chain is now applied only to the financial documents that statutorily require it; everything else is logged normally. Location lookups for the audit record are also cached briefly so a slow lookup cannot delay a save. The statutory trail itself is unchanged.

A new Credit Management workspace shows what each customer actually owes you: open receivables, orders taken but not yet delivered, and goods delivered but not yet invoiced — added up as live credit exposure against the customer’s limit.

Limits can be set per customer with a risk class, an expiry date and a hard block, overriding the limit on the customer master.

Credit is checked when a Sales Order is raised and again when goods are about to leave, catching exposure that has grown since the order was approved. Each check can be configured to block, merely warn, or be switched off, with a tolerance percentage and an overdue-days rule.

Every check is logged with the exposure figures it saw, so a block can always be explained.

Orders held on credit appear in a blocked orders worklist where a credit controller can re-run the check or release the order once payment or an exception is agreed.

Two roles ship with the feature — Credit Controller and read-only Credit Viewer. Help documentation for the module is included. Without configuration the existing order-entry behaviour is unchanged.

An accepted quotation can now be converted into a Sales Order in one step. The customer, line items, quantities, pricing, tax codes and the ship-to / bill-to addresses are carried across, so the order does not have to be keyed again and cannot drift from the offer that was accepted.

Several related quotation fixes ride along in this release.

Purchase Order lines added by hand against a Sales Order are now subject to the same Sales-Order budget control as lines raised through the normal requisition route. Buying beyond what the order allows is caught at entry rather than at settlement.