Tax and Revenue Management

Architecture Overview

The Taxpayer 360 Data Model is a set of Data 360 DMOs that represent the complete tax lifecycle for a taxpayer. From their identity and tax accounts through filings, line items, assessments, payments, and supporting documents. Agencies ingest data from back-office systems into these DMOs by using Data 360 data streams. Corrections and amendments to the model must be done by creating records chained via foreign keys rather than overwriting existing records.

The data model integrates with standard Salesforce CRM data (Account, Contact) and Data 360 platform DMOs (Individual, PartyIdentification, PaymentInstrument, DigitalContent) that are synced from CRM via the CRM connector. Identity Resolution links the agency-ingested taxpayer records to the CRM-synced records by matching on TIN in PartyIdentification.IdentificationNumber.

See the Tax and Revenue data model in the Public Sector Data Model Gallery.

Before continuing with the developer guide, set up your org to use the Tax and Revenue features. See Set Up Tax and Revenuein Agentforce Public Sector Help.

Data Space Naming

The DMO API names that you use in queries depend on which data space your org uses for Tax and Revenue data.

Decide on the target data space before configuring ingestion, identity resolution, or Connect API queries. To learn more about setting up the data space, see Set Up Tax and Revenue in Salesforce Help.

DMO Dependency Tiers

Load DMOs in this order to avoid dangling foreign keys. Every parent record must exist before child records that reference it are ingested. The tiers reflect a topological sort of the foreign key graph.

Required System Fields

Every Tax and Revenue DMO record must include these system fields. Populate them in your ingestion mapping.

Platform SSOT DMOs

These DMOs are standard Data 360 platform objects, not Tax and Revenue-specific. They're shared across Data 360 features and may already exist in your org.

Individual

Represents an individual person. Created via CRM connector sync of the Contact object, or ingested directly from the tax agency's data. Used as a party reference in tax DMOs.

Account

Represents an organization or individual taxpayer account. Created via CRM connector sync of the Account object, or ingested from the tax agency's system.

PartyIdentification

Stores taxpayer identity documents—TIN, SSN, EIN, PAN, NINO, and so on. Created via CRM connector sync of the IdentityDocument object, or ingested directly. The IdentificationNumber field on this DMO is the match key used by identity resolution.

PaymentInstrument

Represents a payment method—bank account, check, or card. Referenced by TaxPaymentDmo and TaxFilingPaymentInstrumentDmo.

DigitalContent

Holds document file bytes. Referenced by TaxDocumentDmo when stored document content is loaded into Data 360. Required only if your agency stores document files in Data 360 directly.

ContactPointAddress

Represents a mailing or physical address associated with a party.

Portal-Referenced Fields

This table lists the fields that each DMO exposes to the self-service Taxpayer Portal. Ingest all DMO field mappings. These are fields that the portal queries actually reference.