About the Settings Page

The person who initially creates a batch is considered the rightful owner. This option has two settings:

• Selected: only the batch owner is permitted to change pledges in a batch.

• Not selected (the default): all privileged users, including users who do not own the batch, can make modifications to pledges in batches.

  A user with DDM Administrator access rights can override this option and change pledges in a batch.

Controls whether the OBO (On Behalf Of) Parishes list in pledge entry includes only the names of parishes that have goals configured.

This option has two settings:

• Selected (the default): only OBO parishes that have goals configured are available for selection (when adding or editing a pledge) in the On Behalf Of dropdown list in the pledge form.

• Not selected: all organizations in your database are available for selection (when adding or editing a pledge) in the On Behalf Of dropdown list in the pledge form.

  If you limit the OBO Parishes list to show only those organizations that have goals but you need an organization that has no goals to be included in the list, you can add the desired organization to the list by specifying a zero-dollar goal.

Controls whether the system displays a default value in the Appeal Code list for each newly created pledge.

This option has two settings:

• Selected: no default value appears in the Appeal Code list for new pledges.

• Not selected (the default): the system displays the value selected for the previous pledge as the default in the Appeal Code list for each new pledge. 

Displays the End date field in pledge data entry. The end date is the last date that payments can be posted to the pledge.

These options give you finer control over how the system handles lockbox imports and contributions imported from Online Giving. Select one:

• Add Imported Pledge: the import process performs no validation checks for an additional active pledge. An active pledge is one with an end date that is either NULL or after today.
  
• Reject Imported Pledge: the import process checks for an additional active pledge associated with the same fund, family, and OBO organization. If a pledge matching this criteria is found, the process returns an error informing the user that an active pledge exists for the donor. An active pledge is one with an end date that is either NULL or after today.
• Update Existing Pledge to Match Import: the import process checks for an additional active pledge. If one is found, it compares the value in the Adjusted Pledge Amount, Frequency, and Fulfillment Method fields. The process then does the following:

  • If an imported contribution is attached to a pledge, the contribution is posted to the existing pledge with the Initial Contribution checkbox deselected (unchecked).

  • Updates other fields in the existing pledge record, as necessary.
    

  • If the value in the Amount field does not match, adds an adjustment so the adjusted amount matches the amount in the imported record.
    

  • If the values in the Frequency and Fulfillment Method fields do not match, changes the values in these fields in the existing pledge record to match those in the imported record.

Controls customer access to the Donor Reports module and, as a result, visibility of donor reports. This option has two settings:

• Selected (the default): shows the Donor Reports button, which gives users access to donor reports.
• Not selected: hides the Donor Reports button, which prevents users from accessing donor reports. 

Controls whether negative refunds appear in Parish Refunds. This option has two settings:

• Selected: shows negative refunds.
• Not selected: hides negative refunds.

Select the checkbox to activate the integration between Development Manager and Online Giving.

After the two systems are connected, the Import > Integration page is visible to enable pledge and contributino records to be imported into Development Manager from Online Giving.

 This setting does not affect ParishSOFT Giving or Digital Offering.

By default, Development Manager uses the ParishSOFT ID (a unique identified assigned by the ParishSOFT system) to identify parish organizations. If you prefer instead to use the organization ID assigned to parishes by your diocese, select the Local Org ID option from the dropdown list. After you make the change, the organization ID assigned by your diocese will appear on the following reports:

• Parish Master
  
• Designation Details
  
• Parish Date Over Goal
  
• Periodic Report
  
• Parish Roster
  
• Parish Refund/Shortfall

Additionally, the organization ID assigned by your diocese can be used when importing goals. Simply enter the organization ID into the OrgID field import file.

  Local organization IDs for parishes are set on the Organizations page in the Diocesan Suite's Administration module. The Local Org ID field in each organization's record is where the value is saved.

This field contains a list of all organizations in the diocese. The organization that is selected from this list appears in the header of all Development Manager reports and is shown in in the top-right corner of every page after the user logs in. The selected organization is responsible for managing the diocese's campaigns. The organization may be the diocese proper or an office like the Office of Development.

Controls whether all contributions entered into Development Manager must be entered by batch to be sucessfully saved.

This option has two settings:

• Selected (the default): batches are required. Batches are required for posting contributions.
• Not selected: batches are optional and are not required for posting contributions.

Controls whether all pledges entered into Development Manager must be entered by batch to be sucessfully saved.

This option has two settings:

• Selected (the default): batches are required. Batches are required for posting pledges.
• Not selected: batches are optional and are not required for posting pledges.

Controls whether a batch can contain pledges or contributions for different funds.

This option has two settings:

• Selected: the account setup on the batch is the default fund for new pledge and contributions. However, the user can override the fund as needed at the individual pledge or contribution level.
• Not Selected: all postings in a batch must be to the same fund.

Lets a user with the appropriate permissions set the default value of the Batch uses pledges checkbox in the setup for all new batches (for a description of Batch uses pledges checkbox, go to Batch Record Details). 

This option has two settings:

• Selected: as illustrated in the batch data entry form below, sets the default value of the Batch uses pledges checkbox to "true" (checked) for all new batches. When the value is "true", the system searches the database to locate a pledge to match contributions to before posting them to a batch. If a matching pledge is found, the system links it to the contribution and displays the pledge icon next to the contribution record in the batch. 

  Depending on the number of pledges in your database, selecting this option can slow data entry because the system needs time to locate a matching pledge.

• Not selected: in the data entry form for new batches, sets the default value of the Batch uses pledges checkbox to "false" (unchecked) for all new batches. When the value is "false", the system does not search the database for a pledge to match posted contributions to. Contributions posted to batches are not linked to pledges, and no pledge icon is displayed next to contribution records in batches.

IMPORTANT

A user can overrided the default value of the Batch uses pledges checkbox locally within a specific batch. This is easily done by changing the checkbox value in the batch from checked to unchecked, and vice versa. However, the user must make such a change before saving the batch because the system does not allow changes after a batch is saved. Additionally, a change made locally applies to the specific batch only.

This option has two settings:

• Selected: pledges can accept OBO changes even after the batch containing the pledges is closed.

• Not selected, OBO changes are not allowed.

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

 This option sets the default display of the Check Number field for new batches. You can override the global setting when creating a new batch. In other words, you can enable the display of the field here but select not to display the field when you create a specific batch.

This option has two settings:

• Selected: the Check Number field is enabled and included in the Tab key sequence for payment and contribution posting.

• Not selected: the Check Number field is disabled and skipped in the Tab key sequence for payment and contribution posting.

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

 This option sets the default display of the Memo field for all new batches. You can override the global setting when creating a new batch. In other words, you can enable the display of the field here but select not to display the field when you create a specific batch.

This option has two settings:

• Selected: the Memo field is enabled and included in the Tab key sequence for payment and contribution posting.

• Not selected: the Memo field is disabled and skipped in the Tab key sequence for payment and contribution posting.

In this dropdown list, select the default search field for batch data entry. When the user posts a contribution to a batch, the system uses the default search field to match the posting on. 

• Family ID: sets the Family DUID, a unique ID used to identify each family, as the default lookup value.
• Member ID: sets the Member DUID, a unique ID used to identify each member, as the default lookup value.
• Diocesan ID: sets the Diocesan ID, a unique ID used to identify each family, as the default lookup value. Note that some organizations are set up to use the Diocesan ID instead of the Family DUID to identify families. This setup is done in the ParishSOFT Family Suite Administration module.
• Pledge ID: sets the Pledge ID, a unique value used to identify a pledge, as the default lookup value.
• Family Name: sets the family's last name as the default lookup value.
• Member Name: sets the member's last name as the default lookup value.
• Family ID and Family Name: sets the Family ID and Family Name as the default lookup fields in the data entry form for batches. In the data entry form, the Family ID and Family Name data are split into separate fields.
• Member ID and Member Name: sets the Member ID and Member Name as the default lookup fields in the data entry form for batches. In the data entry form, the Member ID and Member Name data are split into separate fields.

This dropdown list contains options representing the lookup lists in the application. Select the lookup list whose values you want to manage. 

 The current release of Development Manager provides only one lookup list to manage: Contribution Type. Future releases will give you the ability to manage other lookup lists in the application

Click  to add a new contribution lookup value. Enter information into the Name and Code fields and, if desired, select the Active checkbox.

Click  to edit the details for a lookup value.

Type a descriptive name for the Contribution Type lookup in this field. After you save the lookup value, the name you provided appears in the list on this page and in the dropdown lists throughout the application.

Type an abbreviation for the Contribution Type lookup. For example, you could type "Amex" for American Express or "MC" for Mastercard.

Select this checkbox to make the Contribution Type lookup value visible to users so they can select it from the Contribution Type dropdown list during pledge and contribution entry. If you do not want users to see the lookup value, leave the checkbox blank. 

  The Active checkbox control can be quite helpful when setting up a lookup list. If you do not want users to immediately see a particular lookup value, leave the checkbox blank. When you are ready to give users the ability to select the value during pledge and contribution entry, select the checkbox and save the lookup. After you do this, the lookup is visible to users.

Click  to save a new lookup value or to save edits to an existing lookup value. 

Before saving information entered for a lookup value, you can click  to remove what you typed. You can also click to exit Edit mode. 

Click  to remove a lookup value from the list. The system also removes the lookup value from associated lookup lists throughout the application.