Reference for the Data 360 data model objects (DMOs) that make up the Taxpayer 360 Data Model in Tax and Revenue Management for Public Sector Solutions.
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 item filings and assessments, refunds, 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 connects standard Salesforce data with Data 360 platform DMOs. From Salesforce, the data model uses the Account object as the taxpayer anchor and the taxpayer’s identification number. The tax ID is read from either the standard IdentityDocument object or from a custom field on the Account object. The data model uses the Data 360 platform DMOs Individual, PartyIdentification, PaymentInstrument, and ContactPointAddress.
The Tax and Revenue Management Data Kit syncs the Salesforce data into Data 360. The kit maps the Account object to the Account DMO (Individual DMO for person accounts), and the IdentityDocument object to the PartyIdentification DMO.
To link the agency-ingested taxpayer records to the Salesforce-synced records, identity resolution matches the tax identification number with 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 Revenue in Agentforce Public Sector Help.
Decide on the target data space before configuring ingestion, identity resolution, or Connect API queries. Every downstream step relies on a configured data space. To learn more about setting up the data space, see Set Up Tax and Revenue in Salesforce Help.
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.
| Tier | DMO | Foreign Key Dependencies |
|---|---|---|
| 0—Foundations | Salesforce: AccountDMO, PartyIdentificationDMO Tax Agency: Account, PartyIdentification, Individual, ContactPointAddress | Also created via the Tax and Revenue Management Data Kit mappings for Account and IdentityDocument. Load before all tax DMOs. |
PaymentInstrumentDMO | Platform SSOT DMO. No tax-DMO foreign keys. | |
TaxTypeDMO | No tax-DMO foreign keys. Categories: Income, Payroll, GST, VAT, and so on. | |
| 1 | TaxTypePeriodDMO | TaxType. Filing periods: FY2025, Q1 2025, and so on. |
| 2 | TaxAccountDmo | Account, PartyIdentification, TaxType. The hub that most tax data depends on—represents a taxpayer’s account per authority per tax type. |
| 3 | TaxFilingDmo | TaxAccount, TaxTypePeriod. Self-FK: AmendedFromFiling. Load originals before amendments. |
| 4 | TaxFilingTaxAccountDmo | Junction. → TaxFiling, TaxAccount. |
TaxFilingParticipantDmo | TaxFiling, Individual, Account, PartyIdentification. | |
TaxDocumentDmo | TaxAccount, TaxTypePeriod, DigitalContent. Self-FK: OriginalDocument. Load originals before corrected docs. | |
TaxPaymentDmo | TaxAccount, TaxFiling, TaxTypePeriod, PaymentInstrument. | |
TaxRefundDmo | → TaxFiling, TaxTypePeriod, TaxAccount, PaymentInstrument. Self-FK: OriginalRefund. Load original refunds before reissued refunds. | |
TaxFilingPaymentInstrumentDmo | Junction. → TaxFiling, PaymentInstrument. | |
TaxFilingContactPointDmo | TaxFiling, ContactPointAddress. Load after Tax Filing and Contact Point Address. | |
| 5 | TaxFilingLineItemDmo | TaxAccount, TaxFiling, TaxFilingParticipant. Self-FK: ParentLineItem. Load parent line items before children. |
TaxFilingAssessmentDmo | TaxFiling. Self-FK: PreviousAssessment. Load in assessment-cycle order. | |
TaxDocumentItemDmo | TaxDocument. Self-FK: parent line item. Holds third-party info-return lines (W-2, 1099, Form 16). Formerly TaxDeclarationItemDmo. | |
TaxFilingDocumentDmo | Junction. → TaxFiling, TaxDocument. | |
| 6 | TaxFilingAssessmentLineItemDmo | TaxFilingAssessment, TaxFilingLineItem, TaxFilingParticipant, TaxAccount. Self-FK: parent line item. Formerly TaxFilingLineItemAssessmentDmo. |
TaxFilingLineItemDocumentDmo | Junction. → TaxFilingLineItem, TaxDocument. | |
TaxFilingAssessmentDocumentDmo | Junction. → TaxFilingAssessment, TaxDocument. | |
| 7 | TaxFilingAssessmentLineItmDocDmo | Junction. → TaxFilingAssessmentLineItem, TaxDocument. |
Every Tax and Revenue DMO record must include these system fields. Populate them in your ingestion mapping.
| Field | Description |
|---|---|
DataSourceId | Identifies the source system that produced this record. |
DataSourceObjectId | The source system’s unique identifier for this record. |
InternalOrganizationId | Identifies the Salesforce org. Required for all ingested records. |
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.
Represents an individual person ingested directly from the tax agency's data.
Represents an organization or individual taxpayer account. Created via CRM connector sync of the Account object or ingested from the tax agency's system.
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. In the portal query contract, fields on this DMO are optional. Identity Resolution still matches on IdentificationNumber.
Represents a payment method—bank account, check, or card. Referenced by TaxPaymentDmo and TaxFilingPaymentInstrumentDmo.
Represents a mailing or physical address associated with a party.
Field names, types, and which mappings the portal queries require are in Fields the Tax Portal Queries.
Field names, types, and query requirements for the data model objects the taxpayer portal reads.
Deploy the Tax and Revenue Management Data Kit for Salesforce CRM mappings, and use data streams to load tax agency data into the Taxpayer 360 Data Model DMOs.
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.
Reference for the Connect REST resources the self-service Taxpayer Portal uses to retrieve the logged-in taxpayer’s records from the Tax and Revenue data model objects.
Data Governance Policies for Tax Data
Create DENY and MASK data governance policies to block or redact sensitive internal fields from taxpayer portal queries.
j
