ROS Digital Certificate Signing Issues

Your ROS digital certificate must be loaded into your browser before the process will work.

Please click here to open a PDF document with specific instructions on how to do this, and click here for further help in using Revenue’s online services, including ROS.

Please use the same browser to log into CORE as you do for Revenue/ROS.

Third Party cookies must be enabled on your browser as ROS is seen as a Third Party by CORE.

The Browser you use will also affect your ability to connect. From feedback we have received over the last few years:

  • Chrome ordinarily works
  • Firefox ordinarily works
  • Microsoft Edge has no reported issues
  • Chrome does work, depending on your operating system
  • Safari does not work

 

To sign on CORE you must have an active ROS sub-user certificate issued in the name of the CORE signatory.

The certificate must be issued from the tax registration number or TAIN designated as the signer in CORE, otherwise you get the following error message:

This message means that if you want to sign company accounts as a Director, you must have a sub-cert issued by that company’s ROS Administrator. 

If you are an Agent, you must have a sub-cert issued by the Electronic Filing Agent (EFA) ROS Administrator – this may be a Revenue TAIN or a tax registration number.

The Electronic Filing Agent must have a sub-cert issued in the name of the Agent as recorded with CRO. The Agent name comes up as the signatory.

CORE should show the name of the expected signatory and whether the signer is and Electronic Filing Agent or a Director/Secretary.

Electronic Filing Agents must be approved by CRO to file on behalf of clients.

Below is an example of where information may be viewed on CORE for a B1 Form:

 

If the name of whom the sub-cert was issued to does not exactly match the name of the signatory on CRO, or if the sub-cert was not issued from the correct ROS account, the following types of error can occur:


  • A ROS Certificate must be renewed at least every two years, or they expire and become invalid
  • Where a ROS Administrator certificate expires, all sub-user certificates are suspended and are invalid until the ROS Administrator certificate is restored
  • Where the sub-user certificate is renewed, the previous version of the certificate becomes invalid. This can be a problem if the certificate is being shared. If one user renews the certificate, all copies of the previous version become invalid. The ROS Administrator may suspend or revoke a sub-user certificate at any time

 
Below is the type of message which may occur:

This sections presents a list of links to help you trouble shoot any ROS issues you are having.

Please note: These following links point towards the Revenue website, which is not managed by the CRO.

  • Click here for information from Revenue on signing with ROS
  • Click here for instructions from Revenue on registering with ROS
  • Click here for PDF instructions from Revenue on how to create a sub user ROS Cert
  • Click here for instructions on how to save your ROS cert to your computer, a required action
  • Click here for PDF instructions from Revenue on loading your Digital Signing Cert into your browser. Please remember to ensure you use the same browser to login to CORE as you do for Revenue/ROS
  • Click here for help to address logging in issues with ROS
  • Click here to access the ROS Help Centre