Pledge & Gift - Overview
Before we get into the details of how we work with the Pledge & Gift functionality in Tessitura, lets review how 2Account: Donate2 | Stream2 | Flex2 Forms traditionally processed contributions. This is important to understand the difference if you are deciding which route to go or if you are switching from our traditional approach to the Pledge & Gift approach.
Interchangeable Terms
In the context of 2Account Forms, the terms "Donation," "Gift," and "Contribution" are used interchangeably. They all refer to the money a patron gives to an organization.
Traditional Contribution Processing
Traditionally, we create a Ticket Order in Tessitura. As shown below, that Ticket Order has an order number and contribution. This is the same way website orders are processed through the Tessitura API.
When we process transactions using On Account or a Performance & PriceType, we use Ticket Orders.
Pledge & Gift Donation Processing
When Pledge functionality is enabled, we don't create a Tessitura ticket order and we only allow the use of Funds. You cannot use On Account or a Performance & PriceType with Pledge & Gift functionality.
Batch Processing
Traditional Web Order Processing
We use the same batch that is used by your website. The sales channel on the web orders allows you to distinguish web orders and Donate2 orders.
Gift & Pledge Processing
As shown below, we process the contribution directly on the Contributions tab in the constituents record through the Tessitura Contribution Import Utility. You won't find these contributions in an order. It may take a few minutes for the contribution to be processed by the Tessitura Contribution Import Utility.
Tessitura Contribution Import Utility
This utility is setup to run on a schedule. That schedule is up your organization. The timing of this will determine how long it takes your contribution to show up on the constituent record.
The CIU creates the contribution based on the parameters set when we add the record to the TW_CONTRIBUTION_IMPORT table. It also calculates and creates memberships when the contribution is created.
The reference number (Ref No) replaces the idea of an order number.
Type G = Gift (has no payment schedule)
Type P = Pledge (has a payment schedule)
There are several options when choosing how to process a Gift or Pledge. These options are at the form level providing maximum flexibility.
One-Time Contributions
- Process as a One-Time Gift
Coming Soon
- Process as a One-Time Single Payment Pledge
Recurring Contributions
- Process as a Rollover Pledge
Coming Soon
- Process as Recurring Gifts
Coming Soon
- Process as Recurring Single Payment Pledges
- Process as a Fiscal Year Sync Rollover Pledge
Fix Amount Pledges as part of the Flex2 Pledge Form (Starting Beta 11/24)
- Process as Gifts
- Process as Single Payment Pledges
- Process as a Fiscal Year Sync Pledge
- Process as a Pledge
Processing Contributions as Pledges
For Pledges, we use the Stripe Subscription ID and we store it on the Custom Data tab. DO NOT REMOVE THE STRIPE SUBSCRIPTION ID. This allow us to easily find it for future payments and apply those payments directly to the pledge and payment schedule. If we need to create a roll over pledge because the current pledge is fulfilled, we will transfer the Stripe Subscription ID over to a new pledge.
The initial CIU run creates the pledge and applies the first payment. Subsequent, payments are applied direct to the pledge. The screen shot below shows the first 3 payments of a 12 payment pledge schedule.
Processing Contributions as Gifts
For Gifts, we process the contribution through the CIU. The same delay can take place based on when the the job gets created.
