Correcting a duplicate Child Support customer record 277-09030030
This document explains the process for correcting a duplicate Child Support customer record.
On this page:
Review and decide how to correct
Disable a duplicate child record
Disable duplicate adult record
Process immobilisation of duplicate adult record
Review and decide how to correct
Table 1: this table describes the steps involved in identifying, investigate and determining corrective action on a duplicate customer record. For Service Officers, Service Support Officers (SSO) and Solutions Gateway Team (SGT) Service Officers.
Step |
Action |
1 |
Check for international involvement + Read more ... Check if the record is related to an international case:
If the customer is:
For:
|
2 |
Investigate duplicate record (Service Officer) + Read more ... To confirm if a record is a duplicate record, check:
If uncertain whether 2 records are actually the same person, contact the customer. For help, see Correcting a complex Child Support error.
Where a duplicate customer record:
|
3 |
Review the case (Service Support Officer (SSO) and Solutions Gateway Team (SGT) Service Officer) + Read more ... There are 2 options to manage duplicate records:
|
4 |
Merge the record - which record to keep + Read more ... If one record is a child record linked to an ended case and the other record is an adult record (payee/payer), the adult record must be maintained. This makes sure there are no Centrelink FTB implications for the payee. If the adult record is linked to a payer role, and the case is in progress:
If the adult record is linked to a payee role, and the case is in progress:
If one of the above scenarios do not apply, check how hard it will be to merge the records:
Check which record matches between Cuba and the Centrelink system with the same Child Support Customer Identification Number (CIN):
|
5 |
Determine corrective action (SSO and SGT Service Officer) + Read more ... Decide whether to:
After the CIN is reassigned, select Centrelink Refresh in the External Information window so Centrelink applies the correct CIN:
It is not possible to reconstruct payment histories the same as the original case. The reconstructed case will show:
Reassign any payments attached to the record being disabled. In some circumstances the best option may be to disable the customer record and reassign the payments. |
Disable a duplicate child record
Table 2: this table describes the process for disabling a duplicate child record and is for Service Support Officers (SSO) and Solutions Gateway Team (SGT) Service Officers only.
Step |
Action |
1 |
Check for outstanding processing + Read more ... Do not deviate from the process as it may result in corrupt data that cannot be fixed. Run eligibility before correcting the child record. Fix any eligibility errors and confirm the existing changes as suitable. See Eligibility Cuba Process Help. Wait until the following day. Do not proceed with the correction until the following day so that the customer continues to receive correct assessment notices for case events. |
2 |
Capture details to reconstruct case + Read more ... Copy relevant details from the customer record. Screen shots may help. This includes:
|
3 |
Change name of duplicate customer + Read more ... Change the name of the duplicate customer record:
For example change John Edward Smith to:
|
4 |
Check case status + Read more ... Do not check the case status if the only role for the duplicate child is relevant dependant. Remove the relevant dependant and add to the case, irrelevant of the case status. If the only role for the duplicate child is relevant dependant, go to Step 5. If the duplicate child record has a role in a case with:
Then:
Note: if the duplicate child is a claimed for child in a COA registration period, this does not need to be set back to recorded. Leave this COA registration period. Once the duplicate child is immobilised a CUB Officer must remove the duplicate child from the COA registration period. Use the case fix function as the final step in immobilising the duplicate child record. |
5 |
Set case back to recorded (CUB Officer) + Read more ... Duplicate record linked to more than one case where the duplicate is a child only:
The more changes and registration periods on a case, the more complex the case is. There may be multiple:
A CUB Officer needs to understand, review and copy each screen before setting the case to recorded. Old ended cases Manually add or update the below after the case is set to recorded:
|
6 |
Update Customer Reference Number (CRN) + Read more ... Delete the CRN from the duplicate record. Record the correct CRN on the retained customer record. |
7 |
Delete care and update relationship + Read more ... Delete care records Delete all care records (past and current) for the duplicate child record(s) including relevant dependants. See Care Cuba Process Help. If Centrelink care records exist, CUB SSOs and CUB SGT Service Officers can delete these records. If the only role for the duplicate child is relevant dependant, go to Step 7. Update relationship record Update the relationship details. Disconnect the duplicate child from both parents and/or carers by selecting 'none' for each parent/carer. See Relationship Cuba Process Help. Do not run eligibility. |
8 |
Remove duplicate child record + Read more ... Remove the duplicate child from each registration record attached to the case. Do not run eligibility. |
9 |
Add the correct child + Read more ... Add the correct child to each appropriate registration record, including the Child Details section. Record the care arrangements and relationship details for the child. For a duplicate child involved in more than one case, check all related cases. Make similar adjustments as required. Update any other cases where the child is a relevant dependant. See the: |
10 |
Run eligibility + Read more ... Confirm all care and relationship information has:
Run eligibility. Make sure care details are correct. If not, re-key care by referring to copied care details of the duplicate child record. Make sure the Service Options window is reflecting the original collection status. If there are any unexpected results, correct the discrepancy before saving. Once satisfied with the results in the Pre-confirmation window, save eligibility. |
11 |
Update collection details + Read more ... The collection status should revert to the original collection status. This will be from the start of the registration period, overriding any Opt In/Opt Out decisions. To update collection details:
Note: there may be a slight difference between the amount posted from Opt In/Opt Out adjustments and liability recalculation. This may be due to differences calculating the monthly rate. For example original calculation based on 30.4375 days and new calculation on days in that particular month. The account should return to the original balance. |
12 |
Finalise + Read more ... SGT Service Officer:
SSOs:
Procedure ends here for SSO. The referring Service Officer is to undertake any post action tasks. See: |
Disable duplicate adult record
Table 3: this table describes the process for disabling a duplicate adult record and is for Service Support Officers (SSO) and Solutions Gateway Team (SGT) Service Officers only.
Step |
Action |
1 |
Information for case reconstruction + Read more ... Do not deviate from the process as this may result in irreparable data corruption. Copy relevant details from the customer record. Screen shots may help. This includes:
|
2 |
Change name of duplicate customer + Read more ... Change the name of the duplicate customer record as follows:
Example: Change John Edward Smith to:
|
3 |
Disable Child Support online account + Read more ... Review Child Support online account status. Consider disabling the account if there will be an impact to the assessment (for example, multi case allowance). Disabling the Child Support online account stops wrong details showing to the customer. See Access and troubleshooting Child Support self service and Using Child Support self service. |
4 |
Update CRN and TFN + Read more ... Delete the CRN and TFN from the duplicate record. Make sure the correct CRN and TFN are on the retained customer record. |
5 |
Move funds and clear overpayments + Read more ... Check the case for any:
If there are any, transfer payments, overpayments or funds to the new case and remove from the disabled case. This may involve:
See Reassign Cuba Process Help. There should be no funds disbursed or becoming ready for disbursement after the record is disabled. |
6 |
Check case status + Read more ... If the adult record is a payer and the case status is pended:
This removes the need for the case to be cancelled and recreated. The registration will need to be completed in Cuba. Go to Step 4 of the Process immobilisation of duplicate adult record table. In all other cases, go to Step 7. |
7 |
Delete care arrangements + Read more ... Delete all care arrangements (past and current) for all children attached to the adult record being disabled. This includes relevant dependents. If Centrelink care records exist, CUB SSOs and CUB SGT Service Officers can delete these records. |
8 |
Update relationship details + Read more ... Delete the relationship details connecting each child to the duplicate customer. If the duplicate record is the payee:
If the duplicate record is the payer:
Do not run eligibility. |
9 |
Note child support period and registration details + Read more ... Examine the Child Support Period window and note the relevant dates and length of all child support periods. For any shortened child support periods, manually re-create the child support period in the re-created case. To recreate the case, obtain case registration details including:
|
Process immobilisation of duplicate adult record
Table 4: this table describes the process for immobilising a duplicate adult record and is for Service Support Officers (SSO) and Solutions Gateway Team (SGT) Service Officers only.
Step |
Action |
1 |
Cancel registration + Read more ... Do not deviate from the process as this may result in irreparable data corruption. Disconnect all care and relationship information from the duplicate record before cancelling the registration. Remove child roles and relevant dependent roles where possible. Do not run eligibility. Does the duplicate record have an active case?
Note: this may impact the customer’s FTB entitlements. |
2 |
Update retained customer record + Read more ... Update the customer record to include all relevant details gathered from the duplicate customer record, including:
|
3 |
Re-create new case record + Read more ... Once the original case is ineligible, re-create the case within the correct customer record. Using the information from the original case including:
A new case number is created, that will differ from the original case number. The collection status in Cuba defaults to private collect. Make sure the collection status reflects the previously registered collection status. |
4 |
Run eligibility + Read more ... Once satisfied with the transfer of all relevant case details run eligibility and check the Pre-confirmation window. Make sure there are no unexpected messages. See Eligibility Cuba Process Help. Check the calculation of the liability rates. The annual rates may differ from the original case. If the customer is a payer in multiple cases they would now be properly reassessed as a multi case payer. For any unexpected results:
The process is complete if the adult record:
|
5 |
Modify case details + Read more ... Once the case is re-created, add case details using the original case details including:
|
6 |
Finalise SGT Service Officer + Read more ... SGT Service Officer:
Procedure ends here for the SGT Service Officer. |
7 |
Finalise - SSO + Read more ... Finalise the SSO online request:
See:
Procedure ends here for the SSO. The referring Service Officer is responsible for customer contact and finalisation of the correction. |
Maintain parallel records
Table 5: this table describes the process for maintaining parallel customer records and is for Service Support Officers (SSO) and Solutions Gateway Team (SGT) Service Officers only.
Step |
Action |
1 |
Parallel records + Read more ... Where it is not appropriate to disable one of the customer records, maintain parallel records. This may be necessary where both records have extensive activity. This is not a preferred option. Some international scenarios require parallel records see New Zealand 'In' case management - Registrations between IR, NZ and Child Support. |
2 |
Manually calculate liability + Read more ... If the duplication of a customer record affects the calculation of liability in one or more cases, manually calculate the liability for each affected case. Examples of elements of the formula that may be affected include multi-case allowances or relevant dependant allowance. |
3 |
Formula modification + Read more ... Key the manual formula modification for each affected case. See Agreements Cuba Process Help. |
4 |
Document calculations + Read more ... Document all calculations in the Formula Modification notepad. Make sure each customer record has all the details needed to maintain the case. |
5 |
Check letters + Read more ... Check all letters for correctness. If unsure whether a letter is appropriate pend the letter and seek SSO support. See Letters Cuba Process Help. Do not issue system generated assessment notices for manual variations. Create a unique letter and manual assessment notice. The notice must display the manual calculations used to derive the formula modification. See Letters for Child Support customers. |
6 |
Additional information + Read more ... Any case events which normally trigger a liability calculation, may generate a Liability Calc Required intray. Manually recalculate the liability for all affected cases and amend the formula modification values. |