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.
Before you ingest tax data, complete these steps:
Corrections and amendments must be loaded as new records with a foreign key back to the original, not as overwrites. Records that violate the topological ingestion order (tier by tier) land with dangling foreign keys and fail to resolve at query time.
Important
Ingestion happens in three phases. First, deploy the Tax and Revenue Management Data Kit to map Account to Account and Party and IdentityDocument (or custom field on Account) to PartyIdentification. These mappings create the platform SSOT records that tax DMOs depend on, including the PartyIdentification records used by Identity Resolution. Second, ingest agency-side Account, PartyIdentification, Individual, and ContactPointAddress records that represent taxpayers in the tax agency system of record. Third, ingest the tax-specific DMOs from your agency by using a connector that fits your stack (S3, MuleSoft, or another supported connector).
Deploy the Tax and Revenue Management Data Kit so Account and IdentityDocument map to platform SSOT DMOs before tax data ingestion begins.
The data kit deploys the default mappings for Account and IdentityDocument. Account maps to Account and Party. IdentityDocument maps to PartyIdentification. Those default mappings are sufficient for identity resolution. Manual CRM data streams are the alternate path.
From Setup, in the Quick Find box, enter Data Kits, and then select Data Kits.
Select Tax and Revenue Management Data Kit.
Click Data Kit Deploy, enter the data space and org ID, and then click Deploy.
After the data kit or the manual streams finish the initial sync, ingest tax agency data.
Create CRM data streams for Account and IdentityDocument as the alternate to the Tax and Revenue Management Data Kit.
Skip this task when you deploy the Tax and Revenue Management Data Kit. The data kit applies the default mappings.
In the Data 360 app, click Data Streams, and then click New.
Select Salesforce CRM as the source, and then select your connected org.
Select All Objects, and then find Account.
Set the Category to Profile and the Primary Key to Id.
Click Next, set the Data Space to your Tax and Revenue data space, review the fields, and then click Deploy.
Repeat for IdentityDocument.
Map the data lake object fields to the PartyIdentification DMO. Include IdentificationNumber and IdentificationType. Identity Resolution uses these fields to match taxpayer records.
Create data streams to ingest tax agency identification data into Account, PartyIdentification, Individual, and ContactPointAddress. These agency-side records are distinct from the CRM-synced records created in the previous task.
When you later ingest TaxAccountDmo, set AccountId to the agency-side AccountId from this step and not the CRM-synced AccountId.
In the Data 360 app, click Data Streams, and then click New.
Select your connector (for example, Amazon S3 or MuleSoft).
Configure the connection to your agency’s data source.
Map source fields to Account, and then deploy the stream with Object Type set to Other and the Data Space set to your Tax and Revenue data space.
Repeat for PartyIdentification, Individual, and ContactPointAddress.
Confirm that each stream populates DataSourceId, DataSourceObjectId, and InternalOrganizationId on every record.
Use a Data 360 connector to load tax agency data into the Tax and Revenue DMOs in the correct topological order.
Before ingesting tax DMOs, complete the CRM mappings for Account and IdentityDocument, and complete agency-side Account, PartyIdentification, Individual, and ContactPointAddress ingestion.
The steps apply to any connector. The key requirement is ingesting DMOs tier by tier, parents before children. For available connector options, see Data 360 Connectors and Integrations.
In the Data 360 app, click Data Streams, and then click New.
Select your connector (for example, Amazon S3 or MuleSoft).
Configure the connection to your agency’s data source.
Map source fields to the target DMO fields.
See Fields the Tax Portal Queries for the fields the self-service Taxpayer Portal reads. Map every Required field. A missing Optional field omits that column and the rest of the view still returns.
Set Object Type to Other.
Set the Data Space to your Tax and Revenue data space.
Click Deploy.
Repeat for each DMO, following the tier order in DMO Dependency Tiers. Load DMOs in this sequence:
Tier 0: TaxTypeDmo (CRM-synced Individual, Account, and PartyIdentification, plus agency-side Account, PartyIdentification, Individual, and ContactPointAddress from the previous tasks, must already exist. Confirm PaymentInstrument and DigitalContent load paths with your SME.)
Tier 1: TaxTypePeriodDmo
Tier 2: TaxAccountDmo—AccountId must point to the agency-side AccountId
Tier 3: TaxFilingDmo—load original filings before amendments
Tier 4: TaxFilingTaxAccountDmo, TaxFilingParticipantDmo, TaxDocumentDmo (originals before corrected docs), TaxPaymentDmo, TaxRefundDmo (original refunds before reissued refunds), TaxFilingPaymentInstrumentDmo, TaxFilingContactPointDmo
Tier 5: TaxFilingLineItemDmo (parent line items first), TaxFilingAssessmentDmo (in assessment-cycle order), TaxDocumentItemDmo, TaxFilingDocumentDmo
Tier 6: TaxFilingAssessmentLineItemDmo, TaxFilingLineItemDocumentDmo, TaxFilingAssessmentDocumentDmo
Tier 7: TaxFilingAssessmentLineItmDocDmo
Confirm that each stream populates DataSourceId, DataSourceObjectId, and InternalOrganizationId on every record.
These three system fields are required on every DMO record. Records that omit them fail validation.
After ingesting both core and tax data, configure identity resolution to link the agency-ingested party records with the CRM-synced records. See Identity Resolution for Tax and Revenue.
j
