Excel ‘leaps’ back!

Take a seat suiteSheets, this one’s for the pub quiz!

Did you know that Microsoft Excel thinks 1900 was a leap year?  It wasn’t!

So, what happened?

Why does Excel think 1900 was a leap year?

Back in the early days of Excel, Microsoft made a small decision, they chose to copy how an older system, Lotus 1-2-3, handled dates.  Sounds fairly undramatic.  

However, Lotus 1-2-3 contained a small date calculation error, it treated 1900 as a leap year.  Rather than create compatibility problems between the two systems, Microsoft copied it into Excel.

And it’s still there, Excel will quite happily accept 29 February 1900 as a valid date, even though it never existed!  Whoops!

Why doesn’t Microsoft fix the Excel leap year ‘bug’?

Because changing it now would break millions of existing spreadsheets that rely (knowingly or not) on how dates are calculated. 

Dates would literally shift. Calculations would move. Chaos (of a very spreadsheet kind) would follow.

So the decision was made to leave it as-is.

You can find Microsoft’s take on the matter here - Microsoft (2026)

The quiet takeaway

Worry not, unless you’re doing bookkeeping for the Victorian era, historical data analysis covering early 1900 or entering dates from over a century ago! 

For modern records, everything works exactly as it should.

But it seems even the most reliable tools have a few quirks under the bonnet. Luckily, we’ve spent a bit of time getting to know them to make sure they don’t become yours!

Got a favourite “Excel did what?!” moment, or spotted something equally strange?  Pop it in the comments below, we’re always up for a good pub quiz entry!

Previous
Previous

Quarterly updates, what actually happens?

Next
Next

MTD Categorisation