Both e.voice and e.voice circularity are APIs that deliver carbon data from Rejoose. The difference lies in the type of data they deliver and the systems they integrate with on your side.
The e.voice API converts financial transactions – invoices – into e.voices that contain product-level LCA data for Scope 2 and Scope 3 reporting.
It is typically integrated into your ERP system. Every time you invoice a customer for new or refurbished IT products, the API generates an e.voice showing the carbon footprint of the products listed on the invoice.
Over time, your organisation builds a collection of e.voices that can be used for CSRD reporting.
The e.voice circularity API works differently. Instead of financial transactions, it is triggered by product selections in the system where you register products for refurbishment.
When you select a product or batch of products, the API creates a circular e.voice with data on:
◊ Avoided Emissions: the CO₂ saved by choosing refurbished over new
◊ Refurbishment Impact: the total emissions caused by the refurbishment process (including transport, data wiping, repair, etc.)
Over time, these circular e.voices can be used to generate Refurbishment Carbon Impact Benefits reports.
You can learn more about Rejoose e.voices here.
You can also share this guide for Rejoose API’s with your developer.