You are absolutly correct. I am not excusing this, but thought I would add some color to how something like this gets past QA.
BASE CODE goes through our normal QA process testing before and after the code is changed to make sure we didnt miss something.
But then we also have the CSF development team who does additional work that needs to be applied to the base code. This application layer is applied to based on which country the customers are part of. If you are in Germany, you get the German CSF. in USA you get the USA CSF, etc… Back in the olden days, the USA CSF was part of core, but has since be separated because people in germany dont need 1099 functionality…
So… for electronic filing of 1099 there is a type field that must be populated in order to check the type boxes on the 1099 and the CSF team took care of the problem, adding this new SUB Type field. Since it is Required (per IRS Rules) they marked the field as required. I dont have total proof on this, but in the attempt to be transparent here, it would appear that they only tested to make sure that the field was required. They missed testing with the 1099 checkbox = false. YES, there was an error in the fact that it is only required if the 1099 checkbox is true… (This was BUG #1 - being fixed hopefully for the .5 release).
BUT there was a second “bug” in the fact that on a customer who is upgrading from a database with 1099 true, and SubType = blank, the system didn’t allow you to save without populating this field. This is not really a problem when adding new suppliers, because you would find this out as you save.
We are working on making this HARD ERROR changed to a WARNING instead of a hard stop. I have also requsted that the warning message that is displayed be more descriptive of what is needed.
But note that this does not fix the entire problem with your data. If you have a bunch of suppliers with a 1099 true, then you will still need to populate the SubType field, as this is requried by the IRS… if you submit 1099s without this, they may reject them (according to what I read last night). So… while this second “bug” is hopefully being tweaked, you still have work to do with any 1099 suppliers.
At this point, you should also probably create a BAQ Search or QuickSearch or an updatable dashboard to find all 1099=true supplier with blank SubTypes and populate them with a valid subtype.
2 Likes