What we shipped, in plain language.

Date column filters on the data grids were not matching correctly. Fixed across the application — Sales Orders, Journal Entries, Direct Invoices, Audit Log, Service Tickets, Repair Jobs, Customer Assets, Incidents, Plant Maintenance plans and schedules, Breakdown Reports, Emergency Work Orders, Equipment Health, Support Desk, Tasks, Cut Plans and the Sales Order reports.

The employee record kept one row, so a transfer overwrote the department and headcount as at any past date could not be reconstructed. Employment assignments are now kept as dated history alongside the master.

Records created at go-live are flagged as such, and every point-in-time answer says so — history is honest about starting on deployment day rather than inventing what came before it.

A full recruitment pipeline: job requisition and approval, candidates, applications through configurable stages, interview feedback, offer, and conversion to an employee record.

• Every transition timestamp is owned by the system, so time-to-fill is an outcome rather than something a recruiter can type
• Blind panel feedback — a panellist sees other assessments only after submitting their own, and a submitted assessment is locked
• A requisition against an already-filled position is refused, so vacancy and open requisitions reconcile
• Rehire history is shown with its reason and never blocks; nothing auto-links a candidate to a former employee
• Declines, expiries and no-shows are kept as three different things, each with its own reason
• Compensation is gated like payroll data — an interviewer never reaches it
• Candidate data retention reports before it acts, and anonymises in place so the hiring funnel history survives

Appraisal cycles with a defined rating scale, and training compliance measured against a requirement rather than a course count.

• The rating scale is frozen onto the cycle when it opens, so relabelling a rating later can never rewrite appraisals already given
• “Not rated” is a real answer with a structured reason — never redistributed, never silently completed at the bottom of the scale, and always shown with the coverage beside it
• Compliance is measured only over the employees a requirement actually reaches; certificates carry the expiry stamped when they were issued
• Ratings are visible to the employee, the appraising manager and HR; reporting access grants distributions, not named individuals

A new HR dashboard covering overview, workforce, organization, time & absence and cost, with drill-through to the underlying worklists.

Small populations are suppressed so an individual cannot be identified from an average, and a panel that cannot be built says why rather than showing an empty chart.

Working days and hours now resolve through a configured ladder — company, payroll area, employee type, tenant default. Where none is configured the system asks you to configure one rather than assuming a 22-day month, which understates absence for shift workers and overstates it for part-timers.

An employee used to leave by somebody editing the employment end date — recording no reason, no approver and no rehire eligibility. A separation is now its own record, with a typed reason, an approval, a clearance checklist and a rehire decision.

• The clearance checklist reports outstanding items; it can never trap somebody’s last working day in a validation error
• Exit interviews sit behind their own permission — a line manager sees that an exit happened, not what the departing employee said about them
• Whether an exit was regretted is recorded when a person assesses it, and “not assessed” is never counted as “not regretted”
• The final settlement reads the separation, so every settlement raised before this keeps working

The Help Documentation centre gained articles for the HR foundation (separations, employment history, work schedules), Recruitment, Performance & Learning, and the HR analytics dashboard — including the configuration each module needs before it will work.

The Journal Entry form gained a Simulate step that shows the document as it would post — every leg, both totals, and whether it balances — so an unbalanced or mis-coded entry is caught before it reaches the ledger rather than after it has to be reversed.

Export sales invoices can now carry the additional detail customs and the buyer’s clearing agent ask for — carton numbers and marks, net and gross weights, country of origin, tariff item and SKU references — and produce a customs invoice from it.

• Print layout, plus an Excel export in the format agents expect
• The customs exchange rate is a rate type of its own, so the notified rate used for assessment is not confused with the accounting rate
• Company AD code and district code captured for the shipping documents

The Purchase Order grid, the Goods Receipt page and the Goods Issue to Cost Centre page were tidied — clearer columns, corrected line handling, and consistent behaviour between the three.

An appointment letter can now be produced directly from the Employee Master, filled from the employee’s own record — designation, department, joining date, compensation structure and terms.

• Letter templates are maintained as data, so wording and clauses are yours to change without a code release
• Company letterhead, salutation and signatory blocks resolved from the employing company
• Downloaded as a PDF ready to issue

Data migration moved from dialogs to proper pages with their own addresses — a migration workspace and a variant editor — behind a background job runner, so a large upload no longer holds the screen and its progress can be reopened later.

Tasks now record where they came from, so work raised by another module can be traced back to it. Existing tasks are backfilled by a management command.

Vendor invoices can now be loaded from a spreadsheet through the data migration workspace — download the template, fill it, upload, review the errors row by row and commit only what validates.

The advance payment page gained a Simulate step that mirrors the posting line for line, and a derived totals bar — Advance Recorded, Charges, Withheld, Vendor Receives, Bank Pays.

Where a manual payment lists the open items it will clear, an advance lists the advances the supplier already holds on account, so nobody wires a second one without seeing the first. If that panel cannot be read, it says so rather than showing a clean account.

The Advance Payment and Vendor Down Payment screens were reworked around the header / on-account / charges / totals layout, so the two documents read the same way.

An advance payment now carries the same charge lines a manual payment carries. Charges and withholdings change how much cash leaves the bank, never what is recorded on account against the vendor — so the advance shown as open is always the advance that was agreed.

Withholding more than the advance is worth is refused (that is a refund, not a payment), as is a charge account that cannot be resolved or belongs to another company. An advance raised with no charge lines posts exactly as it always did.

A journal voucher that had been reversed was still being picked up by ledger reads, so the reversal and the original both contributed and the account balance was wrong. Reversed documents are now excluded consistently wherever a balance is derived.

The Bank Book was rebuilt on the corrected reads, with a clearer opening/closing presentation and reconciliation status carried through to each transaction row.

An import consignment records the customs document governing a shipment — exchange rate, FOB, freight, insurance, assessable value and the duty assessed per line per duty head — and matches it to the goods receipt lines it covers.

Posting it raises the landed cost sheet, so duty is capitalised onto exactly the materials Customs assessed it against, rather than being spread across the shipment by value. The form shows the arithmetic — FOB to CIF to assessable value, with the rate and loading percentages visible — not just a total.

Customs Duty Payable is kept separate from the landed-cost clearing account, so “assessed but not yet paid” is always exactly the payable balance.

Advance Authorisation, EPCG and similar licences are now held as records with their quantity and value balances, the duty forgone on every import against them, and the export obligation that follows.

• Shipping bills are attached as discharges; quantity, value and value addition must all clear
• A discharge outside the obligation period is kept and flagged, never quietly counted
• Expiry worklist, EODC pack and a contingent-liability view of the duty at risk
• Every policy parameter is stamped on the licence when it is created, so a historical authorisation is never re-judged against today’s rule

Licence balances are reported, never enforced — a stale balance must not strand goods at a port.

A Duty Setup workspace maintains the duty heads and their mapping to landed cost types, with a Completeness tab that reports the configuration gaps that would refuse a posting — before anyone meets them at the counter.