Future FY pledge payment restriction on posting reports

Hi everyone-

I've come across a curious phenomenon, and I'm not sure if it's an expected function or a system bug.

We've recently had a few occurrences of having future fiscal year pledges both booked and fulfilled this fiscal year. A pledge, when entered, is correctly autorestricted to the first date of the future FY it's meant for. On the Tessitura posting report, this money shows up in the restricted column per usual. No problem here.

However, when fulfilling the pledge, the payment does not show up in the restricted column on the posting report. In looking in the donor record, we can clearly see that the money is still correctly restricted (as applied to the original pledge), but to our Finance department it appears simply as an error, which then needs to be researched, etc. to be sure of accuracy.

To be clear- the system is functioning properly from a practical standpoint- payments on restricted pledges remain correctly restricted. It's more an issue of clarity/cosmetics- because the payment does not appear in the restricted column in the posting report (days, weeks or months after the original pledge was booked) it can cause confusion and get incorrectly flagged as an error.

Does anybody know why this is the case, that payment on a future FY pledge does not show up in the restricted column on posting reports? Any insight is appreciated!

  • The report is working properly.   Revenue (Gift or Pledge) is restricted not the payments.   Unless your site is placing cash in a separate account and releasing it when the revenue is released  I don’t see that this would be a problem.   This can be assisted I believe by running the Fund Activity with Group by Campaign Fund.

     

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Martin Giannini
    Sent: Thursday, July 03, 2014 1:46 PM
    To: McKinley, Leslie
    Subject: [Tessitura Development Forum] Future FY pledge payment restriction on posting reports

     

    Hi everyone-

    I've come across a curious phenomenon, and I'm not sure if it's an expected function or a system bug.

    We've recently had a few occurrences of having future fiscal year pledges both booked and fulfilled this fiscal year. A pledge, when entered, is correctly autorestricted to the first date of the future FY it's meant for. On the Tessitura posting report, this money shows up in the restricted column per usual. No problem here.

    However, when fulfilling the pledge, the payment does not show up in the restricted column on the posting report. In looking in the donor record, we can clearly see that the money is still correctly restricted (as applied to the original pledge), but to our Finance department it appears simply as an error, which then needs to be researched, etc. to be sure of accuracy.

    To be clear- the system is functioning properly from a practical standpoint- payments on restricted pledges remain correctly restricted. It's more an issue of clarity/cosmetics- because the payment does not appear in the restricted column in the posting report (days, weeks or months after the original pledge was booked) it can cause confusion and get incorrectly flagged as an error.

    Does anybody know why this is the case, that payment on a future FY pledge does not show up in the restricted column on posting reports? Any insight is appreciated!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!