Loading
Salesforce Enforces New Security Requirements in Summer 2026Read More

Salesforce NPSP: Household Account Name Resets to "Household" After Contact Address Change

Publish Date: Jul 15, 2026
Description

This article explains why a Household Account name in the Nonprofit Success Pack (NPSP) is overwritten with the literal value "Household" when you edit an associated Contact's address, and how to correct it. The behavior can appear intermittent because NPSP recalculates account names during Contact save and during the nightly TDTM (Table-Driven Trigger Management) account naming job. 

The rename occurs for a Household Account when its Primary Contact (or a Contact triggering the recalculation) has blank First Name and Last Name values, causing the NPSP naming formatter to produce the fallback name "Household." It can also occur when a custom Apex trigger on the Contact object with faulty bypass logic overrides the NPSP naming. No error message is displayed; the account name simply changes on save.

Resolution

Cause 1: A Contact linked to the Household Account has blank First Name and Last Name fields, so NPSP account naming produces the default "Household".

  • Open the affected account and go to the related Contact record and confirm the record has values in First Name [FirstName] and Last Name [LastName]. Populate both fields with the donor's real name; do not leave either blank.
  • Save the Contact. NPSP recalculates the Household Account name on save.
  • Go to NPSP Settings > People > Households and confirm the Automatic Household Naming settings are active. Then, open NPSP Settings > Bulk Data Processes > Refresh Household Data and run it to regenerate names for the corrected records.

Cause 2: A custom Apex trigger on the Contact object overrides NPSP naming and resets the name to "Household" because its bypass logic fails on Contacts with blank first/last name.

  • In Setup > Apex Triggers, list active triggers on the Contact object.
  • Identify any non-NPSP (non-npsp namespace) custom trigger that updates the related Account Name [Name] field.
  • Correct the bypass logic so the trigger exits when First Name [FirstName] and Last Name [LastName] are both blank, then deploy the corrected class from your sandbox to production.
  • Do not attempt to modify NPSP managed triggers such as [TDTM_Account]; managed trigger code cannot be edited. Instead, register a custom TDTM trigger handler in NPSP Settings > System Tools > Trigger Configuration to control ordering and set your custom handler's [Active__c] flag as needed.

Cause 3: The State and Country Picklists feature combined with Household Address handling is interfering with the address save.

  • In NPSP Settings > People > Addresses, set "Household Account Addresses Disabled" to checked (true) to stop address-driven recalculation, or
  • Remove any Country label translations in Setup > Translation Workbench that conflict with State and Country picklist values.

Confirm the issue is resolved by editing the address on the affected Contact, saving, and verifying the Household Account Name field retains the donor's name (for example "Smith Household") and does not revert to "Household".

Knowledge Article Number

005389033

 
Loading
Salesforce Help | Article