Contract Annexes
All Contracts may have Annexes attached to them, which define changes in terms of the original contract. Each Annexe can also be an Extension of the original contract, which impacts the final end date of the contract.
Adding an Annex
In the bottom-right corner of the Contract panel, the Add Annex button allows you to create a new annex for the contract.
When adding an annex:
A dialog similar to the new contract form will appear.
The Contract Type field is read-only and set to Annex.
A switch for Extension is included (default: true).
Viewing and Managing Annexes
If the contract contains any annexes, an expandable panel appears below the parent contract.
This panel displays:
Annex Date From
Reference (if not empty) on the left
Annex Status Badge on the right
The annex panel is expanded by clicking on the Annex row, whereas:
The parent contract's status in the title is hidden.
Three panels for the annex are displayed:
Status
Documents
Details
Final End Date and Extensions
The Date To of the original contract is never updated when annexes are added — it always reflects the date as originally signed and confirmed. Instead, the Final End Date is a read-only, automatically calculated field that represents the maximum end date across the contract and all its active extension annexes (i.e. annexes with Extension set to true).
The Final End Date is displayed on the Contract panel only when a confirmed contract has at least one confirmed extension annex whose Date of Termination or Date To differs from the parent contract's Date To.
Example
A player has Contract A with a Date To of 31.12.2027. The parties agree to two successive extensions:
Annex B extends the contract to 31.12.2028. Contract A's Date To remains 31.12.2027, but its Final End Date becomes 31.12.2028.
Annex C extends the contract further to 31.12.2029. The Final End Date is updated to 31.12.2029.
Auto-expiry in this scenario works as follows:
31.12.2027 - Nothing expires. Although Contract A's Date To has been reached, it still has two active annexes (B and C), so it cannot expire yet.
31.12.2028 - Annex B expires. Contract A does not expire because Annex C remains active.
31.12.2029 - Annex C expires, and Contract A expires as well, since its own Date To has passed and all its annexes are now expired.
Each Contract and Annex expires after its own Date To, but a parent contract can only expire once all its child annexes have expired. Auto-expiry notifications are sent per Contract/Annex individually - an expiry notification for an annex does not mean the parent contract has expired.
The workflow of the Annex is equivalent to the workflow of any contract, meaning that the relevant governing body administrators must approve submissions and termination submissions. Please note that all child annexes must be expired or terminated before the parent contract can be expired or terminated.