Because it is a massive pain in the butt for your report writers / business intelligence people whose tools expect decimal fields. Never mind all the existing code that expects an actual decimal and not an integer. Plus tax folks like like their mills.

> Because it is a massive pain in the butt for your report writers / business intelligence people whose tools expect decimal fields

That's a matter for the ETL that dumps the data on their screens.

Yeah, no. First, sometimes you actually don't get to use a ETL before doing the report, and massaging an integer or float to decimal in an ETL is just going to cause you trouble.