Group Sync reduces duplicate work when portfolio companies (PortCos) are asked to submit ESG data that they have already reported in their own Position Green setup. It automatically fetches eligible, previously reported data and pre-fills matching questions in group company (GroupCo) surveys.
How it works
- PortCo reports ESG data.
PortCos complete ESG reporting (for example VSME, Carbon Management, or other supported modules) in their own Position Green setup. - PortCo opens a GroupCo survey.
When the survey is opened, Position Green checks whether the PortCo has relevant, previously reported data that can be reused. - The Reuse dialogue is shown.
If matching data is found, the PortCo sees a dialogue offering to reuse existing data.
In the dialogue:- Select the reporting year.
- Click “Fetch data”.
- Survey fields are pre-filled
Survey questions that can be mapped to previously reported data are automatically populated.
PortCos can review and adjust all values before submitting the survey. - Fetch can be run again
If the PortCo declines the dialogue initially, Group Sync can be triggered later from the survey menu.
Re-running the fetch updates only mapped fields. If the data in the PortCo's own setup is updated, run the sync again.
Questions & answers
What if the PortCo has multiple org.units?
Data from multiple org.units is consolidated into a single answer in the survey.
Which modules are supported?
Group Sync currently supports data reuse from Carbon Management (CM) and VSME into the Position Green Scorecard. Support for additional modules will be added over time.
Do PortCos need locked modules?
Keeping a standard module that can be automatically updated is strongly recommended.
If versions differ, Position Green fetches only data that can be safely reused and highlights gaps that require manual input.
Can the reporting year be changed after fetching data?
Yes. Re-run the fetch for a different year. Only mapped fields are overwritten.
What happens to manually edited answers?
Manual edits in non-mapped fields remain unchanged. When the fetch is re-run, only mapped fields are updated. Any manual edits made to these mapped fields will be overwritten.
Example: If incomplete data is first shared from the company setup and the missing information is completed manually in the survey, those manual edits are removed when the complete data is later re-shared from the company setup. Manual edits in non-mapped fields will remain unchanged.
Recommendation: Only make manual edits to shared (mapped) data after all relevant data has been fully shared from the company setup.
Requirements & known limitations
The reporting email address in Investment Management (IM) must exist in the PortCo's own setup as well.
Additional behaviour
Repeatable fields in the survey are reset before syncing data from the PortCo's own setup. This happens even if no corresponding data exists in the own setup.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article