2023-12-01 AQ Consultation Session 10

Summary of Discussions

• Apsona and Receipting

• Receipting Utility - inefficiency and voids

• Matching Gifts

• Pledge Write-Off Utility

• HEP integration

• Field suggestions for easier end-user data consumption of gifts and transactions

• Best practices in gift processing

• Support Tickets

• Flows and automation limits

• Reference ID when gift is converted to pledge payment*

• Giving Summaries*

• formalise catching up with customer success from AQ on regular basis

AQ Action Items

• mockup of what a pledge! Write off approval process would look like.

• receipting utility workaround.

• covering account and using the relationship affiliation object to do the word gift credit on certain contacts

• challenge gifts, matching gifts.

• provide documentation on matching gifts

• documentation on SmartBatch 2.0.

• use of the LL. Currency table

• pending request on checking the status of certain enhancement requests.

• Use of Fees to use with Matching Gifts

• Use of Holding Account and receipting

Sydney Action Items

• removing deprecated fields

• clean up Receipting object fields

• Explore use of Chatter and Notifications

• Review unneeded flows from SmartBatch 2.0 upgrade

• Business processes from use of Pledge Write Off Utility

• Parent Account use

• Efficient Page Layouts in Batch and Batch item

• payment number field

• report on gift pledge for amount pledge or rollup fields

• Activate consolidated gift entry type

• anonymity pick list

• any new business process resulting from receiving changes and pledge write off utility

Release 25

• SmartBatch 2.0

  • ability to add custom fields to entry screen

  • Data from custom field is then transferred to Transaction (no flows needed)

• Defect Fixes

  • contact Utilities : toggle triggers component error

  • Receiving utility date fixed to work with Australian timezone

Release 26

• SmartBatcth 2.0

  • Added entry types (Crypto, Venmo, etc.) And different layouts depending on entry type

• Initial amount pledge - calculated A time of gift processing, not change with write offs, etc., can be manually edited

• I can't name updating with disease utility

• Alternate channels - A dress did not update in alternate channels when city was changed

• Contact utilities - Error when creating new account (When you Sir creating is different than who created account)

• Gave recognition credits

  • Add transactions to existing gift produces correct G R C

  • Changing accounts on batch item did not properly change G R C

  • GRC rows no longer duplicate on soft credit

  • 3rd party pay off and third party payment are now both checked on soft credit

• Lockdown the new field Initial Amount Pledge to only GA as other users shouldn’t be able to mock around with this snapshot value

Zendesk

is it possible for all of USD to see all of USYD’s ticket in zendesk

• request if possible to configure zendesk so that everyone from USYD can see USYD raised tickets

Do Not Receipt tick box

• doesn’t live in Gift Pledge

• modify batch approval report to bring in the do not receive from the pledge if payment against a pledge

https://sydneyuni.atlassian.net/browse/tapss-360

Decimal Discrepancies

• decimal discrepancies raise as bug via zendesk ticket
• Ana Simic recreate the gift with decimal discrepancies in UAT

totals in gift pledge

• what is difference between pledge balance and Balance Due → they are the same so we can get rid of one of them

• why in the sample data below we have different values on Pledged Amount from the pledge vs the soft credit. → there is issue in those fields

• 

giving summaries

• we are keen to understand

• We didn't use it before. It was because the field that we can summarize before was very limited at the time, but then within your release that we had we had just had. You can already include custom fields in the summary.

• that we might be able to use it for things like on multi contact households being able to have a summary for each of the contacts.

• if we have designed custom stuff. and there is native functionality within IQ, that does the same thing. Wouldn't we consider moving that over

• the amount of giving per contact during a financial year. So one July to 30 June.

• Priscila Tello-Vela to share some best practices on giving summaries and how we can leverage on this feature
• USYD to share scenarios what we would use giving summaries for
• Priscila Tello-Vela create a summary definition that is looking at tax recognition credit accross all contacts in account, to see their total tax year giving. Also, confirm if summary definition can be run on custom objects, and how to configure