Batch Record Details

Defaults to the name of the organization of the logged-in user who created (owns) the batch. 

The default fund for pledges and contributions posted in the batch. This field can be edited for open batches only.

Unique number assigned by the system that identifies each batch in your system.

Text description assigned to the batch when it was created.

Status of the batch as one of the following: Open, Review, or Closed. This is a system-assigned (read-only) field that cannot be edited in batch details.

The default date assigned to pledges and contributions posted in the batch. The posting date is the date contributions and pledges were given--not the date they were entered into the system. 

Date and time the batch was closed. 

Date and time the batch was created. This is a system-assigned (read-only) field that cannot be edited.

Indicates how the batch was created, for example, manually created or from a lockbox import. This is a system-assigned (read-only) field that cannot be edited.

A global control that determines whether the Check Number field is displayed by default in the batch form for newly created batches and included in the Tab key sequence for contribution posting.

If desired, a user can override the global setting when creating a new batch. For example, you can enable the display of the field here but a user can choose not to display the field when creating a specific batch.

This option has two settings:

• Selected: by default, the Check Number field is displayed in the batch form for new batches and included in the Tab key sequence for payment and contribution posting.
• Not selected: by default, the Check Number field is not displayed in the batch form.

A global control that determines whether the Memo field is displayed by default in the batch form for newly created batches and included in the Tab key sequence for contribution posting.

If desired, a user can override the global setting when creating a new batch. For example, you can enable the display of the field here but a user can choose not to display the field when creating a specific batch.

This option has two settings:

• Selected: by default, the Memo field is displayed in the batch form for new batches and included in the Tab key sequence for payment and contribution posting.
• Not selected: by default, the Memo field is not displayed in the batch form.

This checkbox enables you to control whether the system conducts a pledge search before the user posts a contribution to a new batch.

In the setup for a new batch, the checkbox value is pre-set to selected (checked) or deselected (unchecked). The pre-set value (the default) is managed by the Batch Posting - Use Pledges by Default option in the Batch Management group on the Settings page. The pre-set value applies globally to all new batches. You can, if desired, override the pre-set value for a specific batch. This is easily done by changing the checkbox value when you set up the new batch.

IMPORTANT

If you want to change Batch uses pledges checkbox value for a specific batch, you must make the change before saving the batch. After you save the batch, the system will not allow you undo the setting.

The checkbox has two settings:

• Selected: before adding a contribution to a batch, the system conducts a pledge search to locate a pledge to match the contribution to. If a matching pledge is found, the system links it to the contribution and displays a pledge icon next to the contribution in the batch record.
• Not selected: before adding a contribution to a batch, the system does not conduct a pledge search to locate a matching pledge. Therefore, contributions posted to the batch are not linked to pledges, and no pledge icon is displayed next to the contribution in the batch record.

A global control that lets you configure Quick Posting as the default method for posting contributions to newly created batches. 

Depending on the volume of contribution records that must be entered, getting data into your system can be a time-consuming process. Data entry errors are bound to happen. With the traditional posting method, data is validated as it is entered into each field in a contribution record, and the user must correct any errors before saving the contribution. While this method is effective at reducing data entry errors, it comes with consequences: errored entries can significantly interrupt and slow down a user’s workflow and productivity. With Quick Posting, the system checks the values in a contribution record after all the data in a record is entered. Any errors that are found do not need to be corrected before the contribution is saved. The user’s workflow is not interrupted, allowing them to complete data entry and go back later to correct any errors the system flags. With the Quick Posting method, a user especially proficient at data entry can enter contribution data as quickly as their skills allow.

If desired, a user can override the global setting when creating a new batch. For example, you can enable the Quick Posting option here but a user can choose not to use quick posting when creating a specific batch.

The checkbox has two settings:

• Selected: by default, all newly created batches use the Quick Posting method

Depending on the volume of contribution records that must be entered, getting data into your system can be a time-consuming process. Data entry errors are bound to happen. If you choose to use the Quick Posting method, the system checks the values in a contribution record after all the data in a record is entered, which can help speed data entry. If the system finds errors, you are not forced to correct them before saving a contribution record. Therefore, your workflow is not interrupted, allowing you to complete data entry and go back later to correct any errors the system flags. With the Quick Posting method, if you are especially proficient at data entry, you can enter contribution data as quickly as your typing skills allow.

• Not selected: by default, all newly created batches use the traditional posting method. With the traditional posting method, data is validated as it is entered into each field in a contribution record, and you must correct any errors before saving the contribution. While the traditional method is effective at reducing data entry errors, it comes with consequences: errored entries can significantly interrupt and slow down your workflow and productivity, especially if you are a fast typist and proficient at data entry.

Sets the default method of payment used to fund contributions (for example, Check). From the dropdown list, select the payment method to show by default in the Contribution Type field.

  Specifying a default value for this field relieves the user from having to repeatedly select a value when entering records into the batch. Note that even though a default value is displayed, during data entry users can override it if it does not apply to a given pledge or contribution by selecting a different value from the dropdown list. 

  The values shown in the Contribution Type dropdown list are managed lookups, which are defined on the Settings page. For details, go to Lookups Tab.

Sets the default value (for example, Family ID) for the Lookup ID field, which is used to search for the donor record during data entry. From the dropdown list, select the value to show by default in the field. 

  Specifying a default value relieves the user from having to repeatedly select a value when entering records into the batch. Note that even though the field shows a default value, during data entry users can change override it if it does not apply to a given pledge or contribution by selecting a different value from the dropdown list.

Sets the default value (for example, In Pew) for the Appeal Code field, which is used to specify the method used to solicit the pledge. From the dropdown list, select the value to show by default in the field.

  Specifying a default value relieves the user from having to repeatedly select a value when entering records into the batch. Note that even though the field shows a default value, during data entry users can change override it if it does not apply to a given pledge or contribution by selecting a different value from the dropdown list. 

Name of the individual who created the batch. This is a system-assigned (read-only) field that cannot be edited.

Projected number of pledges in the batch.

This is an optional field. If you leave it blank, the system displays two dashes (--) in the field to indicate that no value was provided when the batch was created.

Projected total dollar amount of pledges in the batch.

Projected number of contributions in the batch.

This is an optional field. If you leave it blank, the system displays two dashes (--) in the field to indicate that no value was provided when the batch was created.

Projected total dollar amount of contributions in the batch.

Use this text field to enter additional information about the batch. 

If editing a batch, you must supply a reason for the change in this field.