Raising Assurance of Support (AoS) debts 005-03060000
This document outlines the process of raising AoS debts. This includes the role of the AoS processing team and service centres in this process and who is responsible for repaying the AoS debt.
On this page:
Review, write off or waive AoS debts
Finalising activities and quality checking
Raising AoS debts
Table 1: For Assurance of Support (AoS) Processing Team only.
Step |
Action |
1 |
Recoverable payment assessment + Read more ... When an assurer cannot provide adequate support, the assuree may be eligible to receive a payment. Before receiving payments, the assurer is contacted to confirm and complete the Assurance of Support Check List (AOCL) screen. For more information on investigating AOS debts, see Assessing and coding the Assurance of Support (AoS) Mod AR. Service Officers may need to request the following resource in the ICT Security Portal (ISP):
See Using the Archive and Culling Engine (ACE) to access archived Assurance of Support (AoS) data. Assurance of Support period There are some instances where the start and end date are blank on the AoS Bond Details (AOBD) screen, for example:
|
2 |
Calculate AoS manual debt + Read more ...
|
3 |
Assurer or assuree has died + Read more ... When a notification is provided that an assuree or assurer has died, Services Officers must:
See Death of income support customer or their partner. Do not contact the executor or third party (verbal or written) until 4 weeks have passed since the customer's death. Exercise sensitivity always when discussing a debt with an executor or third party. See Recovering debts from a deceased customer's estate. For help assessing a customer’s individual circumstances, refer to Local Peer Support (LPS). See Tier 1 technical support - Local Peer Support (LPS). Has the Service Officer identified that an assuree or assurer has died in the past 4 weeks?
|
4 |
Checks before raising a debt + Read more ... Before raising an AoS debt, check if letters to the assurer are inhibited due to family and domestic violence:
Conduct a file review if DOM - Domestic Violence is coded on the AOIL screen. Check if further contact has been made from the assuree for family and domestic violence since the initial social worker contact. Has further contact been made by the assuree?
|
5 |
Check if there is an 'undetermined' debt on the assuree's record + Read more ... Where the assuree (the recipient of the payment) is incorrectly paid, such as due to administrative error or misrepresentation, a debt may be raised against the assuree. This is:
For more information, see the Resources page > Distinction between an AoS debt and a debt arising from a contravention of the Act. If the assuree has a liable debt that is within the AoS period, this debt would not be included in any debts that the assurer would be liable for:
Does the assuree have any debts that fall within their AoS period?
|
6 |
Check for multiple or intertwined records + Read more ... Check if there are any existing or potential multiple or intertwined records (this applies to both the assurer and assuree). See Centrelink Multiple Match List (MML) screen. Does the assuree have a multiple or intertwined record?
|
7 |
Action multiple/intertwined record + Read more ... Check if Data Quality Unit (DQU) has assessed the multiple/intertwined record. Check the Document List (DL) screen for a Display on Access (DOA) DOC by NA8 (DQU region code). Has the multiple/intertwined record been determined by DQU?
|
8 |
DQU determined a multiple/intertwined record + Read more ... Has there been any recoverable social security payments granted on either the primary or multiple record? Yes. Check which CRN has the AoS case coded and check the following:
No. Continue to assess debt. For: |
Manual AoS debts
Table 2: For Assurance of Support (AoS) Processing team only.
Step |
Action |
1 |
Reasons for manual AoS debts + Read more ... Manual AoS debts are raised in the following circumstances:
Note: for help assessing a customer's individual circumstances, refer to Local Peer Support (LPS). See Tier 1 technical support - Local Peer Support (LPS). LPS will determine if contact with the Data Quality Unit (DQU) is needed. See Resources for DQU contact information. |
2 |
Recoverable payment granted on a multiple record + Read more ... When an assuree is granted an AoS recoverable payment on a multiple record, the standard auto review or debt processes are not generated. The reviews only generate when the recoverable payment is on the AoS record, with a Benefit Status of AOE/CUR or AOE/ACC. Give feedback to the Service Officer who incorrectly granted payment on the multiple record if it is clear the error might have been avoided. Use the Staff Feedback Tool. It will be clear in some cases that the Service Officer could not locate the multiple record either due to the:
The Service Officer should contact the assuree and their assurer/s to:
An AoS Service Officer needs to manually raise a determined debt on the assurer's AoS record for all the recoverable payment/s made on the assurer's multiple record. |
3 |
AoS Expiry or Yearly Review with incorrect review start/end dates + Read more ... For an Expiry or Yearly Review:
There are some instances where the start and end date are blank on the AoS Bond Details (AOBD) screen, for example:
For a commencement review, see Assurance of Support (AoS) reviews. If the Process Direct review has a gap in a payment period:
Note: for help assessing a customer's individual circumstances, refer to Local Peer Support (LPS). See Tier 1 technical support - Local Peer Support (LPS). |
4 |
AoS manual debt + Read more ... Manual debts are raised on the assurer record in Customer First or Customer Record via the Add Debt (OPAD) screen. In joint AoS cases, raise a multiple liability debt with the same debt ID by coding the Multiple Liability (OPML) screen. Do not raise separate debts on each assurer's record. If the assurer was not contacted when the assuree claimed the recoverable payment. AoS Service Officer must make 2 genuine attempts to contact the assurer/s to advise of the debt raised. |
5 |
Raise a manual AoS debt + Read more ... On the primary assurer record in Customer First or Customer Record, go to the Add Debt (OPAD) screen, code the fields:
Note: if a customer has a debt that covers multiple social security payments:
Press [Enter] to go to the Component Amount (OPCA) screen. |
6 |
Code OPCA screen + Read more ... Code the fields:
If an error 'E171DB - Component period cannot span two financial years' presents, change the dates to match the Entitlement Period End (EPED) dates. Note: some components of payments received may be on the second page of the Component Amount (OPCA) screen. |
7 |
Finalise manual AoS debt activity + Read more ... Press [Enter] to go to the Assessment Finalisation screen. Enter Y in the Finished? field. Add any notes in Activity Comments field. Is this a multiple liability debt?
|
8 |
Code OPML screen + Read more ... Do not raise separate debts for each assurer. If there are joint assurers, raise a multiple liability debt with the same debt ID:
|
9 |
Adjust existing manual AoS debt amount + Read more ... To adjust a manually raised AoS debt as the 'Determined' debt calculation is incorrect, or needs to be adjusted to comply with a review of a decision, or ARO determination:
See Changing account details on debts raised in the Debt Management and Information System (DMIS). |
10 |
Issue manual letters to the assurer/s and the CBA + Read more ... Create manual letters using:
Staff must:
Note: if the debt is a multiple liability debt, send a Q084 to each assurer. Where a manual letter is required, staff must not finalise the letter until a suitably skilled officer has checked it. The AoS - Yearly and AoS - Expiry Reviews will automatically create the appropriate debt letter. See Creating an Online Advice (OLA), including within an existing activity. Letter to assurer/s:
Letter to CBA:
|
11 |
Adjust bond on the assurer/s records + Read more ... In Process Direct update the bond balance for the AoS case via the AoS Bond Details (AOBD) screen, for future debt recovery or release. AoS period has not expired
AoS period expired
Create a manual Bond Review to follow up return of bond to Services Australia In Customer First, create a manual review on the Review Registration (RVR) screen and complete the fields as follows:
The review will mature on the Due Date coded in the RVR activity. Workload Management will allocate the review for manual action. |
12 |
Document the records + Read more ... Open the AoS Debt Proforma on the Resources page. Complete the Fast Note section of the pro forma. Use Fast Note - select Auto Text > Assurance of Support > AoS Debt > AoS Debt Action. Paste the completed proforma section into the Fast Note text. If there are multiple assurers, document each assurer record for cross referencing. Upload the completed AoS Debt Proforma to all relevant records using Form Type as DBTCAL. See Attaching electronic documents to a Centrelink customer's record using Document Tools in Customer First. |
Review, write off or waive AoS debts
Table 3: For Assurance of Support (AoS) Processing team only.
Step |
Action |
1 |
Required action + Read more ... Is the customer asking for an:
|
2 |
Request for an explanation or application for a formal review of an AoS debt decision + Read more ... If the customer disagrees with the debt decision, see Request for an explanation or application for a formal review. Procedure ends here. |
3 |
Writing off an AoS debt + Read more ... For the Assurance of Support (AoS) Processing team and Debt Recovery team only. Standard write off considerations apply for AoS debts, see Writing off Centrelink debts. Procedure ends here. |
4 |
Waiving an AoS debt + Read more ... For the Assurance of Support (AoS) Processing team and Debt Recovery team only. AoS debts cannot be waived. See Waiving Centrelink debts for details on the process of waiving a debt, but continue below for more process and policy information for waiving an AoS debt. An AoS debt cannot be waived due to administrative error as s1237A of the Social Security Act 1991 only applies where the payment is received by the debtor (assurer). An assurer does not receive the payment so s1237A does not apply. For instance, where an assuree had received an incorrect rate of recoverable payment, due to an administrative error. Although the error was administrative, the payment was made to the assuree rather than the debtor. As such, the debt cannot be waived due to administrative error as the assuree is not the debtor in the AoS case. See the Resources page, Reasons an AoS debt cannot be waived. |
Yearly Review
Table 4: For Assurance of Support (AoS) Processing team only.
Step |
Action |
|
1 |
Open the Yearly Review + Read more ... Note: currently, AoS debts for joint assurance cases must be raised manually The Yearly Review work item will open on the assuree's record, with the:
Select The Process icon is not used for Yearly Reviews. |
|
2 |
Action the Yearly Review + Read more ... Open the AoS Debt Proforma on the Resources page. Complete the AoS Debt Proforma as the review is undertaken. On the Yearly Review screen, is the indicator No data in the Recoverable Payments field?
After completing the Yearly Review with No data, investigate if any recoverable income support payments were paid and have not been raised during the AoS period. To investigate if a recoverable income support payment is paid, check:
Raise the manual debt as needed. See Table 2.
Note: if the Yearly Review is finalised without saving each Payment Component, an AoS debt will not raise in Debt Management Information System (DMIS). A manual debt will need to be raised. See Table 2. |
|
3 |
Finalise the Yearly Review + Read more ... After finalising the Yearly review in Process Direct. Check the:
DOC each assurer's record, use Fast Note - select Auto Text > Assurance of Support > AoS Debt > AoS Debt Action. Upload the completed AoS Debt Proforma to all relevant records using Form Type as DBTCAL. See Attaching electronic documents to a Centrelink customer's record using Document Tools in Customer First. Procedure ends here. |
Expiry Review
Table 5: For Assurance of Support (AoS) Processing team only.
Step |
Action |
1 |
Open the Expiry Review + Read more ... The Expiry Review work item will open on the assurer's record, with the:
Select Note: the Process icon is not used for Expiry Reviews. |
2 |
Action the Expiry Review + Read more ... Open the AoS Debt Proforma on the Resources page:
On the Expiry Review screen, is the indicator No data in the Recoverable Payments field?
|
3 |
No data in the 'Recoverable Payments' field + Read more ... If there are no recoverable amounts, complete the Expiry Review, no user interaction is needed:
After completing the Expiry Review with no data, investigate for any recoverable social security payments paid but not been raised while under the AoS period. Raise the manual debt as needed. To investigate if a recoverable social security payment is paid, check:
If debt has been identified, see Table 2. |
4 |
Data in the 'Recoverable Payments' field + Read more ... Check:
Select each listed Payment Type in the Recoverable Payments field if there are multiple benefit types paid the assuree/s:
|
5 |
Finalise the Expiry review + Read more ...
DOC each assurer's record, use Fast Note - select Auto Text > Assurance of Support > AoS Debt > AoS Debt Action. Upload the completed AoS Debt Proforma and calculations to all relevant records using Form Type as DBTCAL. See Attaching electronic documents to a Centrelink customer's record using Document Tools in Customer First. |
Escalations
Table 6
Step |
Action |
1 |
Escalate ICT issues + Read more ... Where a system issue is encountered, staff must escalate the issue to ICT via Roxy or mySupport. For system issues in: Process Direct, see Using Digital Assistant Roxy in Process Direct Customer First or Customer Record, staff must lodge a mySupport, see Resources for a link Staff must record details on a DOC and await ICT response with instructions. |
2 |
For Commonwealth Bank of Australia + Read more ... Where the system has incorrectly issued a Bank Guarantee Release letter to the Commonwealth Bank of Australia (CBA) before the expiry review has been finalised, with Local Peer Support. See Tier 1 technical support - Local Peer Support (LPS). LPS will escalate to a Service Support Officer (SSO) to seek confirmation from CBA on the bond release status by emailing Business Process Migrants. Staff must not finalise the activity until confirmation has been received. Staff are to:
|
Finalising activities and quality checking
Table 7
Step |
Action |
1 |
Quality checking + Read more ... Yearly and Expiry Reviews have no Quality Management Application (QMA) in Process Direct. Staff not proficient in AoS debts must:
Manual debts raised in Customer First or Customer Record will be automatically selected for Quality On Line (QOL) checking based on proficiency levels of staff. Staff may receive feedback via the Staff Feedback Tool:
The AoS Yearly and Expiry Reviews will automatically create the appropriate debt letter. Where a manual letter is required, staff must not finalise the letter until a suitably skilled officer has checked it. For example, by a:
See Quality On Line (QOL) and Creating an Online Advice (OLA), including within an existing activity. When investigating potential AoS debts, QOL checkers may need to request the following resource in the ICT Security Portal (ISP):
|