I am trying to enter a payment for a customer but I get the error message "This check has been entered for this customer already" Is there any way to override this nagging message. The customer must be using a different bank to write checks from. Long story short I want to post this customer's payment with a check number that just happens to be the same as a previous check. I encounter this annoying issue once or twice a year. How can I do this?
*This post is locked for comments
It is totally bizarre and we found in the customers data where they had multiple iterations of the same check number with different customers. I pulled the core logic from the source proc for raising the error, examined it and all should be well. I "think" we have no other avenues but to contact Microsoft. eConnect internal version on both working/non-working environments matches at 11.0.1.0 at the company level.
Mindy,
That does not sound right - I just searched through our data and we have over 100 instances of the same check number received from different customers. We've never had an issue with this.
Mike, Did you ever resolve the issue? We are experiencing the same issue; in our case the check number already exists for another customer with a different date.
p.s.
The specific error we are getting trying to bring those transactions in again is "Error Number = 11481 Stored Procedure= taRMCashReceiptInsert Error Description = Duplicate check number for this customer already exists in RM00401"
Interesting. My QC group claims that, through eConnect, they have been able to import the same batch of payments (some of which include check numbers) over and over, and the only thing they needed to change on the transactions was the doc date to allow the transactions to be imported in again. We have been on GP2010 RTM since last December, and are testing an upgrade to GP2010 SP3. With SP3, my QC guy can't bring those batches in more than one time, regardless of the doc date. Would this possibly be a "hole" that was fixed in eConnect in either SP1, SP2, or SP3?
Hi Mike,
That has been the case for as long as I can remember. I definitely remember running into in on GP 8.0, at least.
I usually add a -1 at the end of the check. This is usually for re-entries when I void and re-enter. But it would work the same
Hi Victoria, when did GP start requiring that all check numbers be unique per customer ID?
I would like to know this in relation to a) entering a check in Dynamics, and b) importing a payment via eConnect.
Bron is right, there is no setting to override this. :-( GP requires that all check numbers are unique per customer ID.
I actually think this is a good control, as it will prevent you from mistakenly entering the same payment twice. Unfortunately, once in a while you run into a situation where the customer switches banks and/or restarts their check numbering scheme. In that case, both Bron's and Melissa's suggestions are right on - add something to the front or end of the check number and you're good to go. If you don't want it to be too noticeable, you can add a period ( . ) at the end.
I would probably suggest devising a method such as.........
Check Number 123456
Check Number 123456_1
If you get the message you simply add _1 to the number - GP will then accept it..........
I don't think there's a system setting (like in Payables - to override the number)........just a thought
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (