We process pledge reminders each month using the last day of the following month for our run date.  For example, on September 25th, we will run pledge reminders for all pledges that are due in October.  We do this by using the run date of 10/31/2009.  Unfortunately, using 10/31/2009 causes several issues for us.  First, in the history, we would like to see that the pledge reminders were created and mailed out on September 25th. Instead, we are seeing the 10/31/2009 date in the history.  Does anyone know how to resolve this?  It is very misleading when someone reviews the history for the pledge reminders we sent out.  Secondly, the pledge reminders use the run date as the date of the statement.  Once again, we would like it to reflect the September 25th date---the date we processed the reminder.  We manually change each reminder, using find and replace, but this is an extra step we must remember to do each month.  Has anyone else experienced these issues?

Quite frustrating isn't it? 

I agree, I want the date I process/print the reminders in the constit record history, not the run date.  According to knowledge base solution BB503606, it's one of the suggestions they are reviewing. Yeah!    Vote yes if it would benefit your organization.  Don't suppose it will change anytime soon.  It sure doesn't make the history accurate at all.

On your second issue, haven't had that one.  I just ran a test of mine and I get 'as of Sept 21'.  I don't know why it is pulling your run date as the date of the statement.  Are you on the 7.91 update?  (Our update was postponed again due to business office issues.  7.85 pulls current date for us.)