Single Touch Payroll (STP) 108-22070738

The EMCF screen shows the:

• STP Employer Update table
• Employment Income data table

STP Employer Update table:

• Action field: an edit and delete button show when in the STP Employer Update or Earnings and Reporting workflows
• Record Status field: the status of the STP employer’s details reviewed by the customer:
• Confirmed (default status)
• Unconfirmed
• Provisional
• STP Employer Name field: shows the employer’s registered business name
• ABN field: shows the employer’s 11 digit ABN or 9 Digit WPN
• Status field: shows the status of the employer relationship:
• Confirmed (CNF): customer confirms they are working for that employer
• Rejected (REJ): customer advises they do not work for that employer
• Auto-matched (AUT): system has automatically matched the pre-filled employer’s ABN/WPN with that of an existing employer’s ABN/WPN from EANS (auto-matching no longer occurs, but this status may still show)
• Blank: the customer has not reviewed the pre-filled employer’s details
• Submitted On field: the date of the last update to the Record Status. This may also revert to the previous update date if re-confirming the status as part of a correction
• Linked Employer field: the name of the matched employer from the customer’s existing employer list on EANS. This may also be a brand new employer entry

Note: if either the Status, Submitted On or Linked Employer fields are blank, the STP Employer Update workflow must be run to re-confirm the employer status. See Item 3

Employment Income data table:

• A view only reference table of existing employers on the customer’s record (EANS)
• Select the twisty for relevant employers to view historical income from (EAN) to help determine the correct employer to link to

When new STP employer data is available at the time a customer is reporting, the EMCF screen will show with the STP employer details in the Earnings and Reporting workflow in Process Direct.

Service Officers must discuss the pre-filled details with the customer and either confirm or reject the employer details. See Item 3.

If the customer:

• confirms the STP employer, the EMCF screen is not shown again in future reports, unless STP data is available for another employer
• rejects the STP employer and STP data is available in the next reporting period, the STP employer details are pre-filled again for the customer to review
• rejects the STP employer a second time, the STP employer’s details will not pre-fill again and an STP Intervention is generated for further investigation by trained Service Officers. See Single Touch Payroll (STP) interventions Note: this will only occur where a customer rejects the STP employer when using self-service

Before STP employment income can pre-fill for customers and Service Officers, a confirmed STP employer status is needed with completed Status, Confirmed On and Linked Employer fields on EMCF.

The standalone STP Employer Update workflow can be used to confirm or reject a new STP employer, or update an existing STP employer’s record status. Service Officers can also make the same updates on the EMCF screen when using the Earnings and Reporting workflow.

• Key START into the Super Key
• Select the STP Employer Update workflow from Task Selector
• Select Start
• On the EMCF screen, select Edit to launch an STP Employer Update window
• Select Confirmed or Rejected from the Status drop down:
• If confirming, the Employer drop down will list all current employers from EANS
• Select the existing employer name or New Employer from the menu, then Save. Selecting Cancel will go back to the original screen
• If linking as a New Employer, it will pre-fill to EAPP with a pay event of 0.00 with a DOV as the Entitlement period start date (EPSD) that the update is being made
• When selecting Save, a Receipt Date and Channel window shows. Complete the details and select Save
• The EMCF screen will show the provisional updates. Check the details are correct, then select Next to continue
• The EANS screen will show the updated employer with Employer Verification field as STP
• Select Assess and Finalise the task

If the STP employer status is rejected and STP data is available when the customer next reports, the STP employer name and ABN/WPN will show again for the customer to review. If the customer rejects the employer a second time, an STP intervention activity will be created for follow up by trained staff.

Customers making an online claim may be presented with STP employer details that have previously been confirmed. If the customer rejects this employer within their online claim, there will be no change to the confirmed status on EMCF. Staff should not update the confirmed status to rejected.

Note: when an STP employer has been confirmed and linked to an existing employer from EANS, the pre-filled ABN will override the Employer ABN field of the linked employer. The ABN field of the STP verified employer will become greyed out and unable to be updated from EANS.

If an incorrect employer was linked, run the STP Employer Update workflow to update the STP employer status to rejected. This will remove the overridden pre-filled ABN. When the activity is complete, the Employer ABN field of the incorrectly linked employer will revert to its previous status. The STP Employer Update workflow may need to be run again to re-confirm the STP employer and link the correct employer from the existing employer list or select New Employer.

An update to an existing STP employer may be required when:

• a customer contacts to correct their previous rejection of an STP employer
• the incorrect employer was selected from existing employers on the customer’s record and linked to the STP employer
• a fix is required to resolve an error that may show when there are multiple employer entries (STP and non-STP) for the same employer and ABN/WPN that is preventing the customer from reporting in self service
• the previously confirmed STP employer status appears incomplete, for example Status, Confirmed On and/or Linked Employer fields are blank

The STP Employer Update workflow must be run to either re-confirm or reject the employer status. See Item 3.

Note: if the workflow is run to reject an incorrectly linked employer, the workflow must be run again to re-confirm and link to the correct employer. Service Officers cannot reject and confirm in the same transaction. Each action must be completed separately before the next action can occur.

To resolve errors, including E009EA - You cannot enter a duplicate ABN/WPN and E016CQ - Details for this type of income already exist when duplicate entries of the same employer and ABN/WPN exist, complete these steps:

• Review the employer and ABN entries on EANS. Identify all matching employer entries
• Identify the correct employer entry. Things to consider are:
• Do any of the employer entries have an Employer Verification status of 'STP'?
• Is there a recently added employer entry with an Employer Verification status of STP when there was already an existing employer entry with income coded?
• What is the earliest income recorded and the volume of data on each employer entry?
• Is there evidence of previously verified employment income (for example, random samples survey or employment income reviews)?
• When the correct record is identified run the STP Employer Update workflow
• If the STP Employer Update (EMCF) screen shows multiple employers with the same ABN on the Employment Income data table:
• go to EANS
• select edit for the employer that is not STP verified and remove the ABN, select Save and go back to EMCF
• From EMCF, select the edit button to reject the current STP employer status, select Save and finalise the activity

If E016CQ occurs, check if there is another employer entry on EANS with the same ABN/WPN. If so, follow the same steps above before making updates to EMCF to remove the matching ABN/WPN from the other non- STP employer entry on EANS, or if there is no ABN duplication.

• Check there was an existing employer entry on EANS for the STP employer. After rejecting the employer status on EMCF, it removes the linked ABN to the existing employer that the STP employer was linked to. Copy the ABN from the ABN field on EMCF and enter it in the ABN field of the existing employer entry on EANS, and select Save
• When all troubleshooting has been applied, finalise the activity
• Run the STP Employer Update workflow again to confirm the employer status and link the correct STP employer. See Item 3. Select Save and Next
• When on EANS, merge any pay events that were coded on the incorrect or duplicate employer entry onto the correct STP employer entry. To do this, use the Snipping Tool to take a copy of the income details coded on the ‘incorrect or duplicate’ employer. Replicate the coding from the snip onto the STP employer entry. When income is merged to the correct STP employer entry, delete the income from the incorrect or duplicate employer. For more help with coding employment income, see Recording and correcting employment income details
• When all employment income updates have been made, finalise the activity. Note: no arrears or debt should be generated. If arrears or a debt is generated staff must check their recoding before finalising the activity

If a previously confirmed STP employer has reverted to a ‘provisional’ record status, it may prevent STP data from pre-filling for customers or staff. The record status must be updated.

Service Officers can identify this by the Record Status being 'Provisional' without there being a started transaction. The Status field will also show as Confirmed but the Submitted On and/or the Linked Employer fields may be blank.

• Launch the Earnings and Reporting workflow or the STP Employer Update workflow
• Select the delete icon next to the relevant STP employer on the EMCF screen
• If the Record Status remains as Provisional, select the delete icon again
• If the error Row with the index 1 is not in the table shows, perform a refresh by:
• right clicking on mouse, or
• use Ctrl+ R, and
• select ‘reload’
• Go back to the EMCF screen to verify that the STP employer status now shows as Confirmed
• Finalise the activity

If a previously confirmed STP employer’s record status reverts to ‘unconfirmed’ on EMCF, Service Officers can refresh the record status.

Select Retrigger located above the STP employer table on the EMCF screen.

STP data can only be retrieved using the Earnings and Reporting workflow in Process Direct or when customers report using self-service channels. Where Service Officers complete a customer’s report using Customer First, any STP data available with a Date Paid in the reporting period is not retrieved. STP pay events reported by the employer can only be accessed on the EMGI screen in Process Direct. This information is displayed across 3 levels of tables where each level provides more details. To access each level of data, select the twisty next to each row.

Pre-filled STP data cannot be deleted on EMGI, however it can be adjusted when using the Earnings and Reporting workflow. Information can only be edited on the Income Details table at the third level. If Service Officers do not use the workflow, this screen will have view only access.

A high level view of total gross employment income details that have been reported for a certain period. If using the Earnings and Reporting workflow to complete a report or to update past periods, the STP income reported in the reporting period(s) or past periods will show one reporting period at a time. Otherwise, it will show all available STP data for a date range that has been manually selected on EMGI outside the workflow.

This table includes the following fields:

• STP Employer Name: the registered business name with the ATO
• ABN: the 11 digit ABN or 9 Digit WPN of the employer
• Linked Employer: the name of the matched employer from the customer’s existing employer list on EAN
• Gross STP Income: total gross income reported by the STP employer
• Gross Income Reported: the total gross income paid that is confirmed by the customer. If the customer has not made any changes, this figure will be the same as the Gross STP Income
• Income Variation: this indicates if the employer reported Gross STP Income has been adjusted. It will show as either Upward varied, Downward varied or Not varied
• Reporting Period Start Date: the start date of the Services Australia reporting period (EPSD)
• Reporting Period End Date: the end date of the Services Australia reporting period (EPED)

A view of the individual STP pay events paid within a reporting period or past periods. Where a customer is paid weekly, there may be 2 pay events to view for each reporting period or when updating a past period. Otherwise, it will show all pay events for a date range that has been manually selected on EMGI outside the workflow.

This table includes the following fields:

• Action: the edit/pencil option is currently deactivated
• Pay Event Accepted: Yes/No advises if the customer has accepted the pay details, with or without changes
• Pay Event Date: this is the date employment income was paid, as advised by the employer (not necessarily the date the income was received by the customer). See Determining the Date of Event for employment income
• Pay Period Start Date: the start date of the employer’s pay period
• Pay Period End Date: the end date of the employer’s pay period
• Gross STP Income: total gross income reported by the STP employer
• Gross Income Reported: the total gross income confirmed by the customer. If the customer has not made any changes, this figure will be the same as the Gross STP Income
• Commencement Date: the employer reported date of when the employee commenced work
• Employment Status: full time, part time, casual, contract or labour hire
• Cessation Date: the employer reported date that the employee ceased work
• Cessation Reason – the employer reported reason of why the employee ceased work
• Record Status: a default of Confirmed

A detailed view of the individual pay components that have been reported for each pay event within a reporting period/s or past periods.

This table includes the following fields:

• Action: the Edit/Pencil icon is selected to edit the data
• Record Status: a default status of Confirmed
• Wage item: the type of wage item that has been paid, for example, Salary and Wages, Reportable Fringe Benefit Amount
• Component: a breakdown of the type of component that the wage item is. For example, Gross Income, Paid leave, Overtime
• Subcomponent: more detail about the component. For example, unused leave on termination, other paid leave. This is an indication more information may be needed
• Additional information: this will advise if a reported Other allowances component is a reimbursement of work related expenses or not. This response is provided by the customer and determines whether the income is assessable. See Table 4, Other Allowances
• RFB Free Acco or Avg. Weekly Wage: this will indicate the value of free accommodation as part of Fringe Benefits, or the average weekly wage of the customer’s recent income when paid a redundancy payment after ceasing employment
• STP Income Received: gross income of the pay component reported by the STP employer. Note: when a customer adds a pay component that did not pre-fill, this field will show as 0.00
• Income Reported: the gross income amount of each pay component confirmed by the customer. When the customer adjusts the pre-filled STP data amount, it will be different to the STP Income Received amount Note: when a customer adds a pay component that did not pre-fill, this will show the amount the customer has added
• Adjusted Period Start Date: adjusted employer pay period start date, if applicable. This is required when Other paid leave or lump sum payments are reported. See Table 4, Item 18 for more information
• Adjusted Period End Date: adjusted employer pay period end date, if applicable. This is required when Other paid leave or lump sum payments are reported. See Table 4, Item 18 for more information
• Used in PayPP Calculation: Yes/No. Indicates if a pay component is assessable. If not assessable, the pay component is not included in the data mapped to EAPP. For example, some allowances. See Resources for details
• Amount Mapped to: where income is assessable, this field advises the screen that the confirmed income is coded, as either EAPP or IMPS. Otherwise it will be blank

Going to EMGI outside of a workflow will give a view of STP pay events that have already been retrieved. STP data is retrieved for an employer that is confirmed on EMCF when:

• a customer reports through self service or
• a Service Officer has used the Earnings and Reporting workflow in Process Direct

To refresh the view of retrieved STP data, select the date range in the From and To fields. Select search to view all STP data in the relevant period.

There may be times where EMGI does not show any or only some pay events. This may be because the employer has since been rejected on EMCF, or STP pay events were not retrieved due to the following reasons:

• Previous Service Officers have completed a reporting task using Customer First
• STP data was not available at the time the reporting task was actioned
• STP data was available, but did not pre-fill to the customer online, for example, data anomalies, non-EAR employers, partner reported on behalf of the customer. See Resources for further examples

To check if other STP data is available, Service Officers must run the Earnings and Reporting workflow:

• select Update past periods and select the date range to query
• select Search. The Past Period Range table will show Yes in the STP data present field for any reporting periods that STP data is available
• select the relevant reporting periods, then Next. This will show the STP pay events on EMGI for review, one entitlement period at a time

Note: if an employer was previously rejected, Service Officers will need to manually go to the STP Employer Update (EMCF) screen first, confirm the STP employer to allow retrieval of the STP data and then manually go to EMGI.

Where STP data is available at the time a customer reports, it may pre-fill in the reporting task in all self service channels:

• Centrelink online account
• Express Plus Centrelink mobile app
• Interactive Voice Response (IVR)

Where STP data is available to pre-fill in an online report, the reporting task becomes a 2 step process for customers:

• STP confirmation service, and
• Report employment income (REI) service

Once the customer selects the online reporting task, a ‘Before you report’ message shows to advise the customer there are details reported by their employer. The customer then enters the STP confirmation service to review the pre-filled information.

The first time STP data is available, the customer is asked whether they work for the employer. They must review the STP employer’s name and ABN/WPN and confirm or reject the employer. See Reporting employment income online for more details. Once the STP employer is confirmed, the reporting task progresses to show any STP employment income paid in the entitlement period.

Depending on how often a customer is paid and the data available when the customer reports, pay events will show one at a time, for example labelled as Pay 1 of 1, or Pay 1 of 2 and Pay 2 of 2.

If there is more than one STP employer, the STP data will show one employer at a time for the customer to check and confirm or change. The customer must review and confirm the STP data paid from the first employer before being able to review and confirm the employment details reported by the second employer.

Customers have full control over the STP data pre-filled in their reporting task. They can adjust the pre-filled details and add pay components that have not pre-filled yet, if required (See Table 3, Item 3), before confirming the STP employment details and continuing with their report. Customers can check their payslips if they are unsure about the pre-filled details.

When a customer selects Submit and continue at the end of the STP confirmation service, they are confirming their STP data. Customers have multiple opportunities during the STP confirmation service to edit and add to the pre-filled STP data, if needed. If the customer needs to make changes to the confirmed data after selecting Submit and continue, they cannot go back to make changes. If the customer realises that a separate pay event didn’t pre-fill from their STP employer, the customer can add this in the second part of their report.

Note:

• Customers are not able to add pay events paid by non STP employers in the STP confirmation service
• Customers can only add pay components to the pre-filled STP data of the employer they are currently reviewing in the workflow
• When the customer confirms the STP income details online, the data is automatically applied to the EAPP/IMPS screens
• Hours worked are not included in the STP data
• If an STP Pay Event paid in the reporting period is not available at the time the customer reports, the pay event will not pre-fill in a later reporting period

The ‘Reporting tips’ message displays the first two times the customer enters the REI service and advises the customer how to report the right way.

Customers will see the assessable income that was confirmed in the STP confirmation service pre-filled under My pay. If needed, they can add the following details in the REI service:

• additional pay events paid by the STP employer
• income paid by non-STP employers
• income paid to their partner, and
• hours worked in the entitlement period, if needed

Customers are not able to change the confirmed STP employment income in the REI service. See Item 4.

Customers have a further opportunity to review the employment income added before they accept the reporting declaration and Submit their report.

Online guides for customers and staff simulations can help with customer enquiries. See Resources for links.

When STP data is available when reporting, it has a provisional status. Customers can change the pre-filled STP details, if required, before confirming the data. It is important that customers check their payslip/s carefully, if they are unsure about the pre-filled details.

Pre-filled STP data may need to be updated by the customer where the STP employer:

• has made a mistake when reporting pay components and/or amounts
• has made a correction to an amount already reported to the ATO
• submits the final end of financial year (EOFY) payment summary details that incorrectly pre-fill in the reporting task

Customers can select Edit or add pay to adjust a pre-filled STP component amount (or change to zero). For example, they can adjust the amount of a pre-filled pay component or add an additional pay component paid in the same pay event. If a customer is paid weekly and only one pay event has pre-filled, they can select Add pay to add the second weekly pay event details.

Customers are not able to declare other non-STP employment income, partner income or hours worked while in the STP confirmation service. This can be done after the STP data has been reviewed and accepted in Step 1, and the customer has continued to the REI service (Step 2) to complete their report.

Employees may have their employment status reported by their STP employer. A full time employment status may pre-fill up to two times of the data first being reported. Customers can select Edit employment status to update this, if needed. Note: the definition of Full time employment is not the same for the ATO and Services Australia.

When the STP declaration is accepted, no more changes to the confirmed pre-filled STP data can be made by the customer. Customers do not need to upload payslips if they make a change to the provisional STP data, but Services Australia may ask for more information later.

When a customer reviews their STP data and selects Submit and continue in the STP confirmation service, they are unable to change the confirmed STP data through self service channels. This includes where they have not yet completed their report. If the pre-filled gross amount should have been adjusted before it was confirmed, the customer must contact on their regular payment line to discuss.

If a customer realises they needed to add further income details for their STP employer, they can select Add more pay under My pay in the Report employment income service. They will then be able to add pay amounts that did not pre-fill, before finalising their report.

Employment income reported in the last 6 reporting periods can be viewed by customers through self service. Once confirmed, customers are not able to change STP data in a previous report. They must contact Services Australia and give evidence of the changes (payslip/s, a payroll report or a letter from the employer) before Service Officers make any updates.

Evidence is not required where it is clear the changes are only where there has been a duplication of income. Service Officers must clearly DOC this decision and conversation with the customer.

STP data is only available to Service Officers when using the following in Process Direct:

• Earnings and Reporting workflow
• STP Employer Update workflow
• STP Interventions workflow
• manual navigation to the STP Employer Update (EMCF) or STP Employer Wage Items (EMGI) screens (view only)

When STP data is confirmed and accepted by the customer, it is automatically loaded onto the appropriate screens on the customer’s record.

The Employment Income Paid Details (EAPP) screen will show:

• that each assessable employment income component paid in a pay event is coded separately under the one employer name
• a frequency of Long Period (LOP) with the start and end dates of the employer pay period or the duration that certain pay components were paid for (as advised by the customer). LOP is the default frequency code used for all confirmed STP income components. This does not need to be changed. See Recording and correcting employment income details for further information
• DOV as the date the employment income was paid, as reported by the employer. See Determining the Date of Event for employment income
• a verification code of STV for confirmed STP details, or NVE for manually added income by the customer

Confirmed unused leave and termination payments paid when a customer ceases work are mapped to the IMPS screen with a verification code of STP. See Cessation Data.

If a customer contacts querying the pre-filled STP data, Service Officers can provide staff assisted reporting after providing education about reviewing and adjusting pre-filled STP data. Service Officers must use the Earnings and reporting workflow in Process Direct to action the report. See Recording and correcting employment income details for general processing instructions.

Service Officers cannot delete STP data from the STP Employer Wage Items (EMGI) screen. If a customer advises the pre-filled STP data does not match the gross amount paid after checking their payslip(s), before accepting the income Service Officers must:

• adjust the amount, and/or
• add to the pre-filled amounts on EMGI as advised

Adjusting STP data may be required where:

• multiple entries of the same pay event display, for example, adjusting duplicated amounts to 0.00 so only the singular pay event remains
• the STP Date Paid is incorrect. See Item 6 in Table 4
• multiple pay events are pre-filled as a lump sum
• incorrect pay components and/or amounts are pre-filled
• the STP employer makes corrections to previously reported STP data, that impacts the PayPP calculation in the current reporting period
• amounts have already been reported to the agency
• amounts are pre-filled for a pay event paid prior to the customer or partner being in receipt of an income support payment
• a year-to-date (YTD) or payment summary amount pre-fills
• an unusually large gross income amount pre-fills, compared to other recent pay events
• a ‘pay event date’ and/or ‘pay period start and end date’ on or around the 30 June
• negative income component(s) offset by identical positive income component(s) in the ‘Income Details’ table
• a ‘Gross STP income’ of zero and a positive ‘Gross Income Reported’ amount in the ‘Pay Events’ table
• an employment cessation date in the past with unused leave and/or termination payments

Service Officers must:

• discuss and clarify the requested changes to gross STP amounts with the customer, before making any updates. Check DOCs and Document Tools for any relevant evidence (for example, payslips or SU1)
• tell customers the agency may request evidence at a later date
• DOC all details of the discussion

If a customer has regular discrepancies with their pre-filled STP data:

• Service Officers must request payslips to lodge a mySupport request through 'Single Touch Payroll (STP) pre-filled employment data' request form
• the STP program monitor employer behaviour and will escalate discrepancies to the ATO when necessary

Service Officers must not:

• contact STP employers
• tell customers to contact their employer(s) to discuss any differences between the pre-filled STP data and the related payslip

Care must be taken when reviewing the record if a customer contacts to make changes to:

• confirmed STP data, or
• they are returning contact about an STP Intervention

Note: For STP Intervention enquiries, untrained Service Officers must transfer these calls via Services Australia Workspace to the STP Intervention team. Where Services Australia Workspace is not available, transfer the customer to 1800 061 838. Procedure ends here.

Discuss with the customer why the confirmed STP data needs to be changed. Evidence must be provided (payslip/s, a payroll report or a letter from the employer) to verify the confirmed STP data was incorrect and before making any updates.

Do not manually make updates to the STP data directly on the EAPP or IMPS screens.

All updates to STP data must be actioned in the Earnings and Reporting workflow in Process Direct, selecting Yes when asked to update past periods.

After selecting the relevant periods from the Past Period Range, the EMGI screen shows. Each reporting period will show one at a time. When the correction for the reporting period is made, select Accept Income, then Next. This action applies the changes to the EAPP and/or IMPS screens.

Check the following:

• Changes on EMGI are being correctly applied to EAPP. Where duplicated amounts have been adjusted to 0.00, the income that had mapped to EAPP must be deleted
• Income has not been doubled up from having STP data applied where income was originally manually coded with NVE code. Where manually coded income results in duplication of a pay event, delete the manually added entries. Any updates to cessation payments on EMGI may insert a new entry on IMPS. Make sure to delete the previous coding that had mapped

If multiple reporting periods need updating, the workflow repeats until all reporting periods have been actioned.

Where a customer has accepted pay events that have been duplicated, evidence is not required when it is clear the data has been duplicated. Service Officers must Update past periods and zero out each duplicated pay component on EMGI so that only the singular pay event remains.

Once Accept income is selected, the Gross STP Income field will show the duplicated total and the Gross Income Reported field will show the correct singular total for the reporting period.

When going to EAPP, Service Officers must delete the duplicated components so only the singular pay event remains, as system functionality does not allow a correction of $0 to be inserted.

In limited cases, the EOFY payment summary details reported by an STP employer to the ATO may pre-fill in a customer’s report and is confirmed by the customer. These cases may have the following characteristics on EMGI, but are not limited to:

• an unusually large gross income amount, compared to other recent pay events
• a 'pay event date' and/or ‘pay period start and end date’ on or around the 30 June
• negative income component(s) offset by identical positive income component(s), in the ‘Income Details’ table
• a 'Gross STP income' of zero and a positive 'Gross Income Reported' amount in the 'Pay Events' table
• an employment cessation date in the past, with unused leave and/or termination payments

Customers may also advise they ceased work for the STP employer during the financial year, prior to claiming an income support payment.

Check DOCs and Document Tools for any relevant evidence (for example, payslips or SU1) and talk with the customer about the confirmed STP data. If it is clear that the STP data is due to the incorrect pre-fill of payment summary data, update the record using the Earnings and reporting workflow in Process Direct and clearly document the record. No evidence is required. Check that the customer’s reporting frequency is appropriate.

Evidence may be required in some cases prior to Service Officers making changes to the confirmed STP data, where it is identified:

• that the pre-filled employment income was not previously declared while the customer or partner received an income support payment, or
• there are inconsistencies with the information already on the record

Service Officers must document the details of the conversation and the action taken.

Service Officers must use the Earnings and Reporting workflow in Process Direct to make the required updates and :

• record notes of the conversation with the customer
• record the details of changes made on EMGI and the source of the evidence before finalising the reporting activity
• consider requesting payslips and escalating to mySupport where the customer consistently makes changes to the pre-filled STP data that is reported by the employer

If updating a past period of employment income that was manually coded on EAPP, and STP data is available that was not previously accepted, the workflow will go to EMGI to check, confirm or change the STP details.

Once Accept income is selected, the confirmed STP data will update on EAPP. The income that was manually coded must be deleted. This is because updates to EMGI will only update any related STP pay events that had been previously confirmed and mapped to EAPP.

Note: if the Earnings and Reporting workflow task in Process Direct is not selected, the edit option on EMGI is not functional. Service Officers will only be able to view STP data outside of a workflow.

See Recording and correcting employment income details for coding instructions

Check the STP employer status on the STP Employer Update (EMCF) screen is confirmed and all fields are completed, for example, date submitted and linked employer. See Item 4 in Table 1.

After viewing and confirming the STP data, ensure that Accept income is selected. Once the Accept income button has been selected, it will become greyed out.

Check if the STP employer has been linked to an existing employer that is an SWS/ADE employment type. Confirmed STP income will not map to EAPP. Service Officers must manually code the confirmed STP data on EAPP.

If the income was mapped to EAPP but has been inadvertently deleted:

• go back to EMGI
• select the pay event/s that need to be mapped to EAPP again
• select the edit button and then Save without any changes. This will reactivate the Accept income button
• once selecting Accept income, the pay event details will map back to EAPP

STP data reported by employers to the ATO is prepared by Services Australia in near real time to pre-fill in reporting channels. For more details, see The Digital Gateway.

The below circumstances may result in STP data not pre-filling in a reporting statement:

• the employer does not report payroll via Phase 2 STP enabled software yet
• no match was established on the Mutual Client Register (MCR). See Mutual Client Register (MCR) for Service Delivery staff
• the customer has rejected the STP employer twice through self service
• the customer has previously had an employment type of SWS, ADE, AOE, SAC, PSS or PSG recorded on EANS. STP data will only pre-fill in a customer’s online report when there are only EAR employment types on EANS. (STP data would then only be accessed through staff assisted reporting in Process Direct)
• the confirmed STP employer reports payroll later on the day that the customer reports. This may include where one weekly pay event is pre-filled, but a second weekly pay event is not available
• the confirmed STP employer has not reported payroll yet when the customer reports early due to a public holiday or travelling overseas. Employers may delay reporting payroll during shutdown periods
• inconsistent reporting dates from the employer
• missing data attributes resulting in filtering out of STP pay events
• unusual data may trigger a Low Confidence Indicator which will prevent STP data pre-filling
• known system issue where the STP employer’s record status on the STP Employer Update (EMCF) screen reverts to provisional. See Item 6 in Table 1 to resolve
• data transfer delays between the employer, the ATO and/or Services Australia. Check NNUs
• data preparation issues. Check NNUs

Note:

• STP pay events reported after the relevant reporting period do not pre-fill for the customer to review in a later reporting period
• STP data for a partner does not pre-fill for a customer
• Service Officers can retrieve STP data from a previous reporting period that has not been checked by using the Earnings and Reporting workflow. Select the relevant reporting periods from the Update Past Periods screen
• Hours worked are not included in the STP data

Unconfirmed STP data will only pre-fill in the workflow for the reporting period being processed. This means that when a customer’s report has been completed, the workflow does not automatically go to the STP Employer Wage Items (EMGI) screen if it is run again as the STP data has been reviewed and confirmed.

If needing to view or update the current or past STP data, select Update past periods and select the date range to check. This action is needed even when updating an STP pay event confirmed earlier on the same day.

If the Accept Income button is greyed out when completing a reporting task, it means the STP data has already been confirmed. DL will have a DOC with details of the accepted STP data and if there were any variations made.

If no changes are needed to the already accepted income, check the income has mapped to EAPP and finalise the activity.

If the customer has contacted as they confirmed the pre-filled income before making changes, refer to Item 8 in Table 3 about whether evidence is required. Select the edit button for the component that needs to be changed, make the updates and select Save. This will reactivate the Accept income button.

Depending on when a customer reports, there may be times when all pay events paid in the reporting period are not pre-filled. The most common scenarios are where customers are paid weekly, or fortnightly payroll which is reported by the employer to the ATO on the same day the customer reports.

Customers who are paid weekly by their STP employer, may have only one pay event pre-filled at the time of their report. Even if an employer has reported their payroll data on the same day, the STP data needs time to be prepared for it to pre-fill.

The customer must add pay details that have not pre-filled. In some cases, it may be appropriate to discuss with the customer about changing their reporting day. See Changing Entitlement Period End Dates (EPED)

The date of event used to assess employment income is the date the employer pays the employee, not when the employee receives the payment. See Determining the Date of Event for employment income.

Customers and Service Officers are not able to edit the date paid reported by the employer through STP. Usually, the date is correct as it is reported by the employer. Tell the customer to check the Date Paid displayed on the payslip.

If the customer advises the provisional STP date paid is not correct and needs to be changed, tell the customer the pre-filled pay event amount(s) can be zeroed and then re-coded as a new pay event with the date paid when reporting through self service.

Where Service Officers are assisting with the report and the customer states the amounts paid are correct but the date is not:

• Select Accept Income on EMGI
• When on EAPP, select the pencil/edit button and change the provisional date paid only
• DOC the reason why the date paid has been adjusted. Note: if DOCs indicate or the customer advises there is an ongoing issue with the STP paid date see Table 4, Item 8

Customers have control over the STP data that pre-fills and can make adjustments when the pay details do not match their payslip.

There may be times when the data does not match, due to but not limited to:

• the employer having made a mistake when reporting pay components
• the employer reporting final pay details at the end of the financial year, for a previous period already paid
• the employer making a later correction to an amount already reported to the ATO
• missing data attributes filtered out a previous pay event(s). When this is resolved, the missing STP pay event(s) are included in the total of a later pay event
• the employer reporting multiple pay events in the same report

In all cases where a customer advises the pre-filled amounts do not match their payslip, corrections must be made before confirming the data.

Service Officers must not:

• contact STP employers to discuss the STP data
• tell customers to contact their employer(s) to discuss any differences between the pre-filled STP data and the related payslip

Ongoing discrepancies in the STP data transferred to Services Australia must be reported to mySupport once payslips are provided. Cases are investigated and escalated to the ATO, as required. See Table 4, Item 8

Customers can be advised to talk to the employer only where they have questions about their payslip.

Customers have control over the STP data that pre-fills and can make corrections when the pay details do not match their payslip.

In some cases, there may be one-off events where pre-filled data may not match the details on the payslip. Contact Local Peer Support if unsure about the pay components as they may show differently through STP compared to the payslip, but the total gross income is the same.

Where a customer has advised the STP data is consistently incorrect, payslips must be provided to clarify the discrepancies. Once uploaded, Service Officers must lodge a mySupport request through the Single Touch Payroll (STP) pre-filled employment data request form. See Resources for a link.

Where Service Officers are helping a customer report and they advise the pre-filled amount is incorrect, Service Officers must DOC the discussion. Where Service Officers can see the customer has varied pre-filled data in previous reports, make sure payslips have been requested and uploaded, and lodge a mySupport request.

The STP program monitor employer behaviour and will escalate discrepancies to the ATO when needed.

The PayPP amount that pre-fills in a report is the difference between the previous YTD component amounts and the recent pay event. Pay components with a negative amount may pre-fill after the employer has made an adjustment to a previous YTD figure.

Customers must confirm if they have been paid an amount of the pre-filled pay component(s) in their current reporting period and if needed, the amount can be adjusted. If no updates are made to the negative component amount nothing is assessed and the negative amount will not reduce the Gross STP Income total after selecting Accept income. See Resources

In some cases an employee may have a purchased leave arrangement with their employer which may also display a negative amount. See Item 11.

Note: no changes are required to a salary sacrifice pay component with a negative adjustment. Salary Sacrifice components pre-fill for display purposes only and are not used in the PayPP calculation, as the amount is already included in the Gross Income. Service Officers and customers will see Salary Sacrifice components displayed as not assessable.

Some customers choose to use part of their employment income for a purchased leave arrangement. When a customer purchases leave, their gross wage minus the purchased leave amount is assessed as income. This is because the income is assessed when the leave is taken. See Purchased leave for more information.

Depending on how the employer has reported this, it will pre-fill through STP as either:

• a negative adjustment of the Salary and Wages paid leave component, that represents the amount that is purchased to accrue the additional leave
• a reduction of the Salary and Wages Income Gross Amount component, that represents the amount that is accrued as additional leave
• salary sacrifice deduction

A negative amount does not reduce the Gross STP Income total to be assessed. Where the employer has reported this as a negative adjustment to the paid leave or Salary Sacrifice component, customers and Service Officers will need to manually adjust the Salary and Wages Income Gross Amount to reflect the purchased leave amount. See Resources

When customers are reporting through self service channels, STP data will show for each employer one at a time. Customers are only able to report employment income in the STP confirmation service for the STP employer they are currently reviewing. Once all pay details are confirmed for one employer, the next STP employer’s details will pre-fill.

Service Officers using the Earnings and Reporting workflow will also see each employer appear one at a time. Selecting Next after Accept income for the first employer will go to EAPP before going back to the STP Employer Wage Items (EMGI) screen to view the next employer details.

After a customer confirms the STP data in the STP confirmation service, a message in the REI service tells the customer that pay details have been added to their record. The customer will see that only the assessable STP employment income components are populated under My pay.

If a customer contacts to query why amounts pre-filled through STP are different to what has pre-filled under My pay, Service Officers can explain how non-assessable components and an Income Assessment Period (IMP) are assessed.

STP service profiling triggers will place customers on 2 weekly reporting if they are not already when STP data is detected.

These triggers may also take customers off reporting 6 fortnights after confirming cessation details or if there has been no STP data reported for 6 fortnights. See Employment income options online. Note: if a customer states they are no longer working and request to be taken off reporting, Service Officers can update the reporting requirements, however any final pay details reported later through STP may place them back on reporting.

Note: where a customer advises they do not work or get paid by the STP employer and Service Officers have not followed the below actions, the mySupport request will be rejected.

Service Officers must:

• discuss with the customer their reporting requirements
• advise the customer of their self-service reporting options, and register them, if needed
• explain that employment details may pre-fill in their reporting statement via STP from payroll data reported by their employer
• run the STP employer update workflow, or the Earnings and reporting workflow (if the customer is due to report) in Process Direct, to confirm the STP employer

Customers can refer to the Services Australia online guides for myGov, online accounts and mobile apps for assistance with self service tools.

Service Officers can refer to Reporting employment income online or Reporting using phone self service for customer reporting information.

Service Officers can check if the change to reporting requirements is due to STP data:

• go to the Profile Summary (PQS) screen in Customer First
• place S in the checkbox next to the Profile Description of Reporting Profile –Income -2WE stim, then enter to go to Profile details (PQD). If the predictor code 1790 STP data suggests 2WE reporting is:
• not displayed - the update to the customer’s reporting requirements is not due to STP data. Service Officers must review the code description and any DOCs on the record to find the reason
• displayed - STP data has been reported for the customer. Service Officers must ask the customer if they are working and discuss all the details received through Single Touch Payroll

Where STP data pre-fills in a customer’s report, it is a result of an identity match and then multiple checks by the ATO and Services Australia to ensure data integrity. Where there is missing data or inconsistencies, the STP data does not pre-fill. This gives a high level of confidence that the pre-filled STP details are accurate and for the right person.

To check the STP employer details, Service Officers must:

• use one of the following in Process Direct;
• STP Employer Update workflow
• Earnings and Reporting workflow if the customer is due to report

If no STP data shows in the current entitlement period, select Yes at Update past periods in the Earnings and Reporting workflow. Select:

• a date range at least 4 weeks in the past prior to the current reporting period. This searches for any STP data reported in a previous entitlement period that has placed the customer on reporting
• the entitlement periods where STP data is available, and
• Next to progress to the STP Employer Update (EMCF) screen. If the workflow does not go to EMCF screen, the STP employer has been previously rejected, manually enter EMCF in the Superkey field
• Service Officers must discuss the STP employer’s details displayed on the EMCF screen with the customer. Ask the customer:
• have they ever worked for the employer or signed a Tax Declaration Form (TDF)?
• could it be their current employer, but not their trading name? (Check ABN lookup)
• did they have a job trial, one-off or short term work with the employer with no ongoing employment?
• do they get paid any payments from that employer, such as allowances, compensation, income protection or other benefit? This may be coded on the Other income (OINS) screen, Compensation Management Summary (CMS) screens or Trust and Company summary (TRCIAS) screen
• are they paid any other type of income from another source?

Service Officers must then view the income that has been reported by provisionally confirming the employer to get to the STP Employer Wage Items (EMGI) screen. Discuss the employment income with the customer. If the customer confirms they do work for the employer, adjust the STP data if required and confirm the STP details. Finalise the activity.

If the customer still states they do not work or get paid by that employer, Service Officers must navigate back to EMCF, reject the STP employer and finalise the activity.

After this discussion, Service Officers must DOC the record. The customer can be taken off reporting if the:

• customer advises they do not work or get paid by that employer, and
• STP employer details on the EMCF screen have been rejected, and
• customer (and partner) has no other employment income or mutual obligation requirements

Tell the customer that if any further STP data becomes available, the system will place them back onto 2WE reporting.

In some cases, STP employers incorrectly report payments paid to:

• former employees (e.g. retirement-type payments or workers compensation)
• volunteers, for reimbursement of volunteer expenses
• themselves, as sole trader
• beneficiaries of a trust/company that is not employment income earned as an employee

Before escalating the record, Service Officers must make any required updates, as advised in previous steps. This includes:

• updating the OINS screen
• updating the CMS screen
• creating a Complex Assessment Officer (CAO) referral
• rejecting the employer details on the EMCF screen

Service Officers can lodge a mySupport Single Touch Payroll (STP) pre-filled employment data web form to request coding of a reporting override where a customer:

• states they no longer work but get paid an amount from their previous employer, or
• is a volunteer who is paid a reimbursement of expenses, or
• has an active claim on the CMS screen and has identical worker’s compensation income reported through STP

Service Officers must include the following in the escalation notes:

• Name of the employer on the EMCF screen
• Details of the customer’s connection to the STP employer (current or former employee) and the income paid
• If the customer is paid something other than employment income. For example, a retirement type allowance or compensation payment
• If the income source is currently coded on the OINS or CMS screens
• Any income paid from another source
• Any income updated or a CAO referral made before escalation

The following circumstances are exempt from STP service profiling and will not place a customer on reporting:

• no STP component amounts greater than zero
• the customer or partner have MTE continuous income coded
• blind customers (AGB and DSB) who are not in receipt of Rent Assistance (RA) (income and asset test exemption is coded on Pensions Disability the Information (PDI) screen, see Income and assets tests for blind customers
• customers in environment I (International Operations)
• an active ADE employment type with:
• a continuous employment income frequency of 1WE or 2WE
• employment income reported by EER

When a customer is self-employed through a sole trader or partnership and has their business details coded on REBS, there may still be STP data reported. This is where the customer is deemed an employee of another business.

STP data may be reported where the customer is paid as an employee through the payroll of the other business. STP data is not reported if the customer works for the other business and provides an invoice.

If a customer claims they are not an employee and has included that income (with deductions) in their profit and loss statement, ask them if they get a payslip and payment summary from the STP employer or do they issue the business an invoice? See Resources

Referring to the customer’s individual tax return may help. Where income details are recorded from the STP employer at Item 1 of the tax return, they are regarded an employee of that business. See Self-employed or employee?

If a customer confirms the STP employer details is their own sole-trader business refer them to the ATO website for correct reporting of their sole trader business.

Note: Where a customer is self-employed and operating a business through a Private Trust or Private Company, they may also be paid a wage by the trust or company and this employment income may be reported through STP and recorded on EAPP.

When a student is paid a scholarship or stipend payment from their study provider, it is assessed as Other income and coded on the OINS screen. This allows the exempt portion to be excluded from assessment for Equity or Merit based Scholarships so only the excess is assessed as income. See Assessing scholarship income for more details.

The scholarship or stipend may be reported through STP as Salary and wages, Allowances or combined with their usual pay. At this stage, there is no separate process for this to be reported through STP. If Service Officers identify this situation, confirm that the scholarship or stipend is coded on OINS. Customers will need to adjust the pre-filled amount to exclude the scholarship or stipend amount.

Other paid leave can be reported when an employee has taken a period of leave or been paid for an absence. For example, a sick day, public holiday, annual leave, paid day off etc. Customers must advise the duration that the other paid leave was paid for.

When reported through STP, Service Officers may encounter SR353: Enter mandatory field Adjusted – Start Date & End Date for Other paid leave. The field that requires the duration of leave to be coded will be highlighted with a red outline. Service Officers must enter a start date and an end date to reflect the total duration the leave was paid for.

As an example, one day of leave could have a start date of 4 December 2023 and an end date of 4 December 2023. Where there have been non-consecutive days of paid leave in the pay period, the dates do not have to reflect the actual days that were taken off. A start date of 4 December 2023 and an end date of 6 December 2023 could be used to reflect a total of 3 paid leave days. If a customer has been paid 2 weeks of holiday pay, the start date and end date of the reporting period can be used.

Select the Earnings and Reporting workflow in Process Direct. When on the STP Employer Wage Items (EMGI) screen:

• select edit for the Other paid leave component
• enter the start date for the period in Adjusted Period Start Date field
• enter the end date for the period in Adjusted Period End Date field
• select Save

See Leave and termination payments paid by an employer to determine the correct dates to use where the customer has been paid payments on cessation of work.

Some allowances do not fall under their own category through STP, so the employer will report as Other allowances. Customers must advise if the allowance is a reimbursement for out of pocket work expenses they have had. See Allowances paid with employment income for more details.

If the additional information is not coded, SR353: Enter mandatory field Additional Information for Other allowances will show.

Select the Earnings and Reporting workflow in Process Direct. When on the STP Employer Wage Items (EMGI) screen:

• select edit for the Other allowances component
• select the twisty for Additional Information
• select the option the customer advises:
• Other Allowances - Not Reimbursement of employment related costs
• Other Allowances - Reimbursement of employment related costs
• Select Save

Customers must advise the duration that bonus or commission income was paid for. This may be the same duration of the employer pay period or a monthly or quarterly period etc. See Assessment of income for Centrelink payments for more details.

When reported through STP, Service Officers may encounter SR353: Enter mandatory field Adjusted – Start Date & End Date for Bonus or commission. The field that requires the duration of the payment to be coded will be highlighted with a red outline. Service Officers must enter the period that the bonus or commission was paid for.

Select the Earnings and Reporting workflow in Process Direct. When on the STP Employer Wage Items (EMGI) screen:

• select edit for the Bonus or commission component
• enter the start date for the period in Adjusted Period Start Date field
• enter the end date for the period in Adjusted Period End Date field
• select Save

Some customers may be provided a benefit from their employer in addition to their salary. For example, they may have a salary package worth $60,000 being a salary of $45,000 and $15,000 value of a company car, or they may get a $1,500 gym membership provided to them on top of their $50,000 salary. See Assessing fringe benefits for Social Security income test purposes for more information about fringe benefits.

STP employers can report the reportable fringe benefit component with each pay event or as a lump-sum at the end of the financial year. The amount that is reported through STP is the taxable value of the benefit and may appear higher than the benefit. This is known as the grossed up amount. However, the system will apply the non-grossed up amount for the income test assessment.

This arrangement will be reported through STP as Reportable Fringe Benefits. The customer will be asked if the arrangement includes free or discounted accommodation that is provided by the employer. If Yes, the customer can advise the amounts through self-service channels.

Where Service Officers are using the Earnings and Reporting workflow, and the additional information is not coded, SR353: Enter mandatory field Additional Information for Reportable Fringe Benefits will show.

Select the Earnings and Reporting workflow in Process Direct. When on the STP Employer Wage Items (EMGI) screen:

• select edit for the Reportable Fringe Benefits component
• select the twisty for Additional Information
• select the option the customer advises:
• Reportable Fringe Benefits- Include free or discounted accommodation
  Add the accommodation value in the RFB accommodation field
• Reportable Fringe Benefits- Do not include free or discounted accommodation
• select Save

A message shows in the workflow, that 53% of Reportable Fringe Benefits will be calculated and mapped. Reportable Fringe Benefits pre-fill as the grossed up amount, however the non-grossed-up amount (less free or discounted accommodation amounts) will map to EAPP without Service Officers needing to make any adjustments. See Resources.

Note: Some customers may choose to salary sacrifice their income for a benefit. For taxation purposes, the employer may report the Salary Sacrifice - Other component and also report the Reportable Fringe Benefit amount (RFBA) which is typically the value of the salary sacrifice amount multiplied by 1.8868. This may be reported with every pay event or as a lump-sum at the end of the financial year. Where the RFBA component and the Salary Sacrifice - Other component are for the same benefit, the RFBA amount will need to be adjusted to $0.00.

Some customers can choose to sacrifice part or all of their salary towards a benefit. This may be done as a pre-tax or post-tax deduction. See Assessing salary sacrificing/salary packaging arrangements for employment income for more information.

The Salary Sacrifice components pre-fill for display purposes only and reflect the amount that has been sacrificed towards the benefit. These amounts are not used in the PayPP calculation, as the amount is already part of the Gross Income. Any updates made to pre-filled salary sacrifice amounts will not change the total assessable income.

Salary Sacrifice can be reported under the following sub-components:

• Salary Sacrifice - Superannuation - voluntary arrangement of employee contributions into their superannuation fund
• Salary Sacrifice - Other - voluntary arrangement where an employee chooses to sacrifice part/all of their salary towards a fringe benefit. This can include, but is not limited to mortgage payments, car lease, health insurance, rent deductions, entertainment/meals card or childcare fees

Note: employers are required to report the grossed up taxable value of the Reportable Fringe Benefit (RFBA) amount for taxation purposes, which may also pre-fill. Where the RFBA component and the Salary Sacrifice - Other component are for the same benefit, the RFBA component will need to be adjusted to $0.00.

If a customer contacts to discuss the total pre-filled amount, advise how Salary Sacrifice arrangements do not reduce the total assessable income for Centrelink purposes. See Resources.

Unused leave and termination payments may pre-fill in a reporting task when a customer ceases work. The cessation date and reason may also pre-fill. The cessation reason cannot be changed. Customers subject to mutual obligation requirements will be required to give an explanation of why they ceased work, when the cessation reason is voluntary or dismissal. Service Officers must manually generate a UNPP, where required.

When customers are reporting through self service channels, they will be asked to give the number of days the unused leave or termination payments are paid for, or their average weekly wage. This will determine the duration of an Income Maintenance Period (IMP) for customers and/or partners on an IMP affected payment.

For Service Officers using the Earnings and Reporting workflow, enter the start and end dates for the duration of each of the cessation payments, as advised by the customer:

• select edit for the cessation payment/s component
• enter the start date for the period in Adjusted Period Start Date field
• enter the end date for the period in Adjusted Period End Date field
• select Save

Service Officers must make sure the duration provided is reasonable. For example, for an unused leave payment of $900 (annual leave), a 1 day duration would be considered unreasonable, but 5 days would be reasonable.

Verification, such as an SU1, payslip or letter from the employer is required where:

• the customer makes changes to the cessation payments
• there is doubt about the number of days/duration provided.

When unused leave or redundancy payments are pre-filled, the confirmed data will map to the IMPS screen when a cessation date and reason are also pre-filled. Customers or their partners who are not subject to an Income Maintenance Period assessment will not be affected by the coding on the IMPS screen.

Where unused leave and/or redundancy payments are pre-filled and there is no cessation reason and date reported, the amounts will map to EAPP. For customers reporting online, they will be asked if they are still working for the employer. If they answer No, an online task is created to provide an SU1. When the SU1 is returned, the employment cessation details can be updated, as needed. Customers who are not subject to an IMP will also be asked Do you need to advise of any change to your income and assets details? in the reporting workflow, to prompt them to update their circumstances. If they answer Yes, a new Update your income and assets task is added in self service.

When a customer has confirmed ceasing employment with the STP employer, the Employer verification field on EANS will update from STP to STC.

Not all employment cessation information is available via Single Touch Payroll (STP). This means an SU001 is still required in some circumstances.

Some former employers are telling customers they no longer need to complete an SU001 because the information has been sent via STP.

Service Officers must request an SU001 when it is required to accurately assess entitlement or rate of payment.

Customers must provide the number of days or average weekly wage for paid leave paid when completing their reporting statement. Customers can also adjust the amounts of STP income components.

An SU001 may be required even when STP data is available, where the:

• customer changed the amount(s) of any unused leave or termination payments
• duration of the days the leave/termination payments relates to is unreasonable
• customer advises their partner has stopped working

Service Officers may also request an SU001 to investigate whether an Unemployment Non-Payment Period (UNPP) needs to be applied.

STP data is not yet available for new claims. All customers advising in a claim that they or their partner have ceased work in the last 12 months must provide an SU001.