More information

Gift Transactions, Allocations, Amounts, and Linked Secondary Tables

Millennium users within a single institution have vastly differing needs when it comes to viewing or using the constituents' giving information from the data base. Those responsible for data entry, acknowledgment and financial accounting must be able to deal with the extremely detailed factors surrounding a donation. The fund raising officer may be less concerned with those aspects, but need a broader profile of a constituent's giving pattern or participation. Millennium provides for these and several other perspectives on giving information. This topic includes a description of the data that is maintained in a Gift Transaction, and the use of Giving Allocations.

Note: Millennium system administrators or the database administrator can configure audit logging for the Giving data table. For more information, see Audit Log.

Gift Transactions and Allocations

This discussion is intended to give you a more complete understanding of what is happening behind the scenes to manage all of the Giving data that makes up a Transaction, whether it has single or multiple Allocations. While this information is not strictly necessary in order to successfully view, create or edit Giving data, it may be helpful to your understanding to envision the entire process.

For purposes of our investigation, we will use the following example. A constituent sends a donation of $1000 and specifies that $600 should be earmarked for the library and that $400 should go to research. From a fundraising perspective, and as far as the constituent is concerned, this is one gift of $1000. From the Business Office's perspective, there are two allocations of funds to two separate accounts. These Allocations will have many details in common, such as the dates, the tender, the currency, the check number, the deposit number, the batch in which they were processed, and so on. However, there will be two different Account Numbers.

To handle this situation, Millennium provides for the automatic creation of two separate rows in the Gift data table, one for each of the Allocations. The first row to be created is considered the primary row, or Allocation. The fields within these two Gift rows can be described as being in these general groups.

There is some data that is common to all of the Allocations that make up the Transaction, which you will manually enter once, using the Insert or Insert via Default form. That data will automatically be copied and will therefore be identical in all Allocations that make up the Transaction. This includes the following fields, only:
- Type
- Effective Date
- Process Date
- Batch Number
- Check Number
- Currency
- ABA Number
- Solicitation
- Code
- Deposit
- Number
- Tender
- Anonymous
- Secure
- Source
- Conditional?
- Bank Account
- Bank Account Type
There are system-generated fields, which may be the same or different from Allocation to Allocation, in accordance with what the field is for.

For example...

In order for the system to track the linkage between the rows for each Allocation and integrate them correctly in the display, the giftkey field of the master row is copied into the giftallkey for all of the Allocation rows. (Thus, if the giftallkey is equal to the row's own giftkey, then it is the primary, or master, Transaction and there may or may not be additional linked Transactions representing additional Allocations. If the giftallkey is equal to the giftkey field from a different row, then the Transaction is a secondary Allocation, linked to the Transaction identified by the data found in the giftallkey field.)

This set of fields may be displayed if your institution has a reason to do so, but they are not available for use in data entry situations. In the Field Descriptions below, these fields are identified by the expression '(system field)' at the end of the description.
Any of the data fields in the table that do not fit into one of the two categories above, (common data, or system fields) may be edited to be variable by Allocation. Though not limited to this list, the following are those that are most typically used as variables from Allocation to Allocation:
- Purpose (giftrest) Once you identify the purpose (an entry in the Chart of Accounts lookup table), the system will then assign values to the other Account fields in the gift table based on the values in the equivalent fields in the Chart of Accounts. The Account fields are:
  - Account Name (giftacctnm)
  - Account # (giftacctno)
  - CAE Use (giftacctcf)
  - Account ID number (giftacctid)
  - Notify? (giftacctnt)
  - Department (giftacdprt)
  - Division (giftacctdv)
  - Account Goal (giftacctgl)
  - Account Group (giftacctgp)
- Campaign
- Campaign Year
- Classification 1
- Classification 2
- The Amount fields are:
  - Amount/Balance (giftamt)
  - Deductible Amount (giftdeduct)
  - Asset Amount (giftasset)
  - Net Present Value Amount (giftnetpv)
- Comment
- Custom Fields

When you create a new Transaction, you begin by entering all of the data for the primary Allocation. This includes data from both Category 1 (common data) and Category 3 (variable data) as described above. Thus, both kinds of data are shown on a single, Main insert form.

If you are creating a single Allocation Transaction one primary data row is created using the data as entered on the Main insert form.

If you are creating a multiple Allocation Transaction, check the Multiple Allocation? check box on the Main insert form. On Insert, the primary data row (the Primary Allocation) is created, and the system will automatically present a new insert form which you will use to create the next Allocation. Unlike the Main insert form, this Allocation insert form will contain fields from Category 3 (variable) only. Those data fields will default to the data that you entered for the primary Allocation in the Main insert form, but you may edit any or all of them before inserting the next Allocation row. When you click on Insert the system will create the secondary Allocation data row, using the data from this Allocation form, plus the common data as entered for the primary Allocation on the Main insert form, plus the system-generated data, to create the secondary Allocation data row.

Your institution may make modifications to the definition of either the main or the secondary Allocation insert forms to include or exclude data fields or to alter the placement of any of the data in accordance with your institution's needs and in accordance with the Categories of data described above.

For more information on the process of creating multiple Allocations, see the Allocation Data Maintenance topic.

For more information about modifying the Main or secondary Allocation insert forms, see the Custom Display Designer topic.

When Transaction information is displayed in Long, Short or Detail Mode, the display will consist of two areas. The display begins with a main, or primary Transaction display, which consists of the data that is common to all Allocations and the associated Edit button, followed by a short separator bar. Below that separator is the Allocation data. Note that even if the Transaction consists of but a single Allocation, this display convention is followed. If there are additional Allocations that make up the same Transaction, they will be shown following the primary Allocation data, with separator bars between each Allocation. When displayed in Long or Short Mode, a longer separator bar is shown between different Transactions. For more complete information on the way in which Transactions are formatted for display, see the topic, Giving Display.

To simplify our example, a situation was described wherein two Allocations (and therefore two data rows) were created, based solely on the Account Numbers that were specified. In actuality, you may create any number of linked Allocations for the same Transaction, based on the Account Number and/or any of the other data fields from the variable set of Allocation data fields listed above.

Linked Secondary Tables

Each Transaction row may have many attached rows from secondary (or other primary tables behaving as secondary tables) to provide places to store the complete details of a Transaction. The following chart shows the data tables which may be attached to a Transaction row, their intended use, and the behavior that triggers its creation at the time that the original Transaction is created.

Entries in the following linked tables can also be created after the original Transaction has been created.

Correspondence	Shows information concerning the acknowledgment of the Transaction. When used in this way, the row of information is stored with the primary Correspondence table but displayed with the Transaction row.	Triggered by the selection of a Correspondence Name in the original Transaction Insert form. May also be added to an existing transaction via the context menu item, Transactions - Add Correspondence, or Add Correspondence via Default.
Credit Card	Supplies additional confidentiality for the information about the Credit Card number or Bank Account number when a Tender Type of credit card ('cc') or bank draft ('bank') is used	Triggered by entering a Tender of Credit Card or Bank Draft in the original Transaction. May also be added by changing the Tender on an existing transaction to Credit Card or to Bank Draft. If the Tender of the existing transaction is Credit Card, another Credit Card row can be added to an existing transaction via the context menu item, Transactions - Add Credit Card. If the Tender of the existing transaction is Bank Draft, another Bank Draft can be added to an existing transaction via the context menu item, Transactions - Add Bank Draft.
Gift in Kind	Provides further details about a Transaction that is tendered as a gift of time, expertise, company products, real property, etc.	Triggered by entering a Tender of Gift in Kind in the original Transaction. May also be added by changing the Tender on an existing transaction to Gift in Kind. If the Tender of the existing transaction is Gift in Kind, another Gift in Kind can be added to an existing transaction via the context menu item, Transactions - Add Gift in Kind.
Honoree	Gives additional information about non- constituent honorees.	Trigger by clicking the Non-constituentHonoree check box in the Insert form for the original Transaction. May also be added to an existing transaction via the context menu item, Transactions - Add Honor for Non-Constituent.
Payments	Details the expected schedule for the receipt of the payments associated with a Pledge Transaction.	Triggered by entering a Transaction Type of Pledge, Match Pledge, or Expectancy in the original Transaction. With Pledges, and with Match Pledges, if the Display Matching Payment Schedule System Option is set to Yes, you will be prompted to enter details for the creation of a set of Payment rows linked to the Pledge. These act as a schedule for the fulfillment of the Pledge or Match Pledge. Expectancies,and Match Pledges, if the Display Matching Payment Schedule System Option is set to No, trigger the automatic creation of a single, non-billable entry without a due date in the linked Payment table. Payment rows may be added or edited via the Payment Schedule form. This form is accessed via the Payment Schedule icon or via the context menu item, Transactions - Payment Schedule.
Quid Pro Quo	Stores information about any Quid Pro Quo items and their value, that may be associated with the Transaction.	Triggered by clicking to activate the Quid Pro Quo check box in the Insert form for the original Transaction. May also be added to an existing transaction via the context menu item, Transactions - Add Quid Pro Quo Item.
Receipts	Supplies details on the receipt that was delivered to the constituent in response to the transaction.	Triggered by clicking to activate the Receipt check box in the Insert form for the original Transaction. (This function is not yet available.)
Securities	Offers a location to store additional information when the gift is tendered as Securities.	Triggered by entering a Tender of Securities in the original Transaction. May also be added by changing the Tender on an existing transaction to Securities. If the Tender of the existing transaction is Securities, another Gift in Kind can be added to an existing transaction via the context menu item, Transactions - Add Securities.
Serial Receipts	Details about the transaction's serialized tax receipt.	Available only for sites who utilize Serialized Tax Receipting. A Manual Receipt is triggered by clicking to activate the Add Manual Receipt check box on the Insert form for the original Transaction. A Manual Receipt can be added to an existing transaction by using the Edit button menu item, Add Manual Receipt. Serialized Tax Receipts can be generated for one or more existing transactions by using the Issue New Receipts Tax Receipting Process. Access this Process by using Millennium Explorer, Tools>Tax Receipting>New.
Solicitor	Maintains information about the constituent who acted as the solicitor for the transaction.	Triggered by clicking to activate either the Default or OtherSolicitor check box in the Insert form for the original Transaction. May also be added to an existing transaction via the context menu item Transactions - Add Solicitor.
Sustainer Payments	Holds the details of the amount and the month in which each sustainer payment is expected.	Triggered by entering a Transaction Type of Sustainer Pledge with an amount of $0 in the original Transaction. (With Sustainer Pledges, you will be prompted to enter details for the creation of a set of Sustainer Payments rows linked to the Pledge. These act as a schedule for the anticipated months in which payments are expected from the constituent.) Sustainer Payment rows may be added or edited via the Sustainer Payment Schedule form. This form is accessed via the Payment Schedule icon or via the context menu item, Transactions - Payment Schedule.

Transaction Types

Each Millennium Transaction row must be given a Type so that appropriate accounting is possible. Valid Types are contained in the Gift Type lookup table, which should not be modified. Certain types trigger special functions and are recognized by Millennium. For example, a Pledge transaction type will prompt you for a billing schedule or allow payments to be posted. When an Expectancy is paid, the system automatically creates a transaction with a type of Bequest.

When viewing the list of Gift Types, you should be aware that most of the types shown are system-generated, rather than manually entered during data entry. That is to say that when performing data entry, an operator may use the lookup table list box to choose from: Gift, Pledge, Sustainer Pledge, Pledge Potential, Credit, Expectancy,and Bequest, when creating a new Gift Transaction. All other Types are assigned to a Gift Transaction by the system, when you use the prescribed procedures to create those Transactions. Those procedures are necessary, in order to establish the appropriate linkage for certain Gift Transaction rows.

The transaction types are organized in groups of three: the transaction type, the journal of that transaction type, and the void of that transaction type. These three variations of each type provide an audit trail in case you need to make adjustments to the original transaction. Rather than simply deleting a Transaction in that case, Millennium allows you to adhere to the more appropriate bookkeeping practice of journaling the original.

When a particular transaction type is journaled, a separate journal transaction is created, having a negative dollar amount field equal to the amount in the original row. In addition, the system automatically revises the original transaction type to a void transaction.

The following table provides a complete listing of the valid transaction types. Those that are denoted with an asterisk may be used in the Input Transaction form used to create a new Transaction row. All others are system-generated.

Transaction Type	Code	Description}
Gift Transaction * Gift or Gift Journal Gift or Gift Void	g gj gv	Denotes a basic dues transaction in which money is transmitted in a straightforward manner.
Pledge Transaction * Pledge Journal Pledge Void	p pj pv	Indicates a pledge or promise to give. The pledge is recorded as outstanding until payments are posted.
Pledge Payment Trans. Payment Journal Payment Void	y yj yv	Indicates a payment against a pledge transaction. This type is generated by the system through a special edit procedure and should not be entered manually.
Credit Transaction * Credit Journal Credit Void	c cj cv	Used to give credit to a constituent for a contribution even though no "real" money is received.
Honor Transaction* Honor Journal Honor Void	h hj hv	Indicates that a transaction has been made in honor or memory of this constituent. When linked to another transaction, this type is generated by the system and should not be entered manually. Independent Honor transactions may be entered manually.
Expectancy Transaction * Expectancy Journal Expectancy Void	e ej ev	Denotes that a constituent has made a provision in their estate plans to make a bequest. In essence, it is a pledge of a bequest.
Bequest Transaction * Bequest Journal Bequest Void	b bj bv	Records a bequest in which dues income is received from the estate of a deceased individual.
Match Credit Trans. Match Credit Journal Match Credit Void	a aj av	Automatically generated on the corporate or foundation row in the following situation. One constituent gives a gift that is matched and therefore a match pledge is generated for the matching corporation or foundation. In addition, the original constituent's gift is also credited to another constituent or made in honor of another constituent. In this case, an additional transaction is generated for the corporation or foundation with a Type of match credit and linked to the second party's credit or in-honor transaction. This type is generated by the system and should not be entered manually.
Match Pledge Trans Match Pledge Journal Match Pledge Void	mp mj mv	Denotes a pledge by a corporation or foundation to match a donation made by another constituent. A matching gift form is the documentation for this transaction. This type is generated by the system and should not be entered manually.
Match Potential Trans. Match Potential Jour. Match Potential Void	o oj ov	Indicates there is a potential for a pledge by a corporation or foundation to match a donation made by another constituent. The company is known to match gifts; however, a matching gift form has not yet been received. This type is generated by the system and should not be entered manually.
Sustainer Pledge Transaction* Sustainer Pledge Journal Sustainer Pledge Void	sp sj sv	Describes a promise by the constituent to make recurring payments of a specified amount, on a specified schedule, for an unspecified time duration. Thus, the total amount of the pledge is unspecified.
Pledge Credit Trans. Pledge Credit Journal Pledge Credit Void	r rj rv	Automatically generated on a spouse or other row to denote a credit transaction when the initial constituent has made a pledge and you have checked the Spouse or Other boxes under Credit in the Input dialog box. This type is generated by the system and should not be entered manually.
Pledge Potential Transaction* Pledge Potential Journal Pledge Potential Void	t tj tv	Denotes an expectation that the constituent will make a pledge to the institution, but has not yet formalized that pledge. (It is recommended that such transactions be tracked as conditional pledges, but the pledge potential transaction type may also be used for this situation.)
Write-Off Transaction	w	Denotes the portion of a Pledge Transaction that is unpaid but that the institution no longer expects to receive. This type is generated by the system and should not be entered manually.
Cumulative Transaction Cumulative Journal Cumulative Void	z zj zv	Indicates a cumulative entry for transactions. Generally used only during conversions or initial data load to indicate a total of transactions for a particular period.

Amount Fields

The Transaction table includes many fields that are used to hold various dollar amounts that you may want to associate with the Transaction row. These include: gifttotal, giftamount, giftamtplg, giftdeduct, giftnonded, gifttdeduc, gifttnonde, giftasset, giftnetpv, giftmctotl, giftmdtotl, giftmptotl.

Some of these fields are optional, and some are automatically system-generated, as noted. Your institution may not need or want to make use of all of the options described here. They are available for those who do.

Total

The Total field (gifttotal) in a Transaction row holds the sum of the Amounts from all the Allocations that are linked together and displayed as one Transaction, PLUS the Allocation Total Amount from any Transaction that is Joint with this Transaction, PLUS the sum of the Pledge Amounts from any Matching Pledge or Match Credit Transactions that are linked to the original Transaction, PLUS the sum of any Credit Transactions (for the same constituent) that are linked to this Transaction.

Amount/Balance

The primary Amount field (giftamount) in a Transaction row holds the dollar amount of the Allocation. If the Transaction is a Pledge, the field is labeled, Balance and the amount is shown in red in the display. As payments are made to the pledge, the dollar amount of this field is reduced. A non-displaying field (giftalloc) will hold the sum of the Amounts of all Allocations that are linked together with the current Transaction.

Amount Pledged

When the Transaction has a Type of Pledge, Expectancy, or Match Pledge, a non-displaying field (giftorigpl) will automatically hold the amount that was originally pledged. Unlike the Amount/Balance field which holds the amount that remains to be paid on the pledge, this amount is fixed and does not alter when payments are made against the Pledge or when write offs are applied. It shows the sum of the allocations that make up the transaction.

Deductible Amount

To satisfy tax agency requirements, you will need to track the portion of a Transaction that may be considered deductible by the constituent. For instance, if an umbrella worth $10 is sent to the constituent as a result of a gift of $150, then only $140 of the gift is deductible for tax purposes. The Deductible Amount (giftdeduct) field is designed to hold that amount. At the same time, a non-displaying field (giftnonded) holds the amount that is nondeductible. Additional non-displaying fields (gifttdeduc and gifttnonde) hold the total deductible and total non-deductible amounts from all of the Allocations that are linked to the current Transaction.

The preferred technique for tracking deductible and nondeductible amounts is through the use of the Quid Pro Quo row. When a Quid Pro Quo (QPQ) row is linked to a Transaction, the Deductible Amount is automatically reduced by the value of the QPQ item that is identified. This will result in a negative deductible (giftdeduct) amount and a zero non-deductible (giftnonded) amount on the gift types of 'p', 'e', 'mp', 'o', 't', 'sp', 'a', 'r', and 'c'.

In addition, it is possible to flag a Chart of Accounts entry using the 80% Rule field for an automatic Deductible rate of twenty percent. When such an Account Number is identified in an Allocation, the Deductible Amount is automatically calculated to be eighty percent of the Amount that you entered for that Transaction, unless you decline the automatic calculation.

If the Transaction has any Transaction Type other than Gift, Pledge Payment, or Bequest, the Deductible Amount will default to zero. Meaning that all other transactions of 'p', 'e', 'mp', 'o', 't', 'sp', 'a', 'r', and 'c' will have a zero deductible amount (giftdeduct) and a zero non-deductible (giftnonded) amount. If the Transaction Type is Gift, Pledge Payment, or Bequest, and if the Allocation does not use an Account Number that is flagged as described above, and if you do not enter a dollar amount in this field, the system will automatically assign it the same value as the Amount field. The Value amount of any attached Quid Pro Quo rows will be subtracted from that amount.

Pledges, Pledge Payments and Serial Receipts

If your site is utilizing Serialized Tax Receipting then special considerations apply.

When calculating the amounts for a pledge payment tax receipt, the deductible and non-deductible amounts on the pledge transaction are used.
Pledge payments should never have a non-deductible amount.
Set any non-deductible amount on the pledge transaction. For example, link a Quid Pro Quo row to the pledge, not to its payments.
Before a serialized tax receipt can be created for a payment on a pledge, the total of all payments on that pledge must exceed the pledge's non-deductible amount.

Important! These special considerations apply only if your site utilizes Serialized Tax Receipting.

See the Serial Receipts topic for complete information about Serialized Tax Receipting.

Asset Amount

The Asset Amount field (giftasset) is used in connection with the conditional/unconditional designation for pledge transactions. This field is automatically generated by the system based on the information you specify for an Allocation. In addition, a non-displaying field (gifttasset) contains the sum of the Asset amounts from all Allocations that are linked to the current Transaction.

According to FASB (Financial Accounting Standards Board) standards, the dollar amount of a pledge transaction may only be counted as an asset if that pledge is unconditional. (See the topic, Conditional/Unconditional Pledges. If it is unconditional, the asset amount is attached to the original pledge transaction and the subsequent payment transactions have an asset value of 0 (since you have already counted the full pledge amount as the asset value).

If the pledge is conditional, then the asset amount of the original pledge is 0. Each of the subsequent payments has an asset value equal to the amount of that payment.

See the chart showing the Asset and Net Present Value default rules which follows the description of the Net Present Value Amount in this topic.

Net Present Value

The Council for the Advancement and Support of Education has a reporting requirement that is of importance to educational institutions. If you do not report to CASE, this is not a requirement for you but it may be of use.

The Net Present Value field (giftnetpv) is important when calculating the amount of money your institution will have, when you will have it, and what it will be worth when you receive it!

If you leave this field blank during data entry, the system will automatically assign it a value in accordance with the Amount that is was entered (giftamount) and the Transaction Type. See the chart shown below for the possible variations. If you plan to use this feature and enter your own data, you must use a formula to calculate the Net Present Value based on variables such as expected rate of return and the term. These formulas should be available in financial accounting software or from the planned giving officer at your institution. You should then enter or edit the NPV field for the transaction, based on your calculations. In addition, a non-displaying field (gifttnetpv) will contain the sum of all giftnetpv fields in Allocation rows that are linked together as a single Transaction.

To explain the use of the Net Present Value amount field, we'll use the following example.

If a constituent today makes a pledge of $100,000 per year over the next five years, it is likely that the value of the payment made five years later will be something other than $100,000 due to inflation. While this transaction must be considered a $500,000 gift from the fund raiser's point of view for Acknowledgment purposes, the financial planners for the institution must use a different amount when calculating and projecting the available purchasing power of this resource in the future.

Asset and Net Present Value Default Values

The chart below shows the system's rules for the default Asset Amount and Net Present Value Amounts for various transaction types.

If the Transaction Type is:	Then the giftasset or the giftnetpv will default to be equal to:
g - Gift	giftamount
p - Pledge (conditional)	0
p - Pledge (unconditional)	giftamount (The giftasset amount is fixed. It does not change as the giftamount reduces when payments are made against the Pledge)
y - Pledge Payment (against conditional pledge)	giftamount (The operator can override this amount as the Pledge Payment is created.)
y - Pledge Payment (against unconditional pledge)	0 (If the amount of this Payment causes an overpayment of the original pledge, the amount of the overpayment is added to the giftasset field of the Pledge Payment Transaction.)
c - Credit (against an unconditional pledge)	0
h - Honor	0
e - Expectancy	Asset = 0; NPV = giftamount
b - Bequest (either independent, or posted against an Expectancy)	Asset = giftamount; NPV = 0
a - Match Credit	0
mp - Match Pledge (conditional)	Asset = 0; NPV = giftamount
o - Match Potential	Asset = 0; NPV = giftamount
w - Write Off (on conditional Pledge)	0
w - Write Off (on unconditional Pledge, Match Pledge, or Expectancy)	- giftamount
sp - Sustainer Pledge	Asset = 0; NPV = giftamount
t - Pledge Potential	Asset = 0; NPV = giftamount

Match Amounts

To enhance performance and to facilitate certain functions within the Reporting World, some non-displaying amount fields are present in the Giving data rows to track various amounts of matching gift Transactions that are associated with the original Transaction. As a reminder of the matching behaviors, consider the following example.

If John and Mary are spouses, and Mary has an Employment link to a matching gift company, then when John and Mary make a joint donation, a Transaction can be automatically generated for the company with a Type of match pledge, that is linked to Mary's Transaction row. At the same time, another Transaction will be generated for the company with a Type of match credit, that is linked to John's Transaction. Both the match pledge and the match credit Transaction will carry the full amount of the match that will be made. This is true regardless of whether John and Mary's Transactions are jointly owned gifts, or whether one has the full amount as a gift and the other has the same full amount as a credit.

Match Credit Total

The Match Credit Total (giftmctotl) is the sum of the amounts of any Match Credit Transactions that are linked to the current constituent's Transaction. These Transactions would belong to the matching company that is associated with the current constituent's spouse.

Match Due Total

The Match Due Total (giftmdtotl) is the sum of the Amount/Balance of any Match Due Transactions that are linked to the current constituent's Transaction. These Transactions would belong to the matching company with which the current constituent is associated. This amount shows the amount that has been pledged but not yet received by the institution.

Match Paid Total

The Match Paid Total (giftmptotl) is a sum of the Amounts of any Payment Transactions that are have been posted against any Match Due Transactions that are linked to the current constituent's Transaction. These Transactions would belong to the matching company with which the current constituent is associated. This amount shows the amount that has been received toward the match pledge.

Pledge Payment, Credits on the Pledge, and Write-Off Counts and Totals

Pledge payment, credits on the pledge, and write-off counts and totals are calculated by the system for Transactions that have a Type of Pledge, Expectancy, Sustainer Pledge, Match Pledge, Pledge Potential or Pledge Credit. These counts and totals are maintained by the system in the gifts data table. On multi-allocation Pledge transactions, the totals and counts will be calculated per allocation. When a user sets his or her Show/Hide Payments giving display option to Hide, these counts and totals will display with the Allocation.

If your display is set to Short or Long mode, the details of each and every payment, on-behalf-of pledge payment (a payment that was made by another constituent to pay down this pledge), sustainer pledge, expectancy or match pledge, and write-off transaction that links to a pledge, sustainer pledge, expectancy or a match pledge can be shown in the giving data display, or they can be 'collapsed' and displayed as a single line of totals. These totals will be grouped into payments (payments include both pledge payments and bequests), on-behalf-of pledge payments (credits), and write-offs, and include the count and total dollar amount for each type of linked transaction.

For example, three $25 payments, 2 $10 soft credits, and a write-off are posted to a $200 single allocation pledge. These transactions will display in a single line as:

3 Payment(s) for $75.00

2 Credit(s) for $20.00

1 Write-off(s) for -$110.00

If your display is set to Mini mode and if the Group Linked Transactions together in Mini-Display user option is checked, you may choose to either show each payment, credit, and write-off transaction that links to a pledge, sustainer pledge, or match pledge, or choose to hide them altogether. The single line of totals will not be shown in Mini display mode.

If you are viewing a sustainer pledge, pledge, expectancy or match pledge transaction in Detail Display, the linked payments, soft credits and write-off transactions will show regardless of the Show Payments/Hide Payments option that you have selected.

To change the payment display, point to the section header Edit button, or point to the Edit button to the left of any pledge transaction with payments. The menu includes a toggle item that allows you to switch between Show Payments and Hide Payments. If payments are currently displayed, this item will be labeled Hide Payments. If the payments are currently collapsed (or hidden if the display mode is set to Mini), this item will be labeled Show Payments. Click this menu item to switch the display from Show to Hide or from Hide to Show.

Pledge Payments Total

The Pledge Payments Total (giftttlpay) is the sum of the amounts of the payments and bequests that are linked to the Transaction through the gift pledge key (giftplgkey). The sum will increase when a payment or bequest is made, and it will decrease when a previously made payment or bequest is journaled. Transactions that link to the payments or bequests, such as honors, memorials, or credits, will not be included in the total.

Pledge Payments Count

The Pledge Payments Count (giftcntpay) is a count of the payments and bequests that are linked to the Transaction through the gift pledge key (giftplgkey). The count will increase when a payment or bequest is made, and it will decrease when a previously made payment or bequest is journaled. Transactions that link to the payments or bequests, such as honors, memorials, or credits, will not be included in the count.

Credits on the Pledge Total

The Credits on the Pledge total (giftttlcrd) is the sum of the amounts of on-behalf of pledge payments and credit transactions (both have a Type of 'c') that are linked to the Transaction through the gift pledge key (giftplgkey). This sum will increase when a credit is linked to the pledge, and it will decrease when a previously linked credit is journaled. Transactions that link to the credits, such as honors, memorials, or other credits, will not be included in the total.

Credits on the Pledge Count

The Credits on the Pledge count (giftcntcrd) is a count of on-behalf of pledge payments and credit transactions that are linked to the Transaction through the gift pledge key (giftplgkey). The count will increase when a credit is linked to the Transaction, and it will decrease when a previously linked credit is journaled. Transactions that link to the credits, such as honors, memorials, or other credits, will not be included in the count.

Pledge Write-off Total

The Pledge Write-off Total (giftttlwrt) is the sum of the amounts of the Transaction's write-offs. This sum will increase when the Transaction is written-off, and it will decrease when a previous write-off is journaled.

Pledge Write-off Count

The Pledge Write-off Count (giftcntwrt) is a count of the payments and bequests that are linked to the Transaction through the gift pledge key (giftplgkey). The count will increase when the Transaction is written off, and it will decrease when a previous write-off is journaled.

Conditional/Unconditional Pledges

In order to satisfy the standards of the Financial Accounting Standards Board (FASB), pledges must be differentiated as being unconditional, or conditional. In general, an unconditional pledge is binding, and a conditional pledge is a promise to give IF a certain set of circumstances occur and is not legally binding.

It is up to your institution to make a reasonable policy decision on how to define and treat each kind of pledge transaction. It will be vitally important to your auditors that you are consistent in your application of that policy.

Millennium allows you to designate each pledge transaction as either Conditional or Unconditional by use of a check box in the Pledge Information dialog screen at the time that the transaction is created. After a transaction has been entered, you may not edit this designation as a number of the amount fields have already been calculated based on this information. Therefore, careful consideration must be given to this designation at the time that the transaction is entered. Conditional pledges should be entered with a Comment that describes the condition under which the pledge will be fulfilled.

The designation of Conditional or Unconditional for a Pledge transaction has an impact on the calculation of the Asset Amount field.

Unspecified pledges (transactions with a Type of Pledge and an amount of $0) and sustainer pledges are automatically created as conditional transactions.

Match Pledges are automatically created as conditional transactions.

Expectancies are automatically created as conditional transactions.

Pledge Potentials

In addition to unconditional, and conditional pledges, some institutions choose to use the Transaction Type, pledge potential to describe a verbal or an undocumented promise by the constituent that a pledge will be made. Many institutions track such transactions as conditional pledges and do not use the Pledge Potential transaction type. If that is the case at your site, you may edit the Gift Type or Dues Type lookup table entries Pledge Potential (t), Pledge Potential Journal (tj), and Pledge Potential Void (tv), to mark them inactive for data entry.

In general, a pledge potential is not legally binding. They are automatically set to be conditional and therefore have no asset, net present value, nor any deductible value.

You may enter a payment against a Pledge Potential transaction, and you may also update a Pledge Potential to become a conditional Pledge by using the context menu item, Transactions/Make Potential a Pledge.

Giving Campaigns

Most institutions organize their fund raising efforts into various 'campaigns' in order to effectively and efficiently target and manage a variety of fund raising methodologies. Each of the institution's campaigns should be reflected as an entry in the Campaign lookup table within Millennium. The entries in that table may be used in several places within Millennium, including the Giving data tables. One of the fields in the Giving table is used for that purpose, and data may be placed into that field either by the user or by the system. The following 'rules' describe the process by which the system will attempt to fill in that field.

If the user enters a Campaign in the Transaction Insert form during data entry, that Campaign is used for the transaction. No further investigation is performed.
If no Campaign is chosen in the data entry form, the system next checks the Solicitation that was chosen in the Insert form and locates that entry in the Solicitation lookup table. It first checks the Default? flag (the field named sol_mand) for that Solicitation entry. If that is Y, it continues looking at that Solicitation lookup entry and finds the Campaign (sol_mand) and automatically copies it into the Gift or Dues Campaign field in the transaction that is being created. If either of those conditions is not met (this would include a situation in which the Solicitation is blank in the original Insert form or the Campaign is blank in the lookup entry), then go to step three.
If steps 1. and 2. have failed to identify a Campaign, then the system will check the Account that was chosen in the Insert form for the transaction and locate that entry in the Chart of Accounts lookup table. First it checks the Default? flag (chart_mand) for that Account lookup entry and if it is Y, it will continue and look for the Campaign (chart_camp) that is identified with that entry. If both of those conditions are met, the Campaign is automatically entered in the Gift or Dues transaction that is being created. If either of these conditions is not met (this would include a situation in which the Account is blank in the Insert form or the Campaign is blank in the lookup entry), then the Campaign is left blank in the transaction.
If none of the steps above result in the identification of a Campaign for the Transaction, the field is left blank.

Gift Batch and Ledger

Your institution may have a set of procedures for processing transactions in batches for accounting purposes. If so, then each transaction will be assigned to a particular batch with a distinct batch number, and that designation is tracked in Millennium via the Batch Number (giftbatch) field. The batch numbers themselves must be registered in Millennium via the specialized lookup table for that purpose, gift_batch_number, accessed via the Batch Control . In that lookup table, batches are designated as 'open' or 'closed'. If it is open, then the number is available for use when creating or editing giving transactions. In addition, transactions that have been assigned to open batches are also available for editing.

When a batch number is closed (via Batch Control), the system automatically flags all transactions that were assigned to that batch by setting the giftbclose field equal to 'Y'. When that occurs, the system restricts the fields that may be edited within the transaction, in order to preserve the accounting integrity of the batch.

In addition, some institutions track whether and when a transaction has been entered in an accounting ledger system. That information is tracked in Millennium in the non-displaying fields, giftlgrflg and giftldgrdt. These two fields can be added, via the Custom Display Designer, to the Giving Data Display forms, but will not display on Giving Data Maintenance (Insert or Update) forms; these two fields are maintained through the 'back end' of the database.

When the giftlgrflg field is set equal to 'Y', the same editing restrictions are imposed on the transaction as occurs with a closed batch number.

Click here for the list of gift columns that can not be edited if either the Batch Close (giftbclose) or Ledge (giftlgrflg) flags are set to 'Y'.

Column	Column Name in Database	Column	Column Name in Database
Process Date	giftprocdt	Type***	gifttype***
Batch Number	giftbatch	Effective Date	gifteffdat
Campaign	giftcamp	Tender	gifttender
Solicitation	giftsolic	Campaign Year	giftcampyr
Account Goal	giftacctgl	Account Number	giftacctno
Account Division	giftacctdv	Account CAE	giftacctcf
Currency	giftcurr	Asset Amount	giftasset
Net Present Value	giftnetpv	Deductible Amount	giftdeduct
Check Number	giftchckno	Foreign Amount	giftfrnamt
Restriction (Account)	giftrest	ABA	giftaba
Deposit	giftdepost	Constituent Type	giftconst
Conditional	giftrevoke	Bank Account	giftbnkact
Bank Account Type	giftbnkaty	Account Group	giftacctgp
Exchange Rate	giftexrate	Allocation Amount	giftalloc
*** except when changing a match potential to a match pledge

Giving Field Descriptions

Giving Data is stored in the gifts data table. The following fields are included. The field labels and non-displaying designations that are listed here are those that the system uses by default. If you want to override these default settings, you must customize your display definition.

Note: Custom fields are included in the data table, and are available for any purpose that you want to define. These fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms.

Field Name Field Label	Lookup Table	Type Length [Default] {Check}	Description
giftkey non-displaying	none	numeric/number 13,0	The primary key field for all rows in all tables. This field holds a permanent "time stamp" of the precise time and date the row was created. This uniquely identifies a row within the table. This is automatically entered by the system. (system field)
giftid non-displaying	none	char 10	This field holds the ID number of the constituent who owns this row, providing a link between this row and all others in all other tables which also belong to the same constituent. This is automatically entered by the system. (system field)
giftdoc non-displaying	none	char 1 ['N']	This field holds a Y/N flag to indicate the existence of a linked document for this row. (system field)
giftdate no label	none	datetime/date [getdate()]	The date that this Transaction row was last updated. This field is automatically entered by the system. (system field)
giftuserid no label	none	varchar/varchar2 30 [suser_sname()]	The User ID of the operator that last edited this Transaction row. It is automatically entered by the system. (system field)
giftugroup non-displaying	none	char 1 ['Z']	This field holds the Group letter that was associated with the User ID of the operator who last edited this row. (system field)
giftprocdt Process Date	none	datetime/date [getdate()]	The date the transaction is actually processed. This date should be used for internal reconciliation with the business office or accounting reports.
gifteffdat Effective Date	none	datetime/date [getdate()]	The effective date for this transaction. Usually indicates the date the donor wants to receive credit for the transaction or the date you want to assign for fundraising accounting. This may be a date other than the actual date of processing.
gifttrnum Transaction #	none	numeric/number 10,0	A sequential number assigned by the system, used to track transactions. Each user may be assigned a starting number that will be used for this field, if that user creates new transaction rows. That starting number assignment is made in the userlist. When the transaction number is examined in combination with the log on ID of the user who created the row, each transaction in the database can be uniquely identified. This is automatically entered by the system. If a Giving Transaction has multiple, linked Allocations, each will be assigned it's own Transaction #. (system field)
giftbatch Batch #	Gift Batch Number	char 10 [' ']	This field provides a grouping method to associate a 'batch' of transactions that are being processed together. If the Batch is 'closed', editing restrictions are enforced for this transaction. When the transaction is displayed, the label Open or Closed appears in red to the right of the display of the Batch Number
gifttender Tender	Tender	char 6 [' ']	Indicates the way in which a transaction was contributed (for example, cash, check, bank draft, credit card, securities, personal property, real property). Certain tender types trigger additional input forms, so that attached secondary rows may be created. These types are Securities, Credit Card, Bank Draft, and Gift in Kind.
giftcamp Campaign	Campaigns	char 6 [' ']	The fundraising Campaign within the institution that generated this gift. If this field is left blank during data entry, the system will attempt to fill it in, using the Campaign from the Solicitation lookup table entry (as identified by giftsolic) or if not available, the Campaign from the Chart of Accounts entry (as identified by giftrest). For more information, see Giving Campaigns.
giftcampyr Year	none	char 4	The year of the Campaign that generated this gift. This is a four-digit year between 1600 and 2200. Note that some of the standard EIS statistical information uses this field to determine the year of a transaction, and therefore leaving this field blank will have an impact on those statistics.
giftsolic Solicitation	Solicitations	char 6 [' ']	The particular Solicitation effort (usually within a Campaign) that generated this gift.
giftacctno Account Number	Chart of Accounts	char 30	During data entry, the text box labeled Purpose will accept either the Name, Account #, or Code from an entry in the Chart of Accounts lookup table. When a valid choice has been made, several fields from that lookup table row are copied to fields in the Transaction row. This field (giftacctno) holds a copy of the Account Number from the chosen lookup entry. This is automatically entered by the system.
giftacctid Department ID	Chart of Accounts	char 10	During data entry, the text box labeled Purpose will accept either the Name, Account #, or Code from an entry in the Chart of Accounts lookup table. When a valid choice has been made, several fields from that lookup table row are copied to fields in the Transaction row. This field (giftacctid) holds a copy of the Department ID from the chosen lookup entry. This is automatically entered by the system. (system field)
giftacctnt Notify?	Chart of Accounts	char 1 ['N']	During data entry, the text box labeled Purpose will accept either the Name, Account #, or Code from an entry in the Account Numbers lookup table. When a valid choice has been made, several fields from that row are copied to fields in the Transaction row. This field (giftacctnt) holds a copy of the Notify field from the chosen lookup entry. This is automatically entered by the system. (system field)
giftacctgl Goal	Chart of Accounts	char 6 [' ']	During data entry, the text box labeled Purpose will accept either the Name, Account #, or Code from an entry in the Account Numbers lookup table. When a valid choice has been made, several fields from that row are copied to fields in the Transaction row. This field (giftacctgl) holds a copy of the Goal from the chosen lookup entry. This is automatically entered by the system. (system field)
giftacctcf CAE	Chart of Accounts	char 1	During data entry, the text box labeled Purpose will accept either the Name, Account #, or Code from an entry in the Account Numbers lookup table. When a valid choice has been made, several fields from that row are copied to fields in the Transaction row. This field (giftacctcf) holds a copy of the CAE field from the chosen lookup entry. This is automatically entered by the system. (system field)
giftacctdv Division	Chart of Accounts	char 6 [' ']	During data entry, the text box labeled Purpose will accept either the Name, Account #, or Code from an entry in the Account Numbers lookup table. When a valid choice has been made, several fields from that row are copied to fields in the Transaction row. This field (giftacctdv) holds a copy of the Division name from the chosen lookup entry. This is automatically entered by the system. (system field)
giftamount Amount/Balance	none	money/number (19,4)/(16,2) [0]	The amount of the transaction (the amount of the single allocation represented in this row). If the row has a transaction type of Pledge, Expectancy, Match Pledge, or Match Potential, this field will be labeled Balance and it will represent the amount of the promised money that has not yet been received by the institution. For those Transaction Types, entering a Pledge Payment automatically decrements this field.
giftamtplg non-displaying	none	money/number (19,4)/(16,2) [0]	This system-generated field is equal to the original amount of the pledge (p, mp, e, o, t, r, or c - if c represents a pledge credit) transaction, regardless of any payments that have been made against it. If the transaction is joint, this is the individual constituent's share of the transaction, not the full amount. If the transaction has multiple allocations, this is the amount of the pledge for the specific allocation defined by this data row only. Also see giftorigpl. (system field)
giftasset non-displaying	none	money/number (19,4)/(16,2) [0]	The Asset value of the allocation. This field is available to track the Asset value of a gift, in accordance with FASB standards. Each allocation may have its own Asset amount, as assigned and shown within the Allocation Maintenance form.
giftcurr Currency	Currency	char 6 [' ']	The form of currency in which the gift was delivered.
giftanon Anonymous?	none	char 1 [N]	This field contains a flag for those transactions that are to be treated as anonymous gift in published reports. Note that the presence of this flag does not automatically suppress the identity of the donor in reporting or data viewing situations. It does facilitate that suppression in a reporting situation by acting as an easy way to identify such donors.
giftpotflg non-displaying	none	char 1 ['N']	This field is not active at the present time. (system field)
gifthnrmkr non-displaying	none	char 1	When constituent A makes a gift in honor of constituent B or a non-constituent C, the Transaction Type field for A's Transaction is gift (or whatever is appropriate for the donation) and the Transaction Type field for B's Transaction is honor. The gifthnrmkr field for B's transaction will be either 'H' if the honoree is living or 'M' if the honoree is deceased. This field in constituent A's Transaction will be blank. In addition, when constituent D makes a donation on behalf of constituent E, this field in both E's credit Transaction and in D's transaction will be set to 'B'. In the above situations, if constituent A or D's transaction is joint with constituent F, the gifthnrmkr for F is blank. This field is automatically filled by the system when the honoree is a constituent. (system field)
gifthnrkey non-displaying	none	numeric/number 13,0 [0]	If this row represents a donation that the constituent made in honor of others, this field will hold a count of the number of Honor transactions that are linked to this row. If this row represents a donation that someone else made in honor of this constituent, then this field will hold a copy of the key field from the donor's transaction. (system field)
giftjntid non-displaying	none	char 10	When a Transaction is designated as 'Joint' with another constituent (either spouse or other), a copy of the ID number of the second constituent is held in this field. When viewed in the standard Long or Short display, the name of the constituent is shown in the phrase, 'Joint with <constituent's name>.' (system field)
giftjntkey non-displaying	none	numeric/number 13,0 [0]	If this row represents a donation that is joint between two constituents (spouses or others) this field signals that fact to the system. This field in the row belonging to the first constituent is automatically set equal to '1' (primary). In the row belonging to the second constituent, this field will hold a copy of the key field from the first constituent's Transaction row. (system field)
giftjntamt non-displaying	none	money/number (19,4)/(16,2) [0]	If the Transaction represents part of a donation that is jointly held, this field holds the full amount (the sum of the joints) for all allocations. (system field)
giftjntrat non-displaying	none	numeric/number 4,3 [1]	This field is reserved for future use by Millennium. (system field)
giftmtchid non-displaying	none	char 10	If this row represents a donation that is a matching transaction made in response to another constituent's donation, this field will hold a copy of the ID number of the constituent who made the original gift. Since a matching transaction can be linked to one and only one original donation, this information may be used in reporting situations. However, if this row represents an original donation that is going to be matched by another constituent, then this field must be treated as system-use only. It will hold the ID number of the constituent who is making the match, if (and only if) that information was entered during the creation of the original transaction. And since a constituent's transaction may have matches from multiple other constituents, this is not a valid source of that information for reporting situations. (system field)
giftmtchky non-displaying	none	numeric/number 13,0 [0]	If this row represents a donation that is matched by other constituents, this field signals that fact to the system. This field in the row belonging to the first constituent is automatically set equal to the number of matching transaction rows there are that are linked to this row. In the rows belonging to the matching constituents, this field will hold a copy of the key field from the first constituent's Transaction row. (system field)
giftdeduct non-displaying	none	money/number (19,4)/(16,2) [0]	The amount of the allocation that is considered deductible by the IRS. If data is not entered in this field, the system will calculate a value based on several factors. See Deductible Amount.
giftnonded non-displaying	none	money/number (19,4)/(16,2) [0]	This field is automatically calculated by the system as the difference between the giftamount and the giftdeduct. (system field)
giftmrcvd non-displaying	none	char 1 [' ']	This field will contain a flag of 'M' if the transaction is a match pledge, a match potential, or a pledge payment toward either of those transaction types, or a credit issued as a result of a match pledge payment being applied to an individual's pledge balance. (system field)
giftplgkey non-displaying	none	numeric/number 13,0 [0]	When a pledge payment is made, the transaction reflecting the payment is linked to the original pledge through this field. This field in the original transaction will hold a count of the linked pledge payment transactions. In the payment transactions, this field will hold a copy of the key field from the original pledge to which it is linked. This goes for multiple allocations as well, see giftallkey. (system field)
giftjnlkey non-displaying	none	numeric/number 13,0 [0]	When an existing transaction is journaled, the system automatically changes the Type field of the original to a Gift Void, Pledge Void, Bequest Void, etc. Simultaneously, the system creates a replica row with a Type of Gift Journal, Pledge Journal, Bequest Journal, etc. This field in each holds a copy of the key field of the other transaction. (system field)
giftstatus non-displaying	none	char 1	For journal transactions, this system-generated field will contain a minus sign. In this situation, the minus sign is displayed with the amount information, allowing the journal transaction to cancel out the void transaction. For sustainer pledge transactions, this system-generated field will be 'N' if all of the linked sustainer payment rows are marked inactive. When set to 'N', the sustainer pledge will no longer be counted in the number of outstanding pledges (pledges with a balance). For all other transaction types, this field is not used. (system field)
giftchckno Check Number	none	char 12	The number of the constituent's check for this transaction.
giftsecure non-displaying	none	char 1 [N]	This field is reserved for future use.
giftlgrflg non-displaying	none	char 1 [N] {N,Y}	This field is used to track whether or not a transaction as been entered into an accounting system. If it has this field will contain a 'Y', and editing restrictions are imposed on the transaction. (system field)
giftldgrdt Ledger	none	datetime/date [getdate()]	If this transaction has been entered into an accounting system, this field may be used to track the ledger posting date. (system field)
giftnhonr non-displaying	none	char 1 [N]	This system-generated field is used to hold a Y/N flag to indicate the existence of a non-constituent honoree row, linked to this transaction. (system field)
giftsource Source	Source	char 6 [' ']	The source for the information in this row.
giftcrdkey non-displaying	none	numeric/number 13,0 [0]	When linked credit transactions are created at the same time that the original gift is created - this field in the original transaction will hold a count of the linked credit transactions. In the credit transactions, this field will hold a copy of the key field from the original transaction to which it is linked. When linked credit transactions are created after the original gift is created (by using the Add Credit for Transaction menu items), the system will behave differently if the original gift is a multiple allocation gift. -- If the original gift is a multiple allocation gift, and the linked credit transaction is a single allocation transaction, then this field in the original gift's primary allocation row will hold a count of the linked credit transactions, and this field in the credit transactions will hold a copy of the original gift's primary allocation key field. This field in the original gift's secondary allocation rows will be 0. -- If the original gift is a multiple allocation gift and the linked credit transactions are multiple allocation credit transactions, then this field in the original gift's primary allocation row will hold a count of the linked credits' primary and secondary allocation rows. This field in the credit transaction primary allocation row will hold a copy of the original gift's primary allocation key field. This field in the original gift's secondary allocation rows will be 0. This field in the credit transactions' secondary allocation rows will be 0. (system field)
giftspmflg non-displaying	none	char 1 [N]	This field contains a flag indicating that the Matching Transaction that is linked to this row is the result of the spouse's association with the matching gift company. (system field)
gifttype Type	Gift Types	char 6 [' ']	Indicates the type of transaction (for example, gift, pledge, pledge payment, credit, match credit, journal entry, bequest, expectancy, etc.)
giftrest Purpose	Chart of Accounts	char 6 [' ']	This field is used to identify an account from the Account Numbers lookup table to which this transaction should be assigned. During data entry, the text box labeled Purpose will accept either the Name, Account #, or Code from an entry in the Account Numbers lookup table. When a valid choice has been made, several fields from that row are copied to fields in the Transaction row. The giftrest field holds a copy of the code from the chosen lookup entry.
giftaba ABA #	none	char 10	This field has been moved to the creditcard table and is no longer used by Millennium.
giftdepost Deposit	none	char 10	The number of the deposit in which this transaction was included.
giftcrdate non-displaying	none	datetime/date [getdate)]	The date that the row was created. (system field)
giftcruser non-displaying	none	varchar/varchar2 30 [suser-name()]	The User ID of the operator who created the row. (system field)
giftconst non-displaying	Constituent Type	char 6 [' ']	The Constituent Type of the constituent at the time that the Transaction row was created. This field is not updated, even if the constituent's Type changes. This preserves the ability to report on giving amounts, based on the Constituent Type at the time of the gift. This is automatically entered by the system. (system field)
giftclass1 Classification 1	Transaction Class	char 6 [' ']	This field is used to further classify a gift transaction for any site specific purpose.
giftclass2 Classification 2	Transaction Class2	char 6 [' ']	This field is used to further classify a gift transaction for any site specific purpose.
giftpoint non-displaying	none	numeric/number 10,0	This system-assigned field is no longer used or supported. (system field)
giftrevoke Conditional?	none	char 1 [N]	This field is used to attach a (Y/N) flag to a pledge transaction to indicate whether it should be considered conditional or unconditional. If giftrevoke = 'Y', then the pledge is considered conditional. If giftrevoke = 'N', then the pledge is considered unconditional.
giftnetpv non-displaying	none	money/number (19,4)/(16,2) [0]	This field is used to track the net present value of this allocation, in accordance with CASE standards. Each allocation may have its own Net Present Value amount, as assigned and shown within the Allocation Maintenance form.
giftfrnamt non-displaying	none	money/number (19,4)/(16,2) [0]	This field is not yet active. (system field)
giftbnkact non-displaying	none	varchar/varchar2 240	This field has been moved to the creditcard table and is no longer used by Millennium. This field is now classified as a system field and is no longer available for data entry or display.
giftbnkaty non-displaying	Bank Account Type	char 6 [' ']	This field has been moved to the creditcard table and is no longer used by Millennium.
giftccflag non-displaying	none	char 1 [N] {'Y' or 'N'}	This field is used to hold a flag (Y/N) to indicate that there is or is not a linked Credit Card row. (system field)
giftquidfl non-displaying	none	char 1 [N] {'Y' or 'N'}	This field is used to hold a flag (Y/N) to indicate that there is or is not a linked Quid Pro Quo row. (system field)
giftsecflg non-displaying	none	char 1 [N] {'Y' or 'N'}	This field is used to hold a flag (Y/N) to indicate that there is or is not a linked Securities row. (system field)
giftgikflg non-displaying	none	char 1 [N] {'Y' or 'N'}	This field is used to hold a flag (Y/N) to indicate that there is or is not a linked Gift in Kind row. (system field)
giftrecflg non-displaying	none	char 1 [N] {'N' or 'Y'}	This field is not available for use at this time. This field is used to hold a flag (Y/N) to indicate that there is or is not a linked Receipts row. (system field)
giftackflg non-displaying	none	char 1 [N] {'N' or 'Y'}	This field is used to hold a flag (Y/N) to indicate that there is or is not a linked Correspondence row. (system field)
giftsolflg non-displaying	none	char 1 [N] {'Y' or 'N'}	This field is used to hold a flag (Y/N) to indicate that there is or is not a linked Solicitor row. (system field)
giftacctgp Account Group	Chart of Accounts	char 6 [' ']	During data entry, the text box labeled Purpose will accept either the Name, Account #, or Code from an entry in the Account Numbers lookup table. When a valid choice has been made, several fields from that row are copied to fields in the Transaction row. This field holds a copy of the Group from the chosen lookup entry. (system field)
giftexrate Exchange Rate	none	numeric/number 6,5 [1]	This field holds a copy of the exchange rate from the Currency lookup row that is identified in the giftcurr field, at the time that this row was created. This data is automatically entered by the system. (system field)
giftsumkey non-displaying	none	numeric/number 13,0 [0]	This field is used to track linked Transactions. This field will hold a copy of the key field from another Transaction to which this one is linked, such as Pledge Payments linked to a Pledge, Credits linked to a Gift, etc. (system field)
giftfnum non-displaying	none	char 2 ['05'] {'05'}	The file (table) number for the Transaction table. (system field)
giftcomm no label	none	varchar/varchar2 4000	A free text Comment that may be entered and displayed with this row only.
giftsec1 non-displaying	none	char 26	This field is reserved for future use. (system field)
giftsec2 non-displaying	none	char 26	This field is reserved for future use. (system field)
giftlnkfil non-displaying	none	char 2	When this Gift Transaction is to be attached to a Planned Gift or Proposal row, this field in the Gift Transaction table is used to store the number of the table to which it is linked. (system field)
giftlnkkey non-displaying	none	numeric/number 13, 0	When this Gift Transaction is to be attached to a Planned Gift or Proposal row, this field is used to store a copy of the key field from the individual row to which it is linked. (system field)
giftplgtyp non-displaying	none	char 6	When a Gift Transaction is created with a Type of pledge, this field in the Gift Transaction table is used (temporarily) by the system to assist in the creation of the attached Payment row(s). Once the Payment row(s) are created, this field is no longer used or updated by the system. Be aware that this information indicates the pattern that was used in the creation the Payment schedule rows, only. Subsequent edits, additions or deletions to the sets Payment rows, such as the number of payments, the intervals, or the starting month or year are NOT reflected in these pledge billing fields, and therefore these fields (giftplgtyp, giftpaycnt, giftpstrty, giftpstrtm, giftpstrtd) are not recommended for report selection purposes. (system field)
giftpaycnt non-displaying	none	numeric/number 3, 0	See description of giftplgtyp. (system field)
giftpstrty non-displaying	none	char 4	See description of giftplgtyp. (system field) This is a four-digit year between 1600 and 2200. Because it is a system field, it should not be used for reporting purposes.
giftpstrtm non-displaying	none	char 2	See description of giftplgtyp. (system field)
giftgiveid non-displaying	none	char 10	This is a system-use only field and should not be used for reporting purposes. It is used during the insertion of the giving data row to signal the system to generate a link to another constituent who is the source of the money for this transaction. (system field)
giftsolid non-displaying	none	char 10	This is a system-use only field and should not be used for reporting purposes. It is used to signal the system to generate a linked solicitor insert form. (system field)
gifthonrid non-displaying	none	char 10	This is a system-use only field and should not be used for reporting purposes. It is used to signal the system to generate a linked honoree insert form. (system field)
giftcredid non-displaying	none	char 10	This is a system-use only field and should not be used for reporting purposes. It is used to signal the system to generate a linked credit insert form. (system field)
giftcorres non-displaying	none	char 6	This is a system-use only field and should not be used for reporting purposes. It is used to signal the system to generate a linked Correspondence insert form. (system field)
giftalloc non-displaying (except as described)	none	money/number (19,4)/(16,2) [0]	This is the total amount for all Allocations that make up this Transaction. (If the Transaction is jointly owned, this is this constituent's share of the total amount for the Transaction.) This is non-displaying unless the Transaction is a Pledge, Match Pledge or Expectancy. If so, this field displays as the Pledged Amount. If such a pledge Transaction is jointly owned, the amount will be doubled in the Pledged Amount display. (system field)
giftmctotl non-displaying	none	money/number (19,4)/(16,2) [0]	This is the total amount of any Match Credit Transactions that are linked to this Allocation. This amount is automatically calculated by the system. (system field)
giftmdtotl non-displaying	none	money/number (19,4)/(16,2) [0]	This field holds the total amount of Matching funds that have been promised but which have yet to be received in response to this Transaction. This amount is automatically calculated by the system. If a transaction has multiple allocations, this amount is also copied to all secondary allocation rows. (system field)
giftmptotl non-displaying	none	money/number (19,4)/(16,2) [0]	This field holds the total amount of Matching funds that have already been paid in response to this Transaction. This amount is automatically calculated by the system. If a transaction has multiple allocations, this data is copied to all secondary allocation rows. (system field)
gifttotal Total	none	money/number (19,4)/(16,2) [0]	This field holds the total amount of all Allocations that are linked together for this Transaction, all Joint Transactions, Matching Pledge Transactions (OR Matching Credit Transactions), and linked Credit Transactions belonging to this constituent. This information is automatically calculated by the system and when a Gift is displayed, this data is shown in blue on the first line of the display. (system field)
gifttpledg non-displaying	none	money/number (19,4)/(16,2) [0]	This is the total pledge balance (unpaid) for all Allocations that are linked together for this transaction. If the transaction is jointly owned, this is the individual constituent's portion. (system field)
gifttasset Asset	none	money/number (19,4)/(16,2) [0]	This is the total asset amount for all Allocations that are linked together in this transaction. If the transaction is jointly owned, the amount displayed is the constituent's joint share. (system field)
gifttdeduc Deductible	none	money/number (19,4)/(16,2) [0] not null	This is the total Deductible amount for all Allocations that are linked together in this transaction. If the transaction is jointly owned, the amount displayed is the constituent's joint share. (system field)
gifttnonde non-displaying	none	money/number (19,4)/(16,2) [0]	This is the total nondeductible amount for all Allocations that are linked to this transaction. (system field)
gifttnetpv Net Present Value	none	money/number (19,4)/(16,2) [0]	This is the total Net Present Value amount for all allocations that are linked together in this transaction. If the transaction is jointly owned, the amount displayed is the constituent's joint share. (system field)
giftopenfl non-displaying	none	char 1 [N]	This is a flag to indicate whether the transaction has linked credit transactions. (system field)
giftallkey non-displaying	none	numeric/number 13,0	This field is used to track and link Transactions that represent separate Allocations that are part of one gift. If this Transaction row represents a subsequent Allocation (NOT the first or only Allocation), then this field will hold a copy of the giftkey from the Transaction row that serves as the 'master'. If this IS the master Transaction, the giftallkey will be set as equal to the giftkey. Payments are linked to each Allocation via the Pledge Key (giftplgkey) and not the Allocation Key (giftallkey). This data is automatically generated by the system. (system field)
giftallflg non-displaying	none	char 1 ['N'] {'Y' or 'N'}	This is a flag which indicates whether or not this transaction is the primary allocation for a set of linked Allocations. (system field)
gift8020 non-displaying	none	char 1 ['N']	This system-generated field is used to track the existence of an automatic 20% Quid Pro Quo row. If this field is 'N' or blank, there is none attached to this row. If this field is 'A', the automatic Quid was Accepted and if it is 'D', the automatic Quid was Declined.
giftacctnm	Chart of Accounts	varchar/varchar2 80	This field holds a copy of the name of the account from the Chart of Accounts that is associated with this transaction.
giftsolnam	Solicitations	varchar/varchar2 65	This field holds a copy of the value from the Solicitation lookup table entry used in this transaction.
giftbclose Closed (if Y)	none	char 1	This is a system-generated field indicating that the Batch Number for this transaction has been closed. When this field has been set equal to 'Y', editing restrictions are imposed on the transaction. (system field)
giftdiscod Discount (with Membership processing only)	Membership Discount	char 6	This field holds a copy of the code from the Membership Discount lookup table entry that is associated with this transaction. This field is only available for data entry during Membership data entry, and then only to users who have set their Membership Processing option to Giving.
giftdiscnt Discount Amount (shown in Membership form only)	Membership Discount	money/number (19,4)/(16,2)	This system-generated field holds a copy of the amount from the Membership Discount lookup table entry that is associated with this transaction. This field is only available in connection with Membership processing, and then only to users who have set their Membership Processing option to Giving.
giftdate1	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdate2	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny1	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny2	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum1	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum2	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftyesno	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row for any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftlook1	gifts_lookup1	char 6	This custom field may be defined and used by your institution to track any lookup table driven information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftlook2	gifts_lookup2	char 6	This custom field may be defined and used by your institution to track any lookup table driven information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftlook3	gifts_lookup3	char 6	This custom field may be defined and used by your institution to track any lookup table driven information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
gifttext	none	varchar/varchar2 255	This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftacdprt Department	Department	char 6 {' '}	This system-generated field holds a copy of the chart_dprt field from the Chart of Accounts entry that is associated with this transaction. (system field)
giftjcrkey non-displaying	none	numeric/number 13, 0	If a transaction is journaled using the automatic Journal and Correct function, this system-generated field maintains the linkage between the transactions for display purposes. If there is no linked, automatic correcting transaction, this field will be = 0. If so, this field in the voided and journaling transaction is = 1. The same is true for secondary allocations linked to primary, now-voided transaction. In the correcting transaction, and any of its secondary allocations, this field is equal to the time key of the original, now-voided primary transaction. If a correcting transaction is, itself, subsequently journaled and automatically corrected, the time key in this field is retained (to preserve the original linkage) and the time key of the first correcting transaction (now-voided) is copied into the newest correcting transaction and any secondary allocations. If a secondary allocation is individually journaled and then corrected, this field is set to 1 in both the void and journal allocation. In the correcting allocation(s) this field is equal to the time key of the now-voided allocation. (system field)
giftorigpl Pledged (for all pledge types of transactions)	none	money/number {null}	If the transaction is a pledge, match pledge, expectancy, or match potential, this field contains the original amount of the pledge - the sum of all allocations that make up the transaction. It is not reduced by the application of pledge payments or write-off transactions. For transactions of other types, this field will be 0. (system field)
giftcontfl non-displaying	none	char 1	This field is reserved for future use. (system field)
giftpstrtd	none	char 2	See description of giftplgtyp. (system field)
giftcrdtyp	credit_types	char 6	This field functions as a secondary gift type so that the Transaction can be further classified in whatever way your institution desires.
giftccfail	none	numeric/number 2,0	Paya Payment Services Failure. This field holds the number of credit card or bank draft payment processing attempts that fail. (system field)
giftdate3	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdate4	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdate5	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdate6	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdate7	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdate8	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdate9	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdte10	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdte11	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftdte12	none	datetime/date	This custom field may be defined and used by your institution to track any date information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny3	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny4	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny5	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny6	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny7	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny8	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny9	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny10	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny11	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftmny12	none	money/number (19,4)/(16,2)	This custom field may be defined and used by your institution to track any monetary information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum3	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum4	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum5	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum6	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum7	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum8	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum9	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum10	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum11	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftnum12	none	numeric/number 10, 0	This custom field may be defined and used by your institution to track any numeric information associated with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk1	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk2	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk3	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk4	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk5	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk6	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk7	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk8	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk9	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftchk10	none	char 1 ['N'] {'N' or 'Y'}	This custom field may be defined and used by your institution to flag this data row fro any purpose. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
gifttxt1	none	varchar/varchar2 255	This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
gifttxt2	none	varchar/varchar2 255	This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
gifttxt3	none	varchar/varchar2 255	This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
gifttxt4	none	varchar/varchar2 255	This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
gifttxt5	none	varchar/varchar2 255	This custom field may be defined and used by your institution to track any free text information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftlook4	gifts_lookup4	char 6	This custom field may be defined and used by your institution to track any lookup table driven information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftlook5	gifts_lookup5	char 6	This custom field may be defined and used by your institution to track any lookup table driven information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following:. When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftlook6	gifts_lookup6	char 6	This custom field may be defined and used by your institution to track any lookup table driven information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftlook7	gifts_lookup7	char 6	This custom field may be defined and used by your institution to track any lookup table driven information you want to associate with this data row. More Custom fields are not shown on the standard Display or standard Data Maintenance forms. If you want to make use of one or more of the custom fields, use the Custom Display Designer to edit the standard Display and Data Maintenance forms. When using the Custom Display Designer to change Giving display or data maintenance forms, it is very important to make note of the following: When updating a custom field for a credit transaction, not only must the Giving-Giving-Main, Giving-Giving-Main Insert, and Giving-Giving-Main Update be customized - the Giving-Giving-Journal/Write-Off/Credit Update - Forms also must be altered to include the custom field. The Journal/Write-Off/Credit Update - Forms is used to update Credit transactions as well as Journal and Write-Off transactions. The same field cannot be displayed both in Giving-Main and in Giving-Allocation, even though the Customizer allows many more fields into the Allocation display.
giftadesrc (non-displaying)	ade_source	char 30	If this row is created or updated from data that originally came from the ecommerce_pending table, then this field will hold information about the data's import source. Data from the Online Constituent Directory will have a source of Online Directory. Data from Soft Edit users will have a source of Soft Edit. Data whose import source is the ADE Import Tool can be assigned a value (other than Online Directory or Soft Edit) from the ade_source lookup table by the user who executes the utility, or the source can be blank.
giftttlpay (non-displaying)	none	money/number (19,4)/(16,2) [0]	This field is only calculated for Transactions that have a type of 'p', 'e', 'sp', 'mp', 't', or 'r'. It is the total amount of all of the payments ('y') and bequests ('b') that are linked to the Transaction through the giftplgkey. The amounts are totaled and display separately for every allocation. It will not include amounts for any transactions that may be linked to the payments or bequests, such as honors and credits. This field is automatically calculated by the system and will display only if the option to Hide Payments is selected. Point to the section header Edit button, or point to the Edit button to the left of any pledge transaction with payments. The menu includes a toggle item that allows you to switch between Show Payments and Hide Payments. If payments are currently displayed, this item will be labeled Hide Payments. If the payments are currently collapsed (or hidden if the display mode is set to Mini), this item will be labeled Show Payments. Click this menu item to switch the display from Show to Hide or from Hide to Show.
giftcntpay (non-displaying)	none	numeric/number 5,0	This field is only calculated for Transactions that have a type of 'p', 'e', 'sp', 'mp', 't', or 'r'. It is the total count of all of the payments ('y') and bequests ('b') that are linked to the Transaction through the giftplgkey. The count is calculated and displays separately for every allocation. It will not include in the count any transactions that may be linked to the payments or bequests, such as honors and credits. This field is automatically calculated by the system and will display only if the option to Hide Payments is selected. Point to the section header Edit button, or point to the Edit button to the left of any pledge transaction with payments. The menu includes a toggle item that allows you to switch between Show Payments and Hide Payments. If payments are currently displayed, this item will be labeled Hide Payments. If the payments are currently collapsed (or hidden if the display mode is set to Mini), this item will be labeled Show Payments. Click this menu item to switch the display from Show to Hide or from Hide to Show.
giftttlcrd (non-displaying)	none	money/number (19,4)/(16,2) [0]	This field is only calculated for Transactions that have a type of 'p', 'e', 'sp', 'mp', 't', or 'r'. It is the total amount of all of the credits ('c') that are linked to the Transaction through the giftplgkey. The amounts are totaled and display separately for every allocation. It will not include amounts for any transactions that may be linked to the credit, such as honors and credits. This field is automatically calculated by the system and will display only if the option to Hide Payments is selected. Point to the section header Edit button, or point to the Edit button to the left of any pledge transaction with payments. The menu includes a toggle item that allows you to switch between Show Payments and Hide Payments. If payments are currently displayed, this item will be labeled Hide Payments. If the payments are currently collapsed (or hidden if the display mode is set to Mini), this item will be labeled Show Payments. Click this menu item to switch the display from Show to Hide or from Hide to Show.
giftcntcrd (non-displaying)	none	numeric/number 5,0	This field is only calculated for Transactions that have a type of 'p', 'e', 'sp', 'mp', 't', or 'r'. It is the total count of all of the credits ('c') that are linked to the Transaction through the giftplgkey. The count is calculated and displays separately for every allocation. It will not include in the count any transactions that may be linked to the credits, such as honors and credits. This field is automatically calculated by the system and will display only if the option to Hide Payments is selected. Point to the section header Edit button, or point to the Edit button to the left of any pledge transaction with payments. The menu includes a toggle item that allows you to switch between Show Payments and Hide Payments. If payments are currently displayed, this item will be labeled Hide Payments. If the payments are currently collapsed (or hidden if the display mode is set to Mini), this item will be labeled Show Payments. Click this menu item to switch the display from Show to Hide or from Hide to Show.
giftttlwrt (non-displaying)	none	money/number (19,4)/(16,2) [0]	This field is only calculated for Transactions that have a type of 'p', 'e', 'sp', 'mp', 't', or 'r'. It is the total amount of all of the write-offs ('w') that are linked to the Transaction through the giftplgkey. The amounts are totaled and display separately for every allocation. This field is automatically calculated by the system and will display only if the option to Hide Payments is selected. Point to the section header Edit button, or point to the Edit button to the left of any pledge transaction with payments. The menu includes a toggle item that allows you to switch between Show Payments and Hide Payments. If payments are currently displayed, this item will be labeled Hide Payments. If the payments are currently collapsed (or hidden if the display mode is set to Mini), this item will be labeled Show Payments. Click this menu item to switch the display from Show to Hide or from Hide to Show.
giftcntwrt (non-displaying)	none	numeric/number 5,0	This field is only calculated for Transactions that have a type of 'p', 'e', 'sp', 'mp', 't', or 'r'. It is the count of all of the write-offs ('w') that are linked to the Transaction through the giftplgkey. The count is calculated and displays separately for every allocation. This field is automatically calculated by the system and will display only if the option to Hide Payments is selected. Point to the section header Edit button, or point to the Edit button to the left of any pledge transaction with payments. The menu includes a toggle item that allows you to switch between Show Payments and Hide Payments. If payments are currently displayed, this item will be labeled Hide Payments. If the payments are currently collapsed (or hidden if the display mode is set to Mini), this item will be labeled Show Payments. Click this menu item to switch the display from Show to Hide or from Hide to Show.
giftisrcpt Issue Serialized Receipt	none	char 1 ['N']	Set this option to indicate this transaction should receive a serialized tax receipt. Possible final values for this field are Y (Yes), N (No), H (Hold), E ( External), D (Done)

Indices - Giving

Index	Primary	Foreign	Unique	Fields	Sort
pk_gifts	Y		Y	giftkey	ASC
gifts02		Y		giftid	ASC
gifts03				gifthnrkey	ASC
gifts04				giftmtchky	ASC
gifts05				giftplgkey	ASC
gifts06				giftsolic	ASC
gifts07				giftjntkey	ASC
gifts08				giftrest	ASC
gifts09				giftprocdt	ASC
gifts10				gifteffdat	ASC
gifts11				giftcrdkey	ASC
gifts12				giftsumkey	ASC
gifts13				gifttrnum giftcruser	ASC
gifts14				giftallkey	ASC
gifts15				giftbatch	ASC
gifts16				giftlnkkey giftlnkfil	ASC
gifts17				giftdate	ASC
gifts18				giftjcrkey	ASC

Top of Page