Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Safe Pay including wrong voided transactions details

(1) ShareShare
ReportReport
Posted on by

We recently had a check batch was accidentally posted that included every open payable. This resulted in the printing of thousands of checks. We print to a PDF writer so the stock was not lost. Our course of action was to void the entire check batch, turn off safe pay communication and then run safe pay extract process. The file generated but was not uploaded to the bank to avoid confusion and issues with that service. Once the file was discarded, we enabled “Duplicate Check Numbers” on Checkbook Maintenance.  However, now when we are voiding checks that exist from the second use of that number, GP safe pay is outputting the check amount and payee detail from the original mass check run that was posted and entirely voided already.  Our expectation is that the void process of the 2nd instance of the check number would create output for the transaction being voided and NOT the transaction originally voided – regardless that the check number is identical.

I have read ARTICLE ID: 851929  and it is important to note that the Transaction Date is different so I"m not sure why this is happening.

*This post is locked for comments

  • Redbeard Profile Picture
    12,931 on at
    RE: Safe Pay including wrong voided transactions details

    Ryan,

    If it turns out the problem is caused by a bug, then Microsoft should credit the incident back to you.

  • Community Member Profile Picture
    on at
    RE: Safe Pay including wrong voided transactions details

    Appreciate the comments and I guess the answer to open a MSBS incident could likely be the resolution to any issue, hopefully someone else has experienced this and I can safe my annual incidents allotted under our support plan.

    NOTE: We did not disable Safe Pay, but rather only disabled the automated "communication link" such that the file was fully extracted, the bank simply did not receive it.

  • Suggested answer
    Redbeard Profile Picture
    12,931 on at
    RE: Safe Pay including wrong voided transactions details

    I have not experienced this particular issue with Safe Pay, but know from configuring it, Void Transactions are one of the transactions supported by the application.  It appears from your description of the circumstances, you temporarily disabled Safe Pay communication.  I am not sure if this was necessary, or advisable.  

    It is understandable you would not want to officially void thousands of checks with your banking institution, but your attempt to avoid this, may have been more trouble than it was worth.

    I would strongly suggest you initiate a support incident with Microsoft Tech Support, who should be able to help you sort this out.

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

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Almas Mahfooz Profile Picture

Almas Mahfooz 3 User Group Leader

Featured topics

Product updates

Dynamics 365 release plans