---
schema_version: "1"
id: 0d803dd150023902fee73e8abb9833b20c5dc1fb8a9084e0a89ca24762c4eda2
title: Map Custom Recurring Donation Status Values to a State
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/npsp_map_status_to_state.md
canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.npsp_map_status_to_state.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a80eede82e18f930e94955f771a60ac826d0b47446603b14efd6c117d67c92bd
description: When you create custom picklist values for Recurring Donation Status, map them to a State so that NPSP can process records with those custom Status values.
products:
  - Nonprofit
release: "264"
---
# Map Custom Recurring Donation Status Values to a State

When you create custom picklist values for Recurring Donation Status, map them to a State so that NPSP can process records with those custom Status values.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/images/icon_note.png)

Note Your user profile must have access to the `RD2_StatusMappingSettings_CTRL` apex class to use Status to State mapping.

State describes NPSP Recurring Donation processing behaviors. The following States are available:

- **Active**: The donor is actively donating. NPSP creates installment Opportunities as defined by the Recurring Donation schedule.
- **Lapsed**: The donor isn't making donations as expected, but NPSP still creates installment Opportunities as defined by the Recurring Donation schedule.
- **Closed**: The donor stopped making donations for this Recurring Donation. NPSP doesn't create any new installment Opportunities.

Here's how this works in practice. Let's say you create a Status called Expired Card to track when a donor's credit card has expired. You don't want to immediately close out the Recurring Donation because you want to ask the donor if they have updated card information first. In this example, the State behavior you want NPSP to use is Lapsed. There's going to be a lapse in the donor's giving until you can obtain new card information.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/images/icon_important.png)

Important If you don't map your custom Status, you won't be able to create or update Recurring Donations that use those custom Statuses.

To map a custom Status value to a State:

1. Click the **NPSP Settings** tab. If you don't see the tab, find it in the App Launcher (![App Launcher icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/resources-product/images/app_launcher_icon.png)).
2. Click **Recurring Donations** | **Status to State Mapping**.
3. Click **Edit**.
4. Assign a State to each of your custom Status values.
5. Click **Save**.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sfdo-nonprofit_success_pack-264-0-0-production-enus/bd2879e2-2bdc-4012-aa32-dc0c697c4538/images/icon_note.png)

Note Recurring Donations includes standard Status values that are already mapped to their corresponding State: Active, Lapsed, and Closed. These standard Status values are required for Recurring Donations, so don't remove them from your org!