Overview
This article outlines Greenly's detailed delivery process for managing your cross-entity projects, organized by milestones and leveraging Greenly's tools. It walks you through project framing, the kick-off meeting, the data collection process (including how to flag cross-entity data), and how cross-entity activities are presented in your final report.
1. Project framing
To ensure your cross-entity activities aren't overlooked, we follow these key steps:
Create a flow map: We help you develop a visual representation of cross-entity interactions, which we validate together. This helps identify all potential cross-entity flows and makes sure nothing is missed.
Quantify cross-entity expenses: We gather information on your total cross-entity expenses. Comparing these to your overall expenses helps determine if they exceed the relevant threshold (e.g., 5% as recommended by Bilan Carbone®).
Assess accounting accessibility: We discuss how easily you can identify cross-entity expenses in your accounting files, which helps us gauge the level of effort required for data collection and analysis.
By following these steps, we ensure a thorough project framing that accounts for all cross-entity interactions and sets the foundation for accurate carbon accounting.
2. Kick-off meeting
During our kick-off meeting, we cover the following to ensure you understand cross-entity emissions and the project process:
Cross-entity emissions: We define and explain their importance.
Accounting threshold: We discuss the 5% guideline from Bilan Carbone®.
Consolidation rules: We clarify the difference between group and entity-level reporting.
Data collection process: We introduce the templates, timeline, and support available.
Greenly platform: We show you how to input data (flagging process) and visualize cross-entity data in the**"My emissions"** dashboard.
We make sure all stakeholders are clear on the process and expectations for cross-entity emissions accounting.
Flagging process — to effectively manage cross-entity activities, follow these steps for flagging data:
For financial data:
During the import stage: When importing your accounting file, look for a column or checkbox labeled "Cross-Entity Transaction" or something similar.
Flag transactions: For each transaction involving multiple entities within your organization, check this column.
Review and verify: After importing, review the flagged transactions to ensure all cross-entity activities are identified correctly.
For activity data:In the data collection file: Find the "Cross-Entity" boolean column in the data collection spreadsheet.
Mark activities: For activities that span multiple entities, set the value in this column to "True" or "Yes."
Provide additional details: If possible, briefly describe which entities are involved in the cross-entity activity in an adjacent column.
3. Data collection
To make sure we don't miss any cross-entity transactions, we follow these steps:
Flagging alignment meeting: We schedule a meeting with all relevant stakeholders, including accountants and data collectors from different entities. During this meeting, we establish a shared understanding of what constitutes a cross-entity transaction, agree on the criteria for flagging these transactions, address any entity-specific concerns, and ensure alignment on the importance and process of flagging accurately.
Regular check-ins: We have brief calls or send emails to check in on any challenges you're facing in identifying cross-entity transactions.
By following these steps, we minimize the risk of cross-entity transactions being missed or inconsistently flagged during the data collection phase.
4. Report
To ensure cross-entity activities are displayed clearly in the final report, we:
Create a cross-entity section: A dedicated section in the report focuses on cross-entity activities and emissions.
Provide context: We explain what cross-entity activities are and why they're reported separately.
Use visualizations: Flow charts and diagrams help illustrate cross-entity relationships and transactions.
Clear labeling: We clearly label all cross-entity data in charts, graphs, and tables to distinguish it from single-entity data.
Breakdown of cross-entity emissions: We give a detailed breakdown by activity type and involved entities.
Comparative analysis: A comparison of cross-entity emissions to overall emissions highlights their significance.