> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.xap.rocks/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# CCSS Session Error - Reason for Late Change required when Vary/Withdraw outside Timeframe

#  CCS Session Error - Reason for Late Change required when Vary/Withdraw outside Timeframe

This article will assist you with managing the CCS session error of Reason for Late Change required when Vary/Withdraw outside Timeframe.
Note: If you are receiving this warning in relation to a CCSS Enrolment see: CCSS Enrolment Error - Reason required for Late Submission of Enrolment Notice. 

### Meaning:

If you are adjusting attendances for the same financial year more than 28 days from the current date you are required to select a reason for the late submission for CCS to allow the submission to be successful.

### Why the error occurs

The Message of 'Reason for Late Change' indicates that the child has sessions that have been submitted to CCS and have been edited prior to 28 days from the current date. When this occurs CCS require a reason for a successful session to be edited and re-submitted.

Sessions should only be withdrawn/edited for 3 reasons
* The Session **Days** previously submitted were incorrect
* The Session **Fees** previously submitted were incorrect
* The Session **Times** previously submitted were incorrect

The message will be displayed on your Session reports failed to submit email as below and will include the information of:

* The name of the child
* Family name
* Week Start Date that is incorrect
* Total Fees Charged
* Error


![](https://storage.crisp.chat/users/helpdesk/website/5dcba586b1ba9400/image_ahjnlm.png)

### Viewing the Error
When session information is edited via the Session Reports screen, the late change warning will be displayed.

1. Select the **Bookings & Attendance** Screen
2. Select the **Session Reports** screen
3. Search on the **name** of the child
| Note: The Sessions will be in the status of **Completed**
4. Select the required **dates** for correction
5. Select the **3 Dot** menu for each week
6. Select **Submit to CCSS**

![](https://storage.crisp.chat/users/helpdesk/website/5dcba586b1ba9400/image_5msb91.png)

The Submit Session Report screen will display
1. Select **Save & Submit**
2. The error will display regarding the **Late Change information** being required
3. Select **Cancel** to close the pop-up

![](https://storage.crisp.chat/users/helpdesk/website/5dcba586b1ba9400/image_1ij2tfk.png)


4. The Screen will change to display the Reason for Late Change information

![](https://storage.crisp.chat/users/helpdesk/website/5dcba586b1ba9400/image_17euild.png)


###### Adding in a Late Submission Reason

5. Select the **Reason for Change** from the drop-down menu
6. Select **Save & Submit**

![](https://storage.crisp.chat/users/helpdesk/website/5dcba586b1ba9400/image_8xqiu.png)



### Why the error needs to be resolved.

If the message is not resolved this can impact the Service and Guardian for paid CCSS.
* The Session for the child with the error will not submit successfully for processing until the message has been corrected
* Can cause a Breach with CCSS due to the session not being submitted within 14 days required period
* CCS will not estimate on any Sessions not covered by a CCSS Enrolment

|| To assist you further with managing CCSS Errors see: [Help Guide - Managing CCSS Errors](https://help.xap.rocks/en/article/help-guide-managing-ccss-errors-uh2z2r/)