Changes for System Users and CBs 

The steps in the section Approval Process at the bottom of a registration form have been revised to provide more clarity regarding the status of the registration. As a task can also be sent back to the CB or System User, it is highly recommended to refer to the Process History section for more details. The status of a registration can always be found in the section General Data in field Document Status.

The ISCC PLUS Transportation scheme has been removed from the ISCC Certification Schemes in the registration form.

The list of voluntary add-ons has been updated in the registration and certificate sections. Previously this list was only available for ISCC PLUS, the newly available list of add-ons for ISCC EU is as follows:
• 202-04: Food Security Standard
• 202-09 EU Deforestation Regulation (EUDR)
• 205-03: Non GMO for food and feed
• 205-04: Non GMO for technical markets

The updated list of add-ons for ISCC PLUS is as follows:
• 202-04: Food Security Standard
• 202-07: Low ILUC-risk feedstock
• 202-09: EU Deforestation Regulation (EUDR)
• 205-01: GHG emission requirements
• 205-03: Non GMO for food and feed
• 205-04: Non GMO for technical markets

If the EUDR add-on is selected for a First Gathering Point, a new section called EUDR add-on specific information appears on the certificate form. CBs must upload the Auditor legality verification document in this section. Once the certificate has been submitted System Users must upload the Geolocations file and the EUDRx report in this section.

Changes for CBs

The listed CB employees on the ISCC HUB can now be assigned to a specific type of email notification, distinguishing between registration related, certificate related or integrity related emails.

HUB Manuals

The ISCC HUB Manuals for system users as well as CBs have been updated to reflect a detailed guidance on completing the site information and sourcing contact tables.

Changes for System Users and CBs: 

Site information and sourcing contacts 

The list of sites and sourcing contact template has been changed, with newly adjusted validations. This applies to all certificates (for new certificates, already issued certificates and certificates that were drafts at the time of deployment of the HUB update). This allows for site information updates of any certificate to be sent to the UDB. The changes are also reflected in ongoing site information update requests at the time of deployment. This means that whenever a certificate is modified, the new validations become effective. Thus, while optional, it is recommended that system users update the necessary site information on the ISCC HUB before proceeding with certificate modifications to reduce the required corrections of site /sourcing contact information on CB side. 

Downloadable site/sourcing contact templates are specific to each certificate. This is already applicable at the certificate draft stage. This means that the downloaded template only accepts information that matches the details as given in the certificate on the HUB, such as materials specific to each ISCC system. This is intended to reduce the number of errors during the upload process. However, for already audited companies, for which the certificate has not yet been submitted on the HUB, it is necessary to insert already requested data into the new template. This could be done by the system user or the CB as long as the data is checked by the CB and is provided at the time of certificate issuance and submission on the HUB.  

HUB Manuals 

The ISCC HUB Manuals for system users as well as CBs have been updated to reflect a detailed guidance on completing the site information and sourcing contact tables. 

Changes for System Users:

Site information for ISCC EU system users migrated to the ISCC HUB:

Since May 2023, system users have been required to provide information on sites covered by a certificate and associated site-specific information (in short site information) via the site information template (also called UDB template) in preparation for the Union Database (UDB) onboarding.

We have now migrated the site information for ISCC EU certificates into the ISCC HUB. The ISCC HUB has many built in validation checks, meaning only valid data has been migrated. Certificates for which data was provided in the ISCC HUB since it went live have not been overwritten.

Since the data provided by system users is of rather poor quality, all ISCC EU system users are expected to verify this information in the ISCC HUB and to request a change if needed. This is especially important to ensure that correct data is sent to the UDB once the HUB and UDB integration is activated. An update of sites covered by a valid certificate can be submitted by using the button “initiate site information update” on the certificate. Once submitted, a task is triggered for the CB to confirm the change. Only after confirmation by the CB will the change be reflected in the certificate layout in the HUB.

The related system update can be found here.

Changes for System Users and CBs:

Registration submission and modification: 

• Whenever a registration is modified, valid certificates belonging to that registration may require updating too. A pop-up window during registration modification now reminds CBs to update the certificate if required.
• The SAI gold add-on has been removed from the ISCC PLUS add-ons list in the registration form as ISCC has been confirmed SAI Gold compliant.
• The new 202-07 low ILUC-risk add-on has been added to the registration form.

Changes for CBS:

Changes to certificate submission:

• The APS-Archive upload field has been restricted to only accept zip files.
• Any certificate that has been issued before the start of its validity period will now indicate ‘Awaiting validity start’ in the certificate status.
• All certificate ID’s will now be required to follow the format provided in the guidance documents for certificate templates.
• The SAI gold add-on has been removed from the ISCC PLUS add-on dropdown menu. The possibility of indicating SAI gold equivalence in the material annex on certificates remains.
• CBs may now upload their logo, signature, and stamp in their own CB section so that they are directly included in the drafts created when clicking generate certificate on the certificate from in the ISCC HUB.

Certificates in preview:

• A new tab called Original Certificate (version 1) has been added to each certificate on the ISCC HUB. This allows for an easy comparison between the current version of a certificate and the first version, which may be especially useful when reviewing the changes made to the list of sites and sourcing contacts.

Please find the update here on the ISCC website.

There is no need for existing System Users to manually register for the ISCC HUB. In fact, access is facilitated through a single sign-on in the ISCC client section. The login details for the ISCC HUB and the ISCC website are identical. Once a System User is logged in to the ISCC client section, a redirection to the ISCC HUB is available

Therefore, any person assigned by a System User as a legal representative or designated ISCC contact person of a registration is an ISCC HUB System User and can log in to the ISCC HUB using the following link: Click here to log in to the ISCC HUB

Users, who are not yet associated with a System User, can register in the ISCC HUB by submitting the registration form: Click here to request ISCC HUB access. 

Detailed instructions on how to register a new operational unit under ISCC can be found on the Certification Process page: Click the link to the Certification Process page.

The System Users’ legal representatives as well as all named (first and second) ISCC contact persons have full access to the ISCC HUB and are able to change the System User’s registration data in the ISCC HUB.

Legal representatives and all contact persons can assign additional persons to the registration and by that allow them to access the ISCC client section and see (but not edit) the registration data in the ISCC HUB. If a person is assigned as legal representative or contact person to multiple registrations, all registrations and associated certificates are visible to that person once logged in. If a System User has multiple registered sites, only the indicated legal representatives and contact persons for the registration for this site will see the respective registration data.

For details on how to grant access to registration data in the ISCC HUB please refer to the ISCC HUB Manual.

ISCC provides the Certification Body of the System User direct access to the registration data and certificates and certificate-related information of the System User with the right to edit this data. System Users will be automatically informed of such changes. Changes to the registration will only become effective after confirmation of the System User. Changes to certificates will become effective once submitted by the CB.

Only the currently valid certificate belonging to a system user is displayed in the ISCC HUB. The certificate history is not visible in the ISCC HUB. In the certificate database on the ISCC website, however, the entire certificate history of the respective system user is still displayed.

If a person is assigned as legal representative or contact person to multiple registrations, all registrations and associated currently valid certificates are visible to that person once logged in. The List of Sites covered by certificates and Sourcing Contacts are only available for System Users certified under ISCC EU, if the data has been correctly submitted to ISCC.
Further, that person can access basic information about Certification Bodies and the list of materials that can be certified under ISCC.

All registrations are to be submitted directly in the ISCC HUB. It replaces the previously used registration form on the ISCC website. Drafts for new registrations can be saved and thus facilitate the process.

Details on how to register can be found here.

The ISCC HUB enables System Users to change registration data directly by themselves. This includes basic data as well as any other information that was submitted during registration or subsequently (e.g., the scope of certification). In case of changes, System Users have to immediately update their registration in the ISCC HUB.

Please note: ISCC will allow direct access to the ISCC HUB to all legal representatives, first and second contact persons named by the System User either at registration or in later updates. All these persons may change registration data of the System User in the ISCC HUB. If System Users want to restrict the access of certain individuals to the ISCC HUB not only by internal instructions but also vis-á-vis ISCC, they must delete these persons from the list of representatives or contact persons in the respective registration in the ISCC HUB. Please note that there must always be a contact person who can be contacted by ISCC at any time.

For details on how to change the Certification Body of a registration in the ISCC HUB, please refer to the ISCC HUB manual.

For the requirements of a Certification Body change and resulting implications, please refer to the ISCC System Documents.

Changes to certificates will become effective once submitted by the Certification Body. System Users will be prompted by the system to immediately check these changes.

System Users must check if mandatory data in the respective registration is missing. Use the button “Edit Registration” to open the registration in change mode. Check all data for accuracy and if necessary, fill out all mandatory fields (marked with a *). Then, click “save” at the right-hand bottom of the page. The CB receives a task to review and approve the changes. After approval, it is possible to use the functions “Certification Body Change” and “Change Access Rights”.

In the ISCC HUB, the legal representative, the contact person(s) and, if applicable, additional persons of a System User can access the currently valid certificates associated with their registration(s). As before, all certificates are visible and publicly accessible in the certificate database on the ISCC website.

The Certification Body takes full responsibility and ensures that the information that is uploaded in the ISCC HUB and published on the ISCC website according to the System Standards is accurate and complete. This includes, but is not limited to, System User basic data, certificates, audit reports or information on the status of certificates. Certificates can be automatically published upon submission by the Certification Body on the ISCC website without further verification by ISCC.

Entered certificates are immediately displayed in the certificate tables on the ISCC website. The same applies to the pdf-representations of the certificates and the Summary Audit Reports published on the ISCC website. This real-time synchronisation allows interested parties to immediately verify the validity of certificates of System Users.

ISCC reserves the right to hide certificate data, certificate pdfs or Summary Audit Report pdfs from the ISCC certificate table on the ISCC website in case of missing or unclear information in the audit documentation or unpaid invoices.

System Users can change their sourcing contact information directly by themselves in the ISCC HUB. They are obliged to immediately update any change of sourcing contacts (farm/plantations, points of origin) that is part of a certificate.

The list of sites covered by a certificate are external storage facilities or dependent collecting points for which a mass balance is required. They can only be updated by the Certification Body to check if any further steps need to be taken (e.g. Extension audit) before adding a site to the certificate.

All certificates valid at the time of the ISCC HUB Go Live have been migrated to the ISCC HUB. The migration did not include material annex information, however, the certificate database on the ISCC website discloses material information for these certificates.

No, the transfer of Surveillance Audit data is not part of the data migration to the ISCC HUB. However, documentation on the Surveillance Audits conducted by the CB shall also be submitted to ISCC via the certificate section in the ISCC HUB.

The future integration of the ISCC HUB with the European Commission’s Union Database and the ISCC Transaction Database will establish a comprehensive one-stop-shop solution for System Users. Further details on this integration will be communicated in future updates.

Certificates entered by Certificaton Bodies in the ISCC HUB are immediately displayed in the certificate tables on the ISCC website. The same applies to the pdf-representations of the certificates and the Summary Audit Reports published on the ISCC website. This real-time synchronisation allows interested parties to immediately verify the validity of certificates of System Users.