Practical guide
Why Monthly Events on the 31st Skip Some Months
A monthly event on the 31st skips months without that date. It does not automatically move to February 28 or April 30. Choose an exact-day rule or an explicit month-end rule, then inspect the generated dates before replacing an existing calendar.
Choose the date you actually mean
A missing February entry can be the correct result of the recurrence you chose. Under RFC 5545, generated invalid dates are ignored and are not counted as occurrences. February 31 and April 31 are invalid; they are not instructions to select the last valid date. [1]
Exactly the 31st
Use this when the date itself is the requirement. Accept the skipped months.
The last calendar day
Use this when every month must have an entry. February and 30-day months then have their own valid end dates.
An invoice, payment or filing rule may define a third policy such as the previous business day. Confirm that rule separately; a month-end calendar reminder cannot establish the controlling deadline.
Read DTSTART and the month-day selector together
The exact-day form is FREQ=MONTHLY;BYMONTHDAY=31. The month-end form is FREQ=MONTHLY;BYMONTHDAY=-1: minus one selects the final day of each month. A bare monthly rule can inherit the day from DTSTART, so a January 31 start without an explicit selector still deserves careful inspection. [1]
Start on a date that fits the chosen rule. In the examples, 31 January 2027 is both the 31st and the final date of January. Do not use an unrelated January 30 start and expect every calendar to repair the mismatch: RFC 5545 calls the recurrence set undefined when DTSTART is not synchronized with the rule. [2]
Compare six actual occurrences
On a narrow screen, swipe within the table to read the remaining columns.
| Occurrence | Exactly the 31st | Last calendar day |
|---|---|---|
| 1 | 31 January | 31 January |
| 2 | 31 March | 28 February |
| 3 | 31 May | 31 March |
| 4 | 31 July | 30 April |
| 5 | 31 August | 31 May |
| 6 | 31 October | 30 June |
Both columns have six entries. The exact-31st column spans January through October because February, April, June and September do not supply a 31st. COUNT=6 means six generated occurrences, not six consecutive calendar months. The month-end column reaches its sixth entry in June.
Inspect two complete fictional calendar files
These all-day practice files use DATE values and no end property; RFC 5545 gives such an event a one-day duration. TRANSPARENT keeps this informational example out of busy-time searches. There are no invitations or alarms. The timestamp and identifiers belong to these fictional examples, not to an observed import. [3]
Download practice exact 31st (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Examples 1.0//EN
BEGIN:VEVENT
UID:d8a67c43c476de3cf43216f2@daymooncalendar.com
DTSTAMP:20261108T000000Z
DTSTART;VALUE=DATE:20270131
SUMMARY:Practice - Exact 31st
RRULE:FREQ=MONTHLY;COUNT=6;BYMONTHDAY=31
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDARDownload practice last calendar day (.ics)
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DayMoon Calendar//Fictional Examples 1.0//EN
BEGIN:VEVENT
UID:307aad088d3746d09240f8bb@daymooncalendar.com
DTSTAMP:20261108T000000Z
DTSTART;VALUE=DATE:20270131
SUMMARY:Practice - Last calendar day
RRULE:FREQ=MONTHLY;COUNT=6;BYMONTHDAY=-1
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDARCheck a missing month before changing the series
Export a copy and inspect DTSTART, RRULE, RDATE and EXDATE together. First decide whether the missing date is impossible, explicitly excluded or merely outside the display range. An EXDATE can remove a valid 31st; an RDATE can add a chosen extra date. Neither changes the meaning of the month-day selector. [2]
If the stated requirement is every month-end, change the policy rather than manually adding a February 28 event and leaving the other short months unresolved. Keep an original copy and check the full next-year trace. If the requirement is exactly the 31st, preserve the skipped months and label the series accurately.
Two complete decisions
A six-month reporting plan starts on 31 January. Does COUNT=6 with BYMONTHDAY=31 reach June?
No. Its sixth occurrence is 31 October 2027.
The six valid dates are January 31, March 31, May 31, July 31, August 31 and October 31. To get one entry in each of January–June, use the intended last-calendar-day policy; do not interpret six occurrences as six elapsed months.
A February 2028 entry appears on the 29th under BYMONTHDAY=-1. Is that a shifted 31st?
No. It is the final valid date of a leap-year February.
The rule selects the last calendar day directly. An exact BYMONTHDAY=31 schedule still has no February occurrence. These policies can agree in January and disagree later without either date calculation being broken.
Apply the choice in your actual calendar
After checking the exported rule, use the calendar’s supported recurrence editor or test a copied file in an isolated calendar. Compare February, a 30-day month and the final counted occurrence with this trace. These files were checked as examples; their treatment by your particular app was not tested here. For safe copying and subscription choices, use the existing import guide.
Sources and further reading
- RFC 5545 §3.3.10 — Recurrence valueFrequency, intervals, ordinal weekdays, set positions, count/cutoff and invalid generated dates.
- RFC 5545 §3.8.5.3 — Recurrence setDTSTART synchronization, inclusion/exclusion precedence and documented examples.
- RFC 5545 §3.6.1 — VEVENTDATE-only default duration and the distinction between DTSTART and an optional end.