The returns are stored electronically into relational data fields that are well known by their developers. The mapping of these data points between versions of SW should not really be an inssue. The issue is probably a logic issue on how the 2019 SW is ingesting the 2018 data. Proper coding should have debug points and internal logging which is included in the diagnostics files. It just seems that they have junior folks developing and/or coding the SW which they are lost on how to resolve. After 10 weeks of it be reported and a diagnostic files being sent in, for one developer, that equates to essentially 400 man hours to resolve a data import issue. Unbelievable and excuses for them don't fly with me. From an employee/developer perspective, you get what you pay for.
