This page (revision-5) was last changed on 26-Nov-2021 10:22 by JEscott

This page was created on 26-Nov-2021 10:22 by KateN

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
5 26-Nov-2021 10:22 1 KB JEscott to previous
4 26-Nov-2021 10:22 1 KB JMyers to previous | to last
3 26-Nov-2021 10:22 1 KB JEscott to previous | to last
2 26-Nov-2021 10:22 1 KB KateN to previous | to last
1 26-Nov-2021 10:22 1 KB KateN to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 2 changed 9 lines
In order to run the remittance reports the Remittance Update must be run to collect all of the benefit line information and send it to the remittance history tables.
\\
\\
__The Update Benefit Remittance process uses the 'Last Remit Date' on the plan to ensure
that it is not rerunning for a period already processed and to ensure that no periods have
been skipped. During testing ensure that the 'Last Remit Date' is for the period before
the one selected in the report parameter.__
\\
\\
!!Processing Information
In order to run the [remittance|BENEFIT REMITTANCES] reports the Remittance Update must be run to collect all of the benefit line information and send it to the remittance history tables.
The Update Benefit Remittance process uses the 'Last Remit Date' on the plan to ensure that it is not rerunning for a period already processed and to ensure that no periods have been skipped. During testing ensure that the 'Last Remit Date' is for the period before the one selected in the report parameter.
----
!!Report Parameters & Filters
At line 12 changed 6 lines
|__Calendar__|__Mandatory, LOV available__\\Determine which business calendar is to be used.
|__Calendar Period__|__Mandatory, LOV available__\\Determines the period within the calendar specified for which the benefit lines are to be processed.
|__Trial__|__Mandatory, LOV available, defaults as <No>__\\If ‘No’ then the Update is committed. If ‘Yes’ then the Update is not committed and the process may be run again.
|__Exception Level__|__Mandatory, LOV available, defaults as <Exceptions Only>__\\The level of logging desired.
\\
\\
|Calendar|Mandatory, LOV available\\Determine which business calendar is to be used.
|Calendar Period|Mandatory, LOV available\\Determines the period within the calendar specified for which the benefit lines are to be processed.
|Trial|Mandatory, LOV available, defaults as <No>\\If ‘No’ then the Update is committed. If ‘Yes’ then the Update is not committed and the process may be run again.
|Exception Level|Mandatory, LOV available, defaults as <Exceptions Only>\\The level of logging desired.
At line 15 added 8 lines
|Entity|Mandatory, LOV available\\Limits the process to the entity specified.
|Plan Type|Mandatory, Multiple selection, and LOV available\\The benefit plan types to be processed for the employees selected.
|Plan|Mandatory, Multiple selection, and LOV available\\The benefit plan to be processed for the employees selected.
----
![Notes|Edit:Internal.UBRH]
[{InsertPage page='Internal.UBRH' default='Click to create a new notes page'}]