Updating debt Reference Data Facility (RDF) tables for emergency events 107-23042724
Access requirements
Access requirements for updating Treatment Pathway tool for Process Direct debts
To create ‘Rule set’, ‘Cohort’ and ‘Campaign’, access the following roles in PROD (apply through ESSentials):
- ENHANCED TREATMENT PATHWAY OFFICER
- ENHANCED TREATMENT PATHWAY REPORTING
Access requirements for updating RDF tables
Access is requested via ISP, which will highlight a step-by-step process of gaining access. Staff must state the specific table or cluster (first 3 characters of an online table) when requesting online table access.
Apply for access to the following mainframe resources via the ICT security portal:
- RDFENQ - RDF ENQUIRY
- RDFTAB - RDF TABLE SCREEN
- RDFNAT - RDF NATIONAL ACCESS FOR SELECTED APPLICATIONS
RDF table for DMN.EMG.Postcodes
To apply a write off, the EMG table requires a status change (such as a debt becoming determined or a customer circumstance changing). Manual bulk-write offs must be applied to remaining customers within identified disaster areas where auto processes were blocked. For example, where there is no change to a status of a debt (where a customer already has a debt written off to an earlier date than the new disaster end date).
Note: postcode exclusions are often extended past the original end date. Update the RDF table when this occurs.
Table 1
Coding example
Table 2
Column name |
Description |
Format |
Example |
Start.Date |
Emergency start date |
YYYYMMDD |
20170403 |
End.Date |
Can be blank for current events |
YYYYMMDD |
20170919 |
Description |
Emergency description |
Text |
TC Debbie 2017 |
Postcodes |
List of postcodes |
Use comma to separate list of postcodes |
2372, 2469, 2470 |
Duration |
In months |
Number |
12 |
Cancel.Arrangements |
Y will cancel current arrangements |
Y/N |
Y |
Debtor.Writeoff |
Y will write off applicable debts |
Y/N |
Y |
RDF table for DMN.Debt.Recovery.Pause
When the Pause.Enabled field has the value of:
- ‘Y’, the Situational Hardship debt pause functionality is ‘on’, with the corresponding automatic write off (AWO) functionality ‘OFF’ – DMNAWO is not invoked
- ‘N’, the Situational Hardship debt pause functionality is ‘off’. DMIS invokes the corresponding automatic write off (AWO) processing – DMNAWO to undertake the debt pause write off
The banner message in MYO will change depending on the Pause.Enabled choice.
Coding example
Table 3
RDF table for DMN.Sus.Auto.Det.Raise.Debt
Table 4
Coding example
Table 5
Column name |
Description |
Format |
Example |
Record ID (keyword) |
Keyword and debt attribute applied |
Text |
DMNCOVID |
Switch |
Whether the pause is on or off |
ON/OFF |
ON |
Start.Date |
If this date is in the future and the switch is off, the switch will turn on when the future date is reached. |
YYYYMMDD |
20210321 |
End.Date |
If this date is in the future and the switch is on, the switch will turn off when the future date is reached. If HLD AUTO DET is on, this date appears as the date held to for affected activities. Note: this date must be a minimum of 30 days before Due Start Date if it was keyed (28 days for the due date + 1 day for sending the letter the day before + 1 for the DMNFAP MFU to run). |
YYYYMMDD |
20210823 |
Postcodes |
List of postcodes |
Comma separates |
4000, 4115 |
Due.Start.Date |
Due dates on informal account payables will be contain this date or the next date available considering the Max Due Per Day field. Note: this functionality is driven by control records that are controlled within DMIS. DMIS ICT should be engaged to ensure that they are in place. |
YYYYMMDD |
20210922 |
Max.Due.Per.Day |
The maximum number debts allowed to fall due by this process before incrementing the due date on account payables. There are 2 options:
|
NUM |
10000 |
HLD.Auto.Det |
Switch for whether affected auto determined new debt activities will be held instead of completed. |
ON/OFF |
ON |
DFR.Due.Date |
Turns on the informal functionality |
ON/OFF |
ON |
Treatment Pathway Tool coding example for Rule Attribute
Table 6
Column name |
Description |
Format |
Example |
Informal Period Start Date |
Start Date of Informal Period |
DD.MM.YYYY |
21.06.2021 |
Informal Period End Date |
End Date of Informal Period |
DD.MM.YYYY |
20.08.2021 |
Informal Due Date |
This is the minimum due date of a debt, if it is raised during informal period. |
DD.MM.YYYY |
21.06.2021 |
Max daily limit for due date |
Maximum number of debts to be raised with the same due date. This can be updated and an updated value will be applied to quota going forward, and not on past values. |
NUM |
20000 |
Minimum number of due days from raised date |
Minimum number of days difference between raised date and due date (if debt is raised in the informal period). |
NUM |
56 |
Maximum number of rolling days from informal due date |
Maximum number of rolling days defines how far due date can be moved. That is, the maximum due date value if a debt is raised during the informal period. |
NUM |
60 |