TAPSS- 2302

Jira Legacy
server System Jira serverId e9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a key TAPSS-2302

AQ 26: Smart Batch 2.0 Field & Report Types Configuration

Verify that the following new items are added to Batch item object

Object - Batch Item (AQB__Batch_Item__c)

• New Fields

  • Initial Amount Pledged

    • AQB__InitialAmountPledged__c

    • Currency(10, 2)

    • This is the Initial Amount of the Pledge. Voids, write-offs and adding additional transactions to this gift do not change this value.  It is calculated at the time of Batch processing from the total of the Amounts on the Batch Item Transactions with a Type of Pledge.  It can be manual edited after processing but is never updated by the software after processing.

TAPSS- 2302

Jira Legacy
server System Jira serverId e9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a key TAPSS-2302

Custom Fields on Batch Item Transactions

Verify tha the following new items are added to Batch item transactions object

Appraiser's Address

to Batch item transactions object

• Appraiser's NameAddress

  • AQB__AppraiserNameAppraiserAddress__c

  • Text(200255)

  • Copied from Batch Item

  • Future use for configurable screens for Personal/Real Property Gifts

• Hash Value

  • AQB__HashValue__c

  • Text(64)

  • Hash Value for Crypto Currency

• Redemption Value

  • AQB__RedemptionValue__c

  • Currency(9, 4)

  • Redemption Value for Crypto Currency

• Type of Coin

  • for configurable screens for Personal/Real Property Gifts

• Appraiser's Name

  • AQB__CoinTypeAppraiserName__c

  • Picklist (Uses Global Value Set Coin Types)

  • Values (can be added, deleted or changed)

  • Bitcoin

  • Ethereum

  • XRP

  • Dogecoin

  Unknown

  Text(200)

  • Copied from Batch Item

  • Future use for configurable screens for Personal/Real Property Gifts

Defect Fixes

TAPSS-2373 -

Source of Data= Modification

Batch Type = Gift/Pledge Correction

Method = Void

Void and Correction.

Void and add correction - Got an error saying “failed to load opportunities” and the screen is stuck on loading. My gift has not saved yet. Also gift date and gift credit date not appearing at smart batch entry level.

1. Error message was not displayed for below "Void Notation" options:

   Check dishonoured

   Entity incorrect

   Allocation account changed

   Suspense batch error fix

   Anonymity status incorrect

   Entity merge connection

   Chargeback

   Proposal update

2.When I selected "Allocation code incorrect" value and all other values in "Void notation" field, an error message is displayed

Below error message must NOT be displayed

TAPSS-2379 :

TAPSS-2387 -

Josh Berg (Affinaquest Help Desk (Advancement RM))

Nov 5, 2024, 9:42 AM EST

Senoah,
 
Thanks for the question.
 
The Method dropdown in SmartBatch 2.0 is hard-coded and does not reach from the field values as they did in SmartBatch 1.0. At this time, values cannot be removed in SmartBatch 2.0. Inactivating values will not remove them from the Method dropdown in SmartBatch 2.0 and it may create problems down the road, particularly if inactive values are selected. 
 
As a rule, we do not recommend changing the Method picklists on any of the objects. You will get the best gift processing results if you use them as provided, which we are constantly evaluating. 
 
Thanks,
Josh

TAPSS-2395 -

1.Create a batch with Smart Batch 2.0 checkbox ticked

2.Check ‘Gift Date’ and ‘Gift Credit Date' checkbox in batch and click ‘Batch Item’ button

TAPSS-2397-

TAPSS-2399 -

Multiple Soft Credits Added at time of Data Entry

Multiple soft credits can now be entered at the time of data entry in Smart Batch 2.0.

After entering a gift, choose  Save and Add Soft Credit

There is no limit to the number of soft credits that can be added.

Soft Credits can also be added after the Batch Item is created by clicking on the C dot

Choose Add Soft Credit to add another Soft Credit

it also gives you the option to add the soft credit even after you have saved the Batch Item

TAPSS - 2400 -

As a GA user, I want to make adjustments to the Batch Proof report so that when I enter batch using smart batch 2.0, I am seeing the information as it was and can distinguish the soft credit vs hard credit.

• When I use Smart Batch 2.0, soft credits are shown and distinguished with their respective information (anonimity of gift, anonimity of soft credit, pledge being paid down and the number of pledge payments)

• When I use Smart Batch 2.0, ‘Date' ‘Amount' ‘Designation’ ‘Designation Number’ columns are added into ‘Batch Item Automated Soft Credits’ table

• when I use Smart Batch 1.0, it is showing as it is. (this is transitionary, once we are fully on board with Smartbatch 2.0, this information can go)

‘Date' ‘Amount' ‘Designation’ ‘Designation Number’ columns must be added into ‘Batch Item Automated Soft Credits’ table

TAPSS-2393 -

We have raised this with John from peoplesoft team. This can be tested once the integrations are up and running successfully

TAPSS-2406 -

Soft Credits - Automated and Manual Entry with Hard Credit Gifts

Soft Credits are now created as Batch Item Transactions regardless of method of entry.  In Smart Batch 1.0, when soft credits were added at the time of entry of hard credit gifts, either manually or with an automation based on an Account relationship, a row was created in the Batch Item Automated Soft Credit object and the Transactions were created on Batch close.

The creation of the Soft Credits as Batch Item Transactions allows for creating soft credits for partial amounts and other edits to the Soft Credit prior to processing.

This ticket is to address whether there are any existing reports that are currently only looking at Batch Item and understand whether there should be updated reports/dashboard to reflect the extended usage of Batch Item Transaction.

Regression

TAPSS-2016-001

Soft credits are created as Batch Item Automated Soft Credits

Batch proof report shows in its separate section with information about the anonimity of the gift as well as the credit, and it also shows the pledge being played.

TAPSS-2304-001

Create a batch with “Gift date” and “Gift credit date” fields checked on the batch

“Gift date” and “Gift credit date” fields must be displayed while adding a batch item

TAPSS-2037-003

AC4

Pledge Soft Credits Written Off when Pledges are Written Off in Contact Utilities

• create pledge from a household account with pledge soft credit to an organization account

  

• decease contact and write off open pledges
  

  

Pledge Soft Credit has been written off

TAPSS-2037-004

AC5

Primary and Secondary Contact checkboxes throw component errors when toggled

• decease a contact

  

This error message do not appear

TAPSS-2037-005

AC6

Receipting Utility Date fields work as expected for orgs in Australian timezone

• find an transaction that is not voided and that has not been receipted and is created before 10am

  

  in backend the creation date is in previous day

  

• Run receitping utility for that date

receipting utility should pick up the transaction as transaction for that day rather than yesterday

Smart Batch 2.0 testing (Complex Scenarios)

TAPSS-2037-006

AC2 (GA process remains the same and unaffected by the upgrade)

Gift from a foundation with soft credit to a multi contact household with 50/50 LC

• create/prepare the household account

  

• Create/prepare the foundation account

  

• create the gift with soft credit

  

gift and soft credit are created

Soft Credit has GRC

Legal credit should be 0

TAPSS-2037-007

Accidentally discovered as having been fixed in v25

Indirect Contact Auto Gift Recognition

• create an indirect relationship with Award Credit set to true

  

• Enter a gift on the Account

• Same scenario for Ord with indirect contact
  

GRC credit awarded without error

for Org with indirect contact GRC

for reference, in v24 it would give this error icon and cannot close the batch

TAPSS-2037-008

AC2 (GA process remains the same and unaffected by the upgrade)

Transferring an Org Gift or an fully paid pledge from holding to a new designation with soft credit to a household account

• create a Pledge with full payment on Org that has been soft credited to a household account whose contact is indirectly linked to the org account with auto award soft credit
  

  

• create the pledge
  

  

Pledge

Soft Credit

As mentioned this scenario resulted to two GRC on the contact

TAPSS-2037-009

AC2 (GA process remains the same and unaffected by the upgrade)

Continuation from previous test

• Pay the pledge
  

  

Pledge is paid

Soft Credit also paid

TAPSS-2037-0010

AC2 (GA process remains the same and unaffected by the upgrade)

Continuation from previous test

• Void and correct the Gift/Pledge, as paid down pledge (or any pledge with payment) does not offer Void Transaction and Add Correction, do a void of the payment first, then can use a Batch Correction to correct an unpaid pledge (note that Void and Add Correction is not available even after payment has been cancelled) then enter the payment again with the new designation.

  

• void payment first

  

• note “Void and add Correction is still not available, so one has to do Batch Correction instead

  

  use Batch Correction instead

  

• add back the payment

  

Payment and Soft Credit Pledge are Voided

After Batch Correction, both Pledge and Soft Credit Pledge are corrected

After entering the new payment on new Designation

TAPSS-2037-0011

AC2 (GA process remains the same and unaffected by the upgrade)

Convert a gift to pledge payment

• Enter a pledge

  

• Enter a payment

  

• convert gift to pledge payment

  

Gift has been voided

payment has been applied to pledge

TAPSS-2037-0012

AC2 (GA process remains the same and unaffected by the upgrade)

ASOP recurring gift payment Batch

Captured 4 cards due next month and a batch was auto created. All batch items are linked to the recurring gift and pledge.

Smart Batch 2.0 testing (Simple Scenarios)

TAPSS-2037-0013

AC2 (GA process remains the same and unaffected by the upgrade)

PeopleSoft Integration, Validation
- set Batch Review Status to Ready for Validation

Batch Should be either Validated Successfully or Not

TAPSS-2037-0014

Establishing a new recurring gift.

1. Create draft payment schedule

   

2. Generate payment schedule which will auto create a BT transaction, recurring gift and pledge batch.

   

3. Close the pledge batch to create the pledge in the donors account.

   

4. Check next due dates on BT transaction and recurring gift align and BT transaction is ready to capture.

   

New recurring continuity pledge has been created and linked to the recurring gift object.

The payment schedule is active and linked to the recurring gift object.

The BT transaction due date and recurring gift due date match.

TAPSS-2037-0015

Auto creation of a credit card batch

1. Authorise transaction via the virtual terminal

   

2. Capture the transaction via the BT Transaction list view.

   

3. Check the auto created batch and batch items.

   

New transaction would authorise successfully.

New transaction would capture successfully.

Batch will auto create with batch item and batch item transaction.

Batch is auto assigned to the user who captured the transaction.

Batch item is linked to the BT transaction that was captured.

TAPSS-2037-0016

Create and modify from holding a 3rd party pledge payment.

1. Pay down a pledge by a 3rd party. E.g. the pledge is in the foundation name but an individual is making the payment.

   

2. Close the batch and the payment will appear as a soft credit row in the pledge.

   

3. Modify the pledge and payments from holding to a new account in 3 modification batches. a) void the 3rd party payment.

   

   b) modify the pledge.

   

   c) re-enter the 3rd party payment.

   

3rd party payment would successfully pay down the instalment on the pledge.

3rd party payment and pledge would successfully transfer to the new designation.

TAPSS-2037-0017

Creating a Bequest budget and make the deceased contact the signator

1. Create a planned gift pledge on the Estate account.

   

2. Save the gift. Go into the batch item and edit the signator to the deceased person.

No longer able to give 0% legal credit and 100% GRC to a deceased contact if they are a direct contact of the Estate but you can make them a signator after saving the batch.

Waiting until we can use the signator relationship type to have a signator appear in smartbatch.

TAPSS-2037-0018

Create a Multi designation pledge and add a payment.

1. Create a batch item with multiple schedules. One schedule for each designation.

   

2. Create a gift batch and make a payment against the pledge with the payment to be split between the designations.

   

Pledge is successfully created with multiple designations.

Pledge is successfully paid down with one payment splitting into the two designations.

TAPSS-2037-0019

Run reports from smartbatch e.g batch approval report, imodules batch proof, credit card batch proof.

1. Batch approval report located on all batches.

   

2. Credit card batch proof report located on credit card batches only,

   

3. Imodules batch report located on imodules batches only

Successfully run all reports from the batch.

TAPSS-2037-0020

Cheque batch - (check custom fields) add cheque details in description field and check that they appear in the corresponding fields in the batch item.

Change cheque dates using the 'Usyd Batch date' option on the batch details screen.

Add a bequest intention task to a cheque gift from the batch item transaction screen.

Check details transfer automatically from the description field into the batch item bank, BSB and drawer fields.

New bequest task is created successfully from the batch item transaction screen.

Batch dates, batch item dates and batch transaction dates are all updated to the date entered into the Usyd Bank date change function.

TAPSS-2037-0021

Receipting

1. Run receipting utility

   

2. Generate and attach receipt via Apsona.

3. Check that the pdf is attached to the receipt object.

4. Check that the email template is correct.

Receipt object is successfully created.

Apsona report generated a reciept, attaches the PDF receipt to the receipt object and emails the donor using the email receipt template.

Sushma Ramachandrappa to successfully test this I will need emails turned on in UAT. I have already raised this as part of MA testing.