HCM Data Loader Enhancement for US Tax Withholding

We have simplified the process of updating employee Tax Withholding cards through the HCM Data Loader (HDL).

Whenever we update the Federal, State, County, City, or Pennsylvania PSD components on the card, we now add a unique date-effective row to the HDL business object file.

As of this release, the data file includes these rows.

METADATA	Notes
TaxWithholding	Identifies your business object file as updating the Tax Withholding card. Your file must include this component as its first row.
FederalTaxes	Identifies the Federal component on the tax card. Your file must include this component if you’re updating any federal fields.
FederalTaxesBase	Represents all fields and values on the Federal component from 1/1/2016 to 12/31/2019. Any changes to the Federal component since then are covered by subsequent rows, such as FederalTaxes2023.
StateTaxesXX	Where XX is the state postal abbreviation. Identifies the associated state Regional component on the tax card. Your file must include this component if you’re updating any fields for that state.
StateTaxesXXBase	Where XX is the state postal abbreviation. Represents all fields and values on the state’s component. Any changes to the component since then are covered by subsequent rows, such as StateTaxesAK2024.
PennsylvaniaPSD	Identifies the Pennsylvania PSD component on the tax card. Your file must include this component if you’re updating any fields on this component.
PennsylvaniaPSDBase	Represents all fields and values on the Pennsylvania PSD component. Any changes to the component since then are covered by subsequent rows.
CountyTaxes	Identifies a county Regional component on the tax card. Your file must include this component if you’re updating any fields on any of the county components.
CountyTaxesBase	Represents all fields and values on county Regional components. All changes to county taxes are maintained in this row.
CityTaxes	Identifies a city Regional component on the tax card. Your file must include this component if you’re updating any fields on any of the city components.
CityTaxesBase	Represents all fields and values on city Regional components. All changes to city taxes are maintained in this row.
USTaxation USTaxationBase	Represent US tax data.  It is not recommended you use these components except during initial record creation for an employee.

For federal, state, and Pennsylvania PSD taxes, we will add a row to this file for any of these changes.

• Add or remove a field
• Change a field, including its label, type, eligible values, or default value
• Changes to fields whose values are derived by other fields, such as different allowances contributing to total allowances
• Add, remove, or change validation on a field, such as requiring entry in increments of $500

For example:

• FederalTaxes2020:  Includes tax card changes implemented 1/1/2020
• FederalTaxes2023:  Includes the tax card change that introduced the Nonresident Alien field, effective 1/1/2023

Building on our Tax Withholding HCM Data Loader (HDL) business object functionality released in 24A, we have increased the ease of use by providing unique rows anytime there is a field or value change in the Tax Withholding component.  In the new business object file, there is now a unique date effective row for component data entry, for any of the following changes to the component.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• The new row headers follow this naming convention.
  • For component changes effective January 1, it is suffixed with the year, such as FederalTaxes2025.
  • For changes on the first of a month other than January, it is suffixed with YYYYMM, where YYYY is the effective year and MM is the first of the effective month, such as StateTaxesVT202407.
  • For changes effective on a day other than the first of the month, it is suffixed with YYYYMMDD, where YYYY is the effective year, MM is the effective month, and DD is the effective day, such as StateTaxesIN20230915.
• Before you start building your HDL business object file, always be sure to download the latest version.
  1. Start the View Business Objects task.
  2. Search for the Tax Withholding business object.
  3. Download the .dat file.
• When creating your business object file, you must maintain good data hygiene for your tax cards.  For complete info, refer to the Oracle Fusion Cloud HCM Data Loader guide in the Help Center.
  • A Tax Withholding calculation card must have a continuous active Federal component with an edit record without any gaps.
  • If you don't provide a state Regional component for a state that imposes resident tax or work taxes, the payroll process uses default values for tax calculation.
  • If you don't provide a county Regional component for a county that imposes resident tax or work taxes, the payroll process uses default values for tax calculation.
  • If you don't provide a city Regional component for a city that imposes resident tax or work taxes, the payroll process uses default values for tax calculation.
• You don’t need to include higher-level components (such as federal or state) when modifying subordinate component info (such as city or county).  For example, you can define a StateTaxesNY component without a FederalTaxes component.

Key Resources

See the following in the Help Center.

• Oracle Fusion Cloud HCM Data Loader
• Guidelines for Loading US Tax Withholding Cards
• Guidelines for Loading US State Taxes Card Components