voiding historical payroll checks

(0) Share

Report

Posted on by Community Member

We have several payroll checks from a closed (historical) year that need to be voided. I've tried changing my system date to reflect the check's original posting date, but when I do that I get the following error message: "Checks cannot be voided while the year-end closing is in process." Any ideas on how to void a historical p/r check? Thanks.

*This post is locked for comments

I have the same question (1)

All responses (10)

Answers (1)

Sort by

Suggested answer

Naga Kiran Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

If you need to void the check from previous year you need to change the user date to the date of the year the check belongs to. Please have your System and company database backed up before you do this.

1 people found this reply helpful.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Naga-thanks for the reply. I tried changing my date to the year the check was written, but received an error message about year-end close. Have you seen this error message before (please see original post)?

Was this reply helpful? Yes No
Suggested answer

Naga Kiran Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi NEIL,

This message occurs when there is a activity record in table UPR10300. However, the best solution for voiding historical pay checks is given in the below post.

community.dynamics.com/.../39781.aspx

Was this reply helpful? Yes No
Suggested answer

soma 24,410 on at

Like (1)

Report
Copy link

Link copied!

Go to Tools-->Utilities-->Payroll-->Remove Year-End Information window to clear the completed Year-End information.

Note: Before you begin, be sure you back up all company data.

If above steps not resolve your issue, follow below instruction.

Update the field YENDCRTD = 0 as per below KB article.

support.microsoft.com/.../855929

Hope this helps!!!

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report
Copy link

Link copied!

OK-I've voided the checks, thanks to your helpful responses. My follow up question is what to do about series posting the voids. When I go to series post them, I receive the following error message: "The date cannot be before the first day of the most recent historical year."

Any ideas on how to resolve this?

Thank you again.

Was this reply helpful? Yes No
Suggested answer

soma 24,410 on at

Like (1)

Report
Copy link

Link copied!

GP allow us to post one historic year prior to the earliest opening year.

For example: If you have the earliest opening year 2014 with all the prior years to this opening years was closed, for this scenario GP allow us to post one historic year 2013 prior to the earliest opening year 2014.

What is your earliest opening year?

Additionally, run the below query in SQL again company database and attach the result.

select * from SY40101

Also have a look on the below link.

support.microsoft.com/.../851093

Hope this helps!!!

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report
Copy link

Link copied!

Hi Soma,

Here's the result of running the query. Please let me know what you think. Thank you.

YEAR1 FSTFSCDY LSTFSCDY NUMOFPER HISTORYR DEX_ROW_ID

1998 1/1/1998 0:00 12/31/1998 0:00 12 1 11

1999 1/1/1999 0:00 12/31/1999 0:00 12 1 12

2000 1/1/2000 0:00 12/31/2000 0:00 12 1 13

2001 1/1/2001 0:00 12/31/2001 0:00 12 1 14

2002 1/1/2002 0:00 12/31/2002 0:00 12 1 15

2003 1/1/2003 0:00 12/31/2003 0:00 12 1 16

2004 1/1/2004 0:00 12/31/2004 0:00 12 1 17

2005 1/1/2005 0:00 12/31/2005 0:00 12 1 18

2027 1/1/2027 0:00 12/31/2027 0:00 12 0 19

2008 1/1/2008 0:00 12/31/2008 0:00 12 1 21

2007 1/1/2007 0:00 12/31/2007 0:00 12 1 22

2009 1/1/2009 0:00 12/31/2009 0:00 12 1 23

2010 1/1/2010 0:00 12/31/2010 0:00 12 1 24

9208 1/1/9208 0:00 12/31/9208 0:00 12 0 25

8208 1/1/8208 0:00 12/31/8208 0:00 12 0 26

5019 1/21/5019 0:00 1/22/5019 0:00 1 0 27

6636 1/1/6636 0:00 12/31/6636 0:00 12 0 28

2011 1/1/2011 0:00 12/31/2011 0:00 12 1 29

2020 1/1/2020 0:00 12/31/2020 0:00 12 0 30

2012 1/1/2012 0:00 12/31/2012 0:00 12 1 31

2019 1/1/2019 0:00 12/31/2019 0:00 12 0 32

2013 1/1/2013 0:00 12/31/2013 0:00 12 1 33

2014 1/1/2014 0:00 12/31/2014 0:00 12 0 34

8201 1/1/8201 0:00 12/31/8201 0:00 12 0 35

2006 1/1/2006 0:00 12/31/2006 0:00 12 1 20

Was this reply helpful? Yes No
soma 24,410 on at

Like (1)

Report
Copy link

Link copied!

Please provide the answer for the below question, this will helps us to resolve your issue as earlier.

1. What is the posting date for your voids?

2. What is your current opening year?

3. What is your earliest/last closed year?

4. Have you closed all the years prior to the current opening year?

Your reply is much appreciated.

Note: If your issue has been resolved, then mark it as a verified. Because this will helps to some others who having the same case.

Hope this helps!!!

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report
Copy link

Link copied!

Hi Soma, here are answers to your ?'s:

1. The posting dates vary, but they are:

January 5, 2005

January 5, 2006

January 19, 2007

2. Current opening year - I believe you are asking what our existing open year is. We are currently working in 2014.

3. The last closed year is 2013. The earliest closed appears to be 1998.

4. We have closed all years prior to the current open year.

Prior to series posting these voided checks, I did go to 2005, 2006, & 2007 and re-open those periods.

Thank you, Soma.

Neil

Was this reply helpful? Yes No
Verified answer

soma 24,410 on at

Like (1)

Report
Copy link

Link copied!

Neil,

You cannot post more than one year prior to the first day of the earliest open year. Means you can post only on 2013, not able to post prior to the year 2013. This is standard behavior in GP.

For your reference, please have a look on the below link.

support.microsoft.com/.../851093

Better you can void those transactions with using "voiding posting date" of current year.

Note: If your issue resolved, please mark it as a verified. Because this will helps to some others who having the same case.

Hope this helps!!!

Was this reply helpful? Yes No