The difference is:
◊ The input that they are based on
◊ The systems on your side that they are connected to
◊ The data that they deliver
◊ The reports you can use them for
◊ The pricing
The e.voice API converts financial transactions – invoices – into e.voices that contain LCA data for Scope 2 and Scope 3 reporting.
The API is connected to your ERP system, and every time you invoice a customer who buys new or refurbished IT products, the API creates an e.voice that shows the carbon footprint of the products on the invoice:
Over time, you will have created a collection of e.voices that can be used for your CSRD reporting:
You can see an example of the CSR report here.
The e.voice circularity API converts a selection of products into circularity e.voices that contain data about Avoided Emissions and Refurbishment Impact.
The API is connected to the system where you register products for refurbishment. When you select a product or a batch of products, the API creates an e.voice with the carbon footprint of the selected product(s):
Over time, you will have created a collection of circularity e.voices that can be used for Refurbishment Carbon Impact Benefits reporting:
Conclusion:
You can learn more about Rejoose e.voices here.
You can also share this guide for Rejoose API’s with your developer.