Add a Generate Payments Process Screen
The table below explains the items on the Add a generate payments process screen. For information about how to access this screen, refer to Add a Generate Payments Process.
Screen Item |
Description |
Name |
Enter a unique name to identify the generate payments process. |
Description |
Enter a more detailed description to identify the generate payments process, such as an explanation as to why you generate the payments. |
Account system |
Select an account system. Generated payments are added to the account system you select here. The Account system field appears only if your organization configures multiple general ledger account systems and implements site security, and you have rights to work with multiple account systems. |
Generate payments for |
Select the checkboxes for the types of payments to generate. You can generate pledges, recurring gifts, or both. You can also set up the process to include membership installments instead of pledges or recurring gifts. To generate payments for only a selection of revenue records, select Only consider records in the following selection. In the Selection field, search for or create the selection that contains the transactions. If the selection is created from an ad-hoc query or a smart query instance, select Edit Query to edit the query used to generate the selection. When you run the generate payments process, you can change your selection as necessary. |
Payments due on or before |
Enter the date you want the program to use to select the revenue records that require new payments. The program compares this date to the records specified for Generate payments for and selects those that are due on or before this date. To select the date from a calendar, select the calendar icon. If a selected record has multiple installments due on or before the date entered in this field, only the oldest installment is included when you run the process. To generate payments for multiple installments of a commitment that are due on or before the cut-off date, run the Generate payment process and commit its revenue batch multiple times until payments are generated for the installments. When you run the generate payments process, you can change the cut-off date as necessary. |
Consolidate multiple commitments to a single payment by constituent |
To consolidate multiple payments from the same constituent into one transaction, select this checkbox. The process consolidates only payments with the same account number and currency. |
Batch template |
Select the template to use to create the revenue batch that includes the generated payments. The batch template specifies the fields included in the batch and any default values for those fields. The selected batch template must be a for revenue batch that includes the Receipt amount, Account, Reference number, Reference date, Authorization code, Name on card, Rejection message, Card number, Card type, Rejection message, and Expires on fields. If the selected revenue batch template does not include these fields, the process cannot generate the transactions. If the process is generating payments for membership installments, the only batch templates available are membership dues batch templates which include the required fields. To create a revenue batch template for automatic transactions, consult your revenue batch processing manager. |
Batch number |
Enter a unique batch number to use to track the batch generated by the process. Make sure the batch number has not been used for another batch. After you save a batch, you can no longer use its batch number to identify a new batch. When you open a batch, the batch number appears in the top corner of the screen. On the Batch Entry page, the batch number appears next to each corresponding batch. The batch number can be alphanumeric. When you run the generate payments process, you can change your entry here as necessary. |
Batch owner |
Select the user with security rights to process the batch generated by the process. If you leave this field blank, you own the batch by default. |