In Agentforce Nonprofit Fundraising, several fields on the Gift Commitment and Gift Transaction objects are calculated automatically. Administrators and users do not enter values into these fields directly. This article explains what each calculated field represents when it is updated, and what logic determines its value.
It covers the calculated fields on two objects:
Gift Commitment, which represents a donor's pledge or recurring giving arrangement.
Gift Transaction, which represents an individual gift payment made toward a commitment or as a one-time gift.
The article groups the fields into three sections based on how they are updated:
Gift Commitment fields updated in real time when a gift transaction is saved.
Gift Commitment fields updated nightly by the commitment processing job.
Gift Transaction calculated fields.
The following Nonprofit Gift Commitment fields are recalculated automatically whenever a related Gift Transaction is inserted, updated, deleted, or undeleted. The recalculation happens in the same save operation as the transaction change, so the Gift Commitment always reflects the current state of its transactions without waiting for a nightly process.
For these four fields, the calculation only runs on a transaction update if one of these transaction fields changes: Status, Current Amount, Transaction Date, Refunded Amount, or Gift Commitment. For transaction inserts, deletes, and undeletes, the calculation always runs.
In multi-currency orgs, transaction amounts are converted to the Gift Commitment's currency before being summed.
Object: Gift Commitment
Field API Name: TotalPaidTransactionAmount
Field Label: Total Paid Transaction Amount
How and when it is calculated: This field is the sum of the Current Amount of every Gift Transaction on the commitment whose Status is Paid. It is updated in real time whenever a Gift Transaction on the commitment is inserted, updated, deleted, or undeleted. Transactions with a Status other than Paid (such as Unpaid, Pending, Written-Off, or Fully Refunded) are excluded. Because Current Amount already accounts for refunds, partially-refunded transactions contribute their net amount after refunds.
Object: Gift Commitment
Field API Name: WrittenOffAmount
Field Label: Written Off Amount
How and when it is calculated: This field is the sum of the Current Amount of every Gift Transaction on the commitment whose Status is Written-Off. It is updated in real time whenever a Gift Transaction on the commitment is inserted, updated, deleted, or undeleted. Only transactions with Status set to Written-Off contribute to this total.
Object: Gift Commitment
Field API Name: TransactionPaymentCount
Field Label: Transaction Payment Count
How and when it is calculated: This field is the count of Gift Transactions on the commitment whose Status is Paid. It is updated in real time whenever a Gift Transaction on the commitment is inserted, updated, deleted, or undeleted. Transactions with any other status, including Written-Off and Fully Refunded, are not counted. Partially-refunded transactions remain in Paid status and are counted.
Object: Gift Commitment
Field API Name: LastPaidTransactionDate
Field Label: Last Paid Transaction Date
How and when it is calculated: This field is the most recent Transaction Date among all Gift Transactions on the commitment whose Status is Paid. It is updated in real time whenever a Gift Transaction on the commitment is inserted, updated, deleted, or undeleted. If no paid transactions exist, the field is empty.
The following Nonprofit Gift Commitment fields are projected revenue fields. They represent the expected total revenue for a commitment across specific time periods. These values are recalculated during the scheduled commitment processing job that organizations run, which is typically scheduled to run daily.
The projected revenue calculation combines two sources for each commitment:
Scheduled installments from the commitment's active schedules that fall within the current year or next year.
Existing Gift Transactions in the database with a Status of Paid, Unpaid, or Pending that fall within the current year or later.
Scheduled installments that already have a matching transaction in the database are excluded to avoid double-counting. The dates used for period bucketing come from the Transaction Due Date of each transaction or installment, not the Transaction Date. In multi-currency orgs, amounts are converted to the Gift Commitment's currency before being summed.
Because these are projected values, they include future expected revenue, not only revenue already collected.
Object: Gift Commitment
Field API Name: TotalCurrentMonth
Field Label: Total Current Month
How and when it is calculated: This field is the projected total revenue for the commitment for the current calendar month. It sums the Current Amount of all combined scheduled installments and eligible transactions whose Transaction Due Date falls in the current month of the current year. The field is recalculated during each nightly commitment processing job run.
Object: Gift Commitment
Field API Name: TotalCurrentQuarter
Field Label: Total Current Quarter
How and when it is calculated: This field is the projected total revenue for the commitment for the current calendar quarter. It sums the Current Amount of all combined scheduled installments and eligible transactions whose Transaction Due Date falls in the current quarter of the current year. Quarters follow the standard ISO calendar quarters (January to March, April to June, July to September, October to December). The field is recalculated during each nightly commitment processing job run.
Object: Gift Commitment
Field API Name: TotalCurrentYear
Field Label: Total Current Year
How and when it is calculated: This field is the projected total revenue for the commitment for the current calendar year. It sums the Current Amount of all combined scheduled installments and eligible transactions whose Transaction Due Date falls anywhere in the current year. The field is recalculated during each nightly commitment processing job run.
Object: Gift Commitment
Field API Name: TotalNextYear
Field Label: Total Next Year
How and when it is calculated: This field is the projected total revenue for the commitment for the next calendar year. It sums the Current Amount of all combined scheduled installments and eligible transactions whose Transaction Due Date falls anywhere in the next year. The field is recalculated during each nightly commitment processing job run.
The following Gift Transaction fields are calculated from other fields on the same transaction. They are evaluated at the time the record is read or saved. Administrators do not enter values into these fields.
Object: Gift Transaction
Field API Name: CurrentAmount
Field Label: Current Amount
How and when it is calculated: This field is calculated as Original Amount minus Refunded Amount. It represents the net amount of the gift transaction that the organization has retained after refunds. Because Original Amount already includes any donor cover amount and excludes transaction fees, Current Amount also reflects these choices. When a transaction has no refunds, Current Amount equals Original Amount. The value updates automatically whenever Original Amount or Refunded Amount changes.
Object: Gift Transaction
Field API Name: RefundedAmount
Field Label: Refunded Amount
How and when it is calculated: This field is the sum of the Amount of every Gift Refund record associated with the transaction whose Status is Completed. It is updated automatically whenever a Gift Refund is inserted, updated, deleted, or undeleted. Refunds with any status other than Completed are ignored. If the resulting Refunded Amount equals the Original Amount, the transaction's Status is automatically set to Fully Refunded. If the transaction was previously Fully Refunded but the Refunded Amount no longer equals the Original Amount, the Status is automatically reset to Paid.
Object: Gift Transaction
Field API Name: IsPaid
Field Label: Paid
How and when it is calculated: This field is set to true when the transaction's Status is Paid and false for any other status. It is an automatically calculated value, evaluated in real time based on the current Status of the transaction. A transaction that has been partially refunded but remains in Paid status returns true.
Object: Gift Transaction
Field API Name: IsWrittenOff
Field Label: Written Off
How and when it is calculated: This field is set to true when the transaction's Status is Written-Off and false for any other status. It is an automatically calculated value, evaluated in real time based on the current Status of the transaction.
Object: Gift Transaction
Field API Name: IsFullyRefunded
Field Label: Fully Refunded
How and when it is calculated: This field is set to true when the transaction's Status is Fully Refunded and false for any other status. It is an automatically calculated value, evaluated in real time based on the current Status of the transaction. A transaction reaches Fully Refunded status automatically when its Refunded Amount equals its Original Amount.
Object: Gift Transaction
Field API Name: IsPartiallyRefunded
Field Label: Partially Refunded
How and when it is calculated: This field is set to true when the transaction's Status is Paid and its Refunded Amount is greater than zero. It is an automatically calculated value, evaluated in real time based on the current Status and Refunded Amount of the transaction. A transaction that is not Paid, or a Paid transaction with no refunds, returns false.
005321800

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.