My Default List provides gift entry operators with the flexibility to create a set of defaults that can be re-used with any gift batch. Whereas the batch control defaults page allows you to create a set of defaults for use with the transactions in that batch, this page allows you to create and save a set of defaults, which includes a much larger range of values that can be set as defaults. Once a set of defaults is established it can be applied to a batch via the Load Defaults drop-down on Batch Defaults.
An unlimited number of defaults can be created in order to fit the needs of each user. Default rows are tied directly to each user in order to provide each user with an appropriately configured user-experience. Public default rows can also be created in order to provide all gift entry operators with access to standard default rows for use at your institution.
Once defaults are established via this page they can be applied to batches entered through the classic gift and pledge entry forms as well as the streamlined gift and pledge entry form.
To view the My Default List page:
On the Main Menu, click 'Go To' to display the Go To Application.
Click the Gift Batch List Application (Application ID 3010).
Click 'Go'.
When the Gift Batch List appears, scroll through the list and click the ellipses button to view the details.
Click My Default List on the page tree.
My Default List Header Fields:
Default Name |
This is the name of the default. This name can be alphabetical, numerical or a combination of the two. Required |
Description |
This is the description of the default. |
Public |
This check box indicates whether the default is public. Public defaults can be viewed and used by all users. |
Active |
This check box indicates whether the default is active. When a default is no longer needed, the recommendation is to un-check this box and make it inactive, as opposed to deleting the default. |
Copy This Default |
This check box allows you to make a copy of an existing default row, which can be helpful if you have default records that use many of the same defaults. To copy an existing default row:
|
Common Gift & Pledge Defaults:
Gift |
When this check box is checked, transactions in the batch will be marked as gifts, by default. |
Pledge |
When this check box is checked, transactions in the batch will be marked as gifts, by default. |
Transaction Type |
This is the transaction type that will be used as the default for transactions in this batch. Values in this drop-down are validated against tms_transaction_type. |
Pledge Type |
This is the pledge type that will be used as the default for pledges in this batch. Values in this drop-down are validated against tms_pledge_type. |
Tender Type |
This is the code for the medium of exchange for gift transactions in this batch. Sample tender types include Securities, Gift-in-Kin and Life Insurance. Values in this drop-down are validated against tms_payment_type. |
Appeal |
This is the appeal that yielded the gift transactions in this batch. Press F2 while in this field to perform an Appeal Lookup, or type the name of the Appeal. Values entered in this field are validated against the Appeal Header database table. Membership Appeals whose “can be applied to Giving transactions” check box is checked on the Membership Appeal Header form can also be entered here. |
Campaign |
This is the code for the campaign to which transactions in this batch will be credited. Values in this drop-down are validated against tms_campaign. |
Allocation |
This is the number or mnemonic that indicates the allocation to which transactions in this batch should be credited. When a value is entered in this field, the Allocation label will become a hyperlink to the allocation overview for the entered Allocation. This field is context sensitive and you may perform an Allocation Lookup by pressing F2 while in this field. |
Amount |
This is the hard credit amount for each transaction in this batch. For example, if there are several $25.00 pledges to be entered, setting this default to $25.00 will save typing it in each time. If a transaction is encountered for other than $25.00, you can override the amount in that transaction. For transactions with a non-blank Foreign Type, the value in this field will be the default Foreign Amount. |
Reunion |
This is the code for the reunion group for which transactions in this batch will be associated. Values in this drop-down are validated against tms_reunion_camp. |
Acknowledgment |
This is the code for the acknowledgment to which transactions in this batch will be associated. Values in this drop-down are validated against tms_ack. |
Special Handling |
This code indicates what, if any, special handling applies to transactions in this batch. Values in this drop-down list are validated against tms_special_handling table. |
Reference |
This text in this field indicates where (outside of Advance) additional information regarding transactions in the batch can be found. |
Reference 2 |
This text in this field indicates where (outside of Advance) additional information regarding transactions in the batch can be found. |
Source |
The code indicates the default source of information, where information on transactions in this batch originated. Values in this drop-down are validated against tms_gift_src_info. |
Rec Project |
This code indicates the default physical recognition project to which transactions in the batch will be credited. Values in this drop-down are validated against tms_prp_project. |
Anonymous |
This code indicates the level of anonymity requested by the donors being credited for the transactions in the batch. It is important to note the code entered here is simply a tag that flags the item with special notation. This code alone will not suppress the donor’s name or amount, as the code description implies. In order to truly enter an “Anonymous” gift, an institution could, for example, create an entity, without any real data, with the name of “Anonymous001” and associate that user with the transaction. This will ensure the real entity name never displays on reports or anything else attached to the gift. Whether a hard-copy record of the true identity of the donor is kept by the institution in a filing cabinet or other, is at the discretion of the institution. Values in this drop-down are validated against tms_anonymous. |
LM |
This code identifies whether the transaction should be transmitted to the FAS, based on a specific ledger month code. This may be of particular importance to institutions or organizations whose accounting revolves on a ledger month, which may not be synonymous with a calendar month. Values in this drop-down are validated against tms_ledger_month. |
Reporting |
This code describes whether the financial transaction should be included in monthly gift reporting. Values in this drop-down are validated against tms_reporting. |
Transmit |
This code indicates whether the financial transaction should be transmitted to the financial accounting system (FAS). Values in this drop-down are validated against tms_transmit_to_acctg. |
Comment |
This text field can be used to store comments about the transactions in the batch. |
Gift Defaults:
Auto Claim Received |
This check box should be checked if you wish to automatically generate claims for transactions in this batch. The alternative would be not to auto generate claims for transactions in the batch and individually create a claim for each transaction via the claims form. This field is used in conjunction with system option 67, which allows each institution to select a value to be used as a default for the claim form received. If system option 67 is set to 'N', the value of 'N' will be defaulted into the 'claim form received' field n the Batch Control form whenever a batch is created. If system option 67 is set to 'Y', the value of 'Y' will be defaulted into the 'claim form received' field on the Batch Control form whenever a batch is created. Note: if system option 67 = 'Y', system option 68 (auto-update match claim amount) should also be set to 'Y', otherwise you could have claims created when the Form Received is 'Y', but the claim amount is zero. |
Cashier |
This is the identifying tag for the cashier for this batch. Values in this drop-down are validated against the Cashier Tag database table. |
Check # |
This is the check number of the check being processed in this batch, used for matching gift entry. |
CC Type |
This is the type of credit card used to make a payment on the electronic fund transfer transactions in the batch. Values in this drop-down are validated against tms_credit_card. |
Charity |
This is the charity code to which transactions in the batch will be credit. Values in this drop-down are validated against the charity database table. |
Sponsor Amt |
This is the sponsor amount that will be applied to transactions in the batch. The sponsor amount can be used to indicate, for example, the amount received in exchange for material benefit to the contributor (i.e., marketing exposure at an event) for which the contributor is not entitled to receive an income tax receipt. |
Pledge Defaults:
Binding |
This check box indicates whether the pledges in the batch will be binding by default, or whether they can be revoked. |
Recordable |
This check box indicates whether the pledges in the batch will be recordable by default. |
Frequency |
This is the code for the payment cycle for each pledge transaction in the batch. Values in this drop-down are validated against tms_payment_frequency. |
# Years /# Months |
Depending on the Payment Frequency selected, this field indicates the number of years or months to which the payment frequency will apply. # Years will display when you select a Payment Frequency of Annual (A), Quarterly (Q) or Semi-annual (S). # Months will display when you select a Payment Frequency of Monthly (M). |
Pledge Status |
This field indicates the default status of the pledges in te batch. Values in this drop-down are validated against tms_pledge_status. |
Discount |
This is the discounted amount for the pledge transactions in the batch. |
Address |
This is the default preferred address type to which pledge reminders in the batch will be sent. Values in this drop-down are validated against tms_address_type. |
Associated Donor Defaults:
Class |
This is the four-digit class year to be used as a default for transactions in this batch. If there is a preferred class year in the database for the entity being credited with the transaction, the entity's class year will take precedence over this default. |
School |
This is the code for the school associated with the transactions in this batch. Values in this drop-down are validated against tms_school. As transactions are entered into this batch, if there is a preferred school for the entity being credited with the transaction, the school code associated with the entity will take precedence over this default. |
Allocation Division |
This is the division within the allocation to which the transactions in the batch will be applied. Values in this drop-down are validated against tms_alloc_division. |
Program |
This is the code for the program that will be credited with transactions in this batch. Values in this drop-down are validated against tms_program. |
Purpose |
This is the code for the purpose that will be credited with transactions in this batch. Values in this drop-down are validated against tms_purpose. |
Allocation School |
This is the school within the allocation to which the transactions in the batch will be applied. Values in this drop-down are validated against tms_alloc_school. |
Allocation Department |
This is the department within the allocation to which the transactions in the batch will be applied. Values in this drop-down are validated against tms_alloc_division. |
Premium Defaults:
Premium |
This is the premium to which the transactions in the batch will be applied. Values in this drop-down are validated against tms_premium. |
Amount |
This is the value of the premium for tax reporting purposes. |
Declined |
This check box indicates whether the donor has declined or refused the premium and that there is no deduction from the full value of the original gift for tax reporting purposes. |
Comment |
This text field can be used to store comments about the premiums in the batch. |
Giving Codes Defaults:
Type |
This is the type of giving code for the transactions in the batch. Values in this drop-down are validated against the giving_code_types database table. |
Code |
This is the giving code cycle for each premium in the batch. Values in this drop-down are validated against the giving_codes database table. |
Amount |
This is the amount of the giving codes in the batch. |
ID |
This is the ID of the entity to which the premiums in the batch will apply. |
Name |
This is the name of the entity to which the premiums in the batch will apply. |
Text |
This text field contains additional information about the giving codes in the batch. |
Comment |
This text field contains comments about the giving codes in the batch. |