web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Item marked as reconciled in the checkbook but it's not and item cannot be voided either

(0) ShareShare
ReportReport
Posted on by

Hello,

Here's the problem.  I'm hoping someone can help.

We entered a transfer between two of our bank accounts into GP 2010.  The first problem is that although we only entered the transaction once, it appears in the checkbooks twice.  The transfers have two different transaction numbers.  No idea how this would have happened.  We thought it was no big deal and that we would just mark one off as cleared when we did the bank rec, and then the other we would leave uncleared so we could delete it.  Of course things are never that simple with GP.  After we did the bank rec, which was when we noticed the duplicate item, two other problems arose.  The first was that the item we marked as cleared during the bank reconciliation, does not show as "reconciled" in the checkbook.  The item that we left unmarked, instead shows as "reconciled" in the checkbook.  Again, no biggie, right?, since the items are the same dollar amount, same date, etc. - wrong.   The second problem was that we cannot delete the unmarked/uncleared item. When we attempt to do so, we get a message that says "This transfer can't be voided.  It is either marked for reconciliation, has been reconciled, or has already been voided." This makes no sense because when we pull up the bank reconciliation screen to do the next bank rec, the item is sitting in that window and shows as unmarked, making us believe that it is available to tick off with a subsequent reconciliation.  If that was truly the case, we should be able to void it, but we can't.  So it seems to me that there is a miss between the bank reconciliation and the checkbook.  

Please let me know if you have ever seen this before and how you went about resolving it.  

Thank you.

*This post is locked for comments

I have the same question (0)
  • L Vail Profile Picture
    65,271 on at

    I have never seen this but it sounds like something that is going to require SQL to edit some values in the tables. Are you comfortable doing this?

  • Community Member Profile Picture
    on at

    Leslie,

    I have a similar situation with duplicate transfers and I  get the same error message.

    I am very comfortable editing the tables in SQL. I will test in the Test Company and Backup before I edit the live database.

    Do you know what I need to look for or change to get around this error message? Tables and fields would be helpful.

    Thank you very much for any help,

    Dave

  • L Vail Profile Picture
    65,271 on at

    It sounds like the two entries have split the attributes. First, I would decide which one of them is the 'real' entry and which one you want to treat as the duplicate. I would change all of the 'flags' such that the one that cleared is reconciled and the other one is alone with no apply records hanging on it. So you'll end up with one 'good' transfer and one 'bad' transfer. Once all of the details are separated, you should be able to go in and remove the errant transfer. While this was messing up your checkbook register, what was happening to the general ledger?

    Kind regards,

    Leslie

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans