Deleted Payroll Ck

[Kerriberry]

I deleted a payroll check and then turned around and re-entered it. Tried to preview a GL Report and received an error. "Acct #xxx in GL doesn't foolt in Period 24" error. Ran the following Integrity Checks...Reindex Files-Chart, then Reindex Files-Jrnl Header, and finally Data Sync Chart of Accts/Journal. Problem fixed. GL Report and Financials are fine.

However, my 941 and this EE's W2 is overstated by the exact amount of the Deleted Check!!!

Any suggestions?

[Jim Dale]

data integrity? which version? it works well with 2003 & 4. why not reindex rows, change to period one and emp/journal synch. oh reindex everything again. i think u missed some steps

[Kerriberry]

Jim - I'm working with v9.0. I did change to Period 1 first. The only tests I ran were...Reindex Files-Chart, Reindex Files-Jrnl Header, then Data Sync-Chart of Accts/Journal. These were the steps per PT's online Support Center.

I have never ran Data Integrity, nor Reindex of Rows or Data Sync-Emp/Journal.

I will try the two tests above and go from there. Thanks!

[Jim Dale]

Be sure to report your results... Thanks!

[Rose Grinding]

Could it be happening because the check was deleted and not necessarily voided?

IIRC, a couple years ago, I ran accross this problem and re-entering the check screwed up the register entries somehow, so I voided the check as well and made a new check and check number and all was right w/ the world. Granted, not the absolute cleanest solution, but the only one I found at the time that worked.

[RetroCanino]

If you are having problems with EEs, you need to reindex EMployees and then run the EEmployee. Journal Sync Test (from period 1)

Also, as a side note: When you reindex Jrnl Hdr you need to also do Jrnl Row.

[Jim Dale]

Sometimes things like deleting checks do introduce corruption. Often the data verification in 2003 & 2004 will fix this type of problem. Does not work as well in 2002. Each integrity check that you do addresses different problems so RC is right don't ever skip steps when you run them. And PLEASE backup 1st

[TheWolf]

Deleting a check itself should not cause data corruption. If there was a hardware problem, power surge or other anamoly when you deleted it then maybe. Have you tried deleting the re-entered check? Have you checked the payroll journal report to see if it is in balance? Did you change any fields that were set as memo fields to use a GL or vice versa?

[Jim Dale]

Tom is the expert. Corruption is a funny thing though. Sometimes it does get introduced when there is no apparent reason although it is usually related to something that you can measure like brown outs power failures or network activities