🎯 Objective

Supplier contracts previously existed without a structured link to the budget. This feature allows budget lines to be explicitly associated with contracts, enabling budget monitoring and management directly from the contract record.

🚀 Key highlights

• Introduction of parent contracts to group multiple contracts (2-level hierarchy: framework contract → contracts / amendments).
• Linking a contract to a budget line or an external contributor.
• Display of contract information in budget lines, contributor budgets, purchase orders and invoices.
• Redesigned contract record with a hierarchical list, a dedicated Budget panel, and direct links to Finance screens filtered by contract.
• Contracts taken into account in budget-related imports, exports and API.

🔍 In detail

🧩 Parent contracts

A contract can now be linked to a parent contract (hierarchy limited to 2 levels). A parent contract cannot be deleted as long as it has linked contracts.

📝 Enhanced contract information

The contract record now includes the signature date and the signatory (non-archived user), visible in the record, the list, and exports/imports/API.

🔗 Linking to a budget line

The association is optional. The contract must be consistent with the line's supplier. Depending on permissions, a contract can be created on the fly from the budget line. If the contract on an existing line present across multiple fiscal years is changed, two options are offered: replace the contract on the line (affecting all fiscal years) or create a new line from a chosen month.

🧭 Redesigned contract record

The contract list is now wider and hierarchical. A new Budget panel allows viewing the budget, committed, ordered and consumed amounts, filtering by fiscal year, optionally including linked contracts, and accessing Finance screens filtered by contract.

Please note: contracts are carried by budget lines and not directly by purchase orders or invoices. A discrepancy may therefore exist between the budget calculated at supplier level and that of the contract, if not all budget lines are linked to the contract.

🎯 Objective

Until now, several limitations reduced the day-to-day effectiveness of analytical axes: no way to make an axis mandatory, no description to guide data entry, and codes too short to align with ERP reference systems. This release brings three targeted improvements.

🔍 In detail

🔒 Mandatory analytical axes in Finance

A new "Mandatory" setting is available on each Finance axis (Administration > Configuration > Value Lists).

Once enabled, saving a budget line without a value on this axis is blocked. The check applies comprehensively: form entry, grid editing, duplication, Excel import, bulk actions, and simulation integration.

In addition, the budget line creation form has been redesigned: a unified interface organised into 3 tabs (Qualification, Analytical, Budget), consistent with the edit form, and applicable in Finance and Portfolios (Detailed Budget and Simulation).

⚠️ What happens to existing lines upon activation

Enabling the mandatory setting on an existing axis has no retroactive effect: budget lines already created without a value on this axis are not blocked and remain accessible in read mode. The check only applies when a user explicitly modifies a line. Likewise, closing actions (archives, period-end entries, budget rollovers) are not blocked for existing lines with an empty axis.

We recommend auditing your existing budget lines before enabling the mandatory setting on an axis, to identify lines that will need to be completed upon their next modification — and to inform the team members who work on budget lines!

The mandatory setting applies only to Finance module axes in this version. Other modules will be addressed in a future release.

📝 Analytical axis descriptions

A Description field (max. 256 characters) can be filled in for each axis from the Administration. When a description is provided, a help icon appears in grids and forms across the entire platform; hovering over it displays the full description in a tooltip, without cluttering the interface.

📐 Analytical codes up to 30 characters

The limit increases from 20 to 30 characters for unique analytical axis codes, to align with ERP and accounting reference systems. Existing codes are fully preserved. The API and Excel imports support the new codes.

📁 Portfolios

1. New "Actions" column in the Project Review > Planning view :
   
1. Create/view notes, decisions, tasks, risks, flash reports,
   
2. Direct access to the project record or the latest flash report.
   

💶 Finance

1. API Invoices: addition of the accountingRef object to the import (code takes priority).
   
1. It is now possible to specify the accounting reference during bulk invoice imports via API using code and label, with priority given to the code.
   

1. Financial Reports:
   
1. New chart types (Donut chart, Treemap, Area, Line, Radar) with hierarchical drill-down up to 3 levels.
   

👤 Teams

1. 27 new countries available in the working calendar library to facilitate the configuration of local public holidays.
2. Timesheets:
   
1. Column highlighting on hover,
   
2. Display of the budget line reference in timesheets (configured from the Teams module settings).
   
3. Enriched Timesheet export:
   
1. "Total recorded working hours" and "Total recorded hours" columns in the Summary tab, and "Entry (hours)" in the Detail tab.
   

🛠️ Cross-functional

1. Multi-selection statistics, when at least 2 cells are selected in budget grids:
   
1. Average, Sum, Min, Max and cell count.
   
2. New relative date filters (yesterday, this week, this quarter, etc.) that can be saved in views!
3. My Profile: display of the user role.