Single Touch Payroll (STP) - Issue management 277-24011649

The purpose of this DEP is to discard unnecessary STP data that is not required in the:

• STP Mismatch List window, and
• STP Mismatch Summary window

The Discard Zero DEPs will run daily from 7:00 am, and are redirected to Split Submission DEPs from 1:30 pm each day.

Before taking any manual action, Service Officers need to allow the DEP processes to complete. This will increase DEP processing outcomes.

The Discard Zero DEP, will review the:

• Pay Date Level Discard
• Customer Level Discards
• Single Touch Payroll Not reported employees (STPN) only Discards

The DEP will discard STP submissions that meet the following criteria:

• Total Submitted Amount = 0.00
• Total Expected Amount = 0.00
• Total Actual Amount = 0.00
• Submission Lodgement Status = EXCEPTION ERROR

When these conditions are met, the DEP will:

• discard the entire STP submission as it is not required
• add a notepad on all discarded submissions

The DEP will discard customers within a submission that meet the following criteria:

• Expected amount = 0.00
• Actual Amount = 0.00
• Reason = BLANK
• Customer is not expected on that pay date

Before the Discard Zero DEP discards any customer/s, it will go to the Pay Date List window and filter the search to 3 months earlier. This aligns with the 3 month display in the STP Mismatch List.

The DEP will:

• collect all customer lists per pay date and store the data in a table before going to the STP Mismatch List. This is to make sure the DEP does not discard a customer with an expected deduction for that pay date, even if the expected amount is zero
• discard the required customers and enter a notepad on relevant submissions. The notepads detail customer/s:
• that were discarded, and
• customer/s that had zero reported amounts but were unable to be discarded

After the DEP has checked the customer level discards, it will review the entire submission. If only STPN customers remain the entire submission is unnecessary and will be discarded.

The DEP will discard submissions that meet the following criteria:

• The submission displays as:
• Total Submitted Amount = 0.00
• Total Actual/Derived Amount = 0.00
• Customer/s meet the customer level discard rules. If the customer/s don’t meet the customer level discard rules, all remaining customers within the submission must display as:
• Expected Amount = >0.00
• Actual Amount = 0.00
• Reason = STPN

The DEP will enter a notepad on all discarded submissions.

A notepad automatically creates detailing the action taken when the DEP reviews the submission. The notepad is saved on the STP Mismatch List.

The notepads are as follows:

This notepad creates when the DEP successfully discards the submission.

Notepad text:

Digitally Enabled Processing has reviewed and identified that this submission is able to be discarded.

This is due to the Total Submitted Amount, Total Expected Amount and Total Actual Amount all displaying as $0.00.

Details of submission

Pay date: PD

Submission ID: SID

This notepad creates when the DEP successfully discards a customer/s within a submission.

Notepad text:

Digitally Enabled Processing has reviewed the submission to identify customer/s that are eligible to be discarded.

Customer/s that were unable to be discarded require Service Officer investigation. The customer/s are unable to be discarded due to displaying with an expected amount in the pay dates list.

Pay date: PD

Submission ID: SID

Customer/s Discarded

NAME, CSRN

Customers Unable to be Discarded

NAME, CSRN

This notepad creates when the DEP successfully discards the entire submission for STPN customers, once the DEP has checked customer level discards.

Notepad text:

Digitally Enabled Processing has reviewed and identified that this submission is able to be discarded.

This is due to all customers in the submission displaying with a Total Actual Amount displaying as $0.00 and a reason code of STPN.

Details of submission

Pay date: PD

Submission ID: SID

Total Submitted Amount: $0

Total Actual/Derived Amount: $0

This notepad creates when the DEP is unable to discard a customer due to displaying with an expected amount in the pay dates list.

Notepad text:

Digitally Enabled Processing has reviewed the submission to identify customer/s that are eligible to be discarded.

Customer/s that were unable to be discarded require Service Officer investigation. The customer/s are unable to be discarded due to displaying with an expected amount in the pay dates list.

Pay date: PD

Submission ID: SID

Customer/s Discarded

NONE

Customers Unable to be Discarded

NAME, CSRN

When the Discard Zero DEP has not been able to discard a customer with an expected amount in the pay dates list, check the case to see if the customer needs to be delinked.

Check if the:

• case has ended, and there is no debt
• case has changed to private collect, and there is no debt
• ongoing deduction is zero, and there is no debt

In the above circumstances, end employer withholding (EW) as soon as possible. See Table 6, Step 7 in Employer Service Officer (ESO) role in setting up employer withholding (EW) linking.

A split submission occurs when an employer reports multiple STP submissions for the one pay date.

This may occur when:

• an employer has staff on different pay cycles, however the pay date falls on the same day
• the employer is processing:
• pay runs for employees on different rates or conditions
• different pay runs for casual /part time/full time employees
• there is more than one payroll department for the same organisation processing the payroll

Cuba requires one report per pay date to move to the next stage of the reconciliation process.

Where possible, the DEP merge the multiple submissions into one submission.

If the merge is successful, the submission will either:

• remain as EXCEPTION ERROR if a Service Officer needs to take follow up action. E.g., there is a pay cycle mismatch, the customer is STPN - not reported, or
• update to READY FOR ERR. The remaining submissions for that pay date update to RECORD ONLY

When the submission lodgement status changes to FINALISED, an ERR creates in the Reconciliation Report List. The Service Officer can match the ERR to the payment or use top up which can be applied to ERRs from the second Wednesday of the month until the end of the month. See Table 7 in Employer withholding reconciliation and top up.

Note: the merge process does not include s72A deductions.

A notepad automatically creates detailing the action taken when the DEP reviews the submission. The notepad is saved on the STP Mismatch List.

The notepads are as follows:

This notepad creates when the DEP is unable to merge the submission due to:

• customers not matching across all submissions
• amounts not matching due to variations, or
• an amount is received, that is not expected

Notepad text

Digitally Enabled Processing has reviewed and identified that submissions are unable to be merged. Submission to be finalised manually by Service Officer.

Details of the submission

Pay Date: PD

Submission ID: SID

Total Submitted Amount: TSA

Total Expected Amount: TEA

Total Actual Amount: TAA

This notepad creates when the:

• DEP successfully merges the split submission, and
• submission lodgement status updates to ‘READY FOR ERR’ or ‘FINALISED’

Notepad text

Digitally Enabled Processing has successfully merged submissions.

Details of the submission

Pay Date: PD

Submission ID: SID

Total Submitted Amount: TSA

Total Expected Amount: TEA

Total Actual Amount: TAA

NAME, CSRN

Expected Amount: EA

Actual Amount: AA

Reported YTD: RYTD

Previous YTD: PYTD

Note: continue listing all customers

This notepad creates when:

• the DEP successfully merges the split submission, and
• there are actions needing Service Officer intervention

The submission lodgement status remains as ‘EXCEPTION ERROR’.

Notepad text

Digitally Enabled Processing has successfully merged submissions, existing mismatches require Service Officer investigation prior to finalising submission.

Details of the submission

Pay Date: PD

Submission ID: SID

Total Submitted Amount: TSA

Total Expected Amount: TEA

Total Actual Amount: TAA

NAME, CSRN

Expected Amount: EA

Actual Amount: AA

Reported YTD: RYTD

Previous YTD: PYTD

Note: continue listing all customers

This notepad creates when the DEP successfully merges the split submissions. This results in the remaining submission/s updating to ‘Record Only’ as the information is transferred to the merged submission.

Notepad text

Submission updated to Record Only as Digitally Enabled Processing has merged related submissions.

Details of the submission

Pay Date: PD

Submission ID: SID

Total Submitted Amount: TSA

Total Expected Amount: TEA

Total Actual Amount: TAA

NAME, CSRN

Expected Amount: EA

Actual Amount: AA

Reported YTD: RYTD

Previous YTD: PYTD

Note: continue listing all customers

The Split Submission DEPs start their daily run from 1:30 pm to try to merge submissions.

If the DEP has not actioned a split submission and there are no Single Touch Payroll Not reported employees (STPN), this may indicate:

• the pay date is incorrect and needs to be updated and/or assigned
• the removal of a hold auto reconciliation after the DEPs have already run that day

An employer is excluded if:

Avoid actioning split submissions early in the day. This allows the DEPs to action the record.

Check if the employer still needs the multi CSRN.

E.g., the employer has one ABN and multiple records in Cuba (multiple CSRNs) as they previously ran payroll out of multiple locations.

Contact the employer to find out if:

• they now run payroll out of a central location
• all customers need to be linked to the one CSRN
• they will make payments to the one CSRN
• split submissions are received when the employer reports via STP

If the employer confirms all the above are correct, refer the request to merge the multi CSRN to one CSRN to an SSO

The SSO will check:

• the associated records have no existing issues (top up, reassignments, excess cash etc.)
• all payers can be linked to the one employer

The SSO via the site PSM emails the request to National ICS.

National ICS will:

• check the organisation records and make a decision to update the associated records
• notify the SSO of the decision via email

If the decision is to merge the multi CSRN to one CSRN, to allow the employer to get allocated to a DEP for processing, the Service Officer must:

• change the associated record (no longer being used) to a ‘duplicate’ status
• delink the customers from the CSRN with the 'duplicate' status, and
• relink the customers to the correct CSRN
• update the ‘duplicate’ organisation status to DUPLICATE

Note: if the duplicated organisation status is updated to ‘CEASED’ instead of ‘DUPLICATE’ the organisation will still be a MULTICSRN record in Cuba. The DEP is unable to process a MULTICSRN.

Check if the hold auto reconciliation is still needed and if any outstanding issue/s can be actioned.

• The STP split submission payroll date must have all the payers with expected deductions for the pay date in Cuba or it will generate an STPN reason code. Contact the employer to follow up on employees with no deductions reported (e.g. due to NEM)
• If a pay date mismatch is causing the STPN, contact the employer to discuss the pay date. Determine if the
• pay date in Cuba needs updating
• the employer can correct the pay date in their STP reporting, or
• employee is no longer employed and need to be delinked

Once the DEP identifies an employer with split submissions, the submissions must meet the eligibility criteria. Multiple submissions with the same pay date must have all the following:

• Deduction type = EW
• Total Expected Amount not $0.00
• Total Submitted Amount = Total Actual Amount
• Submission Lodgement Status = EXCEPTION ERROR

To make sure the criteria is met:

• action:
• any customer mismatches and employer mismatches
• all deduction variations when first identified
• check:
• the pay cycles and pay date are correct
• customers are linked to the correct employer
• customers are delinked, if a link is not needed
• the linking window, for an election for EW not to apply. Remove the election for EW not to apply as this will report as zero
• the employer is reporting in the correct STP field
  Child Support Deductions (deduction type = D)
  Child Support Garnishee (deduction type = G)
• the employer has the most up to date version of their payroll software, see Table 10

The Australian Taxation Office (ATO) automatically send STP information to child support for the purposes of Employer Withholding for confirmed mutual customers. This is known as ‘ongoing’ pay event information.

Ongoing pay events for the customer will display 1000 of the most recent records. Historical pay event requests make it easier to find any date range requested and display the latest information from the ATO.

Use historical STP year to date information to:

• reconstruct an account, or
• confirm the actioned taken in an STP submission, particularly when the:
• EXCEPTION ERROR is set to FINALISED, and
• YTD can no longer be viewed

From the Cuba Main Menu select > Accounting > Employer Reconciliations > STP Historical Information. This will display the Find Customer window.

Key the customer details (CSRN) and select Find. This will display the STP Historical Information window.

The STP Historical Information window displays up to 1000 pay events.

The Pay Event Requests displays the:

• current request sent for the customer, and
• status of the request

The Pay Events displays the ongoing Pay Event information received for the customer.

Use the Pay Event Request function to display more pay events, go to Step 4.

To display a pay event that is not displayed in the 1000 pay events, use the Pay Event Request function. Use this to request a pay event for aged account discrepancies.

From the STP Historical window select > New. This will display the New Pay Event Request box.

• Key the Period From Date and Period to Date for the pay period needed
• Select Submit

The new request appears in the Pay Event Requests table with the status SENT. The status will change to PROG (In Progress), if the window is refreshed.

Note: if there is an uncompleted request with a status of PROG, a new request will not be made until the previous request is returned.

The response from the ATO can take up to 24 hours

When the request is complete, the request status will change to COMP.

To view the details of the pay event:

• select the required pay event in the Pay Event dialogue box
• select Details

To view the history of a request, from the STP Historical Information window, select History.

• Select Find. This will open the Filter Pay Events Request and Pay Events window
• To refine the search, key the From Date and To Date
• Sort the pay events by selecting:
• Type
• Pay Date
• Payment Period Start Date
• Payment Period End Date
• Employer ABN

If other responses are received, employer contact may be needed. Select from the responses below for more details.

This message indicates a partial response for the period requested has been received. This may mean one or more of the pay events in the requested period could not be retrieved.

This message indicates there are no pay events available for the pay period requested. This may mean the customer was not matched at the time of the requested period as a mutual client with the ATO and no data is available.

A pay event received more than 9 days before the pay date is placed at a submission status of PARKED.

When the pay date is less than 9 days in the future, the submission will be processed, and the status will be updated from PARKED to EXCEPTION ERROR.

There are several reasons to check a Future or Parked submission:

• One of the following intrays are allocated:
• STP RCVD NO EW LINK OR S72A ONE
• STP RCVD NO EW LINK OR S72A MULT
• go to Step 3
• An employer mismatch of 'pay date has been reported more than 9 days in advance' to indicate the submission reported has a pay date in the future, go to Step 4
• An employer calls to advise they have submitted a future pay date in error, go to Step 4

To view the notepad, select the STP Submission details from the Intray Details.

The future pay date is displayed in the notepad.

To action the intrays, see Resources page > Table 4 in Employer reconciliation Single Touch Payroll (STP).

If the date is in the future, it will not display on the STP Mismatch List window unless the date range is expanded.

To search for an STP submission for a future pay date:

• from the Organisation window, select Reconciliation > STP Mismatch Submission window
• select Find and the Mismatch List Find window will display.
• change the To date range to up to 12 months into the future, select Find

If the employer advises they lodged the submission in error:

• update the future pay date submission status to RECORD ONLY
• document the details in the STP Mismatch list notepad, using the STP Reconciliation template > record only

The ONE ABN – MULTIPLE CSRNS mismatch reason displays if an employer reports an STP submission and they have one ABN and multiple CSRNs. Service Officers need to decide if the submission needs to be assigned to an associated CSRN.

Escalate any issues relating to this process to a Service Support Officer (SSO).

Check who the customer is linked to for employer withholding (EW), or if there is a s72A garnishee notice. Compare the current EW or s72A details with the STP submission.

Has the STP submission been assigned to the correct CSRN?

• Yes, procedure ends here, see Single Touch Payroll (STP) - Employer reconciliation
• No, go to Step 3

To select the submission to be reassigned:

• from the STP Mismatch List window, highlight the STP pay date
• in the STP Submission Update box, select
• the Organisation Find window will open

Note: when the STP Mismatch List window opens, if there is an active hold auto reconciliation in place, a warning message displays to alert the Service Officer. The message will not display again until the Service Officer leaves the record, enters another record, or returns to the record.

To view all the associated organisations, key the employer’s ABN into the Australian Business Number field in the Organisation Find window.

• Select the correct CSRN from the Organisation Find list to assign the STP submission to the correct record in Cuba
• Select the select icon to go back to the STP Mismatch List
• Select Save
• Select OK in the pop-up message to confirm the update was successful and return to the Data Submission List

The ABN Mismatch Reason will display blank.

From the Organisation the STP Submission was assigned to:

• select Reconciliation > STP Mismatch Submissions
• highlight the record
• select Notepad
• add a document to explain the assign

Subject: MULTCSRN

Detail: STP Submission has been received for MULTCSRN. Submission has been manually assigned to CSRN xxxxxxxxxxxx. Customer CSRN xxxxxxxxxxxx has a current link/s72A notice for associated organisation.

Employers may report an employee twice in the one pay date for differing reasons. For example:

• They missed reporting for the previous pay date
• They are paying the employee under 2 different awards and their software reports them for each award
• The employee has worked in 2 sections of the business and their software reports them separately
• They have incorrectly reported the employee twice
• There is a system error that has resulted in the employee showing twice

While duplicate reporting creates a mismatch, this is allowed as part of STP, and the employer may be unable to change this.

When a duplicate submission is reported, the following intrays create:

• STP DUPLICATE REPORT
• STP DUPLICATE REPORT REC AMT DIF

For more information about the intrays, see Table 4 on the Resources page in Single Touch Payroll (STP) - Employer reconciliation.

Review past mismatch reconciliation documents to identify if the employer reports this way due to their software.

Is there a document to indicate this is how the employer’s software makes them report?

• Yes, go to Step 3
• No,
• Contact the employer to discuss the duplicate reporting. Check if the employer can update their reporting to prevent duplicate submissions
• If the employer is unable to change the way they are reporting, document the discussion with the employer in the Organisation window notepad and in the STP Mismatch List
  Subject: STP Mismatch – Duplicate reporting
  Detail: Employer has confirmed they are unable to change the way they are reporting STP for duplicate submissions

The STP submission shows as either:

• double the expected amount in the STP Mismatch List window, go to Step 4
• two submissions for the same paying parent with the same pay date, go to Step 5

In the STP Mismatch List, the total actual amount shows as double the expected deduction amount, however the employer total submitted amount matches an expected deduction amount.

For example:

Employer Total Submitted Amount = $100.00

Total Expected Amount = $100.00

Total Actual/Derived Amount = $200.00

To check:

• Highlight the pay date of the EXCEPTION ERROR
• Double click or select Go > Mismatch STP Mismatch Summary

The STP Mismatch Summary window will show the customer listed twice.

Check:

• the difference between the Reported YTD and Previous YTD equals the employer total submitted amount, and
• if the same customer name appears twice for the same reported YTD, previous YTD and payroll date

This indicates the double reporting of the customer in the submission is a Services Australia system error. This duplication can occur when the data does not come through to Cuba and the STP data team has to ‘replay’ the event.

If the difference between the reported YTD and previous YTD has changed by more than what the employer total submitted is, contact the employer to confirm what they deducted for each customer in the submission.

Proceed to action the mismatch, in the STP mismatch Summary window.

Discard the duplicate report for the customer, Cuba will not allow 2 entries for the same customer on the same pay date.

To discard a customer from the submission, from the STP Mismatch summary window:

• Highlight the duplicate customer record
• Select DISCARD from the Pay event Deduction Status
• Select save

Escalate any issues to a SSO who can escalate to National ICS, via the site PSM if needed.

Action the duplicate submission in the STP Mismatch List window. Cuba will not allow 2 submissions for the same customer and the same pay date to be finalised to the reconciliation report list:

• Update the duplicate submission to RECORD ONLY
• Document in the STP Mismatch List notepad for the duplicate pay date using the STP Reconciliation template > Record only

The ADV reason code is for manual reconciliation only. If ADV is used for an STP reporter, Cuba cannot calculate a previously deducted payment in the next expected pay date. Cuba will only show the expected amount.

Using ADV in STP can cause an out of sync account.

Reason for an ADV variance in the deduction amounts may include:

• the customer is taking holidays and making advance deductions
• the customer may have requested their employer to deduct extra money, e.g. to address debt
• the employer may include deductions for future pay periods during holiday periods such as Easter and Christmas

If the amount reported for the customer is more than the expected amount, contact the employer to confirm the reason for the extra deduction.

If the employer advised the:

• extra deducted amount is not an advance deduction:
• select the appropriate reason code for the variation
• procedure ends here
• reported deduction is for a future pay date, go to Step 2

Has the employer submitted deductions for more than one customer?

• Yes, go to Step 3
• No:
• update the actual deduction amount in the STP submission to the actual deduction for that pay date
• manually create the next pay date ERR
• document the deduction reported was reported with the previous submission as XX number of deductions and the ADV reason code cannot be selected. Note: if the extra deductions submitted is more or less than expected confirm reason and use the appropriate reason code

If the employer has deducted an advance deduction for one customer and all other customers have not been reported for the future pay date:

• create an ES RECONCILIATION FUTURE RCVD intray
• document the details of the advance deduction i.e., customer name, CSRN and actual amount, to support correct reconciliation of the deduction in the next pay date

Do not manually create an ERR for one customer if there is more than one customer linked to the employer. Creating an ERR will mean the STP report for the future pay date cannot be created for reconciliation.

Occurs overnight when:

• a payment is received on the employer account that matches the expected amount and expected pay date, and
• the STP submission has not been reported

Cuba creates the ERR and auto reconciles to the payment. The not reported STP auto-reconciliation ERR has a create ID of NRSTP. See Hold auto reconciliation and Single Touch Payroll (STP) auto reconciliation.

Note: STP Employer records will not auto-reconcile when there is more than one pay date created in a month. STP employers who report weekly or fortnightly need manual matching to the payment/s.

Contact the employer if deductions have not been reported through STP and Cuba is auto reconciling the pay date to the payment received (NRSTP).

Ask the employer if they have stopped reporting deductions via STP. If they have, end the STP Reporter Indicator, see Table 6, Step 5 in Single Touch Payroll (STP) – Employer reconciliation.

If the employer advises they have changed payroll software. Does the new software support the STP reporting of deductions and garnishees?

• Yes, go to Table 9
• No, end the STP indicator, see Table 6, Step 5 in Single Touch Payroll (STP) – Employer reconciliation

When escalating a STP issue to an SSO, provide the following information via email.

• Organisation name, CSRN and organisation contact name
• Digital Software Provider (DSP), e.g. MYOB, Quickbooks, Employment Hero
• The version of the software the employer is using. Are they using the latest version of their payroll software? See Table 10 for the different software options
• Description of the issue?
• E.g., the Total Submitted amount is reporting as $0.00 for the period reported, the Total submitted amount is reporting as the YTD amount, the pay period is reporting as the same start and end date
• If the employer has attempted to resolve the issue with their software provider? If so, what was the outcome/response?
• Screenshots from the employer of the pay event report/s they are submitting to the ATO
• Any extra information from the employer and any work around to correct the problem

The Service Officer must:

• document the STP issue/s in the Organisation Details window notepad
• create an EW Account Cleansing intray (copy and paste the notepad from the Organisation Details window into the intray notepad)
• contact the employer, where further information is required, and refer back to the SSO,
• keep the employer locked until the STP issue is resolved

Check the:

• Digital Software Provider (DSP) details are documented
• employer has:
• confirmed they are using the latest version of their payroll software
• contacted their software provider to attempt to resolve the issue and details of the outcome
• Service Officer has:
• locked the employer
• created an EW Account Cleansing intray, and
• documented the details of the STP issue in the Organisation Details window notepad and copied the notepad to the intray

If further action is required, refer to the Service Officer.

If the Service Officer has provided all the required information, escalate the STP issue via email to the site PSM.

• Review the STP issue referral
• Liaise with the SSO if further information is needed
• Liaise with the SSO if a mySupport form for Cuba issue is needed and get SD number from SSO before referring the STP issue to National ICS

If the SSO has provided all the required information, escalate the STP issue via email to National Intensive Collection Services (ICS).

• Review the STP issue
• Liaise with PSM if further information is needed
• monitor the STP reporting for resolution

Where the issue cannot be resolved with the employer and their software provider, National ICS will refer the issue to Child Support Program.

The software used by an employer can affect the STP reporting. Payroll software can be classified in 2 ways:

• Cloud based software
• Desktop based software

Cloud based software is one central software application for the employer. Each employee/payroll officer accesses the same version. If one employee/payroll officer downloads the latest update, all staff processing payroll will be using the latest version of the software.

Features of Cloud based payroll software:

• One central location for software
• Each staff member logs into the same version
• After applying the update, all staff will be accessing the most recent version

Desktop based software is downloaded and stored on each person’s individual computer. This means that if one employee/payroll officer updates their software, but another employee/payroll officer does not, Services Australia may receive several types of reporting.

If an employer had a software issue that has been fixed, a mixture of reporting may be received.

Features of desktop based software:

• Software is stored on each individual desktop computer
• Staff can all be using different versions of the software
• Staff need to individually download the software to their computer

Service Officers must investigate if an employer confirms STP data has been reported and not received (STPN).

This may indicate that there are STP pay events where the deduction data has not flowed through to Cuba.

This is a known data migration issue and is not a software issue, therefore do not ask the employer to follow up with their software provider.

Check:

• if the employer has one or more linked paying parent/s, and
• the STP submission has one or more paying parent/s with the STPN reason variation code, and
• the difference between the Total Submitted Amount and the Total Actual/Derived Amount is the expected amount for the Paying Parent/s with the STPN reason variation code, and
• the payment received matches the Total Submitted Amount in the STP submission (if remitted), and
• the next pay date reported reflects the full YTD amount in the Total Actual/Derived Amount for the paying parent that was STPN in the previous pay date due to the pay date reporting gap. (Cuba is unable to derive the actual deduction if there is a pay date reporting gap)
  Note: STP Historical Information will also show pay day reporting gaps.

Services Officer who are unsure if the deduction was reported and not received, can seek support from an SSO.

Were all of the above criteria met?

• Yes, go to Step 3
• No, contact the employer to confirm the reason why no deduction was reported for the STPN customer/s

• Update the actual deduction amount for the STPN customer/s in the STP Mismatch Summary window.
• Once the actual deduction amount is updated the Total Actual/Derived Amount must equal the Total Submitted Amount reported by the employer.
• Document the STP Data reported and not received details in the STP reconciliation template
• Escalate the data migration issue to National ICS. See Table 9

STP matching batch runs daily, including public holidays. The batch completes employer matching first. If errors and/or warnings are identified in the STP matching batch the submission will go the mismatch list window.

Any non-matched employer submissions will appear in the STP Data Submission List with ABN mismatch reason NOABN and will have a submission lodgement status of EXCEPTION ERROR.

National ICS run a weekly NOABN report to:

• identify STP submissions that have not been attached to an organisation CSRN, and
• determine if the submission should be manually assigned

National ICS will check if the new ABN has created, since running the weekly NOABN report.

Has the new ABN been created?

• Yes, National ICS will:
• manually assign the submission to the new ABN
• create an Organisation Follow up intray
• add documentation, go to Step 3 to review action/s required

• No, National ICS will:
• manually assign the submission to the associated ABN in Cuba
• create an Organisation Follow up intray
• add documentation, go to Step 3 to review action/s required

National ICS will add one of the below documentation templates to the Organisation Follow up intray.

STP submissions have been received by a New Organisation ABN xxxxxxxxxxx Name xxxxxxxxxxx which appears to be an associated employer. (Optional text – The new org has been created CSRN xxxxxxxxxxxx and marked as associated.)

The PP in the STP submission has a notice or was linked to Associated ABN xxxxxxxxxxx Name xxxxxxxxxxx which is a different ABN, and this requires urgent review for a delink\relink and new org creation so that the notice is legally valid.

An STP submission has been received by a New Organisation ABN xxxxxxxxxxx Name xxxxxxxxxxx which appears to be an associated employer.

PP in STP submission has a current notice with an Associated ABN xxxxxxxxxxx Name xxxxxxxxxxx which is a different ABN.

Please review for a New Org creation and create a Collection Activity Required intray on the PP for the withdrawal and re-issue of a new s72A notice.

An STP submission has been received by a New Organisation ABN xxxxxxxxxxx Name xxxxxxxxxxx. This org has since been created and assigning the STP submission to the new org CSRN xxxxxxxxxxxx.

STP submission received xx/xx/xx for ABN xxxxxxxxxxx

This ABN has Multi CSRNs.

STP submission has been manually assigned to MULT CSRN xxxxxxxxxxxx.

An STP submission has been received by an ABN xxxxxxxxxxx Name xxxxxxxxxxx which has an incorrect status of duplicate and appears to be an associated employer.

This requires a review for:

delink\relink

organisation status to be updated from duplicate to active and

employer to be updated as associated and reported as associated.

A s72A STP submission has been received by a New Organisation ABN xxxxxxxxxxx Name xxxxxxxxxxx which is associated, however the PP reported is not a child support customer.

Employer contact is required to request cease reporting via STP for the non-child support customers.

STP reporting manually assigned from the NOABN report will auto finalise to the reconciliation report list with status of INIT where:

• the new ABN (new organisation) has been created in Cuba
• the payer has been delinked and relinked to the new organisation
• the total submitted amount matches the expected amount and the total actual (derived) amount
• there are no employer exception mismatches at the warning or error level, and
• there are no employee exception mismatches at the warning or error level