Our screens could be different because our claim reconciliation only allows date spans except for Medicare FSSINQ which includes name spans.
I did experience something similar with a very basic script that looped through a directory of 835s and entered each file name for eCare to import. It took me a while to actually find what was causing it. I noticed that sometimes if you tab through to hit a field that has default data that you need to change, sometimes eCare would not highlight the entire field. I went through a lot of script iterations to try and work around it, but ultimately I asked our Nebo programmer to make that field blank by default.
In my experience, I would look for any time you're entering data to make sure it's 100% accurate and make sure the script is slow enough for eCare to react. Sometimes it even throws an error with the SQL statement that is erroring and that could help.