You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Develop a reporting module to automate the preparation of quantitative and qualitative data for annual submissions under Article 6.2, ensuring compliance with the latest guidance.
Pre-Filled AEF Reporting Format:
Enable the automatic pre-filling of the agreed electronic format (AEF) for Article 6 Carbon Reporting (CR) submissions.
Use templates such as AEF_Agreed_electronic_format.xlsx for data pre-filling.
Support exporting data in the AEF table format for compliance purposes.
Inclusion of Additional Reporting Information:
Beyond the AEF, incorporate other quantitative and qualitative information required by Annex V of Article 6.
Ensure flexibility to adapt to additional reporting requirements as guidance evolves.
Automated Pre-Checks and Validation:
Implement automated pre-checks for draft submissions to identify errors or omissions.
Include a Validation Button to allow users to confirm data accuracy before submission.
Provide a checklist to guide users on the required information and steps for successful submission.
Access for Article 6 Technical Expert Review Teams:
Create a secure area for authenticated access by Article 6 technical expert review teams.
Provide access to both public and confidential information relevant to the review process.
Enable communication between the UNFCCC Secretariat and Parties undergoing review directly within the system.
Develop a reporting module to automate the preparation of quantitative and qualitative data for annual submissions under Article 6.2, ensuring compliance with the latest guidance.
Pre-Filled AEF Reporting Format:
Inclusion of Additional Reporting Information:
Automated Pre-Checks and Validation:
Access for Article 6 Technical Expert Review Teams:
Article 6.2_AEF Introduction_Secretariat presentation.pdf
The text was updated successfully, but these errors were encountered: