Considerations of Balance Initialization for Canada
In addition to the general guidance provided in the Overview of the Balance Initialization general help topic, consider the following when initializing balances for Canada.
- When initializing Workers’ Compensation balances, you must create the account information before processing the balance initialization.
- When initializing Provincial Medical balances, you must create the account information before processing the balance initialization.
- If there are associated Hours balances to the base balance (for example, Vacation and Vacation Hours), you must also initialize them. When initializing the Hours balance, the dimension must be the same as the associated base balance.
- When initializing Inception-to-Date (ITD) balances, the Payroll referenced in the batch must exist in the previous year and have payroll periods defined for that previous year. This is because the process attempts to create a balance initialization in the previous year. The process goes as far back as required to distinguish between the dimensions in the batch. For example, if the batch only contains a PTD and an ITD, it needs to go only as far back as the beginning of an earlier period to be able to satisfy the two rows written. If however there are YTD and ITD lines, it uses the first day in the year for YTD, and also needs a day earlier than that to set the ITD.
- Periods other than year-to-date may be required to be loaded, such as period-to-date or inception-to-date. Determination of what additional dimensions are required depends on when the upload activity takes place and the needs of the customer.
- Dimensions other than 'Relationship' may be required to be loaded, such as 'Assignment'. Determination of what additional dimensions are required depends on the level of the element. Taxes are calculated at the relationship level, so they require initialization of dimensions at the ‘Relationship’ level. Other elements may be created at the assignment levels; therefore dimensions must be initialized at that same level. For example, if an element is created at the Assignment level, the balance dimension to initialize is at that same level (‘Assignment Tax Unit Year to Date’ as an example).
- In many cases, specific dimensions are only valid for specific levels of
balances. This is primarily the case for provincial level taxes. For example,
for balance Provincial Tax Gross, the dimension Relationship Province Year to
Date refers to the fact that Province (Area1) must accompany the balance load to
indicate what jurisdiction the Provincial Tax Gross balance is related to. For
example, the numerical value of ‘19’ (Area1) refers to Quebec. The following is
what the Area context represents for Canada:
- Area1 identifies the province, entered as the numerical geography code for the province. Refer to the Geography Codes for Canadian Provinces topic.
For further information, see the section Considerations and Prerequisites for Balance Batches of the Overview of Balance Initialization topic in the Help Center.
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. For each context, there is a context name, and associated value. 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 a case where the Maintenance and Support involuntary deduction balance for the Relationship Tax Unit, Third Party Payee, Reference Code Year to Date dimension requires an additional context, in order to define the reference code, you would populate these values:
| Attribute | Value |
|---|---|
| ContextOneName | Reference Code |
| ContextOneValue | 123456 |
If the context you are 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)
For example, in one case where you need to populate the ContextOneName and ContextOneValue fields for the dimension Relationship Tax Unit, Statutory Report Type Year to Date, the following attributes should be populated:
| Attribute | Value |
|---|---|
| ContextOneName | Year End Forms |
| ContextOneValue | T4_RL1 |
Provincial Medical Example
As another example, in the case where you need to populate the ContextOneName and ContextOneValue fields for the dimension Relationship Tax Unit Province, Reference Code Year to Date for Provincial Medical balances, the following values should be populated:
| Attribute | Value |
|---|---|
| ContextOneName | Reference Code |
| ContextOneValue | PM_<Provincial Medical Account> |
Workers’ Compensation Example
In the case where you need to populate the ContextOneName and ContextOneValue fields for the dimension Relationship Province, Reference Code Year to Date for Workers’ Compensation balances, the following values should be populated:
| Attribute | Value |
|---|---|
| ContextOneName | Reference Code |
| ContextOneValue | WC_<Account number>_<Classification unit> |