Adding 30 Days and Adding One Month Give Different Dates. Here Is Why.
Adding one month to a date seems like the same thing as adding 30 days. It is not. Add one month to January 31 and you get February 28 (or February 29 in a leap year). Add 30 days to January 31 and you get March 2. The same starting point, two different operations, two different results. Both are correct answers to different questions. Most people ask one when they mean the other.
This is the core of why date arithmetic is harder than it appears. Calendar math does not follow the same rules as regular arithmetic. Days, months, and years are not interchangeable units. A month is not 30 days. A year is not 365 days. The units are irregular, nested in non-uniform containers, and subject to periodic correction rules that introduce exceptions on top of exceptions.
Understanding where these irregularities come from, not just that they exist, helps in knowing when to count days and when to count months, and when the difference between the two methods matters enough to require a calculator.
The Calendar Gregory Inherited
The Julian calendar, introduced by Julius Caesar in 46 BCE following consultations with the Egyptian astronomer Sosigenes, was a major improvement over the preceding Roman Republican calendar, which had become so badly misaligned with the solar year through inconsistent intercalation that Julius Caesar himself reportedly found January occurring in autumn. The Julian reform set the year at 365 days with a leap day every four years, creating an average year of 365.25 days.
The problem was that the actual solar year, the time it takes Earth to complete one orbit around the sun, is approximately 365.2422 days. The Julian average of 365.25 is 0.0078 days too long. Over centuries, this small error accumulated: by the sixteenth century, it had shifted the calendar roughly ten days off from the solar cycle, pushing the spring equinox, and with it the calculation of Easter, away from its historically defined position.
Pope Gregory XIII commissioned a reform, guided by the astronomer Christopher Clavius and the physician Aloysius Lilius. The reform was announced in the papal bull Inter gravissimas, issued on February 24, 1582. The key innovation was a new rule for century years: a century year would be a leap year only if divisible by 400. This eliminated three leap years every 400 years (1700, 1800, and 1900 became common years; 2000 remained a leap year), producing an average year length of 365.2425 days, accurate enough that the Gregorian calendar drifts only about one day relative to the solar year every 3,300 years.
To correct the accumulated drift from the Julian period, October 1582 simply lost ten days. October 4 was followed by October 15. Anyone born between October 5 and October 14 in any previous year suddenly had no birthday that month.
Why Months Are Difficult Units
The irregularity of months dates to the Roman calendar, where months of 28, 29, 30, and 31 days were assigned through a mix of astronomical observation and political manipulation. Legend holds that Julius Caesar's posthumous influence gave July 31 days, and Augustus Caesar later extended August to 31 days to avoid having his eponymous month shorter than July, taking the days from February in the process. Whether this account is accurate or apocryphal, the practical result is a month distribution that carries no mathematical symmetry.
The twelve months of the Gregorian calendar have lengths of 28, 29, 30, or 31 days, with February fluctuating between 28 and 29. Adding one month to any date in a 31-day month runs into the end-of-month clipping problem. If you add one month to March 31, there is no April 31, so the result clamps to April 30. The same problem applies to January 31, October 31, and December 31. A program that adds months by computing the corresponding day number in the target month must decide how to handle this, and different software systems make different choices, producing silent discrepancies in business applications.
Why This Matters for Practical Calculations
Date calculations that span months encounter the irregular month problem repeatedly in everyday contexts.
Contracts with net-45 payment terms require the date that is exactly 45 days from the invoice date, not 1.5 months. The distinction matters at month boundaries: net-45 from January 20 falls on March 6, not February 20 plus 15 days (which would be March 7 or 8 depending on the year).
Medication refill schedules are similarly affected. A 30-day supply prescribed on January 31 runs out on March 2 (in a non-leap year), not February 28. If the pharmacy's system treats a 30-day supply as "one month," the patient may be told to return February 28, two or three days before the medication actually runs out.
Loan term calculations raise the same issues. A loan term of 24 months beginning June 30 ends June 30 two years later. But a loan specified as 730 days (roughly 24 months) beginning June 30 in a non-leap year may end on a different date, depending on whether leap years fall within the term.
The inclusive versus exclusive counting problem compounds all of this. "How many days between January 1 and January 31?" has two defensible answers. Include both endpoints and the answer is 31 days. Count only the days between them and the answer is 29 days. Legal contracts, financial instruments, and insurance policies often specify which counting method applies precisely because the ambiguity creates real disputes. The ISDA Master Agreement, which governs most over-the-counter derivatives contracts, defines multiple day count conventions ("Actual/360," "Actual/365," "30/360") specifically to resolve this ambiguity for financial calculations where small differences accumulate into large dollar amounts.
Leap Year Edge Cases
February 29 exists only in leap years: years divisible by 4, except century years not divisible by 400. This produces a class of edge cases that are not hypothetical.
A person born on February 29, 2000 (a leap year) has a legal birthday that exists only every four years. Courts and government agencies have consistently handled this by designating February 28 or March 1 as the effective birthday in non-leap years, but different jurisdictions make different choices. A driver's license in New Zealand becomes valid on February 28 in non-leap years; in the United Kingdom it becomes valid on March 1. The difference is a day, which can matter for age-gated activities.
Software systems that store dates without leap year awareness fail at February 29 in non-leap years in ways that can be hard to reproduce. A subscription billed monthly to a customer who subscribed on February 29 may fail to generate a billing date in most months, requiring a fallback rule, and inconsistent fallback rules between the billing system and the account management system produce customer-facing errors that are difficult to diagnose.
Conclusion
The practical approach to date calculations is to use tools that implement full Gregorian calendar logic rather than arithmetic approximations. The common mistake is converting to days by multiplying months by 30 or years by 365, then computing with the approximated day count. This is fast and usually close, but it produces errors of several days at month boundaries, and those errors compound when the calculation spans multiple periods.
For deadline tracking, contract management, project planning, and any other work where the specific date matters, exact day counts derived from actual calendar logic are what protect against the edge cases that approximate arithmetic misses. A date calculator that knows the true length of each month, which years are leap years, and whether to count endpoints inclusively or exclusively gives a reliable answer in a fraction of a second. ToolHQ's date calculator computes the exact number of days between two dates, or the target date a specified number of days from a starting point, using complete Gregorian calendar rules including century leap year exceptions.
Frequently Asked Questions
What is the difference between adding days and adding months to a date?
Adding days counts forward by an exact number of calendar days. Adding months moves to the same day in a future month, capped at the last day of that month if the date doesn't exist (e.g., March 31 plus one month is April 30).
How do I calculate a date 90 days from today?
Count forward exactly 90 calendar days from today's date. A date calculator handles this precisely including leap years. Mental arithmetic or month counting can introduce errors of several days.
Is February 29 always the leap day?
Yes. The Gregorian leap year rule adds February 29 in years divisible by 4, except century years (1900, 1800) which are not leap years unless also divisible by 400, making 2000 a leap year but 1900 not.
How do I count days inclusively vs exclusively between two dates?
Inclusive counting includes both the start and end date. Exclusive counting includes only the days between them. Contracts often specify which method applies. A date calculator can return both counts.