Notification Handler (NOHL) 111-26010010
Expand allThis page contains both a summary and a detailed explanation of the Notification Handler (NOHL) rules.
On this Page:
NOHL Rules summary index
Index of NOHL Rules summary details
Table 1: This table contains a list of Notification Handler (NOHL) rules. Click on the selected rule to jump to a summary of the rule.
|
Items |
Rules |
|
NOHL Rules summary See also: |
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 22, 23, 31, 32, 33, 34, 35. 37, 38, 39, 40, 42, 43, 44, 45, 98, 99 FAO The rules have been broken up into 3 categories: New Claims, Reassessments and Retrospective Reassessments. New Claims
Reassessments Rules 33, 34, 40, 43, 44 and 45 deal with what is known as 'deferring' the effect of an event on a customer's entitlement, unlike rule 32 which takes the event into account from when it happened.
Retrospective Reassessments Referral to FCC SSO Refer any queries about the operation of the NOHL rules, or where NOHL has deferred payment of arrears until reconciliation and the customer meets hardship provisions and requires payment before then. The FCC SSO will investigate and determine if using the PYAJ screen is appropriate. |
NOHL Rules - summary
Summary of NOHL rules
Table 2: This table contains a summary of the Notification Handler (NOHL) rules. The Resources page also contains a series of graphic examples.
|
Rule |
Definition |
Value |
|
0 |
This is an override for manual rates. The Effect Date is the date entered by the Service Officer, i.e. the start date for the manual rate. |
|
|
1 |
This is a change which will result in a rate increase or no change. The customer has notified 'in time' and the event is in a period which has already been paid. Note: where the change involves employment income, and there is a rate increase, rule 15 will be applied instead of rule 1. |
Rate Increase: Date of Effect = Date of Receipt. No Change: Date of Effect = Date of Event. |
|
2 |
This is a change which will result in a rate increase or no change. The customer has notified 'late' and the event is in a period which has already been paid. Note: Where the change involves employment income, and there is a rate increase, rule 16 will be applied instead of rule 2. |
Rate Increase: Date of Effect = Date of Receipt. No Change: Date of Effect = Date of Event. |
|
3 |
This is a change which will result in a rate decrease. The customer has notified 'in time', actioned in the same period as the event, and the event is in a period which has already been paid. (This is the Holiday Processing or Advance Stripping Rule.) |
Date of Effect = Date of Event |
|
4 |
This is a change which will result in a rate decrease. The customer has notified 'in time', and the event is in a period which has already been paid. (Entitlement Period Start Date rule (EPSD). |
Date of Effect = Date Paid To + 1. |
|
5 |
This is a change which will result in a rate decrease. The customer has notified 'in time' and the office action occurs after the end of the following period. The event is in a period which has already been paid. |
Date of Effect = Notification Period End Date +1. |
|
6 |
This is a change which will result in a rate decrease. The customer has notified 'late', and the event is usually in a period which has already been paid. |
Date of Effect = Date of Event. |
|
7 |
This is a change which will result in a rate increase or no change. The customer has notified 'in time', the event is in the same period as the receipt date and the period has not yet been paid. Note:
|
Rate Increase: Date of Effect = Date of Receipt. No Change: Date of Effect = Date of Event. |
|
8 |
This is a change which will result in a rate increase or no change. The customer has notified 'late', and the event is in a period which has not yet been paid. Note: where the change involves employment income, and there is a rate increase, rule 18 will be applied instead of rule 8. |
Rate Increase: Date of Effect = Date of Receipt. No Change: Date of Effect = Date of Event. |
|
9 |
This is a change which will result in a rate decrease. The customer has notified 'in time', and the period has not yet been paid. Note: where the customer is a Stimulus customer, rule 10 will be applied instead of rule 9. |
Date of Effect = Date of Event. |
|
10 |
This is the Stimulus/Reporting Rule. It applies to all reporting customers who have notified 'in time'. This rule can also apply to any NSS customer when processing a pre-transition date. Note: where a customer has notified 'late' they will be treated as Notification reporters |
Date of Effect = Date of Event. |
|
11 |
This is the 'deferred' Effect Date of an event earlier in the assessment. |
Date of Effect = Date of Event. |
|
12 |
This rule occurs where the date being processed is prior to the first circumstance change recorded in the activity, or where there is no circumstance change, the date must be prior to the Review of Original Decision Start Date and the confirmed rates indicate that NOHL previously did not defer on this date. Where neither of these dates exist in the activity, the rule will occur for all dates being processed in the activity where the confirmed rate indicates that NOHL previously did not defer on this date. |
Favourable Decisions: Date of Effect Date = Later of DOV and EPSD of DOA. Unfavourable Decisions: Date of Effect = Date of Original NOHL deferment. |
|
13 |
This rule occurs where the date being processed is prior to the first circumstance change recorded in the activity, or where there is no circumstance change, the date must be prior to the Review of Original Decision Start Date and the confirmed rates indicate that NOHL previously did defer on this date. Where neither of these dates exist in the activity, the rule will occur for all dates being processed in the activity where the confirmed rate indicates that NOHL previously did defer on this date. |
Favourable Decisions: Date of Effect = Later of DOV and EPSD of DOA. Unfavourable Decisions: Date of Effect = Date of Effect applied to original decision. |
|
14 |
This rule was only produced for cases actioned before 20 Sep 2003. This rule occurs if the date being processed is prior to the first circumstance change in the activity and the date being processed is the first date being processed. |
Date of Effect = Date of Event (and the calculated rate applies). |
|
15 |
This is a change which will result in a rate increase. The customer has notified 'in time' and the event is in a period which has already been paid and contains earnings changes. |
Date of Effect = Entitlement Period Start Date of Date of Receipt. |
|
16 |
This is a change which will result in a rate increase. The customer has notified 'late' and the event is in a period which has already been paid and contains earnings changes. |
Date of Effect = Entitlement Period Start Date of Date of Receipt. |
|
17 |
This is a change which will result in a rate increase. The customer has notified 'in time', the event is in the same period as the receipt date, and the period has not yet been paid and contains earnings changes. Note: if the date being processed is after the Date of Receipt (DOR) or PGA exception rules apply, then Date of Effect = Entitlement Period Start Date of Date of Event. |
Date of Effect = Entitlement Period Start Date of Date of Receipt. |
|
18 |
This is a change which will result in a rate increase. The customer has notified 'late' and the event is in a period which has not yet been paid and contains earnings changes. |
Date of Effect = Entitlement Period Start Date of Date of Receipt. |
|
22 |
This rule occurs if the date being processed relates to a review of an Original Decision, as recorded on the Review of Assessment (ROA) screen, from within the provisional activity. Where the ROA screen has been recorded, the review of decision process will commence from the earlier of:
|
See the Rule 22 and 23 table. |
|
23 |
This rule occurs if the date being processed relates to a review of an Original Decision, as recorded on the Review of Assessment (ROA) screen, from within the provisional activity. Where the ROA screen has been recorded, the review of decision process will commence from the earlier of:
|
See the Rule 22 and 23 table. |
|
31 |
Where a reassessment activity includes events that have occurred prior to the start of the financial year previous to the current financial year. |
Date of effect = 1 July of financial year previous to the current financial year. |
|
32 |
Where events recorded in the new claim activity have occurred after the start of the financial year prior to the current financial year. |
Date of Effect = Date of Event. |
|
33 |
Event is a change in the customer’s combined estimated taxable income or Child Support assessment, notification is after the event date, and the result is unfavourable. |
Date of Effect = later of date paid to plus 1 day and Date of Event. |
|
34 |
Event is a change in the customer’s combined taxable income or Child Support assessment and/or assessment method, notification is after the event date, and the result is unfavourable. Event is receipt of monthly disbursement amounts from Child Support, details are received late and decision is unfavourable. Event is cancellation of Income Support Payment (ISP)/Department of Veterans’ Affairs (DVA) payment, where FTB is to be forced to the base rate of Part A and notification is after the event date. Event is grant of an ISP for a dependent child of the customer, event date is a date prior to date paid to plus 1 day. Event is death of a child, event date is prior to date paid to plus 1 day, a lump sum bereavement payment option has been selected and notification given within 14 weeks of the child’s death. |
Date of Effect = later of date paid to plus 1 day and Date of Event. |
|
35 |
Event is supply of verified adjusted taxable income and/or maintenance income received during a financial year. |
Date of Effect = beginning of relevant financial year the verified details apply to. |
|
37 |
Events within provisional activity have event dates prior to the start of the confirmed reassessments (over deferment, and NOHL advises that at this start date, the new assessment will be a confirmed favourable deferment period). Events within provisional activity are circumstance events only, the event concerned occurs prior to the start of the confirmed deferment, and NOHL advises that at this start date, the new assessment will be unfavourable. |
Date of Effect = Initial date of event of confirmed deferment period. |
|
38 |
Events within provisional activity have an event date in the middle of the confirmed deferment, and NOHL advises that at this point the assessment will be favourable. Events within provisional activity are circumstance events only, the event concerned occurs within the middle of the confirmed deferment, and NOHL advises that at this point the assessment will be unfavourable |
Date of Effect = Date of event in the provisional activity. |
|
39 |
Events within provisional activity include income events, the event concerned occurs prior to the start of the confirmed deferment, and NOHL advises that at this start date, the new assessment will be unfavourable. Events within provisional activity include income events, the event concerned occurs within the middle of the confirmed deferment, and NOHL advises that at this point the assessment will be unfavourable. |
Date of Effect = Later of end date of confirmed deferment period and date paid to plus 1 day. |
|
40 |
Event is the commencement of a Blended Family arrangement, via a link of two current FTB customers. The link date is prior to both customer’s date paid to plus 1 day. |
Date of Effect = Next available payday of either the customer or partner (whichever is first) after today’s date. |
|
42 |
This is the FTB Reconciliation rule. Date of Effect is always the Date of Event, except for blended family deferments (which remain unchanged). Note: it is possible that an event in the previous financial year will cause no deferment in the reconciliation, but it may cause a deferment in the current financial year. |
Date of Event. |
|
43 |
Event is the recording of any child maintenance related event and the result is favourable. |
Date of Effect = later of date paid to plus 1 day or Date of Event. |
|
44 |
Event is the recording of any child maintenance related event and the result is unfavourable. Event is receipt of monthly disbursement amounts from Child Support. Details are received/loaded late, (i.e. customer now has a date paid to in the month the disbursement amounts are to be applied from) and decision is unfavourable. |
Date of Effect = later of date paid to plus 1 day or Date of Event. |
|
45 |
Event is receipt of monthly disbursement amounts from Child Support. Details are received/loaded on time (i.e. prior to a customer's date paid to in the month the disbursement amounts are to be applied from). Event is receipt of monthly disbursement amounts from Child Support. Details are received/loaded late, (i.e. customer now has a date paid to in the month the disbursement amounts are to be applied from) and decision is favourable. |
Date of Effect = 1st of the following month. |
|
98 |
This is 'day one' of the transition period for the customer. It is a date which has been inserted into the assessment so that daily rates are set up correctly for this date. It has no business rule associated with it, and does not affect other dates. |
|
|
99 |
This is an override. The Notification Handler (NOHL) has been told what Date of Effect to use by the benefit system. It will appear for Dates of Commencement calculated by the New Claim process, and for decisions by Child Support that have been entered on the Benefit Action (BA) screen. |
NOHL Rules in detail index
Index of NOHL Rules detailed description items
Table 3: This table contains a list of Notification Handler (NOHL) rules. Click on the selected rule to jump to a detailed description of the rule.
|
Items |
Rules |
|
NOHL Rules in detail See also: |
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 22 and 23, 98, 99 |
NOHL Rules in detail
Detailed description of NOHL rules
Table 4: This table contains a detailed description of the Notification Handler (NOHL) rules.
|
Rule(s) |
Action |
|
0 |
This is an override. It will appear for Dates of Effect recorded by the Service Officer on the MAR screen as the start date for a manual rate. |
|
1 |
This is one of several rules about favourable determinations (determinations resulting in the customer's rate increasing or remaining the same). These favourable determination rules all result in the Date of Effect (DOE) being the later of the Date of Receipt (DOR) or the Date of Event (DOV), where the rate is increasing. It is almost always DOR, but if we have been notified in advance, and the system is letting the date be processed rather than setting up a review, then it will be DOV. Where the rate remains the same, the Date of Effect (DOE) will equal the Date of Event (DOV). When Rule 1 applies, the situation is usually that a change is notified and we then defer the effect of that change to the day we are notified. For example, the customer phones on 10 September to tell us about an increase in income from 1 September. The change in rent is recorded on the relevant screen with a DOV of 1 September. The activity has a DOR of 10 September. The date of effect rules say that the change in rate is effective from 10 September. You will see Rule 1 applied on 1 September and then, on 10 September (the Date Of Effect for the change), you will see Rule 11 applied. It is important to note that where the change in circumstance relates to employment income, rules 15 to 18 will display. This is due to the fact a different Date of Effect is applied in order to apportion the employment income over an entitlement period. So when NOHL decides not to apply a change in rate at the DOV but at a later date, you'll see the relevant rule at the DOV and a corresponding Rule 11 applied at the actual DOE. For Parenting Payment Partnered, there is an exception built into the system. This exception applies where the PPP customer is partnered to an NSS stimulus customer and the change of circumstances is, or includes, a change in income. The exception says that the date of effect of the change is the date of event of the change. For these cases, we have not deferred the date of effect so you'll only see Rule 1 applied at the DOV. You will not see Rule 11 applied. Rate Increase - Date of Effect = Date of Receipt No Change - Date of Effect = Date of Event |
|
2 |
A favourable determination rule. In this situation the customer has notified late and has already been paid for the period in which the event occurred. Date of Effect (DOE) is the later of Date of Receipt (DOR) and Date of Event (DOV). Because we are dealing with changes which have been notified late, Date of Effect would normally be Date of Receipt. When Rule 2 applies, the situation is usually that a change is notified and we then defer the effect of that change to the day we are notified. For example, the customer phones on 10 September to tell us about a decrease in investment income from 20 August. The change in income is recorded on the relevant screen with a DOV of 20 August. The activity has a DOR of 10 September. The date of effect rules say that the change in rate is effective from 10 September. You will see Rule 2 applied on 20 August and then, on 10 September (the Date of Effect for the change), you will see Rule 11 applied. It is important to note that where the change in circumstance relates to employment income, rules 15-18 will display. This is due to the fact a different Date of Effect is applied in order to apportion the employment income over an entitlement period. So when NOHL decides not to apply a change in rate at the DOV but at a later date, you'll see the relevant rule at the DOV and a corresponding Rule 11 applied at the actual DOE. Rate Increase - Date of Effect = Date of Receipt No Change - Date of Effect = Date of Event |
|
3 |
This rule generally only applies when we have advance stripped payments (the old holiday processing) In this scenario there is an unfavourable determination (rate decrease), the customer notifies the change of circumstances in the same entitlement period as the change occurs and we also action the change in that same period, but the period has already been paid or stripped. Date of Effect = Date of Event. |
|
4 |
This is a NOHL rule that makes Date of Effect (DOE) apply from the Entitlement Period Start Date of the period in which we are actioning the change. This arises when the customer tells us about a change which results in their rate going down (an unfavourable determination) and the customer has notified that change in time (within their notification period). In this case, we have already stripped one payment for the customer between when the event occurred and when we action the change. The customer has told us in time so we do not want to raise a debt, however we do want to reduce their rate as soon as we can. This rule says we reduce their rate from the beginning of the entitlement period in which we action the change. So the customer keeps their entitlement for the period we had stripped before we action the change. Their full next entitlement period is paid at the decreased rate. When Rule 4 applies, we defer the change in entitlement until the beginning of the period in which we action the change. This means you will generally see two rules, at different dates, applied in the reassessment. For example, the customer phones on 10 September to tell us about an increase in income from 1 September. The change in income is recorded on the relevant screen with a Date of Event (DOV) of 1 September. The activity has a Date of Receipt (DOR) of 10 September. Their entitlement period ended on 7 September. We action the change on 10 September. We have already paid the customer for the entitlement period ending on 7 September so the date of effect rules say we reduce their rate from 8 September. You will see Rule 4 applied on 1 September and then, on 8 September (the date of effect for the change), you will see Rule 11 applied. So when NOHL decides not to apply a change in rate at the DOV but at a later date, you'll see the relevant rule at the DOV and a corresponding Rule 11 applied at the actual DOE. Date of Effect = Date Paid To + 1 Day |
|
5 |
This is a NOHL rule that sets the Date of Effect (DOE) to the day after the end of the Notification Period. It is similar to Rule 4 in that it applies when we make an unfavourable determination (the customer's rate decreases) after being notified of a change in circumstances. The customer has notified the change of circumstances within their notification period. For this rule to apply, we haven't actioned the change until more than one payment has passed. We are not going to reduce the rate from the date of event but we are going to recover as much as we reasonably can of the money we have paid the customer. The rule says the customer can keep any money for the full notification period but that we can recover entitlement for the period from the day after the end of the notification period. The customer will have a debt from the day after the end of the notification period until the date they are paid up to (their "date paid to"). This is the same as the October 1997 changes in debt processing. When Rule 5 applies, we defer the effect of the change in entitlement from the Date of Event (DOV) until the day after the end of the notification period. This means you will generally see two rules, at different dates, in the reassessment. For example, the customer rings on 10 September to tell us they moved into government housing on 1 September. This means they are no longer entitled to rent assistance and their overall rate goes down (we make an unfavourable determination). The customer's entitlement periods end on 7 September, 21 September and 5 October. We do not action this change until 1 October. The customer has been paid for the entitlement periods ending on 7 September and 21 September. The date of effect rules say we reduce their entitlement from 16 September (their notification period ended on 15 September). There is a recoverable debt from 16 September until 21 September. You will see Rule 5 applied on 1 September and then, on 16 September (the date of effect for the change), you will see Rule 11 applied. So when NOHL decides not to apply a change in rate at the DOV but at a later date, you'll see the relevant rule at the DOV and a corresponding Rule 11 applied at the actual DOE. Date of Effect = Notification Period End date + 1 Day. |
|
6 |
In this scenario there is an unfavourable determination (rate decrease), the customer has notified the change of circumstances late (after the end of the notification period) and the customer has usually been paid for the period in which the event occurs. There is a recoverable debt from Date of Effect (Date of Event). Date of Effect = Date of Event. |
|
7 |
A favourable determination rule (the customer's rate is going to stay the same or increase). In this situation the customer has notified in time and has not yet been paid for the period in which the event occurred. This doesn't really make any difference - Date of Effect (DOE) is the later of Date of Receipt (DOR) and Date of Event (DOV). You'll generally see two rules applied, at different dates, in this reassessment. Rule 7 will apply at the DOV and Rule 11 will apply at DOR (which is the date of effect). Where the Date of Receipt is on or before the Date of Event, there will be a Rule 7 on the Date of Event, and no Rule 11. It is important to note that where the change in circumstance relates to employment income, rules 15-18 will display. This is due to the fact a different Date of Effect is applied in order to apportion the employment income over an entitlement period. For Parenting Payment Partnered, there is an exception built into the system. This exception applies where the PPP customer is partnered to an NSS stimulus customer and the change of circumstances is, or includes, a change in income. The exception says that the date of effect of the change is the date of event on the change. For these cases, we have not deferred the date of effect so you'll only see Rule 7 applied at the DOV. You will not see Rule 11 applied. Rule 7 will not display for the above circumstances where the customer is a stimulus/reporting customer. Rule 10 will display instead. This allows the Date of Effect to be set as the Date of Receipt. Rate Increase - Date of Effect = Date of Receipt No Change - Date of Effect = Date of Event |
|
8 |
A favourable determination rule (the customer's rate is going to stay the same or increase). In this situation the customer has notified late but has not yet been paid for the period in which the event occurred. This doesn't really make any difference - Date of Effect (DOE) is the later of Date of Receipt (DOR) and Date of Event (DOV). Because we are dealing with changes which have been notified late, Date of Effect would normally be Date of Receipt. You'll generally see two rules applied, at different dates, in this reassessment. Rule 8 will apply at the DOV and Rule 11 will apply at DOR (which is the date of effect). It is important to note that where the change in circumstance relates to employment income, rules 15-18 will display. This is due to the fact a different Date of Effect is applied in order to apportion the employment income over an entitlement period. Rate Increase - Date of Effect = Date of Receipt No Change - Date of Effect = Date of Event |
|
9 |
In this scenario there is an unfavourable determination (rate decreases), the customer has notified on time and the customer has not yet been paid for the entitlement period in which the event occurs. We reduce the customer's rate from date of event - there is no debt because haven't yet paid any entitlement to the customer for the entitlement period in which the event occurs. We can reduce the customer's rate from Date of Event (DOV). Rule 9 will not display for the above circumstances where the customer is a stimulus/reporting customer. Rule 10 will display instead. This allows the Date of Effect to be set as the Date of Receipt. Date of Effect = Date of Event. |
|
10 |
Stimulus/reporting customers who have notified 'in time' will have Date of Effect always set to Date of Event. If a stimulus/reporting customer notifies 'late' then they will be treated as Notification customers and other rules will be applied. The notification period for stimulus customers is the period in which they are required to lodge their fortnightly form. Where a stimulus customer has not lodged their form for the current entitlement period, they will not be paid until they lodge therefore, where they have not been paid (due to non-lodgement) and they notify of a change in circumstance for this non-paid period, this notification is considered to be 'in time'. It is only where the statement reporter has been paid, and they notify of a change that occurred for this paid period, that the notification is considered to be 'late'. Where the customer's payment has been stripped early due to holiday processing, and they notify of a change after Date Paid to but before their EPED (i.e. the DOV is still within this current pay period), then this notification is still considered to be 'in time'. |
|
11 |
In processing a number of changes in circumstances, the date of effect rules require us to defer the Date of Effect (DOE) from the Date of Event (DOV). For example in Rule 1 and Rule 7 where we defer the Date of Effect to the Date of Receipt (DOR), or in Rule 4 where we defer the Date of Effect to the beginning of the entitlement period in which we action the change. At the Date of event, you see which particular rule applied at that date (e.g. rule 1 or 4 or 7). The reassessment then works through any more dates and eventually comes to the date of effect we decided to use when we deferred the effect from DOV. When we reach this "deferred DOE" we say we are applying rule 11. This will always be shown in conjunction with a business rule (1-9). |
|
12 |
Rule 12 says "this is the system mirroring an earlier decision to apply a rate change at date of event". You can disregard the rule. There are a series of "rules" used when we are processing dates before the earliest date of change in the current activity. These are significant for refresh and reassessment actions recorded on the BA screen. These rules are generally just the system saying it has checked what to do to make sure it mirrors any decisions from previous activities. However, there is no legislative basis to increase the rate (and hence calculate arrears) from a date of effect in the past. Where the decision is favourable, the date of effect will be deferred to the start of the current entitlement period (generally date paid to + 1). (See also Rule 13 and Rule 14.) For example, if there was an earlier activity processing a loss of custody for a child and this resulted in the customer's rate decreasing. This change in custody was notified late and we applied date of effect Rule 6 which meant date of effect was date of event. Let's say the custody change was on 1 September and the change was notified on 30 September. The date of effect rule applied when that reassessment was done was Rule 6 and the decrease in rate applied from 1 September. If, on 10 November, you code a refresh action on the BA screen and specify a date of effect on the refresh action as 25 August, then, in the refresh activity, the system needs to mirror the original decision not to defer the change which happened on 1 September. |
|
13 |
There are a series of "rules" used when we are processing dates before the earliest date of change in the current activity. These are significant for refresh and reassessment actions recorded on the BA screen. These rules are generally just the system saying it has checked what to do to make sure it mirrors any decisions from previous activities. However, there is no legislative basis to increase the rate (and hence calculate arrears) from a date of effect in the past. Where the decision is favourable, the date of effect will be deferred to the start of the current entitlement period (generally date paid to + 1). (See also Rule 12 and Rule 14.) For example, if there was an earlier activity processing a decrease in income leading to an increase in rate. Let's say the income change was on 1 September and the change was notified on 10 September and the date of effect rule applied when that reassessment was done was for example, Rule 1. We had decided to defer the effect of the change in rate from 1 September (DOV) to 10 September (DOR, also DOE). If on 4 November you code a refresh action on the BA screen and specify a date of effect on the refresh action as 25 August, then in the refresh activity the system needs to defer the change which happened on 1 September to the start of the current entitlement period. Rule 13 says "this is the system mirroring an earlier decision to defer a rate change". You can disregard the rule. |
|
14 |
This rule was only produced for cases actioned before 20 Sep 2003. There are a series of "rules" used when we are processing dates before the earliest date of change in the current activity. These are significant for refresh and reassessment actions recorded on the BA screen. These rules are generally just the system saying it has checked what to do to make sure it mirrors any decisions from previous activities. (See also Rule 12 and Rule 13.) Rule 14 applies at the "date of effect" of the action coded on the BA screen. There is no change of circumstances. This rule applies when we are looking at the first reassessment for a period before the first circumstance change in this activity. The rate that is used is the calculated rate (significant for Refresh activities). You can disregard this rule - it is just the system saying "I am finding the right rate to use at the start of the refresh/reassessment process". |
|
15 |
This is one of several rules about favourable determinations (determinations resulting in the customer's rate increasing) and includes changes to earnings. These favourable determination rules all result in the Date of Effect (DOE) being the later of the Entitlement Period Start Day (EPSD) of either the Date of Receipt (DOR) or the Date of Event (DOV). It is almost always EPSD of the DOR, but if we have been notified in advance, and the system is letting the date be processed rather than setting up a review, then it will be the EPSD of the DOV. When Rule 15 applies, the situation is usually that a change to earnings is notified and we then defer the effect of that change to the Entitlement Period Start Day of the day we are notified. For example, the customer phones on 10 September to tell us about a decrease in income from 1 September. The change in income is recorded on the relevant screen with a DOV of 1 September. The Entitlement Period Start Day for the customer is 31 August. The activity has a DOR of 10 September. The date of effect rules say that the change in rate is effective from 31 August. You will see Rule 15 applied on 31 August. So when NOHL decides not to apply a change in rate at the DOV but at a later date, you'll see the relevant rule at the EPSD of the DOV. For Parenting Payment Partnered, there is an exception built into the system. This exception applies where the PPP customer is partnered to an NSS stimulus customer and the change of circumstances is, or includes, a change in income. The exception says that the date of effect of the change is the date of event of the change. For these cases, we have not deferred the date of effect so you'll only see Rule 15 applied at the EPSD of the DOV. You will not see Rule 11 applied. Date of Effect = Entitlement Period Start Date of the Date of Receipt |
|
16 |
A favourable determination rule. In this situation the customer has notified of an earnings change late and has already been paid for the period in which the event occurred. Date of Effect (DOE) is the later of Entitlement Period Start Date (EPSD) of the Date of Receipt (DOR) or Date of Event (DOV). Because we are dealing with changes which have been notified late, Date of Effect would normally be Entitlement Period Start Date of Date of Receipt. When Rule 16 applies, the situation is usually that a change is notified and we then defer the effect of that change to the start of the entitlement of the day we are notified. For example, the customer phones on 10 September to tell us about a decrease in income from 20 August. The Entitlement Period Start Day for the customer is 31 August. The change in income is recorded on the relevant screen with a DOV of 20 August. The activity has a DOR of 10 September. The date of effect rules say that the change in rate is effective from 31 August. You will see Rule 16 applied on 31 August. So when NOHL decides not to apply a change in rate at the DOV but at a later date, you'll see the relevant rule at the EPSD of the DOV. Date of Effect = Entitlement Period Start Date of Date of Receipt |
|
17 |
A favourable determination rule (the customer's rate is going to increase). In this situation the customer has notified a change in earnings in time and has not yet been paid for the period in which the event occurred. This doesn't really make any difference - Date of Effect (DOE) is the later of Entitlement Period Start Date (EPSD) of Date of Receipt (DOR) and Date of Event (DOV). You'll generally see two rules applied, at different dates, in this reassessment. Rule 17 will apply at the DOV and Rule 11 will apply at DOR (which is the date of effect). Where the Date of Receipt is on or before the Date of Event, there will be a Rule 17 on the Date of Event, and no Rule 11. For Parenting Payment Partnered, there is an exception built into the system. This exception applies where the PPP customer is partnered to an NSS stimulus customer and the change of circumstances is, or includes, a change in income. The exception says that the date of effect of the change is the date of event on the change. For these cases, we have not deferred the date of effect so you'll only see Rule 17 applied at the DOV. You will not see Rule 11 applied. Date of Effect = Entitlement Period Start Date of Date of Receipt |
|
18 |
A favourable determination rule (the customer's rate is going to increase). In this situation the customer has notified of an earnings change late but has not yet been paid for the period in which the event occurred. This doesn't really make any difference - Date of Effect (DOE) is the later of Entitlement Period Start Date (EPSD) of Date of Receipt (DOR) and Date of Event (DOV). Because we are dealing with changes which have been notified late, Date of Effect would normally be Entitlement Period Start Date of Date of Receipt. You'll generally see two rules applied, at different dates, in this reassessment. Rule 18 will apply at the DOV and Rule 11 will apply at DOR (which is the date of effect). Date of Effect = Entitlement Period Start Date of Date of Receipt |
|
22 and 23 |
Rule 22 and 23 will appear for cases where an Original Decision is being reviewed in the activity, and as an outcome of the review, a favourable determination has been made. The date of effect for this favourable determination will depend on the following:
|
|
98 |
This is "day one" of the transition period for the customer. It is a date which has been inserted into the assessment so that daily rates are set up correctly for this date. It has no business rule associated with it, and does not affect other dates. You can ignore this rule after the transition period. |
|
99 |
This is an override. NOHL has been told what Date of Effect to use by the Service Officer or the benefit system. Situations where you will see Rule 99 include Dates of Commencement calculated by the New Claim process, decisions by the Service Officer that have been entered on the Benefit Action (BA) screen and exception date of Effect rules for circumstance changes such as Compensation and DVA payments. |
Rules 22 and 23
Detailed description of NOHL rules 22 and 23
Table 5: This table contains a detailed description of Notification Handler (NOHL) rules 22 and 23.