Statements Print Incorrect Data

[annie51ks]

I installed pca2003 in late July, upgrading from 2002. Now my statements print incorrect data. I've figured out pt is combining previous customer balances from the last printed statement with the current one printing on some statements, but others just show an incorrect beginning balance, current month activity, and a correct ending balance. I checked previous months and they show incorrect beginning balances also, as do test statements for future months. The upgrade conversion completed with no problems, and I've run data checks that return no errors. General Ledger amounts are correct. I print balance forward statements and the only work-around is to print open item statements, which I don't want. What's going on here, and how can it be fixed? If it can't be, can I go back to my 2002 version and how do I do that after 6 weeks of posting? Thanks!

[chikamic]

Due to the fact that your problem is with an upgrade, I would use my free phone call to Peachtree and see what they suggest.

[rmh7069]

I'd be interested in the solution you find. I've experienced the same problem with incorrect balances forwards and other quirky statement data.

I emailed peachtree three weeks ago and have not received a response. I guess, I will phone.

What is odd, is that I can preview each statement individually before printing and the amount is correct, but if you batch print (as certainly everyone does) they are wrong.

As with the original poster, the conversion went seamlessly, and data verification reports no errors.

HELP!


rh

[chikamic]

Since my last post it has been discovered that this is a known program problem and the only workaround at this point is to print open item rather than balance forward or print them one at a time.

As I suggested in my last post you should call Peachtree to register your complaint. The more customers that have issues the faster they work to solve the problem.

Good Luck.

[chikamic]

Attached is a note from a Peachtree VP. It was received by hcohn another poster on this forum.

As you point out, we have heard from customers who've experienced problems printing statements in the batch mode after converting to v. 2003. The problem appears to occur only under certain conditions and as such we've only heard from a very small percentage of customers who have upgraded. Nevertheless, it's an issue that we take very seriously and are working to address. We expect to release a downloadable update for 2003 in early November that will include a remedy for this problem. In the meantime, the only remedy we can offer is to advise customers who are impacted to print statements individually. I realize this is an inconvenience and will therefore be viewed as a less than desirable workaround for many customers. We apologize for that inconvenience and are working to offer a more substantial resolution in the upcoming update. We will utilize Peachtree.com to announce the date of that service release.

I thought I would post it on this thread since it addresses the same issue.

[rmh7069]

...For the info. I feel a little better knowing they acknowldge the problem and are working on it.

rh

[KWUJanelle]

Has anyone had this problem in prior versions of PT? I just started my job 10/1 and we could not make sense of the balance forwards on quite a few statements (acct. w/zero balance prior month showing an amount for balance fwd on statement).

About the middle of Oct. we upgraded to PT Complete 2003. The fix for 2003 can not come quickly enough even though there are not a large number of complaints as of yet.

[rmh7069]

Started up Peachtree today and the automatic upgrade window popped up. Seems the service release is finally here and this annoying problem has been addressed.

After installing the update, I previewed my customer statements and it seems the problem is resolved.

Whew!

rmh

[annie51ks]

Great! Thanks for the update. I believe I'll wait a few days to see if anything crops up on the new patch. I'd hate to compound the problem at this stage in the game!

[ELLIE]

I also installed pca 2003 in July updating from an older version and have the same problem. After spending hours on the phone with Peachtree techs, the problem is still unresolved. In my case, the error is caused by invoices that were "realigned" by the new version. Now, although the invoices exist and have been paid, they still appear on the statements as open. The total on the statement, though, is in fact correct. Also, if I try to open the "cash receipts" for these invoices, the system tells me that the invoice does not exist. I strongly suspect that there is a programming flaw that Peachtree is unable or unwilling to fix. Is there anyone out there that can help!!!!!!!!!!!

[chikamic]

Some of your problems seem to be a result of corrupt data rather than program problems. Backup your data and run data verification.

[TheWolf]

Originally posted by ELLIE
I also installed pca 2003 in July updating from an older version and have the same problem. After spending hours on the phone with Peachtree techs, the problem is still unresolved. In my case, the error is caused by invoices that were "realigned" by the new version. Now, although the invoices exist and have been paid, they still appear on the statements as open. The total on the statement, though, is in fact correct. Also, if I try to open the "cash receipts" for these invoices, the system tells me that the invoice does not exist. I strongly suspect that there is a programming flaw that Peachtree is unable or unwilling to fix. Is there anyone out there that can help!!!!!!!!!!!

Non-existing invoice error messages are caused by corrupt data.

The new patch, which now has a reg patch for the constant support message reminder, fixed the statement problems for all of my customers. If the patch does not correct your problem and you continue to get non-existing invoice errors you may want to look into getting your data repaired.

[ELLIE]

Sequence of events:
July 2002: Update to new PT complete without any problems
Aug. 2002: Run "data verification"
Outcome: Eight (8) pages times 18 lines (aprox 150) of so called trailing invoices--- Message from system: " A sales Journal transaction dated---with reference---for $-- has leading or trailing spaces in the reference number field. These spaces were deleted."
These were invoices that had been entered, posted and paid without any problems in the previous PT version.
NOW they show up in the customer statements as unpaid, although the actual total on the statement is correct.
Futhermore, I cannot open the cash receipts since these are now
"nonexisting" invoices.

I have downloaded the newest "patch" and it has done absolutely NOTHING.

Has anyone experienced the same problem and is there ANY HOPE!

[TheWolf]

These errors are releated to data damage. There is no patch to fix this. The leading and trailing spaces error should not be a problem unless these invoices were in beginning balances area for customers. You will want to search the Peachtree Knowledge Center for Non-Existing Invoice errors and follow their directions. I had it once and was able to fix it.

[ELLIE]

Originally posted by TheWolf
These errors are releated to data damage. There is no patch to fix this. The leading and trailing spaces error should not be a problem unless these invoices were in beginning balances area for customers. You will want to search the Peachtree Knowledge Center for Non-Existing Invoice errors and follow their directions. I had it once and was able to fix it.

I did follow Peach suggestion for this problem and although, by recreating the invoice with a space and dot at the end, I can open the cash receipt screen for the non-existing invoices, the system does not allow any changes nor deletions since it still cannot find the "original" invoice. And, of course, the invoices do show up on my statements as open although the total is in fact correct. How did you manage to do it??Please let me know since this is driving me NUTS!!!!

[chikamic]

If the problem was not fixed by the procedure, you will either have to restore a backup made before the non existing invoices appeared or you will need to have the data repaired.

[shopper]

I purchased 2003 in July and haven't been able to batch print my statements since. The patch they said would fix it did not, now they're saying February...I want to revert to 2002, but they say I'll lose all my transactions since July! Plus, I closed the year 2000 in November, and now all my balances are wrong. I can't even print accurate ledgers in order to re-load 2002 and re-enter the transactions! My boss wants me to ditch 2003, start a new company in 2002, and enter beginning balances.... Help!

[dhart@pmn.com]

We too have the issue with some statements including paid invoices, and the statement total is not correct (includes the bogus records).

We have run Data Verification and the resulting logfile has two Balance Forward records with "...leading or trailing spaces in the reference number field".

What is the resolution to this problem? TheWolf states this error is no big deal UNLESS in beginning balances for customers.
------------------------------------------------------------------------------
Also the log reveals approximately 200 records with the following error:

** A Sales Journal transaction dated --/--/-- to account 12203 is orphaned (no longer contains certain linked information).
Peachtree deleted this transaction because it was badly corrupted.
The Chart/Journal data synchronization test was started
to further investigate and resolve other transactions that
might be impacted by this error.

[ELLIE]

I am so glad that someone reopened this can of worms. My problems were CAUSED by the Data Verification module of PT complete acct 2003. The Non existing invoices were CREATED by running the DATA Verification. Those same invoices were NOT a problem prior to the upgrade. IF the data had been corrupted...would the previous version not had the same problem??????????????
(Please see my Nov. 2002 post for details)

[dhart@pmn.com]

Ellie:

It seems that in our case it was the upgrade, not the data verification utility, that casued our problems. We didn't run the data verification until after noticing the statement problem, so I don't believe data verification caused the problem.

Unless of course Peachtree automatically launched the data verification during the upgrade process...hmmm...

[ELLIE]

Please see my reply to LDRYSDALE which is also a reoccuring problem that ties in directly with "our situation". Should we call for a revolution..maybe we should all e-mail Peachtree directly and see if we cannot get at least some kind of a response from them..I hope this suggestion will not get me locked out of this forum but ....we really should be able to get some better answers to reoccuring problems, don't you think???

[dhart@pmn.com]

I'm on the phone with Peachtree tech support as we speak (er, type). I'll post a reply if that discussion proves fruitful.

[ELLIE]

I wish you better luck than I had since a year later, I still have to generate our statements one at a time, using for the most part our open a/r
Please let me know if you meet with any success, I would really appreciate it.

[ELLIE]

I would really like to keep this problem in the forefront. It has been ignored for much too long.
How do we make PT aware of the fact that many of us are having the same problem?
Maybe they just hope we will "go away"?

[dhart@pmn.com]

The simplest way to let them know is to call or email their support team.