| | | |
|---|
| 1 | Testamentary Trust | what is the use of the field called Testamentary Gift? So you set it to true, if you know it's a Bequest. if you're already tracking it as a record type of planned gift, why would you also set it to? True? So it's just an added field.
| |
| 2 | Rommel’s Update | Confluence pages for AQ consult with notes and tasks are created and shared with Priscila. I reviewed the recordings and captured important points and action item so we can have them in a list and track their progress/completion Raised zendesk ticket (Pledge correction on a grant with soft credit versus pledge with soft credit had different results on transaction type (v24)) which i discovered when testing out scenarios Workaround for pledge correction bulk entry filter the entries as trim as possible use Apsona to delete batch correction items that we don’t intend to do correction on (object list with filter). Use this with caution not to mass delete other objects or records. then close the batch correction caveat : batch correction does not auto correct a the linked soft credit to a payment. Suggest to batch correct both the payment and the soft credited pledge…. and then link the new soft credit to the new corrected payment transaction. this workaround needs to be discussed before use so it is clear when to use it and how.
| https://support.affinaquest.com/hc/en-us/requests/8576 |
| 3 | Pledge Write off | an idea that Priscila’s colleague might be able to conceptualize a LWC however might be challenging when we have different write off reasons and pledge writeoff only works at one reason at a time. maybe we can use normal smartbatch writeoff instead of the utility
| |
| 4 | Receipting | Account Address Temporary - why is this stamped on the receipt? we are not sure, it was defined in feb of 2021. It’s not being used in Apsona receipting. Hand deliver receipt. In the olden days we allowed development offices to request that instead of us immediately posting the receipt. they could pick up the receipt and then send it with either other documentation or write a nice, you know. Warm message to the donor that accompanies the receipt so they could, you know, write on the receipt for that personal touch. But we don’t seem to use this anymore. walked through why we have different Apsona report and why they can’t be consolidated into one email and non email cannot be combined because of Apsona limitation of not being able to do both in one merge action. potentitally we can consolidate reprint and grant into the email receipt as they are just different in template and we can conditionally change the template on an Apsona merge action.
One of our biggest issue is when receipts are being voided when we do not intend to void and reissue the receipt. We dont reissue receipt for change of designation. we only want to update the receipt when it is moving from holding account. Not if it is a processing error or actually changing the designation. On the designation we have an indicator if it is a holding account. most time consuming when doing receipting when running receipting utility there is a wait before you run apsona we can only choose generate one file but it wouldn’t attach on object as apsona limitation. But user reckon they used to be able to both (consolidated file and attach individual files) if don't have gift acceptance we hold receipt. later on when we get acceptance we need to then issue the receipt we also have challenge where we need to issue separate receipts for one gift. what we do we adjust GRC, generate receipt and we adjust again and generate another receipt multiple transactions are being consolidated by the receipting utility when we want to split them. work around is we artificially enter them in different batch or different day. another proposed work around is to tick one trasaction’s void flag so that receipting utility doesn’t pick it up. we think receipting utility should ultimately be re-written
| |
| 5 | Gift Officer notification | DO’s can follow account so they get notified. but we are not sure how this is supposed to work. we do use chatter, mainly to talk about things (i.e. we are working on opportunity) leverage chatter, create a group and use that to notify users we have some notifications setup in the system (i.e. when someone dies) leverage stewardship? we setup chatter update then we can deprecate some of the files like the hand deliver receipt
| |
| 6 | | | |
| 7 | | | |
| 8 | | | |
| 9 | | | |