Updating debt Reference Data Facility (RDF) tables for emergency events 107-23042724

Check that all required information has been provided for the emergency event to be coded. This information includes:

• all relevant approvals
• postcodes to be included
• whether:
• a pause is to be applied to raising and/or recovery. In this case, use the DMN.Sus.Auto.Det.Raise.Debt table. Also check that the informal account payable process is activated
• Situational Hardship/Flexible repayment option rules apply. In this case, use the DMN.Debt.Recovery.Pause table
• any write off or quarantine options apply
• existing payment arrangements will be cancelled
• this activation affects other activations
• the duration of the pause, including the pause end dates for:
• raising, and
• recovery

Create a share drive folder for the event in the Debt Correspondence and System share drive. This will be located under the ‘Emergency Management’ folder. Name this folder after the emergency event that has been activated. For example, ‘QLD March floods 2022’. Make sure all changes are made correctly.

Has all required information been received?

• Yes, go to Step 2
• No, do not proceed. Procedure ends here

Key the postcodes into the RDF tables based on information received.

Note: the Families and Child Care (FCC) Programme are responsible for updating the Families RDF table to finalise the activation of a debt pause on raising and debt offsetting for Family Tax Benefit (FTB)/CCS debts.

The following tables may need to be coded with the relevant details:

• DMN.EMG.Postcodes DMN
• Debt.Recovery.Pause
• DMN.Sus.Auto.Det.Raise.Debt

See the Resources page for coding guides and additional information about the RDF tables.

Are there debts in Process Direct that require Treatment Pathway coding?

• Yes:
• code the rule sets based on the information received and agreed parameters. These should reflect the RDF rules keyed within the Debt Management and Information System (DMIS)
• see the Resources page for guide to coding the Treatment Pathways
• go to Step 3
• No, go to Step 3

To finalise, complete coding for:

• the RDF tables, and
• Treatment Pathways

Immediately after coding the RDF tables, request another team member to conduct a quality check to ensure coding is correct.

Has the other team member confirmed the coding has passed quality assurance?

• Yes, go to Step 3
• No:
• correct the RDF table coding errors and undertake further quality assurance
• once coding is corrected, go to Step 5

Automatic checks of the RDF table occur daily.

An email will be sent to the relevant team the next day from Debt Services if any of the following errors are identified:

• postcodes are incorrectly coded with 3 or 5 digits i.e. 234 or 87249
• the comma between postcodes is missing
• bad postcode or postcode range is detected

If no errors with the RDF coding have been identified, then no email will be issued.

Has an email been received?

• Yes. If an email has been received, investigate and correct any errors
• No, procedure ends here