Public Sector Developer Guide

Public Sector Data Models
Public Sector Standard Objects
PublicSectrSltn Namespace
Public Sector APIs
Public Sector Standard Invocable Actions
Public Sector Tooling API Objects
Public Sector Metadata API Types
Public Sector Associated Objects
StandardValueSet Names and Standard Picklist Fields
Upload Files to Amazon S3
Accounting Subledger
Action Launcher
Business Rules Engine
Criteria-Based Search and Filter
Decision Explainer
Discovery Framework
Engagement
Group Membership and Households
Identity Verification
Intelligent Document Reader
Interest Tagging
Omnistudio Business REST APIs
Outcome Management Developer Guide
Record Alerts
Record Rollup Definitions
Service Process Studio
Tax and Revenue Management
Ingest Tax Data into Data 360
Identity Resolution for Tax and Revenue
Tax and Revenue Connect API
Data Governance Policies for Tax Data
Timeline
PDF

Identity Resolution for Tax and Revenue

Create an Identity Resolution ruleset that links agency-ingested taxpayer records to CRM-synced records by using a Tax Identification Number match. This allows the taxpayer portal to show each taxpayer's own data when they log in.

Before configuring Identity Resolution, complete both phases of data ingestion:

  • Salesforce object mappings (Account, Contact, IdentityDocument) via the CRM connector
  • Agency-side Account and PartyIdentification records, plus tax agency data in the Tax and Revenue DMOs

See Ingest Tax Data into Data 360.

Salesforce and Data 360 are independent systems. Identity Resolution (IR) links the two by finding records that represent the same real-world taxpayer: the CRM-synced records created at portal registration and the tax agency records ingested from your systems. IR then merges them into a single Unified Account profile.

The IR rule for Tax and Revenue uses an exact match on PartyIdentification.IdentificationNumber with a filter for SSN (Social Security Number) identification type. When a match is found, IR creates link records connecting the Unified profile to each source record.

When a taxpayer logs in to the portal, the Connect API resolves their identity by using this path:

  • ContactId (from the authenticated portal session)
  • → mapped Account (CRM-synced)
  • → AccountIdentityLink → UnifiedRecordId
  • → all source party IDs linked to that Unified profile
  • → TaxAccount WHERE AccountId matches → TaxFilingTaxAccount → TaxFiling → children

IR isn't real-time. It runs on a schedule (several times per day). Immediately after a taxpayer registers, IR hasn't yet linked their records, so the portal correctly shows that "no data found". This is expected behavior, not an error. To test the full data-visible path in a test org, either wait for a scheduled IR run or trigger one manually.

Important

Create the Identity Resolution Ruleset

Create an Identity Resolution ruleset scoped to the Account DMO with a custom match rule on PartyIdentification.IdentificationNumber.
  1. In the Data 360 app, click Identity Resolutions, and then click New.
  2. Select Create New Ruleset, and then click Next.
  3. Select your Tax and Revenue Data Space.
  4. Set Primary data model object to Account.
    Account, not Contact or Individual, is the primary DMO for Tax and Revenue Identity Resolution. At runtime, this resolves through AccountIdentityLink, not IndividualIdentityLink.
  5. Optionally enter a ruleset ID, and then click Next.
  6. Enter a ruleset Name, and then click Save.
  7. On the ruleset page, go to the Match Rules section and click Edit.
  8. Click Next.
  9. Click Add Match Rule, select Custom Rule, and then click Next.
  10. Configure the match criteria.
    1. Set data model object to PartyIdentification.
    2. Set Field to IdentificationNumber.
    3. Set Match Method to Exact.
    4. Click Configure under Advanced Settings.
    5. Set Party Identification Type to SSN.
    6. Click Back to Basic Settings and confirm that Advanced Settings shows Applied.
  11. Click Next and save the match rule settings.

Run the Identity Resolution Ruleset

Manually trigger an Identity Resolution run in a test org to verify that agency records and CRM records merge into a single Unified Account profile.

In production, IR runs automatically on a schedule several times per day. In test orgs, trigger it manually after loading test data to verify the full end-to-end path: taxpayer registers → CRM connector syncs → IR links records → portal shows taxpayer's data.

  1. In the Data 360 app, click Identity Resolutions.
  2. Select your Tax and Revenue ruleset.
  3. Open the dropdown, and click Run Ruleset.
  4. After the run completes, verify that link records exist connecting the CRM-sourced Account and the agency-sourced Account to the same UnifiedRecordId.