Alignment of Care Manual Follow-up (MFU) activities 277-51170000
For Centrelink and Child Support staff only.
This page contains information on the Alignment of Care MFU process and explains the FAO REA activities that result from care information transferred between the Child Support and Centrelink.
On this page:
Number of carers or percentage of care MFUs
Left Care Without Consent (LWC) MFU
Alignment of Care review of decision MFUs
General Alignment of Care MFUs
Principal Carer/'With Child' rate - Alignment of Care MFUs (CLI/MFU)
AoC MFU Processing Principles
Table 1: this table provides overarching process instruction for Alignment of Care Manual Follow Up activities to ensure correct data exchange with Child Support when applying Alignment of Care updates.
Item |
Description |
1 |
Date of receipt (DOR) + Read more ... Any updates made to care arrangements based on information in a MFU should be applied using the ‘date the MFU was received’ (DOR of the MFU) as this is the date the information was first received at Centrelink (not the 'decision date' (DCS) included on the MFU). See Correct DOR when applying care decisions. Make the updates within the MFU. If the Date of Receipt (DOR) is more than 12 months in the past, update the source code to CSSAL to allow the correct DOR to be used. Where there are multiple MFU activities with:
Multiple MFU activities due to appeal/objection. An appeal/objection decision may change a care percentage. Where there are multiple MFU activities for the same child, with the same DOV, but a different care percentage:
|
2 |
Date of effect (DOE) rules + Read more ... The Centrelink system will automatically determine and apply the correct DOE under Family Assistance law as long as the correct DOV and DON are recorded by Child Support. Similarly, if Centrelink records the correct DOR when applying care decisions and the correct DOV for the care changes the Child Support system will automatically determine and apply the decision correctly under child support law. Note: for Alignment of Care activities, if the DOR is more than 12 months in the past, update the source code to CSSAL to allow the correct DOR to be used. |
3 |
Pending child support care decision + Read more ... When actioning Alignment of Care MFUs, the MFU will relate to an Accepted (ACP) care assessment by Child Support. The MFU may also contain details of a newly commenced child support care assessment (pending care decision), as indicated in the text on the MFU. Pending care decisions will have a status of 'PND'. Do not apply the PND care to the record until the decision has been accepted (ACP), as it is not a final decision. Once the 'accepted' care decision is received from Child Support, it will automatically apply via the data exchange or a new MFU may be generated. Where CSU staff identify an ACP and PND line for the same DOV and DOR, email Centrelink Liaison team (CLU) requesting the pending care line to be deleted. |
4 |
View details of child support care decision + Read more ... Specialist staff with child support system access can view child support care decisions in Cuba. Details about a care decision made by Child Support for a child are available from:
|
5 |
MFU activity on child record + Read more ... If a child has their own Centrelink record, any MFU generated in relation to the child will be generated on the child's record and not the carer's record. To view details, go the Childs Relationship page:
Access the Child Relationships page from the Child Task Selector (CHTS) or by keying:
When a MFU is created on the child's record, and there is no indication as to which carer the MFU relates to. To work around this:
|
6 |
Documenting updates using Fast Note + Read more ... Create a DOC within the MFU/FAO activity. Note: if the MFU is generated on a child's record, create a DOC with the care details and action taken on the relevant carer/s record using Fast Note, select Auto Text, use Families > Update > Child Support Care Decision If the care decision is the result of a Child Support objection decision, use Fast Note, select Auto Text, use Families > Updates > Child Support Care Objection Decision |
7 |
Troubleshooting + Read more ... To query care details directly with Child Support without Cuba access:
For CSU staff with Child Support system access:
System issues/limitations: |
8 |
General AOC MFU processing requirements + Read more ... Care updates must be made within the MFU activity When updating care based on the MFU details, updates must be made within the MFU activity where possible. If error E012ZZ 'Entry Required' presents when updating the FTB Shared Care (FSC) screen, change the source to External and continue. Exceptions to this include where a care decision has been made in relation to a non-linked carer. If the care decision relates to a non-linked carer, see Linking a child to a customer's record. Any updates made to care arrangements based on information in a MFU must be applied using the 'date the MFU was received' (DOR of the MFU) as this is the date the information was first received at Centrelink. See Correct DOR when applying care decisions. MFU may contain care details for the other carer If the relevant child is in a different environment to the carer, the MFU will be generated on the record of the carer in the same environment as the child, provided the child does not have their own record. For example:
Some MFUs are mandated activities Some MFUs are mandated activities. This means they cannot be 'C'ancelled and must be finalised via the Assessments Results (AR) screen, even for those which require no action/update. Care decision for multiple children If the care decision received generates an MFU, a MFU will be created for each child involved. Recording care updates Update the Care Alignment Details (!CADDS) screen to reflect the accepted care decision (!CADDS is only automatically updated to show 'accepted' if the care is not included in an MFU). If a step-parent is claiming FTB for the child, the P24845 step-parent workaround may need to be applied. See Notification and assessment of shared care arrangements for Family Tax Benefit (FTB). The Agency field on the FTB Shared Care (FSC) screen must display Child Support Agency. Check maintenance grouping Check the Maintenance Entitlement Group Summary (MNGS) screen and update if required. Check the Ripple Manager Consequences (RMC) screen Ripples created within activity via the RMC screen as a STA - Started to link care updated to other carers as a started activity. Check and finalise these activities. See Ripple manager consequences. The Resources page contains MFU reasons and keywords, examples, scenarios and information about the letters produced with the Change in Care Arrangements script. |
Retrospective Care Assessment
Table 2: this table is for CSU/INC staff only
Step |
Action |
1 |
A035MN - Retrospective Care assessment received + Read more ... Reason for MFU: A retrospective child support care assessment is received for a child in a partner's or ex-partner's care for a period before the relationship ended or commenced. For example, a customer may have separated from the other parent of the child on 1 May 2025 and a MFU is generated for the child with a DOV of 25 April 2025 and a care percentage of 50%. This means we need to determine why Child Support has made a care decision in a period where we have the customer as partnered. Action required This MFU may be generated due to Centrelink advising Child Support of care and More than 2 Carer indicator = Yes.
Is the 'More than 2 Carers' indicator is 'Y' for the relevant date of event?
|
2 |
Action required to complete MFU (if not impacted by known issue) + Read more ... Complete initial record checks: (once checks are completed, return to this step)
Has the customer (or their current partner if they are claiming the FTB) been FTB CUR/CZR since the DOV of the CS care decision?
|
3 |
Check for existing Centrelink care decision + Read more ... Centrelink has the same care decision already coded for the carer and:
Centrelink does not have the same care decision already coded for the carer: |
4 |
Centrelink does not have the same care decision already coded for the carer + Read more ... A customer may advise different dates of separation to Centrelink and Child Support. When a customer advises Centrelink of separation, a care decision for any children that were part of that relationship is made using the DOR of the activity, this applies even when the care screens on the Centrelink system have not been updated. In cases where a customer later advises Child Support of separating and they give Child Support an earlier separation date, Child Support may make a care determination using the DOV of the separation date which overrides the later DOV Centrelink has already determined. See examples on the Resources page. The changed relationship status is recorded in Centrelink (but from a different DOV) and:
The changed relationship status has not yet been recorded in Centrelink. If:
|
5 |
Customer and other parent are not partnered on MS + Read more ... This may occur where the customer advises Child Support of reconciliation with the other parent before advising Centrelink. Go to the Activity List (AL) and Document List (DL) screens to check for any customer contact about the change to relationship status. If the customer's change in marital status is:
|
6 |
Customer and other parent are partnered on MS + Read more ... The customer may have advised Child Support they have separated but not yet advised Centrelink, or Centrelink may have a separation update in progress (MOC/SUOR assessment, benefit transfer, etc). Check the customer’s record for advice of changed relationship status. If:
|
7 |
Finalise the MFU + Read more ... Note: where retrospective details are being reviewed, consider potential Family and domestic violence (FDV) impacts that may have occurred or could occur based on this information. See Separating safely - protecting personal details.
Procedure ends here. |
Number of carers or percentage of care MFUs
Table 3: this table is for CSU/INC staff only.
Step |
Action |
1 |
Number of carers or percentage of care MFUs + Read more ... MFU types include:
Complete record checks: (once checks are completed, return to this step)
Has the customer (or their current partner if they are claiming the FTB) been FTB CUR/CZR since the MFU care DOV?
|
2 |
Check the MFU type + Read more ... For: A024CH – Number of carers more than 2, Go to Step 3 A025CH - Care greater than 100%, Go to Step 4 A027CH - Carers > 2 recorded, CSACARE assessment received, Go to Step 5 A029CH - CSACARE received, same assessment in ISIS, Go to Step 6 |
3 |
A024CH - Number of carers more than 2 + Read more ... Reason for MFU: More than 2 Carer indicator = Yes received from Child Support and the child is in the care of 3 or more people and these details could not be transmitted in the data exchange. Action required: Compare the child support care assessment with care details recorded:
|
4 |
A025CH - Care greater than 100% + Read more ... Reason for MFU: Care percentage more than 100% indicator = Y received from Child Support. In most cases, this MFU is generated when the parents have become partnered. A MFU activity may display on each person's record and will most likely say that both carers have 100% care. This is because when parents reconcile, Child Support generally gives effect to the reconciliation by coding the child/ren in care as 100% each for both parents (200%) from the date they reconciled. Action required: Record the child's CRN from the MFU and the DOV that has > 100 Y. Note: the MFU may have more than one decision in it Go to the Marital Status (MS) screen. Does the customer display as partnered on the MS screen?
|
5 |
A025CH - Customer displays as partnered on the MS screen + Read more ... Compare the MS DOV to the care DOV. If the care DOV is:
Procedure ends here. |
6 |
A025CH - Customer displays as not partnered on the MS screen + Read more ... Check the Activity List (AL) and Document List (DL) screens for any customer contact about the change. If the customer's change in marital status is:
Note: if there is a MFU on both parents' records advising 100% care for each, coding will depend if one or both members of the couple received FTB for their mutual children while separated, see Table 2 > Step 2 of Family assistance customer becomes partnered. Create a DOC within the MFU activity and finalise activity. See Table 1 > Item 6. |
7 |
A027CH - Carers > 2 recorded and CSACARE assessment received + Read more ... Reason for MFU: There are more than 2 carers for the child on the Centrelink system and a child support care assessment is received. Action required: Select the MFU for the child, Go to Step 9. |
8 |
A029CH - CSACARE received, same assessment in ISIS + Read more ... Reason for MFU: A completed care assessment is recorded on the Centrelink system and a completed child support care assessment is received and the only difference is the care percentage. This MFU is also created where Centrelink have recorded ICC and let the system assume the percentage of care, rather than coding a percentage on the FSC screen. Action required: Note the child's CRN, DOV and percentage from the MFU, then go to the CHC screen for the child. Check that the child is coded ICC of the customer for the DOV and note if the child is coded ICC of any other carers as at this DOV. Go to the FSC screen. Is there a percentage recorded on the FSC screen for the customer for the DOV?
|
7 |
A029CH - Percentage recorded on the FSC screen for the customer for the DOV + Read more ... If the existing decision was made by:
|
8 |
A029CH - Percentage not recorded on the FSC screen for the customer for the DOV + Read more ... If there is not a percentage on the FSC screen for the DOV, it means the Centrelink system will make assumptions on the care percentage. If the child is coded ICC of:
|
9 |
Manually align the care decision + Read more ... Select the MFU for the child. If Centrelink does not have the same care decision already coded for the customer, manually update the relevant child support care decision for the child using the correct DOR, see Table 1 > Item 8. If a step-parent is claiming FTB for the child, the Notification and assessment of shared care arrangements for Family Tax Benefit (FTB), Step-parent workaround may need to be applied. Make a principal carer determination for the child if the customer or other carer is claiming or receiving an income support payment. Create a DOC within the MFU activity and finalise activity. See Table 1 > Item 6. Action any MFUs for the same child/case/care period on other records. Procedure ends here. |
Left Care Without Consent (LWC) MFU
Table 4
Item |
Description |
1 |
A026CH - Child LWC recorded & CSACARE assessment received (LWC coding) + Read more ... Reason for MFU: Left care without consent (LWC) for a child has been recorded and a subsequent child support care assessment is received within the 14 (or 26) week review period. Note: it can also be created if a child support care decision is received with Disputed care indicator = Yes. In this case, separate action is required, see Item 2 Action required: If a MFU activity displays on a child's record, view details. See Table 1 > Item 4. Make sure the customer is eligible for LWC coding for the child. See Table 1 > Item 7:
Is LWC coding correct?
|
2 |
A026CH - Child LWC recorded & CSACARE assessment received (child support disputed care) + Read more ... Reason for MFU: Care arrangements were initially advised to the Child Support Agency and the child support care decision has Disputed care indicator = Yes. This is a trigger that the customer may be eligible for LWC (left care without consent) coding for the child. Note: it can also be created if LWC (left care without consent) is coded in Centrelink system and a child support care decision is received in the review period. In this case, separate action is required, see Item 1. Action required: If a MFU activity displays on a child's record, view details. See Table 1 >Item 4. View child support care decision details. See Table 1 > Item 3. If the child support care decision needs to be clarified, to view evidence used for the child support care decision, or if there is a system issue, see Table 1 > Item 7. If Child Support does not have evidence supporting LWC coding, contact the customer directly to discuss whether LWC criteria are met. Does the customer meet LWC eligibility?
|
Alignment of Care review of decision MFUs
Table 5
Item |
Description |
1 |
Explanation or formal review of decision needs related care period + Read more ... Keyword: #APL* * = wildcard for COM/FIN/ODM. Note: this is a reassessment activity, not an MFU. Reason for REA: A FAO/REA activity is created after the Internal Review/Explanation script has been used to record a request for an explanation or application for a formal review of a decision with a 'care' reason code of PDC, PRS, PSC, PTS or CSR. Complete the FAO/REA activity before finalising the explanation or formal review of decision. If this is not done, an edit will display to make sure the link is completed within the next explanation or formal review of decision activity. Action required: See Table 4 > Step 1 of Internal review process for care decisions. |
General Alignment of Care MFUs
Table 6 This table is for CSU/INC action only
Step |
Action |
1 |
A030CH - Disputed care recorded + Read more ... Reason for MFU: Automatically generated 98 days after the Date of Notification for Disputed Care Indicator = Yes on the Care Alignment Details page. Action required: Cancel the automatic MFU and wait for manual FAL to generate. |
2 |
A031CH - Change of care received for deceased child + Read more ... Reason for MFU: Generated when a care transaction is received from Child Support regarding a child who is recorded as deceased by Centrelink. Action required: If a MFU activity displays on a child's record, view details. See Table 1 > Item 4. View the care details and date of death details, if required email the Centrelink Liaison Team (CLU) for more details. Care may need to be aligned if:
Refer the case to the Level 2 Policy Helpdesk for advice. The Resources page has a link to the Helpdesk. |
3 |
There is missing Adequate Care data on the customer's record to complete the FTB Lump Sum Claim: A027FY + Read more ... Keyword: AOCMFU Reason for MFU: The customer's lump sum claim for Family Tax Benefit (FTB) has been pending for at least 32 days for any reason and adequate care information is still required to complete the claim. Action required: Contact the customer to confirm they have a post 1 July child support assessment for the child, or to obtain the care arrangement details. Does the customer have a post 1 July 2010 child support assessment for the child?
In Customer First, select the MFU activity and see the AOC and Lump Sum Claims - Adequate Care (!FYLSCD) screen. Select the relevant child and record 'YES' in the Does the customer have adequate information for this claim to proceed? field. Create a DOC within the MFU activity and finalise activity. See Table 1 > Item 6. |
4 |
A035CH - Change in primary carer for Baby Bonus (BBY) or Parental Leave Pay (PPL) + Read more ... Reason for MFU: A child support care assessment has been received for a carer currently receiving, or who has previously received BBY/PPL for a child. The assessment determination has reduced the care percentage to less than 50% during the BBY/PPL relevant period. Action required:
|
Principal Carer/'With Child' rate - Alignment of Care MFUs (CLI/MFU)
Table 7
Step |
Action |
1 |
Percentage of care has changed for child. Check “with child” rate. Check Principal Carer Status + Read more ... Keywords: WCHILD and AOCREV Reason for MFU: A child support care assessment has been received and the percentage of care has changed for a customer in receipt of a social security payment that attracts a higher 'with child' rate of benefit. Relevant income support customers:
Action required: If a MFU activity displays on a child's record, view details. See Table 1 > Item 4. Where care percentage has been reassessed to below 55% and the change is more than 10% from the previous assessment a principal carer determination must be made. If the change is not more than 10% and the percentage of care is between 46% and 54%, a reassessment is not required unless the carer without principal carer status claims they are now the principal carer.
|
2 |
Percentage of Care has changed for child. Check customer's Principal Carer status for correct entitlement + Read more ... Keywords: AOCCSC and AOCREV Reason for MFU: A child support care assessment has been received and the percentage of care has changed for a customer in receipt of an income support payment as a principal carer. They may no longer be eligible for a higher rate of payment or Parenting Payment (PP) if they are no longer a principal carer. Action required: If a MFU activity displays on a child's record, view details. See Table 1 > Item 4. Note: for Alignment of Care activities where a DOR more than 12 months in the past is required, it may be necessary to cancel the MFU and create a new activity with source code CSSAL.
If the customer is single and receiving JobSeeker Payment (JSP), Youth Allowance (job seeker) or Special Benefit (SpB) and the principal carer status is changing, the PCCD screen will be automatically updated based on SSC screen coding. If the customer is in receipt of Parenting Payment Single (PPS) the Child/Override (CHOC) screen may need to be updated for Service Rsn: PPS from the date of change. To determine if the CHOC screen needs to be coded and for how to code, see Child/Override (CHOC) screen. If the child is no longer in care of the customer, the child should be coded with left Customer Care (LCC) on the Child in Care (CHC) screen. If the child support care decision needs clarification or there is a system issue, see Table 1 > Item 6. Create a DOC within the MFU activity and finalise activity. Use Fast Note, select Auto Text, use Families > Updates > Principal Carer determination. Where PP cancellation occurs, create a separate DOC. Use Fast Note, select Auto Text, use Parents > SUS/CAN/RES > PP Cancelled/Suspended. |