End-of-month date alignment
Not all months have the same number of days. For example, February has 28 or 29 days, while other months can have 30 or 31.
When Planon calculates a new contract end date - for example when extending or shortening a contract - or determines a next notice date, it automatically adjusts the day so that the date remains logical. You do not need to make any manual corrections.
This behavior is called end-of-month date alignment. End-of-month date alignment ensures that contract dates remain consistent and logical, even when months have different lengths.
How Planon adjusts dates
Planon looks at the day of the original end date and applies specific rules.
Key idea: If a contract ends on the last day of a month, Planon keeps all future calculated dates on the last day of the month.
Days 1–27
• No adjustment is needed
• The same day is used in the new month
February 28 or 29 (end of February)
• If the original date is February 28 (non-leap year) or February 29 (leap year), this is treated as end-of-month
• All future dates are set to the last day of the month (28, 29, 30, or 31)
Day 29
• If the date moves to February -> it becomes February 28 or 29
• In all other months -> the date remains the 29th
Day 30
• If the date moves to February -> it becomes February 28 or 29
• In other months:
◦ If the original date is in a 31-day month -> the date stays the 30th
◦ If the original date is in a 30-day month and the result month has 31 days -> the date becomes the 31st (end of month)
Day 31
• Always treated as end of month
• The date is always set to the last day of the new month (28, 29, 30, or 31)
Example
A contract ends on January 31 and is extended by one month:
• February does not have a 31st
• Planon automatically sets the new end date to February 28 (or 29 in a leap year)