Hi Brus,

Hard as this may be to believe, we have not had any previous reports of anything similar to this. I'll be interested to see what process she's using.

If you used the "authorization number" from the credit card terminal as the "check number" it would be unique and would avoid the "duplicate payment" problem.

Is there a reason that you are not using the "direct" method of sending the batches to Receivables? This would send the payment method across as well (if you're using AR 9.0A).

She then went in and manually changed the second error batch with the correct errors but they did not post accurately, they posted with the values of the first batch of errors.

This doesn't make any sense. We've never had a batch "not post accurately". Does she mean it didn't post the way she expected? What was she expecting and what actually occured? If she could religously make a backup prior to posting, then she would be able to send us the data if something didn't post "accurately" and we would be able to see what she was seeing.

I'm sure we'll track this down. If she's using an unexpected procedure, we should protect against it.

Is it possible she's copying files back and forth between systems?