Reporting screens 110-18120555

The Reporting Requirements Task Selector (RPTS) screen gives access to the 8 screens that display a customer's reporting requirement.

Only some of these screens allow updates to a customer's reporting requirement.

The following steps provides details on the screens in the Report cluster.

The EARR screen is used for recording reporting outcomes with employment details.

The RPRS screen summarises the customer's reporting requirements. It cannot be updated.

On selecting an entry, the system will display the Reporting Regime Details (RPRD) screen where the record can be updated.

The RPRD screen displays and allows updates to the customer's reporting requirements.

The RPTI screen displays and allows reissue of reporting forms, letters and statements that have been issued to the customer.

The RPTC screen displays the details of reporting forms, letters and statements.

Selecting any line on this screen displays the wording of the form, letter or statements.

The RPRH screen displays the history of a customer's reporting instances and the channel used to report in.

The RAD screen displays and allows edit of a customer's payment delivery day and entitlement period end day (EPED).

The LRC screen is a search screen for customers who have not reported on time.

The SSAF screen displays and allows edit of a customer's access to the Reporting service through self service (online accounts, Express Plus Centrelink mobile app and phone).

The display of eligibility status refers to a customer's eligibility to report their employment income through self service for that particular fortnight. It does not affect a customer's ability to register for self service.

The EARR screen can record both a report and employment income at the same time.

The EARR screen does not pass through the Assessment Results (AR) screen unless:

• continuing income is recorded, or
• other screen updates are included in the EARR screen activity

The RR screen:

• displays outstanding reporting periods and types, including today or future periods
• may allow the Expect Event field and the Report Indicator (IND) to be updated

Record Expected Events against the Report Types displayed.

Note: Use the RR screens, not EARR screens, if mutual obligation/participation requirements result(s) are not being recorded with:

• a Reporting Statement, or
• EAN Report Type

The EARR screen allows recording of:

• a Reporting Statement or EAN Report Type
• updates to casual employment income, or
• updates to a mutual obligation requirement report result for a job seeker

To access, code 'EARR' in the Nxt: field or select from the Reporting Task Selector (RPTS) screen:

• DTR Date: display only, shows the earliest Date Due of any SU19 or EAN Report Type that is due
• C/P: shows if an income update is about the customer or partner. Mandatory for new employer entries
• Employer Name: allows recording or displays the name of the employer who sent the income amount
• Amount $.cc: allows recording of new income amounts for new or existing employers. Mandatory for new income entries
• Freq: the period over which the amount applies
• Mandatory for new income entries
• Defaults to blank unless a listed employer entry has continuing income recorded against it
• If no entry for an employer income update, the field value defaults to ONE or IOP
• Field Help (?) lists other valid frequencies
• Hrs Pf: number of hours worked for a listed employer for the fortnight. Mandatory for new income entries
• Emp Sts: the type of employment from which income is derived. Mandatory for new income entries
• Ver: how the customer's employment income has been verified
• Mandatory field
• If a code (other than NVF - not verified) is entered, the screen flow will go to the Actual Earnings Details (EAAD) screen
• Record details of employment income on the EADD screen Income Type: for type of employment income
• For example, EAR - earnings from employment
• Use Field Help (?) if needed
• DOV: the Date of Event of earned income displayed. Mandatory for new income entries
• AMR: the Activity Management Reference number that last updated an employer entry

Each line on the RR screen represents a report that is due.

Future report dates display, but with all fields protected.

The return or report of the following Report Types can be recorded:

• S19 - Reporting Statement
• EAN- Employment Income Report

A stimulus code of STM will generate a payment to the customer.

The RR screen also allows Expected Events to be recorded for some Report Types. Complete the RR screen when

• a customer is due to report, and
• their employment income is updated on the Employment Income Summary (EANS) screen instead of the EARR screen

The RR screen fields are:

• Date Paid To: display only. Shows the last Entitlement Period End Date for a payment
• Date Reported To: display only. Shows the last finalised reporting period end date for a Reporting Statement or EAN Report
• Date Due: display only and shows when a Report Type is due
• Report Type: display only
• Report Ind Y/N: Report Indicator, to record that a report has been returned
  Note: Report Types that require a 'result' will not also require an input in this field
• Report Result: if a customer reports a Report Type that requires a result. Field Help (?) shows valid values for each Report Type
• Stim Code: display only. Indicates if the Report Type will affect payment issue
• Expect Event: allows the recording of expected casual income or payment cancellation in the next reporting period
• AMR: Activity Management Reference number of the activity that recorded the Report Type

The RPRH screen shows a history of all report types that are completed and returned. It is a display only screen.

If there are no historical reports this screen will not display any report details.

The RPRH screen is accessed by:

• keying 'RPRH' in the Nxt: field, or
• selecting the screen from the Reporting Task Selector (RPTS) screen

If the RPRH screen has multiple pages, view by

• scrolling via [F7] / [F8], or
• entering a page number in Page of field

The RPRH screen is sorted by the Date Reported with the most recent date appearing first. Report Types for the same date are sorted alphabetically.

The fields in the RPRH screen are:

• Date Reported: date of receipt of a report for a particular report type
• Time Reported: system time of the Activity that was recorded on the customer's record
• Reporting Period Start Date: start date of the period the Report Type covered
• Reporting Period End Date: end date of the period the Report Type covered
• Report Type: type of requirement reported
• Who: who recorded the report on the system. This can be a Service Officer or the customer via Self Service (online, Express Plus Mobile applications or phone)
• Chan Used: the Channel is how the report was made by the customer to the system
• Sys: shows the Host Application area responsible for the report requirement
• AMR: Activity Management Reference number of the activity that recorded the report

This screen displays a summary of the Reporting Requirements that make up a customer's Reporting Regime. These Reporting Requirements are defined by Report Types and their characteristics.

The screen displays future, current, historical and deleted occurrences, plus variations of Report Types. No data on this screen indicates that a customer has not had a Reporting Requirement.

The RPRS screen is for display purposes only. Updates cannot be made on this screen.

Access the Reporting Regime Details (RPRD) screen via the RPRS screen. It displays the customer's Report Types in detail and allows updates.

The RPRS screen also displays whether or not a customer is deemed to be an assisted reporting customer.

To place a customer on reporting or take them off:

• Open the RPRS screen
• Select Reporting Summary via workspace in Customer First
• Key 'RPRS' in the Nxt: field
• Select Reporting Regime Summary from the Reporting Task Selector (RPTS) screen, or
• Go to Assessment Results (AR) screen
• Select RPRS from Optional Actions in Customer First, or
• Key 'K' in the Go to: field in Customer Record
• in Customer First
• view multiple pages of the RPRS screen by selecting the page number or selecting the Next> or <Prev buttons
• select the Start Date link on the relevant Reporting Regime summary line to go to the RPRD screen for the Report Type occurrence
• in the Customer Record
• view multiple pages of the RPRS screen by
• scrolling via [F7]/[F8], or
• entering a page number in the Page of: field
• Enter 'S' next to a Reporting Regime summary line to go to the RPRD screen for the Report Type occurrence. Multiple lines can be selected. Selected entries are displayed in the same order that they appear on the RPRS screen

Sometimes information on the RPRS screen does not match the Profile Summary (PQS) screen.

If the customer displays as 2WE Stim on the PQS screen but does not have a current reporting regime on the RPRS screen:

• go to the PQS screen
• key 'Y' in the Reprofile: field

This will align the Reporting Regime with the profile details.

The first 2 fields summarise Report Types whose next report is either due or overdue:

• Next Reports Due DD MM YY: the next report due on or after the system date and the Report Types due on that date
• Overdue Reports: the Report Types due before the system date that have not been reported yet

The rest of the screen shows a summary of future, current, historical and deleted Report Types. Each occurrence displays on a separate line. Historical and deleted lines are shaded.

The following fields display:

• Start Date: start date of a particular occurrence of a Report Type
• Type: the type of report the customer needs to respond to. For example 'S19' - Reporting Statement - for job seekers
• 'EAN' - Earnings - for payment types without mutual obligation requirements/participation requirements (including students)
• Multiple Report Types may be listed. A second occurrence with a future Start Date and a different characteristic may also exist. Past Report Types are also displayed
• Next Report Due: the date the Report Type is due to be reported. Only the current occurrence of a Report Type will have this date displayed
• Stim Code: indicates whether payment to a customer will be authorised if they do not contact for the Report Type
• Freq: how often the customer must contact for the Report Type or if they have been taken off reporting
• Rsn: shows how a Report Type and its characteristics were determined
• Auto reasons are used where the Report Type is applied by the Reporting Cluster based on the Service Profiling capability
• Manual reasons are used where a new Report Type is added or the Stimulus Code or Frequency characteristics of an existing Report Type has been manually overridden
• Man Rsn Expiry: the date a manual Reason for Requirement is due to expire
• Sys: the host system of the payment for which the Report Type applies
• Asst Rpt: shows if a customer needs help reporting. It will display a 'Y' if a customer is deemed to require assistance, otherwise it will be blank
• Form Type: describes the type of Report Statement the S19 reporter is issued with. Valid values are 'S19 Application for Payment' or 'RIA' (Reporting Income and Activity - for regular self-service reporters)
• The AMR: (Activity Management Reference number) is the activity which has created a Report Type

The RPRD screen displays and allows updates to the characteristics of a Report Type such as:

• the type of report
• when the next report is due
• if payment stimulus will be applied
• the frequency of the report
• why it is required
• a manual expiry date
• how they are permitted to report, and
• whether or not the customer is identified as an assisted reporting customer

The Report Type of 'EAN' can also be inserted on this screen.

Select individual Report Types from the Reporting Regime Summary (RPRS) screen to view the RPRD screen for that Report Type.

RPRD entries are created by automatic system processing, however:

• the auto information can be overridden with manual requirements, and
• new Report Types added

Historical and deleted occurrences are also displayed.

Update the RPRD screen by selecting Change Report Form Type via the Reporting Summary page. This will show the Reporting Regime workflow, see Step 2.

The Reporting Summary page displays the customer's reporting details through the sections:

• Next/Overdue Reports
• Current/Future Reports
• Update options available for the customer
• Reporting history

The Reporting Regime workflow is accessible on the Reporting Summary page by selecting 1 of the options from the 'Update options available for the customer' section.

To access the RPRD screen:

• select a requirement line from the RPRS screen. This option is only available in Customer Record
• code 'RPRD' in the Nxt: field, or
• select the screen from Reporting Task Selector (RPTS) screen

Note: when going to the RPRD screen, if any Report Type occurrence already exists, the RPRS screen displays first. Press [Enter] without making a selection to display a blank RPRD screen. This allows a new Report Type to be entered.

If multiple Report Types are selected from the RPRS screen, they show in the same order as the RPRS screen. To view each entry, scroll through selections by pressing [Enter] or by using [F23]/[F24]. This option is only available in Customer Record.

Access Screen Help Text by pressing the ? icon located in the top right of the screen in Customer First or by selecting [F1] in Customer Record.

• The fields in the RPRD screen are:
• Report Type: defines the details the customer needs to report. The field is automatically populated based on payment type, Service Profiling results and mutual obligation requirements/participation requirements. Certain Report Types can be added manually. This field is mandatory when updating the screen. Future, current, historical and deleted occurrences of a particular Report Type and its characteristics are displayed. Update the the Reason For Requirement: and Manual Reason Expiry: fields for manual updates. Valid values and characteristics are:
• S19 - Reporting Statement (SU19) form
• EAN - Employment Income Report - the only Report Type that can be updated directly from the RPRD screen. It is used for customers without mutual obligation/participation requirements, including pensioners of Age Pension age
• ACC - Account Statement
• IMP - Income Maintenance Preclusion Questionnaire
• SWP - Seasonal Work Preclusion Questionnaire
• EVR - Earnings Verification
• EER - Electronic Employer Reporting
• PBI - Failure Investigation (no longer used)
• Start Date: the date a particular Report Type will apply from. Display only field. For student claims, check that the Start Date corresponds with the start date of claim. If this date is incorrect, code the Manual Reason Expiry field with a 'dummy' date to reassess the Start Date for reporting. Examples of incorrect dates include a date more than 14 days in the future, or from today only
• Report Next Due: the date a current Report Type is next due to be reported by the customer. Display only field and is set when a new Report Type is created. Automatically updated every time the customer reports or the current Report Type Frequency is updated. Only current Report Types have a Report Next Due date
• System: indicates the host system of the payment that the Report Type applies to (NSS, PGA or PEN)
• Report Form Type: indicates if customer is reporting via SU19 or Reporting Statement. Only valid for S19 Report Type
• RIA - Income & Activity Statement (for regular self-service reporters)
• S19 - SU19 Application for Payment
• Reason: if the Report Form Type is updated manually, enter the Reason: field. Valid values are:
• For report Form Type of RIA only: AUT - Regular Self Service Reporter
• For Report Form Type of S19 only: NCL - New Claim, NRS - Not regular Self Service Reporter
• For any Report Form Type: CLR - Customer Request, CSA - CSA Override
• Stimulus Code: indicates whether ongoing payments will be authorised if the customer fails to report. Automatically populated, based on Service Profiling results and mutual obligation/participation requirements. The field can be updated manually. Valid values fare:
• STM (Stimulus) - report required for current period payment issue
• RWS (Return With Statement) - report required with another report type. For example, S19 or EAN for current payment issue
• DST (Delayed Stimulus) - report required for next period payment issue
• Frequency: how often a customer must contact for a Report Type
• Mandatory field if the screen updated manually
• Auto populated based on Service Profiling results and mutual obligation requirements/participation requirements
• If a Report Type is no longer required, use 'OFF' value to end the Report Type requirement
• Record 'OFF' for a Report Type of 'EAN'
• Other Report Types will have a Frequency of 'OFF' determined by Service Profiling and the Reporting cluster
• In Customer First, select the ? in the top right of the screen to access Screen Help for valid field values
• In Customer Record, select [F1] to access Screen Help to show valid values for this field
• Reason For Requirement: how a Report Type and its characteristics are calculated for the customer
• Auto populated based on Service Profile results and other customer circumstances
• Update if the Report Type:, Stimulus Code: or Frequency: fields on the RPRD screen are manually updated
• If manually updated, update the Manual Reason Expiry: field
• When a manual Reason for Requirement is entered, auto profiling does not apply until the Manual Reason Expiry date is reached
• In Customer First, select the ? in the top right of the screen to access Screen Help which shows valid values for this field
• In Customer Record, select [F1] to access Screen Help to show valid values for this field
• Manual Reason Expiry: the date a manual Reason for Requirement is to expire.
• A Manual Reason Expiry date can only be recorded if a manual Reason for Requirement is also recorded
• Manual updates of Report Type:, Stimulus Code: and Frequency: fields on the RPRD screen need a manual Reason for Requirement.
• Record a Manual Reason Expiry date unless otherwise stated
• The Expiry date serves as a review date. Decide if auto profiling of a record should resume or if a manual Reporting Requirement should continue to apply
• Allowable Channels: how a customer can contact for a particular Report Type
• Each Report Type has its own Allowable Channels
• There are default Allowable Channel values for different Report Types
• Use Channel fields to add or remove channels
• In Customer First, select ? to the right of an Allowable Channels field to access Screen Help. This will display valid values, including Report Type/Allowable Channel combinations
• In Customer Record, enter a ? in an Allowable Channel field to access Screen Help. This will display valid values including Report Type/Allowable Channel combinations
• IVR - Phone Self Service
• PER - Personal
• MOB – Mobile. This option is not available via Customer Record
• PHO - Smart Centre Call
• POS - Postal or Fax
• WEB - Internet
• Delay Issue: If Reporting Statement (SU19) form is delayed for a customer with:
• A Report Type of 'S19'
• Reporting frequency of greater than '2 Weekly'
• Send delayed forms to the customer 2 weeks before the Report Next Due date
• The default value is 'N' but can be manually updated to 'Y'
• Assisted Reporter: identifies if a customer requires assistance to report
• Manually update the field with a 'Y' if a customer is deemed to require assistance, otherwise leave it blank
• The indicator will be automatically transferred to the RPRS screen
• AMR: Activity Management Reference number of the activity that recorded the Report Type

Add New Report Types of EAN on the RPRD screen.

If no other Report Type exists:

• a blank RPRD screen displays and
• new Report Type and characteristics can be added

For other Report Type occurrences, the RPRS screen shows a message to check the summary screen before adding new Report Types.

Press [Enter] with no selections to display a blank RPRD screen. This allows insertion of a new Report Type.

Note: customers and partners usually have the same reporting frequency. When manually updating the Report Type always check whether their partner's Report Type needs updating.

Only add or take 'OFF' Report Type 'EAN' on the RPRD screen. Insert Other Report Types on their source screens.

Only 1 current occurrence of a Report Type can exist at a time. Update existing current Report Type. Do not insert a new Report Type.

Record an (I)nsert action when recording a new Report Type on the RPRD screen.

To code the RPRD screen when adding a new Report Type of EAN:

• Report Type: EAN - Employment Income Report
• Stimulus Code: STM (Stimulus) - report required for current period payment issue
• Frequency: 2WE

Reason For Requirement:

• In Customer First, select the ? in the top right of the screen to open Screen Help. This shows valid values for this field
• In Customer Record, select [F1] to access Screen Help. This shows valid values for the field
• Update the field if the Report Type: Stimulus Code: or Frequency: fields on the RPRD screen are manually updated
• Update the Manual Reason Expiry: field if these fields have been manually updated
• Records with a manual Reason for Requirement are not subject to auto profiling, until the Manual Reason Expiry date is reached
• Manual Reason Expiry: the date a manual Reason for Requirement is to expire
• The Expiry date is a review date. Users must decide if auto profiling should resume or if a manual Reporting Requirement should continue to apply
• Allowable Channels: the methods a customer can use to contact for a particular Report Type. Each Report Type has its own Allowable Channels. There are default Allowable Channel values for different Report Types. Channel fields are used to add or remove channels
• In Customer First, select the ? icon to the right of an Allowable Channels field to access Screen Help. This will show valid values including Report Type/Allowable Channel combinations
• In Customer Record, enter a ? in an Allowable Channel field to access Screen Help. This will show valid values including Report Type/Allowable Channel combinations
• Assisted Reporter: identifies if a customer needs help to report
• Manually update the field with a 'Y' if a customer requires assistance. If not, leave it blank
• The indicator is automatically transferred to the RPRS screen

Take customers 'OFF' employment income reporting when they:

• Have ceased work and do not have mutual obligation/participation requirements, and
• Can provide paid leave/termination payment details. Override the Service Profiler to change the customer to a notification reporter
  Note: this also applies if the customer advises of NIL paid leave/termination payment
• Cannot provide paid leave/termination payment details. The Service Profiler will determine the reporting regime. Manually override the Service Profiler if the customer asks to be removed from reporting
  Note: ensure the customer's partner, if they have no mutual obligation/participation requirements, has also been removed from reporting
• Override the Service Profiler to change the customer to a notification reporter if:
• they do not have mutual obligation/participation requirements
• usually have variable employment income, and
• they advise their income is now stable

Always advise the customer of new reporting requirements and notification obligations.

Notification reporters must:

• report changes to their circumstances, including changes to income, within 14 days
• contact in person or Smart Centre to update their income details for their income support payment

Try to update the income estimate for Family Assistance payments such as Family Tax Benefit and Child Care Subsidy. Tell the customer the family income estimate is:

• separate from the income support payment, and
• can be updated online

To take a customer off reporting, use the Reporting Summary in Customer First or follow the below process:

Code the RPRD screen:

• Report Type: leave as EAN - Employment Income Report
• Stimulus Code: STM (Stimulus) - Stimulus required on due day
• Frequency: If employment income reporting is no longer required:
• Use 'OFF' to end the reporting requirement in Customer First or
• Select 'End this type' in Customer Record
• Note: only record a Frequency of 'OFF' for a Report Type of 'EAN'
• Reason For Requirement: update with the code that matches the customer's circumstances
• In Customer First, select the ? in the top right of the screen to access Screen Help. This shows valid values for this field
• In the Customer Record, select [F1] to access Screen Help. This shows valid values for the field, including:
• BVP - Bereavement Period
• DIS - Discretionary
• ECR - Employment Change - Regular Inc (not available in Customer First)
• HOL - Customer on Holiday
• NLW - No Longer Working
• TFC - Temporary Family Commitments
• TIN - Temporary Incapacity - Family
• TPR - Third Party Reporting
• Manual Reason Expiry: the date the manual Reason for Requirement is to expire. Leave blank and it will automatically use default date or can overstrike with a new date. This needs to be done twice for the system to accept the new date

If using the default date, tell the customer to contact if their circumstances change before the default date. For example, if using code 'HOL' the default is 98 days. If the customer returns before this date and re-commences employment:

• advise them to contact, and
• update reporting regime

Select Report Types using the RPRS screen. These will show on the RPRD screen.

When selecting current or future Report Types, the Report Type characteristics will show on the RPRD screen . Update these if applicable. This allows future dated Report Types to be updated and applied immediately.

When selecting historical or deleted occurrences, the RPRD screen is protected. This is to prevent changes to historical report characteristics when:

• the report occurrence has a Frequency of 'OFF', or
• is superseded/logically deleted by a later Report Type

A Report Type occurrence with a Frequency of 'OFF' and a future Manual Reason Expiry date can be updated. This allows

• manually recorded 'OFF' reason overrides to be shortened or ended, and
• auto profiling to reapply to the record

Note: this functionality is only available in Customer Record.

Manually update the characteristics of Report Types S19 and EAN on the RPRD screen.

All other Report Types have all fields protected. Updates to their characteristics must be made on their Report Type source screen. These updates then show on the RPRD screen.

Record changes to current or future Report Types using either an 'I'nsert or a 'C'orrect action. Reporting cluster processing either:

• creates a new occurrence of a Report Type, or
• deletes an existing occurrence, and
• creates a new occurrence if the same Start Date is calculated for the new occurrence

Report Type occurrences cannot be manually deleted by users.

The Start Date of a Report Type for a New Claim generally defaults to the Date of Commencement of the payment being reported.

Reporting Requirements for existing customers align with the 14 day payment period of the payment. For example, a Report Type occurrence Start Date will be the customer's Entitlement Period End Date (EPED) plus 1 day.

Automatic application of Report Type occurrences will apply a 7 day rule to decide if the Start Date will be the last EPED or the next EPED plus 1 day.

Manual updates of new or existing Report Types will always calculate a Report Type occurrence Start Date equal to the last EPED that has been paid plus 1 day. For example, the start of the current payment period for the customer. Manual updates cannot be applied with a future Start Date.

Recording a manual Reason for Requirement automatically sets a default Manual Reason Expiry date if one is not entered.

Note: some manual Reasons have shorter maximum Expiry periods while others do not require an Expiry date.

Update the EPED for a customer on the Entitlement Delivery (RAD) screen. Changing an EPED also changes the customer's Due to Report date.

Calculate the EPED from the Start Date of a Report Type. A new occurrence for a current Report Type will be created. A new Due to Report date and Reporting Statement will be sent to the customer.

Change the Manual Reason Expiry date to equal the new EPED date if:

• an EPED is changed while a manual Reason for Requirement is in place and
• a Manual Reason Expiry date also exists

For assisted reporting customers, manually update the Assisted Reporter: field on the RPRD screen with a 'Y'. A Display on Access DOC is created to alert that the customer is an assisted reporter.

If the customer has not reported by their due to lodge date, contact them to discuss their obligations.

If assistance is no longer required:

• remove the indicator from the RPRD screen, and
• expire the Display on Access DOC by typing today's date in the Expiry Date: field

Access the LRC screen via the Late Reporters script. Only the designated officer in each service centre should use this screen. It uses a large amount of system resources.

The Late Reporters script is in the Assessment/Contact/Newclaim sub menu.

To manually access the LRC screen, (if the script is unavailable), code 'LRC' in the Nxt: field and press [Enter]. Use the following criteria to search for late reporting customers and press [Enter]:

• Mandatory
• Region
• System (such as, NSS)
• Reporting Date - this date may be in the past, today or up to 14 days in the future
• Optional
• Postcode
• Assisted Reporter status
• Benefit type code
• Community code

The resulting list will show:

• names
• home and/or mobile phone numbers, and
• if a customer is an assisted reporting customer who has not reported by a specified date to stimulate their payment

Note: Restricted Access records will not be displayed.

If the Assisted Reporter indicator is coded as Y to identify an assisted reporting customer, these customers only are displayed.

If the Assisted Reporter option is not chosen, a list of all customers who match the search criteria will be displayed. If any of these customers are assisted reporting customers, the Assist: field will display a 'Y' against their record.

Within the list display, [F7] and [F8] allow scrolling to the previous and next pages.

A selector field is provided next to each customer. 'S'electing a customer record will show the Reporting Regime Summary (RPRS) screen for that customer.

Multiple selections from the displaying page can be made. If multiple customers are selected, the next record is accessed by coding 'NX' in the Nxt: field.

When re-entering the LRC screen after viewing the customer record(s), a new search based on the original search details will display the updated list. The last record viewed displays on the top line.

If a single customer is selected and is taken to the RPRS screen, the system will go back to the LRC screen if no input is entered in the Nxt: field and [Enter] is pressed.

To print the late reporting customer list, either:

• code 'Y' in the Print: field at the bottom of the screen then press [Enter], or
• code 'P' next to a record on the list and 'Y' in the Print: field to print the list from that selected record to the end of the list

The Printer No: and Class: fields must also be completed.

This screen displays a summary of current and outstanding forms, letters or statements that are part of a customer's reporting requirement.

Current or outstanding reports will be displayed on this screen. When a report requirement is finalised or expires it is no longer displayed on this screen. If no current report requirement exists this screen will not display any details.

Some forms, statements or letters required for reporting can be reissued from this screen.

The RPTI screen can be accessed by:

• coding 'RPTI' in the Nxt: field, or
• selecting the screen from Reporting Task Selector (RPTS) screen

If no current or outstanding report type exists, the screen is protected and an information message will be displayed.

If there are multiple pages of the RPTI screen, view by scrolling [F7] / [F8] or enter a page number in the Page of field.

RPTI screen is sorted by Due Date order with the next Report Type due appearing as the first line on the screen. If multiple Report Types are due on the same date they are listed in alphabetical order.

The select field precedes all lines displayed and is used to view or reissue a report, see Item 5.

• The remaining fields are display only fields
• Issue Date: date the reporting form, letter or statement was sent
• Report Type: the form, letter or statement type that was issued
• End Date: date a form, letter or statement is due to be returned or reported or the report period's end date
• Issued: whether a form, letter or statement was sent by the system or manually reissued
• Sys: indicates the host system of the payment that the Report Type applies to, for example, NSS, PGA or PEN
• AMR: Activity Management Reference number of the activity that recorded the Report Type

The select field can be used to:

• 'S'elect a line to view more information in the Report Type Components (RPTC) screen see Item 6, or
• reissue a report via post or local print. Report Types that can be reissued:
• S19 - SU19
• R19 - Recipient Statement Notice
• IRM - Intensive Review Model
• SWP - Seasonal Worker Preclusion questionnaire
• IMP - Income Maintenance questionnaire
• RIS - Reporting Statement

Code 'P' next to the entry to be reissued to bring up a confirmation field in the screen footer. After confirming the reissue, the report is printed centrally and posted to the customer's current address.

Code 'L' next to the entry to be reissued to bring up confirmation and printer fields in the screen footer. After confirming the reissue, the report is printed locally.

Confirmation of the reissue request and a local printer destination (if not defaulted) is required for the report print.

Note: the preference would be to use the Reissue Report workflow.

What if the RPTI screen is blank or does not list the required form?

The RPTI screen displays a summary of current and outstanding forms, letters or statements that are part of a customer's Reporting Requirement.

If a customer requests a form that is not present on the RPTI screen, first check the Reporting Regime Details (RPRD) screen to confirm the customers reporting requirement.

Note: if the customer has returned the last report, there is a slight delay between the report being processed and the next Reporting Statement generating. During this delay the Reporting Statement may not appear on the RPTI screen.

If the customer does not currently have a reporting requirement they will need to be placed on reporting via the Reporting Regime Details (RPRD) screen table, before a Reporting Statement can be issued.

RPTC screen displays the content of a customised report sent to a customer. It is accessed by 'S'electing a Report Type from the RPTI screen. A current or outstanding report can be reissued from this screen.

Current or outstanding reports are displayed on this screen. When a report requirement is finalised or expires it is no longer displayed on this screen. If no current report requirements exist this screen will not display any report details.

Text paragraphs listed on the RPTC screen can be expanded to display the text of a form.