EDC Batch Numbers

I'm trying to figure out what is going on with our EDC Batch Numbers, and a partially settled batch (according to the bank) but according to RMS completely settled.

We settle all our transactions at the end of every day. So I would assume we would just have one Batch Number per day. But on quite a few days we have multiple batch numbers does anybody know what could cause this? Sometimes we also seem to skip numbers and go out of sequence (in other words we go from batch # 991, skip 992, 993 -996, then we have 001, then 997, 998, 999, 001 (duplicated) the next ten batch numbers are in the proper order. According to our bank's transaction logs the different batch numbers are for the same day are created within a minute or so and the "closing" managers are not having to settle or click on settle multiple times and our Internet connection is very solid.

Also I just noticed that our batch number reset to 1 after it reached 999, seems kind of strange. Why not just let it run?

I'm using RMS SO 2.0.0114

I'm trying to figure out what is going on with our EDC Batch Numbers, and a partially settled batch (according to the bank) but according to RMS completely settled.

We settle all our transactions at the end of every day. So I would assume we would just have one Batch Number per day. But on quite a few days we have multiple batch numbers does anybody know what could cause this? Sometimes we also seem to skip numbers and go out of sequence (in other words we go from batch # 991, skip 992, 993 -996, then we have 001, then 997, 998, 999, 001 (duplicated) the next ten batch numbers are in the proper order. According to our bank's transaction logs the different batch numbers are for the same day are created within a minute or so and the "closing" managers are not having to settle or click on settle multiple times and our Internet connection is very solid.

Also I just noticed that our batch number reset to 1 after it reached 999, seems kind of strange. Why not just let it run?

I'm using RMS SO 2.0.0114

Todd, thanks for your reply, here are my answers/remarks:

1. Our processor allows up to 6 or 7 digits for batch numbers but maybe not all processors allow for this. Of course this wouldn't matter much if we would only use one batch number per day and the batch numbers wouldn't repeat until about every 2 1/2 years but that's not the way it is in our case.

1. Yes I am using the build in CC processing.

1. The bank shows the exact same batches as RMS shows.
2. There is no time sorting issues. When I look in the VisaNetAuthorization table during the day I can see several different batch numbers being used/requested and they are not even in chronological order.
3. The batch number that was skipped was not settled the day before.

It seems to me that the "roll over" from batch 999 to 1 issue that was supposedly resolved does still exist. Has anybody else run across this?

Todd, can you think about any other reason why RMS SO 2.0.0114 would create multiple CC batches? How does RMS determine the next or current batch number? Does it use the highest "open" batch number available?

Todd, thanks for your reply, below are the follow up answers/questions:

1. I've never had a duplicate batch error until last week when RMS SO was showing that two different batch number 1s were settled fine twice within a three day period, but the acquiring bank showed a QD on their side (for the

2nd batch number 1). Again the only time that we've had this happen was right after the role-over from batch 999 to batch 1.

1. I have always had the batch size set at the highest number possible which is 9999, opposed to the default which is/was 400 (I believe).

2. Your are correct in regards to the hot fix, but I seem to remember reading about a 999 issue somewhere else but I can't seem to find it or remember where I read about a similar problem.

1. Number 2 should not be an issue as are batch sizes are nowhere close to

9999.

1. We only have two add-ons (RR Promotions and Newest Auto log out) which have only been installed for several months but the multiple batches per day problem has been happening since day 1 (about 1.5 years now).
2. We don't have any custom stored procedures or triggers.
3. I reindex on a regular basis.
4. We don't use offline mode at all (registers have no offline database setup/defined).

5 & 6. Where or how does the VisaNetBatchID in the VisaNetAuthorization table come into play if the batch number is determined from the VisaNetBatch table?

New question: As mentioned we settle batches every day but sometimes (new) managers forget to settle. Is there a way to only settle transactions from a certain day (i.e only transactions from yesterday but not from today)?

Thanks you!

Todd, thanks for the answers.

1. Processor claims that they can handle whatever we "throw" at them
2. I'll double check all my registers to see if there maybe is a register that (inadvertently) has a wrong/low max batch size number, because this could cause the described behavior correct?

1. No I meant 9999 which was referring to the max batch size.

Any other suggestions?

Does anybody else have this problem?