All business activities are of course embedded in business and tax year cycles (aswell as monthly and weekly and daily cycles), built out of working weeks, days and hours; this results in often quite complex calculations to match processes to the exact intervals of time due to elapse, before a deadline, or a dividend, etc., (due to leap years and bank holidays and the like).
These kinds of clock and calendar issues can be handled quite elegantly using for example ready made Java classes, so that statistical models built using "continuous time lines" can be mapped in useable ways into business activity cycles.
It's a tedious but totally necessary aspect of coding projects in a human business environment involving actual human working cycles and other patterns (and exceptions such as leap years, etc.)