Skip to navigation Skip to content

Reporting overview 110-18120553




This document provides an overview of reporting requirements.

On this page:

Determine reporting frequency

Change in reporting requirements

Failed cancellation Manual follow up (MFU)

Determine reporting frequency

Table 1

Expand table

Step

Action

1

Check for mutual obligation requirements

Is the customer receiving a payment that has mutual obligation requirements (regardless of any exemptions)? Check the Activity and Exemption Summary (AEX) screen in Process Direct to confirm.

This does not include ABSTUDY, Austudy or Youth Allowance (YA) students. For Farm Household Allowance (FHA) customers, see Reporting Requirements in Assessing income for Farm Household Allowance (FHA).

2

Check eligibility for variable reporting

Refer to Reporting requirements for customers receiving a payment with mutual obligation requirements to check if the customer is eligible for variable reporting.

Does the customer satisfy the variable reporting criteria?

3

Check for employment income

Does the customer or partner have employment income?

Note: to report employment income before departure or while overseas, see Recording and correcting employment income. To report income earned overseas, see Foreign income and assets.

4

Customer is a 2 weekly reporter

The customer must report every 2 weeks in order to receive payment, unless the only income that is paid meets a MTE exception.

The customer can view their future reporting periods in their online account on the Next reporting periods page.

A self service option is available The customer may have to:

If the customer fails to report, they will not receive payment.

Genuine attempts must be made to transition customers to report via self service options before assisted reporting is completed, unless an Exception applies.

Exceptions to 2 weekly reporting

Customers in receipt of Disability Support Pension (DSP) (Blind) or Age Pension (Blind) will be notification reporters and are not required to declare income unless they are claiming Rent Assistance (RA). Partners of these customers, who are not exempt from the income and assets test, will be subject to normal reporting conditions and consideration should be given to placing them on 2 weekly reporting.

Procedure ends here.

5

Customer is a variable reporter

Variable or 'Statement' reporters will continue to be paid every fortnight based on circumstances that are known. They must also submit a reporting statement at regularly determined intervals.

The customer must report changes to their:

  • income, or
  • circumstances

These changes might affect their payment on the EPED for the period that the change occurred.

If the customer fails to report by their due date, payment may be cancelled and/or a debt may be raised.

Procedure ends here.

6

Customer is a notification reporter

The customer must report any changes to their income or any other circumstances within 14 days.

The customer will continue to be paid every fortnight based on the circumstances that are known.

If the customer fails to report a change in income within 14 days, they might be overpaid, and a debt may be raised.

Customers can advise any changes to their circumstances:

  • using self service options
  • via phone through a smart centre, including TTY and multi-lingual services
  • in person at their local service centre, visiting a service officer service or community agent, and
  • in exceptional circumstances, in writing by letter or fax

Notification customers with continuous employment income can advise of changes using self service options. Customers can:

  • notify of changes from the start date of their current entitlement period (EPED + 1), or
  • for a change which will occur up to 30 days in the future

Service Officers will only need to action these changes where they are unable to auto complete due to:

  • Disability Support Pension (DSP) customer recording over 30 hours per week
  • Carer Payment (CP) customers recording 'hours of care not met exceeds 25 hours per week'
  • Care provided varies from week to week

Youth Allowance (YA) and Austudy students

If currently a notification reporter, customers can use self service options to advise of changes, including:

  • the date they or their partner began work, and
  • their employers' details

Change in reporting requirements

Table 2: This table outlines how to change a customer’s reporting requirements.

Expand table

Step

Action

1

Change in circumstances

A change in circumstances can mean a customer needs their reporting requirements changed. If the customer or their partner:

  • start paid work and need to be placed onto two weekly statement reporting, go to Step 2
  • stop receiving employment income and request statement reporting requirements are removed, go to Step 3

2

Customer or partner start paid work and need to be placed onto two weekly statement reporting

Do not set new statement reporting requirements on the RPRD screen in any system.

Where it is necessary to amend reporting requirements in RPRD, staff must use the RPRD screen in Customer First. Do not use Process Direct to add or change reporting requirements, as this may apply an incorrect start date to the requirement.

Do not overwrite a future reporting start date using the RPRD screen as this may apply a reporting requirement without the necessary notification period.

Check if the customer:

  • has a future 2WE statement reporting entry on the Reporting Regime Summary (RPRS) screen commencing from the start of the next entitlement period, no further action is required
  • is receiving a payment with mutual obligation requirements with a variable reporting frequency other than 2WE, for example 4WE (four weekly) or 12W (twelve weekly). The customer will need to be changed back to a fortnightly reporter. See Reporting requirements for customers receiving a payment with mutual obligation requirements
  • currently has a manual reporting override of the reporting frequency of OFF on the current RPRD screen (a Reason other than SPM or NCL). Insert or amend an end date in the Man Rsn Expiry field
  • has a reporting frequency of OFF on the current RPRD screen with a Reason of SPM or NCL or the RPRS screen is blank, go to the Profiling CSA Identified Circumstances (PQCIC) screen in Customer First. On PQCIC:
    • If the customer has a current (override) Reason code of OFF recorded, update the end date of the line to today's date to end the override
    • If the customer has a current (override) Reason code of SNO recorded, escalate the record to have the code removed by an authorised user. See Table 1 >Item 8 in Single Touch Payroll (STP) troubleshooting
    • If there is no current line, record the code 2WE in the Reason field to place the customer onto two weekly statement reporting (this may start from the beginning of the next entitlement period)

Procedure ends here.

3

Customer or partner stop receiving employment income and request statement reporting requirements are removed

If the customer or their partner receives a payment with mutual obligation requirements, see Reporting requirements for customers receiving a payment with mutual obligation requirements.

A customer cannot be turned off statement reporting until they have been paid all outstanding amounts.

Do not set new statement reporting requirements on the RPRD screen in any system.

Where it is necessary to amend reporting requirements in RPRD, staff must use the RPRD screen in Customer First. Do not use Process Direct to add or change reporting requirements, as this may apply an incorrect start date to the requirement.

Check if the customer:

  • currently has a manual override (Reason other than SPM or NCL) of 2WE on the current RPRD screen, add or amend the end date to today's date in the Man Rsn Expiry field
  • has a reason of 2WE on the current RPRD screen with a Reason of SPM or NCL, go to the Profiling CSA Identified Circumstances (PQCIC) screen in Customer First. On PQCIC:
    • If the customer has a current (override) Reason code of 2WE or REI recorded, update the end date of the entry, to end the override
  • If there is no current entry, record a Reason code of 'OFF' on PQCIC to take the customer off two weekly statement reporting.

Procedure ends here.


Failed cancellation Manual follow up (MFU)

Table 3

Expand table

Step

Action

1

Failed cancellation Manual Follow Up (MFU)

When a customer fails to report within 14 days from their report due date, their payment will automatically cancel Failed to report (FRP). Where this automatic cancellation fails to occur, a MFU activity will be created and allocated to Service Officers via Workload Manager (WLM) as a ZIAM_REA_FAILCAN work item.

Review the record to determine the most appropriate outcome and complete the MFU:

  • Select the earliest started REA activity from the Activity List (AL) screen
  • Navigate to the Activity History Details (HAY) screen
  • Check for any system errors under Notes (there may be multiple pages)
  • If an error is displayed, take corrective action of the error as required
  • Go to the Assessment Results (AR) screen, check that the outcome is correct
  • Finalise the REA activity
  • Cancel any duplicate REA activities on the customer's record with the same keywords
  • DOC the record, see Getting it Right (GIR) Minimum Standards