Resolving Common H-CLIC Errors

This article outlines how to identify and resolve common validation errors when submitting H-CLIC data.

TABLE OF CONTENTS

• Important Information
  • TADUTY
  • PNEED -  Old age & 16/17 households
• Troubleshooting Common H-CLIC Validation Errors
  • ACCOM_PR 
  • ASSESS_DATE 
  • ASSESS1 (REASONLOSS)
  • ENTRY_DATE
  • CURRENTACCOM, REASONLOSS, LASTACCOM
  • LASTACCOM
  • LCON_DEST
  • LCON_REL
  • P_START_DATE / R_START_DATE
  • REASONAST & REFERRAL
  • TADUTY & TA_OTHER (Combined)
  • TA_OTHER (on its own) 
  • TA_EXIT_DATE 
  • Household Owed TA but no TA Provided
• “Unauthorised” error message
• Error Validating the Submission
• HCLIC API - Errors that show on DELTA than weren't on the HCLIC Report

Important Information

TADUTY

Error: Cannot be interim duties unless; assessment date (1.5) has not taken place, no prevention duty is owed, or prevention duty was unsuccessful.

This error been resolved by DELTA on the 

PNEED -  Old age & 16/17 households

MHCLG are investigating the behaviour of this validation. MHCLG have advised ignoring the message and leave existing cases unchanged.

Troubleshooting Common H-CLIC Validation Errors

This section helps you identify, and fix validation errors found in H-CLIC submissions, including missing or inconsistent data. 

ACCOM_PR 

Error: ACCOM_PR - Error: If prevention ended in Homeless (4.6), (i.e. the applicant is homeless at home), then accommodation outcome (4.8) must be same as current accommodation (1.13) or a non-settled accommodation such as “living with friends or family”. Care leavers that remain in a 'Departure from institution: Looked After Child Placement ' should be reported in ' Social rented supported housing or hostel '.

ACCOM_PR must match CURRENTACCOM or be marked ‘other’.

Fix:

The Accommodation outcome after prevention (ACCOM_PR) must match Application at time of application (CURRENTACCOM)

1. Check Accommodation at time of application in Main Application Details or Homelessness Information task.

2. Complete the Accommodation Outcome after Prevention question on the Prevention Duty task.

3. Complete Local authority location of accommodation outcome Prevent if this question becomes mandatory otherwise leave blank

ASSESS_DATE 

Error: Date of assessment of circumstances is before homeless application date

Fix:

1. Check date of assessment in Assessment of Circumstances.

2. Update Homeless application date in Eligibility so that the Homeless application date is the same or before the date of assessment.

3. Click Save.

ASSESS1 (REASONLOSS)

Fix:

1. Open Main Application Details or Homelessness Information task

2. Update Main reason for loss of settled home.

3. Change Accommodation at time of application.

4. Click Save.

ENTRY_DATE

Error: Must not overlap prevention duty.
Fix:

1. Ensure ENTRY_DATE is after prevention end date in the Prevention Duty task.

Or that the ENTRY_DATE is between apply date in the Eligibility task and assessment date in the Assessment of circumstances task.

CURRENTACCOM, REASONLOSS, LASTACCOM

• CURRENTACCOM: Update Accommodation at time of application in the Main Application Details or Homelessness Information task.

• REASONLOSS & LASTACCOM: In the Main Application Details or Homelessness Information task, update Accommodation when last settled based on the answer to reason for loss of settled home and current accommodation.

LASTACCOM

Error: This error occurs when the Accommodation when last settled is blank

Fix:

1. Complete the Main Application Details task, and then Accommodation when last settled.

2. Click Complete and Next.

LCON_DEST

Error: Occurs when any of the below apply.

• Decision is “Homeless + priority need + unintentionally homeless + no local connection – referred to another Local Authority"
• There’s a value in "Local Connection Destination Authority" but it's not needed. E.g. the case is “Homeless + priority need + unintentionally homeless – s193(2) duty” 
• "Local Connection Destination Authority" is populated with your own authority

Fix:

1. On the decision task remove the answer to "Local Connection Destination Authority" if

• The name of your local authority has been entered, or
• If the Outcome of decision is not "Homeless + priority need + unintentionally homeless + no local connection – referred to another Local Authority"

2. Click Save

LCON_REL

Error: This error occurs when the Local Connection Destination Authority has been answered. If the case has not been referred to another LA under local connection, then this should be blank.

Fix:

1. Go to the Relief Duty task.

2. Clear the selected answer from the dropdown.

3. Click Save.

P_START_DATE / R_START_DATE

Error: Must be same day or 1 day after assessment date.

Fix for both:

1. Confirm Assessment Date in Assessment of Circumstances.

2. Go to Prevention Duty or Relief Duty task as appropriate.

3. Correct the start date.

4. Click Save.

REASONAST & REFERRAL

Error: Mandatory value missing.

Fix:

1. Click on the error link.

2. If the task does not exist, go to Main Application Details and complete the task.

3. If cancelled or unanswered, restore the task and select a dropdown reason.

4. Click Complete and Next.

Note: These errors often result from incomplete workflows or changes not being re-saved.

TADUTY & TA_OTHER (Combined)

Fix steps vary by case stage:

1. Check the case Type as this helps to speed up finding the cause and resolving.
2. Have they been placed in TA? *note down dates 

   1. No - Have the Retired TA questions been answered (Prevention/Relief)?

   2. Yes - Were they placed in TA after Relief Duty? 

3. Does the TA Tenancy Case ID match this case?
4. Has the TA been excluded from H-CLIC?

Did you know: Retired TA questions still affect validation if completed incorrectly.

TA_OTHER (on its own) 

The error TA_OTHER relates to which local authority district the TA is located in. The schematron only picks up those where the TA was marked as being located outside of the borough whereas the new validation asks for the location of the TA regardless of whether it is in or out of borough. Depending on your version of TA, the element is in different locations. 

Fix:

1. Go to the TA Property.

2. In Essentials: Use Administration task.

3. Answer “Temporary accommodation out of area”.

4. Select Local Authority area the TA is located in.

5. Save and rerun validation.

In TAP/TARA: 

• Go to H-CLIC task.

• Answer “Temporary accommodation out of area”.

• Select Local Authority area the TA is located in.

• Save and rerun validation.

Note: The TA_OTHER error now triggers even for in-borough placements. It must always be completed regardless of location.

Did you know: For more information on HCLIC validations, please read this article.

TA_EXIT_DATE 

Fix if TA is linked to wrong case:

1. Click the TA record.

2. Confirm TA Tenancy Case ID.

3. If this is incorrect, click on the TA Tenancy Tasks, then click the Transfer Case Id to this TA.

4. Select the related case ID.

5. Save the changes.

6. Then click into the case and revalidate icon. 

Fix if exit date is stuck:

1. Go to the case details page, click Get the H-CLIC report for this case. 

2. Open the XML and review the TA section to see what's currently populated.

3. Go back to the case and click into the active or most recent TA placement.  

4. Change the tenancy start date to a different date.  

5. Save the changes.  

6. Revert the tenancy start date back to the original date.  

7. Save again.  

8. Return to the case details screen again and re-download the H-CLIC XML.

9. Open the updated XML and check the TA section: 

   • If there's an active TA placement, the TA_EXIT_DATE line should now be removed. 

   • If there’s no active TA placement, the TA_EXIT_DATE should have updated accordingly. 

Example Original XML:

After Fix 

Household Owed TA but no TA Provided

Errors: The three errors below are displayed on the case.

Date entered temporary accommodation (system generated) (TA_DATE)

ERROR : This field is mandatory and requires a value

ENTRY_DATE

ERROR : This field is mandatory and requires a value

TATYPE

ERROR : This field is mandatory and requires a value

Fix:

1. Click on create new TA tenancy. 
2. Click on the green plus next to "Temporarily remains in property" or "Made own arrangements for temporary accommodation"

3. Enter the start and end date (if applicable) to cover the period from when the Main Duty starts until it ends.

“Unauthorised” error message

This section covers how to fix authorisation errors when validating or submitting H-CLIC data.

Error: "There was an error validating the submission (unauthorised)"

Fix:

1. Go to Settings > Manage My Partner Setup.

2. Update your DELTA username and password.

3. Click Save.

4. Click the crown icon to verify.

Note: Unauthorised errors are usually caused by outdated DELTA login details.

Error Validating the Submission

This section covers what to do when an error displays after clicking on the H-CLIC report to validate cases through the schematron.

Error: There was an error validating the submission (A sequence of more than one item is not allowed as the second operand of '-' (, ) (2244))

Cause: The error is caused by more than one Main Applicant on a case.

Fix: 

1. Create a People list report with the following filters
   • Case Opened Date - Just Display
   • Relationship - equals - Main Applicant
2. Generate the report
3. Copy data
4. Paste into Excel Ctrl + Shift + V
5. Delete rows above column headings
6. Insert pivot table
7. Add case id to row
8. Add relationship to Values
9. Click in the first row, second column of the pivot table
10. Sort Z-A look for any showing more than 1
11. Go  into each case and change the relationship so that there is only one Main Applicant
12. Once all affected cases have been updated generate a new H-CLIC report

HCLIC API - Errors that show on DELTA than weren't on the HCLIC Report

1. Generate a new HCLIC report for the quarter you need to report on.
2. Click View and look through the cases to make sure they have been validated recently and that all cases have an OK status. 
3. If there are any errors that need fixing, fix and then generate a new report and repeat the process. 
4. If all cases show ok then you can submit with confidence that there will be no further errors.

Did you know: Once the report has been submitted, it will show as ingested. 

Note: If you have previously submitted a report for that quarter, submitting a new report will overwrite the data that has already been submitted, including any fixes.