Emissions — Integrations

Entering your carbon data by hand works, but it doesn't scale. As soon as you manage dozens of pieces of equipment, hundreds of invoices or several sites, the Integrations tab in dAio Business automates collection: import your historical data in bulk via a CSV file, then connect your existing systems (fleet, energy, IoT) to feed your emissions continuously, with no re-keying.

The result: a carbon inventory that is always up to date, more reliable calculations and reports ready for audit.

Tip: start with the CSV import to catch up on your history, then set up webhooks for the continuous flow. This avoids a data gap between your existing records and real time.

CSV import

The CSV import is the fastest way to load a large volume of data at once. You'll find it under Emissions > Integrations, in the CSV import section.

Steps

1. Open the Integrations tab in the Emissions section.
2. Under CSV import, select the data type to import from the drop-down list.
3. Click Import a CSV and choose your file.
4. dAio processes the file and shows the number of rows imported out of the total detected.
5. Check the result in the corresponding tab (Equipment, Invoices or Scope 3).

Importable data types

Type	Destination tab	Expected data
Equipment	Equipment	Name, type, fuel, consumption, annual hours, quantity
Energy invoices	Invoices	Supplier, invoice no., electricity (kWh), gas (m³), amount
Indirect emissions (Scope 3)	Scope 3	Category, transport mode and distance, or amount spent

Tip: to learn the exact format expected for a data type, first export an existing record from the relevant tab. You'll get the column order and the units to follow.

Warning: make sure your numeric values use a dot as the decimal separator (45.2, not 45,2) and that the units match those expected (kWh, m³, L/h). A malformed row is skipped and won't appear in the imported total — always compare the number of imported rows against the number of rows in your file.

Webhooks and connectors

The Connectors section lists the integration endpoints available to receive data continuously from your systems. Each connector shows its status — Active (usable immediately) or Soon (under development) — and, where applicable, its endpoint.

Active connectors expose an endpoint in the format:

POST /api/b2b/orgs/{org_id}/...

where {org_id} is your organisation's identifier. The data sent is attached to your emissions and included in the next calculation.

Fleet webhook

Automatically receive fuel consumption data from your vehicle fleet. Each reading is converted into Scope 1 emissions. Expected JSON format:

{
  "vehicle_id": "V-001",
  "fuel_type": "diesel",
  "liters": 45.2,
  "date": "2026-03-15",
  "odometer_km": 125430
}

Energy webhook

Integrate your smart meter readings to automatically feed your electricity and gas consumption (Scope 2), without entering invoices manually.

IoT webhook

Connect your IoT sensors (energy, machinery, buildings) for real-time emissions monitoring, as close as possible to actual usage.

Tip: keep your API keys and webhook URLs out of your code repositories and share them only with the sending systems. Contact us to generate the credentials for an active connector.

Native connectors coming soon

The following native integrations are under development. They will appear with the Active status in the Connectors section as soon as they become available:

Connector	Type	Status
Geotab	Vehicle fleet	Planned Q3 2026
Verizon Connect	Vehicle fleet	Planned Q3 2026
Schneider Electric	Energy / IoT	Planned Q4 2026
Siemens	Energy / IoT	Planned Q4 2026
Caterpillar	Heavy equipment	Planned Q1 2027
SAP	ERP	Planned Q1 2027

Info: contact us to suggest a connector, prioritise an integration or discuss a custom development tailored to your information system.

Best practices

• Catch up on history first: import your past data via CSV before connecting real-time flows, so you have an annual baseline for comparison.
• Validate every import: always compare the number of imported rows against the number of rows in your file to spot rejections.
• Normalise your files: a consistent decimal separator and consistent units prevent most import errors.
• One source per data type: avoid feeding the same equipment via both CSV and a webhook, to prevent double counting.
• Recalculate after integration: run a calculation after an import or a burst of data to update your dashboard and your reports.

Tip: once your data is automated, generate an emissions report with AI analysis to turn this inventory into a concrete action plan.