Does this correctly account for leap years?

Yes, February's actual last day is computed directly from the Gregorian leap year rule for that specific year, 29 in a leap year and 28 otherwise, rather than assumed.

Is this the same as a day-31 rule with a constrain policy?

They agree in every month that has 31 days, but a day-31 constrain rule pulls back to the last day only in shorter months, while this rule always targets the last day regardless of the month length.

End-of-Month Recurrence Planner

Generate a schedule that always lands on the true last day of each month (28 through 31), never a fixed day number that would land on the wrong day in a short month.

Want a fixed day of month, with an explicit fallback policy? See Monthly Date Rule Generator.

Want to learn more?

Recurrence Drift: Why "Every Month on the 31st" Breaks

Worked example

Starting January 31, 2027, this rule generates January 31, then February 28, then March 31, each date being the true final day of its own month rather than a fixed day number. Continue the schedule to April and it lands on April 30, again the real last day, even though April never reaches 31. This is the key difference from a fixed day-31 rule under a constrain policy, which happens to agree with this rule in every 31-day month but disagrees everywhere else, since a constrain rule is still anchored to the number 31 first and only falls back to the month's actual last day when 31 does not exist.

Common mistakes

Using a fixed day-31 rule with a constrain policy when what is actually needed is always-the-last-day. The two rules agree only in months that have exactly 31 days.
Assuming this rule needs a specific day number entered at all. It intentionally has none, since its entire purpose is to always resolve to whatever the last day of each month happens to be.

Limitations

The generated preview is bounded to 500 occurrences or 5 years, whichever limit is reached first, which keeps the schedule fast to generate and easy to review.

Frequently asked questions

Does this correctly account for leap years?: Yes, February's actual last day is computed directly from the Gregorian leap year rule for that specific year, 29 in a leap year and 28 otherwise, rather than assumed.
Is this the same as a day-31 rule with a constrain policy?: They agree in every month that has 31 days, but a day-31 constrain rule pulls back to the last day only in shorter months, while this rule always targets the last day regardless of the month length.