2023-11-13 AQ Consultation Session 3

wakil pledge

• pledge amount 20m started but overtime reduced

• pledge schedule changed overtime.

• Balance due is correct

• Original Amount Pledge is totally wrong

• soft credit is what’s not correct, balance should match the original gift.

• all write off in the system are us trying to modify the pledge, we have not done an actual write-off

• clarified the original pledge amount and Priscila will be studying how to fix the data and give a write up.

https://sydneyuni.atlassian.net/browse/BI-420

Mackenzie Bequest

• correct pledge amount, the original pledge transaction.

346405 Bequest

• this gift’s got overpayment

• Prior commitment on overpayment row is not ticked as

• balance doesn’t go down as it usually does.

• Priscila will be studying how to fix the data and give a write up.

• we tested overpayment if it should have the prior commitment ticked?

• when we did the conversion did we do all the voids?

• we need to fix migrated data where both members of household were soft credited when only one should be. This is because in advance soft credit is at contact level while in AQ it is at account level

•  

soft credit voids but does not add back when adding the transaction back to the same gift number

Procedure:

• void payment

• modify gift

• add back payment

for bequest, as they are fully paid, we cant use pledge correction

we have a request to AQ for pledge correction to support paid pledges.

in advance we are able to do it in one batch, but in Jarvis we have to do them for multiple batches which flicks back and forth as we have approval process for each batch.

Priscila will ask their internal team

https://sydneyuni.atlassian.net/browse/TAPSS-336

AQ upgrade Data fix

third party payment issue fixed in v22.

@Monica Kluegel reckons this need to be fixed before end of year. But @Yeng Sembrano notes that gift is going up not down so she isn’t too worried about it.

AQ did provided scripts to fix data and we ran them where ever possible but there is not guarantee that they worked 100% as there wasn’t a post update data validation. I did some quick check but I noticed there were still some that seem to have not been fixed and they could be because they were very old and/or converted data(i.e. GRC on soft credit).

@Monica Kluegel suggests that offline we put together a concerted plan to fix the data. and maybe run it by with Priscila

https://sydneyuni.atlassian.net/browse/TAPSS-1014

using pledge correction batch where there is third party payment

Covering Accounts

migration straightforward one, but we still have the more complex ones pending to be migrated. because soft credit is on account and in advance we have only on contact being soft credited, in Jarvis, both contacts in the same household will then get the soft credit. we don’t know how to manage that.

GRC on Soft Credit is now existing in v24. However we have some concerns about adjusting the GRC on a soft credit.

you cant set the GRC on smartbatch, you can set at account first and smartbatch take that as default.

we want to control people from ticking the “Related Account Receive Soft Credit”, lock this to GA.

there are some issues in adjusting GRC on soft credit, it was fixed in v26, we can test it - we can show it next session.

where we are up to on the soft credits, what we have migrated?

https://sydneyuni.atlassian.net/browse/TAPSS-1014

https://sydneyuni.atlassian.net/browse/TAPSS-331