5.1 Benefit Programs, Benefit Schedules & Beneficiary Data Architecture

5.1 Benefit Programs, Benefit Schedules & Beneficiary Data Architecture

Exam Focus: Social safety net and public assistance programs—such as the Supplemental Nutrition Assistance Program (SNAP), Temporary Assistance for Needy Families (TANF), the Low-Income Home Energy Assistance Program (LIHEAP), and Childcare Development Block Grants (CDBG)—require a data architecture that cleanly decouples overarching legislative policies from discrete citizen entitlements and actual service disbursements. On the AP-222 examination, architects must understand how Public Sector Solutions (PSS) standardizes these assistance structures, how multi-member households are modeled, and how authorized awards translate into audited financial or non-financial service deliveries.

---

Core Benefit Management Data Architecture

Historically, health and human services agencies deployed siloed legacy applications for each assistance program. Food assistance lived in one mainframe, cash welfare in another, and subsidized childcare in a third-party portal. This fragmentation prevented a holistic view of constituent need, duplicated administrative overhead, and resulted in frequent over-disbursements.

Salesforce Public Sector Solutions resolves this fragmentation through a unified, modular Benefits Management data model built directly on the platform. The architecture distinguishes between policy definition, cataloged offerings, scheduling mechanisms, and constituent-level execution:

┌───────────────────────────────────────────────────────────────────┐
│                     Program (e.g., SNAP)                          │
│    • Statutory Authority, Fiscal Year Budget, Sponsoring Agency   │
└─────────────────────────────────┬─────────────────────────────────┘
                                  │ 1:M
                                  ▼
┌───────────────────────────────────────────────────────────────────┐
│               Benefit Type (e.g., Food Assistance)                │
│    • High-level categorization across departmental boundaries     │
└─────────────────────────────────┬─────────────────────────────────┘
                                  │ 1:M
                                  ▼
┌───────────────────────────────────────────────────────────────────┐
│         Benefit (e.g., Monthly SNAP EBT Nutrition Allotment)       │
│    • Unit of Measure: USD ($)    • Default Quantity: 450          │
└───────────────┬───────────────────────────────────┬───────────────┘
                │ 1:M                               │ 1:M
                ▼                                   ▼
┌───────────────────────────────┐   ┌───────────────────────────────┐
│       Benefit Schedule        │   │      Benefit Assignment       │
│  • Recurring cadence & slots  │   │  • Awarded to Constituent     │
│  • Calendar rules / capacity  │   │  • Authorized Qty & Frequency │
└───────────────┬───────────────┘   └───────────────┬───────────────┘
                │ 1:M                               │ 1:M
                ▼                                   ▼
┌───────────────────────────────┐   ┌───────────────────────────────┐
│        Benefit Session        │   │     Benefit Disbursement      │
│  • Discrete service event     │   │  • Actual payout or delivery  │
│  • Attendance / Utilization   │   │  • Reconciles against ceiling │
└───────────────────────────────┘   └───────────────────────────────┘

The Foundational Benefit Management Entities

1. Program (Program): Represents the macro-level public initiative, legislative mandate, or grant-funded service. Examples include State Childcare Development Fund, Emergency Rental Assistance Program (ERAP), or Supplemental Nutrition Assistance Program. The Program record defines operational start and end dates, sponsoring government departments, target populations, and overall fiscal budgets.
2. Benefit Type (BenefitType): Provides a standardized classification taxonomy across multiple programs. A single agency might offer diverse benefits categorized under Cash Assistance, Nutritional Support, Vouchers, Subsidized Childcare, or Workforce Training. Standardizing benefit types enables cross-program analytics and portfolio reporting.
3. Benefit (Benefit): The specific, deliverable unit of assistance offered under a Program. For example, under the Childcare Development Fund Program, an agency might define two distinct benefits: Infant Daycare Center Subsidy and After-School Care Voucher. The Benefit record defines the default quantity, standard monetary value, eligibility criteria links, and associates with a specific Unit of Measure.
4. Unit of Measure (UnitOfMeasure): Standardizes the quantification of assistance delivered. Crucially, benefits in PSS are not restricted to monetary currency. A UnitOfMeasure can represent Currency (USD), Hours (for childcare or respite care), Meals (for senior nutrition programs), Days (for temporary emergency shelter), or Vouchers / Transit Passes. This abstraction allows the same data model to power cash transfers and physical commodity distribution.
5. Benefit Schedule (BenefitSchedule): Establishes recurring delivery patterns, disbursement intervals, or scheduled appointments. For non-monetary services—such as parental education classes, job readiness seminars, or weekly clinical visits—the BenefitSchedule defines recurrence rules (e.g., Every Tuesday and Thursday at 10:00 AM), maximum capacity, and assigned caseworkers or facilities.
6. Benefit Session (BenefitSession): The concrete, individual calendar occurrence generated by a BenefitSchedule. Caseworkers use BenefitSession records to track real-time attendance, roster capacity, check-in timestamps, and service completion.

---

Beneficiary Architecture: Modeling Individuals and Households

One of the most complex architectural aspects of benefits administration is modeling who receives assistance. In commercial CRM, relationships center on individual consumers or B2B corporate hierarchies. In government social safety net programs, eligibility and benefit allotments are determined at the Household or Assistance Unit level.

Person Accounts for Individual Citizens

In Salesforce Public Sector Solutions, individual constituents are universally modeled as Person Accounts. Person Accounts fuse standard Account and Contact capabilities into an integrated record, maintaining:

• Legal Name, Preferred Name, and Aliases;
• Social Security Number (SSN), Individual Taxpayer Identification Number (ITIN), or State Resident ID (secured with Shield Platform Encryption);
• Date of Birth, Gender Identity, and Language Preferences;
• Employment status, monthly earned wages, and disability verifications.

[!IMPORTANT] Architectural Standard: Never model citizens as standalone Contacts under a generic 'Dummy Citizen Account'. This legacy pattern breaks standard PSS capabilities, including Discovery Framework assessments, Actionable Relationship Center (ARC) graphs, and Agentforce constituent grounding.

Modeling Multi-Person Households and Assistance Units

Under federal and state statutory regulations (e.g., 7 CFR § 273.1 for SNAP), an assistance unit is defined as individuals who live together and customarily purchase and prepare meals together. A single physical address may house multiple distinct assistance units (e.g., an elderly grandparent on fixed income living with an adult daughter who has her own dependent children).

To represent these fluid socioeconomic relationships, PSS employs the Party Data Model and Party Relationship Groups:

                               ┌────────────────────────────────────────────────┐
                               │    Party Relationship Group (Household)        │
                               │         "The Rodriguez Household"              │
                               └───────────────────────┬────────────────────────┘
                                                       │
         ┌─────────────────────────────────────────────┼─────────────────────────────────────────────┐
         │ Role: Head of Household (Primary Enrollee)  │ Role: Spouse / Co-Applicant                 │ Role: Dependent Child
         ▼                                             ▼                                             ▼
┌────────────────────────────────┐            ┌────────────────────────────────┐            ┌────────────────────────────────┐
│         Person Account         │            │         Person Account         │            │         Person Account         │
│     Maria Rodriguez (Mother)   │            │     Carlos Rodriguez (Father)  │            │     Elena Rodriguez (Age 4)    │
│  • SSN: Encrypted              │            │  • SSN: Encrypted              │            │  • Needs Childcare Subsidy     │
│  • Earned Income: $1,400/mo    │            │  • Earned Income: $1,100/mo    │            │  • Counted in Household Size   │
└────────────────────────────────┘            └────────────────────────────────┘            └────────────────────────────────┘

1. Party Relationship Group (PartyRelationshipGroup): Represents the collective household or economic unit. It functions as an Account record type, grouping family members together for aggregate means-testing, asset evaluation, and household-level benefit assignments.
2. Account Contact Relationship (AccountContactRelation / ACR): Binds individual Person Accounts to the Household, defining explicit administrative and familial roles:
   • Head of Household / Primary Payee: The primary adult constituent legally responsible for application attestations and receiving disbursements.
   • Spouse / Co-Applicant: Adult whose income and assets must be included in the aggregate household financial calculation.
   • Dependent Child: Non-earning member qualifying the household for higher income thresholds, childcare allocations, or child tax credits.
   • Ineligible / Excluded Member: An individual residing in the dwelling (such as an undocumented relative or sanctioned individual) whose personal needs are excluded from the benefit calculation, but whose earned income may still be counted toward household income under statutory deeming rules.
3. Contact Contact Relationship (ContactContactRelation / CCR): Maps peer-to-peer interpersonal relationships between household members independent of the household entity, such as Parent-Child, Legal Guardian-Ward, or Spousal / Domestic Partner connections.
4. Actionable Relationship Center (ARC): Provides caseworkers with an interactive, graphical visualization of the constituent's entire household graph directly within the Public Sector Service Console, allowing caseworkers to view linked benefit enrollments, active cases, and income streams across all family members.

---

The Benefit Assignment Lifecycle: Awarding Entitlements

When a constituent or household applies for assistance and passes statutory eligibility screening, the agency issues a formal benefit grant. In Public Sector Solutions, this legal entitlement is captured in the BenefitAssignment object.

┌─────────────────┐       ┌─────────────────┐       ┌─────────────────┐       ┌─────────────────┐
│ 1. Application  │       │ 2. BRE Rule     │       │ 3. Benefit      │       │ 4. Active       │
│    Submitted    │──────>│    Adjudication │──────>│    Assignment   │──────>│    Disbursement │
│ (IndividualApp) │       │ (Expression Set)│       │ (Entitlement)   │       │ (Drawdown)      │
└─────────────────┘       └─────────────────┘       └─────────────────┘       └─────────────────┘

BenefitAssignment vs. ProgramEnrollment

A common point of confusion on the AP-222 exam is the distinction between ProgramEnrollment and BenefitAssignment:

• ProgramEnrollment: Represents the constituent's broad registration within an overall government program (e.g., Jane Doe is enrolled in the SNAP Program as of October 1, 2026). It tracks enrollment dates, primary caseworker, and overall program standing.
• BenefitAssignment: Represents the specific, quantified, enforceable award of aid. A single ProgramEnrollment may result in multiple concurrent or sequential BenefitAssignment records (e.g., an ongoing Standard Monthly Food Allotment of $450/month, plus a temporary Emergency Disaster Food Supplement of $200 for November 2026).

Key Attributes of BenefitAssignment

• EnrolleeId: Polymorphic lookup referencing either an individual Person Account (for individual-specific aid like job training or disability support) or a Household Account (for household-level assistance like SNAP or TANF).
• BenefitId: Lookup to the specific Benefit record catalog definition.
• Quantity: The authorized amount per frequency interval (e.g., 450.00 dollars, or 40.00 childcare hours).
• UnitOfMeasureId: Confirms the measurement unit (USD, Hours, Units).
• Frequency: Standard picklist defining the award cadence: Monthly, Weekly, Bi-Weekly, Daily, One-Time, or Hourly.
• StartDateTime & EndDateTime: The statutory certification period during which the constituent is authorized to receive aid (e.g., a 12-month certification from October 1, 2026 to September 30, 2027).
• AssignmentStatus: The active operational state of the award:
  • Pending: Eligibility determined, awaiting supervisor approval or initial fund encumbrance.
  • Active: Constituent is currently authorized and receiving scheduled disbursements.
  • Suspended: Disbursements paused due to unverified income changes or failure to submit interim reports.
  • Terminated: Benefit revoked early due to disqualification, exceeding income limits, or client request.
  • Expired: Benefit reached its natural EndDateTime without successful recertification.

---

Service Delivery Tracking: Benefit Disbursements vs. Authorized Ceilings

Authorizing a benefit is only half the administrative lifecycle. Public agencies must track actual delivery, reconcile payments with state warrant systems or EBT card processors, and guarantee that total assistance delivered does not exceed the statutory ceiling.

The Benefit Disbursement Record (BenefitDisbursement)

Every time money is transferred to an Electronic Benefit Transfer (EBT) card, an ACH direct deposit is sent to a constituent's bank account, a physical voucher is mailed to a landlord, or a vendor invoice is paid, a BenefitDisbursement record is generated against the active BenefitAssignment.

┌────────────────────────────────────────────────────────────────────────┐
│         Benefit Assignment: Monthly SNAP Nutrition Allotment           │
│   • Authorized Quantity: $450.00 / Month                               │
│   • Certification Window: 2026-10-01 to 2027-09-30                     │
└───────────────────────────────────┬────────────────────────────────────┘
                                    │ Tracks Drawdowns
        ┌───────────────────────────┼───────────────────────────┐
        ▼                           ▼                           ▼
┌───────────────────────────┐ ┌───────────────────────────┐ ┌───────────────────────────┐
│   Benefit Disbursement    │ │   Benefit Disbursement    │ │   Benefit Disbursement    │
│ • Date: 2026-10-01        │ │ • Date: 2026-11-01        │ │ • Date: 2026-12-01        │
│ • Amount: $450.00         │ │ • Amount: $450.00         │ │ • Amount: $450.00         │
│ • Status: Disbursed       │ │ • Status: Disbursed       │ │ • Status: Scheduled       │
│ • Ref: EBT-TX-883019      │ │ • Ref: EBT-TX-914520      │ │ • Ref: Pending Batch Gen  │
└───────────────────────────┘ └───────────────────────────┘ └───────────────────────────┘

Reconciling Authorized Amounts vs. Actual Utilization

1. Cumulative Balance Monitoring: Automated roll-up logic and scheduled platform events aggregate BenefitDisbursement records against the parent BenefitAssignment. If a constituent is awarded a one-time emergency housing assistance grant of $3,000, disbursements to landlords ($1,500 for back rent and $1,500 for security deposit) increment the utilized amount. The platform automatically blocks any subsequent disbursement that would exceed the $3,000 authorized cap.
2. Pro-Rated Disbursements: When a constituent is approved midway through a calendar month, standard PSS workflows calculate pro-rated initial allotments (e.g., an approval on October 18 yields a pro-rated 13-day disbursement for October, followed by full monthly allotments on the 1st of each subsequent month).
3. Non-Financial Utilization & Attendance: For services quantified in hours (such as subsidized daycare) or physical sessions (such as vocational training), service providers log attendance using the Public Sector Partner Portal or Service Console. Each logged attendance record generates a BenefitDisbursement that draws down the authorized hours on the child's BenefitAssignment. If a parent is authorized for 40 hours of infant care weekly, the system alerts the caseworker if provider billings exceed 40 hours.
4. Disbursement Status Reconciliation: Disbursements transition across Scheduled, Submitted, Disbursed, Failed, and Cancelled. Integration Procedures call external state payment mainframes via Named Credentials. When the external mainframe returns an ACH confirmation or EBT settlement file, the BenefitDisbursement status updates to Disbursed with the external banking reference number. If a direct deposit bounces, the status updates to Failed, instantly notifying the caseworker.

---

💡 Real-World Exam Scenarios & Case Analysis

Scenario 1: Multi-Child Subsidized Daycare Allotment

A county Department of Social Services administers a childcare subsidy program. An applicant, Sandra Miller (a single mother), has two children: Marcus (age 2) and Chloe (age 7). Marcus requires full-time infant care (40 hours/week), while Chloe requires after-school care (15 hours/week). The county reimburses authorized licensed daycares directly on behalf of the family.

How must the Lead Architect structure this in Public Sector Solutions?

• Identity Architecture: Create three Person Accounts (Sandra, Marcus, Chloe). Link all three under a single Party Relationship Group representing the Miller Household. Assign Sandra the role of Head of Household and both children the role of Dependent Child via AccountContactRelation.
• Catalog Modeling: Under the Childcare Program, define two Benefit records: Full-Time Infant Daycare (Unit of Measure = Hours, Default Frequency = Weekly) and After-School Care (Unit of Measure = Hours, Default Frequency = Weekly).
• Entitlement Generation: Create two distinct BenefitAssignment records:
  • One for Marcus linked to Full-Time Infant Daycare with Quantity = 40, Frequency = Weekly.
  • One for Chloe linked to After-School Care with Quantity = 15, Frequency = Weekly.
• Disbursement Tracking: As the contracted childcare facility submits weekly attendance logs, generate BenefitDisbursement records against each child's respective BenefitAssignment, tracking billed hours and issuing vendor payments.

Scenario 2: Emergency Energy Assistance (LIHEAP) One-Time Vendor Payment

A municipal utility assistance agency approves a household for a one-time crisis heating grant of $650 under LIHEAP. The funds must be paid directly to Northern Gas & Electric (a commercial utility company) to prevent a gas shutoff, rather than disbursed to the citizen's personal bank account.

What configuration satisfies standard PSS best practices?

• Record the approval as an active BenefitAssignment for the constituent's Household Account with Quantity = 650.00, UnitOfMeasure = USD, and Frequency = One-Time.
• Create a BenefitDisbursement linked to the assignment with DisbursedAmount = 650.00.
• Populate the payment payee reference on the disbursement linking to the utility provider's standard Business Account (Northern Gas & Electric), ensuring the voucher and ACH batch output routes funds directly to the utility enterprise while decrementing the household's authorized LIHEAP allotment.