CMS Rejections

top_tip_-_rejections.pdf Download full guide with screenshots

Non-portal filings (counter, email, mail)

The registry should assess and make a determination if the application or document should be Accepted or Rejected for ALL filings.

The ONLY scenario that the registry can reject the filing of an application or document is via a work queue task.
If an application or document is not directed to a work queue for review by the registry, the filer will receive an automated acknowledgement email advising the filing has been accepted by the court. (In the case of an application, the application will also be automatically issued by the system and available for service).
It is important that applications/documents are not rejected after communications have been sent advising the filing has been accepted.

The table below outlines the appropriate steps that should be followed for each scenario.

Scenario	Step
Rejection of non-portal filing (counter, email, mail)	Advise the filer that the application/document is rejected Provide reasons for the rejection to the filer Record the rejection and reasons in CMS (refer to 'Rejected a document' in the common tasks SOP, Rejections)
Rejection of portal filing via a work queue	Reject the filing in CMS via the work queue task, entering reasons for the rejection (refer to 'Action a work queue task to review documents' in the common tasks SOP, Rejections) In addition to the automated system notifications, contact the filer to explain the reasons for the rejection and provide advice re next course of action
It is discovered that a document or application that has been previously auto accepted/issued has deficiencies	Contact the filer to explain the deficiencies in the filing Request the application/document be re-filed after appropriate corrections Make detailed case notes in the Register of Actions (ROA) Advise presiding judicial officer if appropriate DO NOT reject the application/document in CMS

This page was last updated: Thursday 20 June 2024 - 10:20pm