Overview
This article explains how users with a consolidated (parent) account can collect and submit module data at the group level, rather than entity by entity. It covers how to access modules from the parent account, how consolidated data collection works alongside entity-level collection, and how to avoid duplicating data across both levels.
Key benefits / use cases
Save time by importing data once at the parent level instead of repeating the process for each entity
Flexibility to collect data at whichever level suits your organisation — parent, entity, or both
Maintain a clear audit trail by submitting data from a single centralized account
1. How to access a module from the consolidated account
Log in to your consolidated (parent) account on the Greenly platform. You can usually identify it by its name, which follows a format similar to Group Company Name – 2025.
You can track each entity’s task progress in Progress > Task details > Entity, use the Org Chart tab, or go directly to Data > Data Collection.
Select the module you want to complete. Modules that support centralized import are automatically available at the parent level as soon as they are open in at least one child entity. This includes the Buildings module (coming very soon), as well as most end-to-end, lightweight, and advanced modules, except for Cloud modules (AWS/Azure), Food, and Raw material, goods and packaging purchases modules.
Download the Template from the consolidated account (this version is tailored for consolidated data collection and lets you allocate each data point to a specific entity), then follow the standard data collection process for that module. To ensure that data entered from the consolidated account is assigned to the correct entities, make sure to complete the Entity column in the template. If needed, also complete the Supplying entity column for cross-entity activities to avoid duplicates.
💡 Don't see the module? Make sure the module has been opened in at least one of your child entities first. A module must be active in a child entity before it becomes available for centralized import on the parent account.
2. Collecting data at the parent level vs. entity level
You can collect data both at the parent account level and at individual entity levels — these two options can be used alongside each other.
Choosing one option does not prevent you from using the other. However, be careful not to duplicate data collection between entities and the consolidated account. If the same data is submitted at both levels, it will be counted twice in your consolidated results.
A good rule of thumb:
Use the parent account for data that applies to the whole group or is easier to manage centrally (e.g. a single supplier file shared across entities).
Use entity-level accounts for data that is specific to each entity.
3. Avoiding and reviewing duplicates
Cross-entity data point: During data collection, please flag any inter-entity data points to avoid the risk of double counting or incorrect emissions allocation. For each affected line, please specify the service-providing entity and the receiving entity, where applicable.
This may occur, for example, when one entity provides a service to another. In the case of freight, Entity A may transport goods on behalf of Entity B. As a result, both entities could potentially report the same shipment: Entity A as outbound freight carried out for Entity B, and Entity B as freight purchased from a service provider — in this case, another entity within the group.
To ensure that the shipment is correctly accounted for at the individual entity level while avoiding double counting at the consolidated group level, please indicate in the file of entity B whenever the service provider from another entity within the group.
⚠️**Don’t flag the activity as cross-entity in both entities; otherwise, it won’t be counted at all at the group level. In most cases, you should mark the activity as “cross-entity” on the service-receiving entity rather than on the service-providing entity.Duplicates:
When completing an activity-based module, Greenly may identify potential duplicates between the activity data submitted in the module and transactions already recorded in the financial data.
These potential duplicates are displayed in the Quality controls step, under the Activity duplicates** tab. They help you check whether an activity has already been accounted for through financial data, in order to avoid counting the same emissions twice in the consolidated results.
Please contact our support team if you need any assistance, either via the chat or by sending your request to [email protected]
FAQs
Which modules support centralized import from the parent account?
Most modules support centralized import. A module becomes available on the parent account automatically once it is open in at least one child entity. Note that some modules — such as Cloud modules (AWS/Azure), Food (end-to-end), Product Purchase and Employee — do not currently support centralized import.
Financial imports remain at entity level for the moment, but categorization is possible at group level! (more info)
Can I complete a module from the parent account without it being open in every entity?
Yes. The module only needs to be open in at least one child entity to appear on the parent account. However, only the entity for which the module is open can be selected in the file when selecting which entities the data applies to. In each module, there is a banner indicating which entities currently have the module open.
If I submit data from the parent account, do I still need to do anything at entity level?
Not necessarily. Once data is submitted from the parent account, it is assigned to the relevant entities automatically. You only need to act at entity level if you want to add entity-specific data, or if you need to review or correct potential duplicates.
What happens if I mark a module task as "Done" from the parent account?
For supported modules, marking a task as Done at the parent level will automatically mark it as Done for all child entities that have data in that module.