Overview of Balance Initialization for the US
The US Legislative Balances are balances that Oracle Payroll Cloud uses to perform accurate tax reporting and payroll tax calculations, such as for W-2 reporting and State Quarterly Wage Listings.
Whether they're required or not, that's determined at the individual employee level. For example, if an employee doesn't participate in the company 401 (k) plan, the Deferred Compensation 401k balance isn't needed for that employee.
For a list of the balances to load, supported dimensions and the process overview, refer to the document below in the US Information Center.
US Information Center
https://support.oracle.com/rs?type=doc&id=2063588.2
US Legislative or User-defined Context Columns
There are six legislative or user-defined contexts, which must be populated if the balance dimension expects a value for these contexts. These contextual values are used because columns are not available to populate legislative or user-defined data. Instead, they require entry in the user-defined context columns as outlined below. For each context, there is a context name and value attribute. For example:
- ContextOneName
- ContextOneValue
Populate the context name attributes with the name of the context usage for that legislative or user-defined context, and the context value attributes with the actual value of that context.
For example, in case the Child Support involuntary deduction balance for the Relationship Tax Unit, Third Party Payee and Reference Code Year to Date dimension requires an additional context, in order to define the child support reference code, you populate these values:
| Attribute | Value |
|---|---|
| ContextOneName | Reference Code |
| ContextOneValue | 123456 |
If the context you're populating is a lookup, populate the context fields in the following manner:
- Context Name: Populate with the lookup type meaning
- Context Value: Populate with the lookup code (not the lookup type meaning)
Let's take another example. If you need to populate the Context One Name and Context One Value fields for the Relationship Tax Unit, Area1, Tax Unit2, Area5,6 Year to Date dimension for PA Act 32 balances, you would populate these values:
| Attribute | Value |
|---|---|
| ContextOneName | Area5 |
| ContextOneValue | 700102 |
| ContextTwoName | Area6 |
| ContextTwoValue | 220401 |
| ContextThreeName | Tax Unit 2 |
| ContextThreeValue | 22 |
These legislative contexts are required only if the employee’s work or residence is in a jurisdiction subject to Pennsylvania Act 32.
The meanings of the additional PA Act 32 contexts are:
- Area5 = Resident Political Subdivision (PSD) Code
- Area6 = Work PSD Code
- Tax Unit 2 = Tax Collection District Code
Area attributes for Initializing US Balances
Along with the core attributes, details of which are available in the View Business Objects task, there are area attributes that may be relevant for your US balances:
| HCM Data Loader Attribute | Functional Description |
|---|---|
| AreaOne |
State information for the balance value. Supply the geocode for the state. For more information, refer to Template: BI Publisher Report: United States - State, County and City Geography Codes |
| AreaTwo |
County information for the balance value. Supply the geocode for the county. For more information, refer to Template: BI Publisher Report: United States - State, County and City Geography Codes |
| AreaThree |
City (or tax district for Pennsylvania) information for the balance value. Supply the geocode for the city, or tax district for Pennsylvania. For more information, refer to Template: BI Publisher Report: United States - State, County and City Geography Codes |
| AreaFour |
School district information for the balance value. Supply the geocode for the school district. |