What we shipped, in plain language.

Any signed-in user could export the full contents of any grid they could open, to Excel or PDF, regardless of role. Two new permissions now control it: Export to Excel and Export to PDF.

• Applied uniformly to every grid in the application — not screen by screen, so a new screen cannot ship ungated by accident
• Enforced on the server for the export endpoints as well as hidden in the interface: the toolbar button is presentation, the server check is the control

Administrators: grant these permissions to the roles that need them as part of this upgrade.

Earnings, allowances, overtime, terminal benefits, deductions, statutory and technical wage types are seeded into every tenant, so compensation plans, income-tax records and payslips can be configured immediately instead of starting from an empty list.

Seeding is keyed on the wage type code, so a re-run changes nothing and an administrator’s edits to an existing wage type are never reverted.

Uploading a corrected version of a file created a second copy of every row rather than matching and updating the existing ones. Matching is now reliable, and soft-deleted rows no longer claim a key they should have released.

Foreign-key lookups now resolve on keys that are genuinely unique, a lookup field is only ever upgraded to a better one, and a date typed into a date-and-time column is accepted instead of rejected.

A lookup can be constrained to a subset of candidate records, so an ambiguous name resolves within the right scope. A separate utility identifies and merges tasks that earlier uploads duplicated.

Upload a logo against the tenant and it is shown on the sign-in page for that tenant’s address, before anyone has signed in. A tenant with no logo uploaded sees the page exactly as before.

The ship-to address lived only on the order header, so a single customer purchase order covering several destinations had to be entered as several sales orders — splitting the commercial document to describe a logistics fact.

• A sales order line can now name its own delivery address; a line that names none continues to use the header address, exactly as before
• Nothing is backfilled and existing orders are unchanged
• Material planning now distinguishes identical lines bound for different destinations. Previously four identical lines to four warehouses collapsed into one — a 75% short plan, announced only in a log line

Combinations that would record something untrue are refused rather than saved: a line addressed to a different customer, a delivery note line bound somewhere other than the note, and consolidating notes with different destinations onto one invoice.

The worksheet no longer opens empty until a paging control is touched, and a second attempt to save the same set of edits no longer reports “Nothing to save”.

The task list can be narrowed to a due-date window, and a change to a task’s planned end date is noted in its chat, so the reason travels with the date.

A task that has not been finished is now its own status. It renders in the ordinary colour and only turns red once its planned end date has passed, so “not done yet” and “overdue” stop looking the same.

The task worksheet gains a Pivot Analysis tab, and both the worksheet and the pivot remember your layout — column order, widths, grouping and filters — as named variants saved per user.

Debit and credit notes offered the full tax code list regardless of the company on the note or whether it was a customer or a vendor note. The list is now scoped to both.

Simulating a posting shows who created the document, drafts included, so a preview passed to a reviewer carries its own authorship.

This is deliberately not the same list as the Outstanding Payables tab beside it. That one shows invoices and debit notes inside the selected fiscal year; Open Items shows the sub-ledger’s own uncleared items in both directions across every year — so an unadjusted advance appears here and nowhere else on the page.

Totals come from the server over the same filters, never from the rows on screen, and an item carrying no exchange rate is excluded by name on the banner rather than quietly folded in.

Provisioning ran the full set of roughly 1,270 schema migrations against an empty database — upwards of eight hours for a recent onboarding, and growing with every release.

A new tenant is now created as a file-level copy of a pre-migrated template: no schema statement is re-executed, and the clone starts fully up to date. The cost is the size of the template, not the number of migrations.

• The template is kept level with the live schema as part of the normal upgrade run
• The old path remains the last rung — no template, a stale template or a failed clone all fall back to the full migration run, correct and merely slow, with the reason logged

The journal entry screen now opens on the fiscal year that contains today, and vendor invoices open as a worklist of what needs attention rather than the entire history. Both grids also stopped issuing a query per row, so they load faster on top of loading less.

Presentation and filtering improvements across the Vendor Ledger and the Bank Book.

The Payments Received form derives the currency and exchange rate from the invoices selected, and drives the amount from them, so a foreign-currency receipt cannot be captured against a mismatched rate. A manual General Ledger entry added to an export receipt now carries its own foreign amount.

Saving a receipt without picking any invoice did not hold it unapplied — it settled the customer’s open items oldest-first at posting time. An unidentified remittance therefore cleared invoices on a guess, on a posted document, which then had to be unpicked.

A receipt can now be marked on account, so “not chosen yet” and “deliberately unapplied” are different states. Existing receipts are unaffected.

Down payment requests, advance payments and on-account payments all put money on the debit side of a supplier account before an invoice is settled in cash. One page now shows everything an invoice can be cleared with and applies it.

• Setting an advance against an invoice is a reclassification, not a payment — no bank account moves on this screen
• Fixes a live defect: an invoice relieved by a down payment adjustment still read as fully open, so the next payment run proposed it at full value and the supplier could be paid twice for the part already advanced

Work centres, machines and skills are now described as data — what each resource is capable of, how much of it there is, and when it is available — and the scheduler honours those limits instead of assuming infinite capacity.

• Capability master data with its own maintenance screens and navigation
• Capacity profiles and reservations shared by the scheduler and the delivery promise, which is what stops the two disagreeing
• The legacy first-in-first-out scheduler has been retired

A constraint solver now produces the schedule, and a planning board shows the result before you commit to it.

• Running and publishing are separate acts — a run writes only its own proposed dates, and publishing is a distinct permission that moves the live ones
• Scheduling weights are yours to set per tenant, so the plan reflects what your factory actually optimises for
• The solver is an upgrade, never a dependency: if it is unavailable the run falls back to a finite-capacity heuristic over the same problem and records which engine produced the plan
• A capacity overrun is reported as a warning to be judged, not a hard refusal