This is a known COSMETIC error that doesn't effect the current year return ... it will be fixed in a future update.
View solution in original post
