1. What is the Tax Jurisdictions card for the US?
  2. Override Resident Tax Jurisdiction for Multiple Employees Using HDL

Override Resident Tax Jurisdiction for Multiple Employees Using HDL

To apply resident tax jurisdiction overrides to multiple employees, use an HCM Data Loader (HDL) file with the CalculationCard business object.

To override the system-derived resident tax jurisdictions, you must include an override component:

  1. Include the CalculationCard METADATA block for each employee card you're updating.

    For this attribute

    This is what you enter

    LegislativeDataGroupName

    LDG of the card you're updating

    DirCardDefinitionName

    Tax Jurisdictions

    AssignmentNumber

    PayrollRelationshipNumber

    Identifiers of the employee owning the card

    EffectiveStartDate

    Start date of the card

    This is usually the employee's hire date.

    CardSequence

    Unique numerical identifier for the card

    • For employees with multiple cards, this is a sequential identifier, based on the order the card was created, starting with 1.

    • For employees with only one card, this is always 1.

    For example:

    METADATA|CalculationCard|LegislationDiscriminator|LegislativeDataGroupName|DirCardDefinitionName|DirCardDefinitionId|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|LegislativeDataGroupId|SourceSystemOwner|SourceSystemId|CardSequence|DirCardId|TaxRepUnitName|PayrollStatutoryUnitName
MERGE|CalculationCard||ZHRX_USVS_ST LDG One|Tax Jurisdictions||E955940008195913|2024/01/01|4712/12/31||||1|||

  2. For each card you are modifying, add a CardComponent METADATA block to create the Override component.

    For this attribute

    This is what you enter

    DirCardCompId

    AssignmentNumber

    PayrollRelationshipNumber

    Identifiers of the employee owning the card

    EffectiveStartDate

    Start date of the card component

    EffectiveEndDate

    End date of the card component

    ComponentSequence

    CardSequence

    Unique numerical identifier for the card

    • For employees with multiple cards, this is a sequential identifier, based on the order the card was created, starting with 1.

    • For employees with only one card, this is always 1.

    DirCardCompDefId

    DirCardCompDefName

    LegislativeDataGroupName

    LDG of the card you're updating

    DirCardDefinitionName

    Context1

    State's 2-digit Geocode identifier

    Context2

    Not used for jurisdiction overrides

    Context3

    Not used for jurisdiction overrides

    Context4

    Not used for jurisdiction overrides

    Context5

    Not used for jurisdiction overrides

    Context6

    Not used for jurisdiction overrides

    ParentDirCardCompId

    DirCardId

    SourceSystemOwner

    TaxRepUnitName

    PayrollStatutoryUnitName

    ParentDirCardCompDefName

    ParentComponentSequence

  3. For each override you're making, add a CalculationValueDefinition METADATA block.

    For this attribute

    This is what you enter

    EffectiveStartDate

    Start date of the override

    EffectiveEndDate

    End date of the override

    LegislativeDataGroupName

    LDG of the card you're updating

    ValueDefinitionName

    AssignmentNumber

    PayrollRelationshipNumber

    Identifiers of the employee owning the card

    DirCardDefinitionName

    DirCardCompDefName

    SourceId

    SourceSystemOwner

    ComponentSequence

    CardSequence

    Unique numerical identifier for the card

    • For employees with multiple cards, this is a sequential identifier, based on the order the card was created, starting with 1.

    • For employees with only one card, this is always 1.

    Context1

    State's 2-digit Geocode identifier

    Context2

    Context3

    TaxRepUnitName

    PayrollStatutoryUnitName

  4. For each override you're making, add a EnterableCalculationValue METADATA block.

    This block identifies the calculation value definition associated with the field.

    For this attribute

    This is what you enter

    EffectiveStartDate

    Start date of the override

    EffectiveEndDate

    Date when you discontinue the override

    LegislativeDataGroupName

    LDG of the card you're updating

    ValueDefinitionName

    AssignmentNumber

    PayrollRelationshipNumber

    Identifiers of the employee owning the card

    DirCardDefinitionName

    DirCardCompDefName

    Value1

    ValueDefnId

    SourceSystemOwner

    SourceSystemId

    ComponentSequence

    CardSequence

    Unique numerical identifier for the card

    • For employees with multiple cards, this is a sequential identifier, based on the order the card was created, starting with 1.

    • For employees with only one card, this is always 1.

    TaxRepUnitName

    PayrollStatutoryUnitName

    Here's an example that defines County, City, and Within City Limits overrides.

    METADATA|CardComponent|DirCardCompId|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|ComponentSequence|CardSequence|DirCardCompDefId|DirCardCompDefName|LegislativeDataGroupName|DirCardDefinitionName|Context1|Context2|Context3|Context4|Context5|Context6|ParentDirCardCompId|DirCardId(SourceSystemId)|SourceSystemOwner|SourceSystemId|TaxRepUnitName|PayrollStatutoryUnitName|ParentDirCardCompDefName|ParentComponentSequence

METADATA|CalculationValueDefinition|EffectiveStartDate|EffectiveEndDate|LegislativeDataGroupName|ValueDefinitionName|AssignmentNumber|DirCardDefinitionName|DirCardCompDefName|SourceId(SourceSystemId)|SourceSystemOwner|SourceSystemId|ComponentSequence|CardSequence|Context1|Context2|Context3|TaxRepUnitName|PayrollStatutoryUnitName

METADATA|EnterableCalculationValue|EffectiveStartDate|EffectiveEndDate|LegislativeDataGroupName|ValueDefinitionName|AssignmentNumber|DirCardDefinitionName|DirCardCompDefName|Value1|ValueDefnId(SourceSystemId)|SourceSystemOwner|SourceSystemId|ComponentSequence|CardSequence|TaxRepUnitName|PayrollStatutoryUnitName

MERGE|CalculationCard||ZHRX_USVS_ST LDG One|Tax Jurisdictions||E955940008195913|2024/01/01|4712/12/31||||1|||
MERGE|CardComponent||E955940008195913|2024/04/01|4712/12/31|1|1||Resident Tax Jurisdictions Override|ZHRX_USVS_ST LDG One|Tax Jurisdictions|36||||||||||||Resident Tax Jurisdictions|1

MERGE|CalculationValueDefinition|2024/04/01|4712/12/31|ZHRX_USVS_ST LDG One|County|E955940008195913|Tax Jurisdictions|Resident Tax Jurisdictions Override||||1|1|||||

MERGE|EnterableCalculationValue|2024/04/01|4712/12/31|ZHRX_USVS_ST LDG One|County|E955940008195913|Tax Jurisdictions|Resident Tax Jurisdictions Override|113||||1|1||

MERGE|CalculationValueDefinition|2024/04/01|4712/12/31|ZHRX_USVS_ST LDG One|City|E955940008195913|Tax Jurisdictions|Resident Tax Jurisdictions Override||||1|1|||||
MERGE|EnterableCalculationValue|2024/04/01|4712/12/31|ZHRX_USVS_ST LDG One|City|E955940008195913|Tax Jurisdictions|Resident Tax Jurisdictions Override|3040||||1|1|| 

MERGE|CalculationValueDefinition|2024/04/01|4712/12/31|ZHRX_USVS_ST LDG One|Within City Limits|E955940008195913|Tax Jurisdictions|Resident Tax Jurisdictions Override||||1|1|||||

MERGE|EnterableCalculationValue|2024/04/01|4712/12/31|ZHRX_USVS_ST LDG One|Within City Limits|E955940008195913|Tax Jurisdictions|Resident Tax Jurisdictions Override|E||||1|1||