The Household Account model
NPSP's default architecture places every Contact inside a Household Account. Gifts are entered against individuals, but giving history rolls up to the household — so "The Alvarez Household" shows the family's combined relationship with the organization. Run the grouping below to watch raw contacts resolve into households with roll-up totals.
Incoming contacts (ungrouped)
Grouping logic in this simulation: shared last name + shared mailing address → same Household Account. NPSP also supports manual household management for non-traditional households, name variations, and roommate scenarios.
Hard credits vs. soft credits
A hard credit belongs to the legal donor of record — the contact or account on the Opportunity. A soft credit recognizes someone else's connection to the gift (a spouse, the household, a matching-gift employee) without double-counting revenue. Enter a gift below and watch the credit ledger update.
Enter a gift
Married contacts in this simulation automatically soft-credit their spouse, mirroring NPSP's Automatic Household Soft Credits. Matching gifts hard-credit the employer Account and soft-credit the employee.
Credit ledger
| Gift | Constituent | Credit type | Amount |
|---|---|---|---|
| No gifts recorded yet. Enter one above. | |||
Why totals don't double-count
Finance reports on hard credits only — that's actual revenue. Development reports may include soft credits to understand relationships and total household influence. Conflating the two is one of the most common nonprofit reporting errors.
Constituent deduplication
Duplicate constituents fragment giving history, generate duplicate mailings, and break tax receipt accuracy. This module scans a sample constituent file for likely duplicates using normalized name comparison, nickname mapping, and shared email/address signals — then offers a merge preview where the surviving record keeps the best value for each field.
Constituent file (12 records)
Tax receipt batch run
High-volume receipt production is where data quality becomes legally visible: every receipt must reflect accurate gift data, deduplicated constituents, and — critically — each donor's stated communication preferences. Run the weekly batch below and review the exclusion log: who was skipped, and exactly why.
This week's receiptable gifts
| Donor | Gift | Channel preference | Status flags |
|---|
Batch rules in this simulation: honor Do Not Mail / Do Not Email flags, route by preferred channel, hold records with failed address validation, and skip anonymous gifts from printed acknowledgment lists.
About this simulator
Built to demonstrate working knowledge of the Salesforce Nonprofit Success Pack data model: Household Accounts vs. the one-to-one and Person Account models, Opportunity-based gift entry, automatic household soft credits, duplicate management strategy, and preference-aware donor communications. All data is fictional and generated in the browser.
The logic here mirrors what I built and ran in production for nearly three decades — multi-source data integration, deduplication via unique indexing, validation frameworks, and exception handling for malformed records — translated into the NPSP vocabulary and object model.