Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

Missing Transaction from Payroll Integration to Payables

Posted on by 2

Hi,
I can't seem to find a whole lot of information out there about Payroll Integration to Payables (GP Extension) so I'll cross my fingers I can find an expert here!

I've got an employee that has had a child support deduction every week for the last 8 years and it's integrated into Payables with no problem... except for this pay run.  The amount was deducted from his check, but the record was not in the AP Batch that's created through PIP.  How can I find out what happened?  No settings have changed on this employee since last week (we audit everything PR related). 

Originally I thought it got rejected because of a duplicate document number (SMITH 10/24, which occurred in 2008) , but I see that there are other entries with more than one of the same Document Number.

Does anyone have any suggestions where to look? 

Thanks in advance!

Jim

*This post is locked for comments

  • Joshua Page Profile Picture
    Joshua Page on at
    RE: Missing Transaction from Payroll Integration to Payables

    That PIP document number isn't standard, it's normally along the line of "PIP00000000000001234".

    I know there is a few 3rd parties that have their own version of PIP, and some of them allow you to customize the doc number. If I remember correctly Integrity has a PIP product and it allows you to change the doc number, is it possible you are using their PIP product or another 3rd party PIP product?

    It's possible a duplicate like that against the same vendor, especially on the same date, might cause some problems but I'm not entirely certain. I know there's a few common report modifications that a duplicate like that would cause an issue with however. If a product inserted it like that into the work tables it's entirely possible that the system, would allow it to post through since all indexes on the tables that use DOC NUMBER also have DEX ROW ID in them as well (so wouldn't cause a dup key\index error).

    Joshua

  • Jim Lines Profile Picture
    Jim Lines 2 on at
    RE: Missing Transaction from Payroll Integration to Payables

    Joshua,

    Thanks for responding.  I had not thought of manually entering the transaction to see if there was a block on  duplicate document numbers.  I confirmed that this IS indeed the case, our setup is to not allow duplicates.  However, if you take a look at the screen shot attached, I have two transactions with the exact same document number (GONZALEZ 10/24) from the same day.  The only difference is the Transaction Description which is the deduction code reference.  This doesn't make sense to when comparing to my issue.  Do you have any thoughts on this?

    Also, do you happened to know where the document number is set up for PIP?  It would seem like a good idea to add the two digit year to the doc number, assuming there would be enough space, to prevent this going forward.

    I appreciate any help you can provide!  Thanks!

    Jim

  • Suggested answer
    Joshua Page Profile Picture
    Joshua Page on at
    RE: Missing Transaction from Payroll Integration to Payables

    Hello Jim!

    Duplicate Doc number could cause actually still be the issue. A vendor can only have a doc number used once per transaction type. If you go into the PM Transaction entry window and enter the exact same document number do you get a warning message?

    Another possibility is that there was an interruption when GP was trying to process PIP (most likely there would be others that did not have their PIP transactions created in this case).

    If you have a test company you can restore live to test and then run a new payroll (for this one person will be fine) and see if you can process PIP with a different doc number.

    Set up a test company that has a copy of live company data by using SQL Server 7.0, SQL Server 2000, SQL Server 2005, SQL Server 2008, or SQL Server 2012

    support.microsoft.com/.../871973

    If you can it was most likely an interruption or, as you initially suspected, a duplicate doc number.

    Joshua

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans