December 2025 Changelog
| Release Date | Type | Key | Area | Release Notes |
|---|---|---|---|---|
| 12-5-2025 | Bug | EN-72992 | Operations | Operators have frequently been forced to refresh their webpages after encountering the error ‘Error in update: Table schtxt has been updated…’. Underlying issues that may have been causing this error have been addressed. |
| 12-5-2025 | Story | EN-71158 | Demurrage & Claims | Added a configuration option to allocate demurrage proportionally by port based on net time incurred at each loading and discharging port, supporting cumulative (reversible) laytime calculations and accurate split of demurrage or despatch across terminals and cargoes |
| 12-4-2025 | Bug | EN-74516 | Operations | In Tow voyages, fixed an issue where specifying a rate differential without a linked Contract ID could lead to an error when attempting to load the voyage. |
| 12-4-2025 | Bug | EN-73350 | Tasks & Alerts | Previously, clicking "Apply to Estimate" on a webhook response which included category Id did not auto-populate the field . This has now been addressed and fixed by including a string responsible for the webhook. Clicking "Apply to Estimate" on a webhook response should populate the category field like "Vetting status". |
| 12-4-2025 | Bug | EN-72971 | Bunker Management | Previously, for non-operator bunker lifting if users tried to link an existing purchase the Bunker purchase window opened a blank form. This was addressed by adding a check that now populates the Bunker purchase form with valid data after linking. |
| 12-3-2025 | Bug | EN-73582 | Invoicing & Payments | When refresh the freight invoice, the due date was not set back to the contract default value. This has been fixed. |
| 12-3-2025 | Bug | EN-73524 | Demurrage & Claims | Fixed an issue where the Audit Trail for Claims did not display the actual old and new values when a claim was updated, improving visibility into claim changes for analysts |
| 12-1-2025 | Story | EN-56428 | Voyage P&L | A New dropdown field has been added to the Cash Invoices grid on the Emissions Tabs of the TC In/Out, Cargo/VC In contracts called ‘Type’ that has the following options:
On the TC In / Out contracts: - Per CO2 Ton (default value) - Lumpsum On the Cargo / VC In contracts: - Per CO2 Ton (default value) - Per Cargo Unit - Lumpsum When lumpsum is set, the Price column will be greyed out and and blank and the Quantity field will be purely informational and only used to determine outstanding balance. When Per Cargo Unit is selected, the amount will be calculated using the Price and the BL Qty on the cargo contract (if there is no BL Qty then it will default back to the CP Qty). A new field, Default Type, has also been added to the parent level which will set the default value to be applied to the line item in the grid. |