Emission mapper

What is the Emission Mapper?

The Emission Mapper is a smart transformation layer in the Position Green platform that translates customer operational data - starting with spend data - into emissions estimates by intelligently connecting data points with our Emission Factor Library (EFL).

It forms the bridge between raw input (e.g., supplier spend) and calculated carbon emissions, automating a process that was previously manual, repetitive, and error-prone.

It’s especially relevant for Scope 3 emissions, where input data varies widely and customers struggle to align it with recognized emission factors.

How to use it

1. Go to Data Reporting in left menu, then select Upload data and click Start mapping emissions.

2. Upload file by browsing files on your computer or dragging and dropping in the file area.

3. When a file has been uploaded click Continue.

4. When the file has been upload you will be able to view the mapping for each post in the uploaded document.

5. The Confidence label indicates the confidence of the AI mapping and it recommended to double check entries, especially those with label Medium or lower. Click the Mapped Emission factor for other suggestions in a dropdown menu.

6. When entries have been checked and correct emission factor has been selected, click Confirm to complete the data import.

7. The imported data is now added to the relevant measures.

8. Insights and Reporting - Mapped emissions can be visualized and tracked through Position Green dashboards and reports.

Current Scope and Limitations

FAQ

Is there a certain format required for the file upload?
No, AI will automatically detect the relevant columns.

Which columns are required?
Account number and account name are required. Other columns such as amount, supplier, and transaction details can improve the accuracy of the mapper, but are not required.

Amount will of course eventually be needed to calculate emissions, but is not required for the initial mapping exercise. So for example, companies could frontload the work of mapping emission factors before their year-end financial data is ready, then do another import with amounts once it's ready.

Which emission factors are supported?
Exiobase global factors only (for now)

What about accounts that aren't relevant for Cat 3.1? How do you prevent, for example, scope 1 fuel data from being mapped here?
We have logic in place to detect whether accounts are relevant for 3.1. This will exclude accounts that aren't relevant (e.g. revenue accounts) or that belong in another scope or category.