Term
| Describe two steps used to generate the financial schedules in payment correction. |
|
Definition
- First a product delivery case is created and the reassessment information is used to create the evidence for the case.
- When that case is subsequently activated the evidence is used as the basis for the financial schedules. |
|
|
Term
Which of payment corrections could be delivered within the original PDC as opposed to creating a correction case.
- underpayment correction
- overpayment correction |
|
Definition
| - underpayment correction |
|
|
Term
|
Definition
- Payment Correction ( individual schedules for each component o/u paid )
- Overpayment ( single liability schedule)
- Underpayment (single benefit schedule) |
|
|
Term
| What is a name of configuration Option that allows to select between Payment Correction and one of legacy products? |
|
Definition
Use Rolled Up Reassessment
Products:
YES = use Payment Correction
NO = use Overpayment or Underpayment |
|
|
Term
| What three(3) options the "Automatic Overpayment Case Processing" allows to select. |
|
Definition
1. Create Case that requires Approval
2. Create, Approve, Activate (p. Corr. only)
3. Generate Task to let user consider creating a case. |
|
|
Term
| What two(2) options the "Automatic Underpayment Case Processing" allows to select. |
|
Definition
1. Create Case that requires Approval
2. Create Underpayment Component on the original PDC. |
|
|
Term
| What CBAS will do when the option "curam.miscapp.checkforliveliabilities" is set to 'YES' |
|
Definition
| When Underpayment is detected Always creates a separate case to deliver underpayment when liability exists. |
|
|
Term
| What the CBAS will do if the option "curam. miscapp. underpmtcase. createfornomineediff" has value 'YES' |
|
Definition
The default value of this property is 'YES', meaning that a separate case will always be created to deliver the underpayment when
the nominee currently assigned the component is not the nominee under-
paid. |
|
|
Term
| What will happen to correction case generation when the payment was cancelled and invalidated. |
|
Definition
If the underpayment correction is
for a period that has been paid, but the payment was cancelled and invalidated, then a separate case will always be created to deliver the under-
payment. |
|
|
Term
| What Correction PDC will always be automatically created, approved and activated. |
|
Definition
| - Net Zero Correction case |
|
|
Term
| Name some Product-wide configuration parameters that could impact assessment. |
|
Definition
• product periods;
• the product rules for eligibility/entitlement, key decision factors and decision details; and
• rate data |
|
|
Term
True or false:
Financial schedules will only be created from assessment determinations. |
|
Definition
|
|
Term
| Can the worker choose if the eligibility check uses "in edit" evidence or only Active evidence? |
|
Definition
|
|
Term
| Wher can the user see Snapshot Determinations? |
|
Definition
|
|
Term
| What is a "Coverage Period" in Curam. |
|
Definition
| Coverage period is a period of constant eligibility, entitlement and explanation for a determination. |
|
|
Term
A determination covers the full lifetime of the case.
True or false |
|
Definition
|
|
Term
| Name high level steps to arrive to eligibility data. |
|
Definition
1. Triggering action is intercepted;
2. Engine identifies product periods;
3. Engine uses CER rules to calculate eligibility and entitlement for each product period;
4. The Engine calculates the eligibility and entitlement across the lifetime of the case by "splicing together" the eligibility and entitlement from each contributing product period;
5. The Engine stores (on the database) a determination result containing the eligibility and entitlement data (as well as key decision factors and decision details, covered elsewhere in this document). |
|
|
Term
| What is Objective Tag in CER? |
|
Definition
An objective tag is a frequency at which an objective may be delivered.
Commonly for payment objectives, the objective will support a mixture of
delivery frequencies, e.g. daily and weekly. |
|
|
Term
| What is an Objective in CER? |
|
Definition
| An objective is something "delivered" by a product delivery case to a particular target. Commonly an objective is a payment of some kind of benefit or allowance paid to a client, but an objective could also be (for example) an amount to bill, or a non-monetary outcome. |
|
|
Term
| What are typical patterns that the creation of Objectives follows in CER? |
|
Definition
• Single Objective.
For a given objective type, there is always exactly one objective instance for the case; and/or
•
Multiple Objective.
For a given objective type, there is one objective instance for each member of the case who meets certain criteria. |
|
|
Term
| The actual number of financial components required to represent various financial schedules depends on: |
|
Definition
- nominee component assignments,
- nominee delivery patterns,
- period to which the schedule applies
- case decision objective tags |
|
|
Term
| Name what could lead to Financial Component being split within coverage period. |
|
Definition
Any changes to the component assignment during the cover period are used to split the initial virtual component into multiple, nominee specific parts.
Any changes to the nominee's delivery pattern during the cover period are used to split it again into multiple, delivery pattern specific parts. |
|
|
Term
| Into what three(3) Financial Components will the coverage period be split once the nominee and the delivery pattern splits are applied? |
|
Definition
- ramp-up financial component
- recurring financial component
- ramp-down financial component |
|
|
Term
| In what seven(7) ways could the the effective date for the financial component be calculated? |
|
Definition
- Issue in Advance
- Issue in Arrears
- Issue for Full Month
- Once-off Issue
- Issue in Advance - N Days Prior to Issue Date
- Issue in Arrears - N Days Prior to Issue Date
- Issue in Advance - on the Nth Day of Month Prior |
|
|
Term
| What the Case Decision Objective Tags determine? |
|
Definition
These are also defined in the rule set assigned to the product on which this
case is based. An Objective Tag represents how a particular objective is awarded for a specific period of time (from days to years). An objective may have several objective tags. For example, a Loan Parent benefit product may have two objective tags, one applying 'per day' and one 'per week'. An objective tag can be an amount of money or a formula that evaluates an amount of money for a specific objective. |
|
|
Term
| Can one deduction on a case result in multiple Instruction Line Items within a single payment. |
|
Definition
| Each active case deduction item defined for a case will result in the generation of one or more financial components depending upon the number of nominees affected. One or more deduction instruction line items will then be generated for each financial component. |
|
|
Term
| Name three financial settings that are configured for deduction processing on Benefit case. |
|
Definition
1. maximum deduction rate,
2. minimum deduction amount,
3. and minimum payment amount.
A minimum payment amount can be configured for all benefit products. This is the minimum amount of
money that a participant must receive after all deductions have been deducted from the total benefit
payment. |
|
|
Term
In order to create a deduction on a case, a deduction category must be selected.
True or False |
|
Definition
True
For example, if a deduction has a category
of "third party", then only deductions belonging to the third party category are displayed for selection when a user creates a third party deduction on the case. |
|
|
Term
Deduction categories available at the case level must first be configured as
part of deduction administration.
True or False |
|
Definition
|
|
Term
| What settings can be applied to deducted amount? |
|
Definition
- maximum amount
- minimum amount
- default amount |
|
|
Term
Can priority of the deduction be automatically assigned.
Yes/No |
|
Definition
|
|
Term
Are the overlappling deductions allowed?
Yes/No |
|
Definition
Yes.
By default, overlapping deductions are allowed on a case. This means that more than one deduction of the same type covering the same time period can be activated on a case. |
|
|
Term
| Can every deduction of a third party category be applied to every participant type. |
|
Definition
Participant type configuration defines the participant types available for selection as part of the create
applied and third party deduction processing.
he participant types available for configuration include
person, employer, external party, product provider, information provider, service supplier and utility. |
|
|
Term
| What are Case level settings for deductions? |
|
Definition
- Creating
- Selecting Category
- Entering Deduction Amount or Rate
- Assigning a Variable deduction to a Component
- Assigning a Variable Deduction to a Nominee
- defining deduction Start and End Dates
- Changing the Deduction priority
- Activating/Deactivating a Deduction
- Overriding the maximum deduction rate
- Cancelling the Deduction |
|
|
Term
| Name Workflow Events raised by Deductionprocesses. |
|
Definition
Activate Deduction
A workflow event is raised when a deduction is activated.
Deactivate Deduction
A workflow event is raised when a deduction is deactivated
Create Deduction
A workflow event is raised when a deduction is created.
Modify Deduction
A workflow event is raised when a deduction is modified.
Expire Deduction
A workflow event is raised when a deduction has naturally expired. A deduction naturally expires on the last date it is effective. |
|
|
