The error being thrown was:
That's fairly straight forward, it just means that the date I am trying to convert doesn't have enough precision for the format that I am trying to convert it to. The SQL below demonstrates this...
Interestingly the error disappears when I add a month and day to my date value i.e. 20160101 is OK even though my format expects hours, minutes and seconds too.
My workaround takes advantage of the above find by padding the date up to 8 characters (yyyymmdd) as required. It consists of two rpad operations, one for the day and one for the month to cater for inputs of the 'yyyy' and 'yyyymm' formats.
This is the end result...
It's not the best solution but will get you out of a bind if you really need to pad dates like this.