In short
- Hedgehog has few integrations today, and a customer named more integrations as the thing to change.
- Only two or three of your data sources change often enough to justify automating.
- An integration moves data. It does not decide what the data means, which is the slow part.
An integration in a carbon platform is an automated connection to a system you already run, an accounting ledger, a fuel card portal, a utility account or a travel tool, so nobody has to export a file and upload it by hand each month. It is worth having when the same file moves every month at volume, and worth very little when a source updates once a year. Before you shortlist vendors on integration count, count your own high-frequency sources. Most companies find there are two or three, not twenty.
Since we sell one of these platforms, the honest disclosure goes at the top rather than the bottom. Hedgehog has few integrations with other software today. A paying customer named more integrations as the single thing they would change, on G2 in June 2026. If automated connections are the centre of your business case, read the rest of this page as an argument about what to test rather than as a pitch, and test us on that specific point.
What does an integration actually do, and what does it not do?
It moves data from one place to another on a schedule. That is the whole function, and it is a real saving when the file is large or frequent.
What it does not do is decide what the data means. A ledger export arrives with your own cost centre codes and supplier names. Somebody still has to say that this account maps to purchased goods category 1, that one is business travel, and this other one is a lease that should not be in the inventory at all. The mapping is done once and maintained afterwards, and it is the part that consumes the time.
So the honest description of an integration is: it removes the export and the upload, not the accounting. Vendors demonstrate the first part because it looks impressive on a screen. The second part is where your year actually goes.
Which data sources are worth connecting?
Judge each source on two axes, how often it changes and how many rows it produces. Automate the top right, upload the rest.
| Source | How often it changes | Volume | Worth automating |
|---|---|---|---|
| Accounting or ERP purchase ledger | Monthly | Thousands of lines | Yes, if the mapping is stable |
| Fleet telematics | Continuously | High | Yes, for a large fleet |
| Fuel cards | Monthly | Moderate | Marginal, a monthly export is quick |
| Travel booking system | Continuously | Moderate | Yes, if travel is material to you |
| Utility meters and bills | Monthly or quarterly | Low | No, upload is faster than the setup |
| Waste and water | Quarterly | Low | No |
| Headcount and floor area | Annually | Tiny | No |
| Supplier-specific factors | Occasionally | Tiny | No, these arrive by email anyway |
Read the table honestly against your own business and the shortlist usually shrinks to the ledger plus one operational system. That is the integration requirement worth paying for. The rest is a monthly export that takes somebody twenty minutes.
Why do integrations save less time than the demo suggests?
Three reasons, all of which show up in the second month rather than the first.
The mapping needs maintaining. New suppliers, new cost centres and new account codes appear constantly. An unmapped line is either missing from your footprint or sitting in a catch-all category that quietly distorts it.
The source data was not built for this. Finance systems record value, not mass or distance. An automated feed of spend gives you a spend-based footprint, which is a legitimate starting point and not the same thing as activity data.
Somebody still has to check it. An automated import that nobody reviews produces a very confident wrong number. The review is the same review you would do on an uploaded file.
None of this means integrations are not worth having. It means the time saving is in the mechanics, not the judgement, and your business case should be sized on the mechanics only.
What do other vendors offer, and does it matter?
Some publish specific connections and it is fair to weigh them. EcoHedge, for instance, claims native one-click integration with Xero, QuickBooks and Sage on its comparison page, read on 27 August 2026. If your books are in one of those and your footprint is mostly spend-based, that is a genuine convenience and you should factor it in.
Two cautions when you compare, both of which apply to every vendor including us.
A published logo is not a working connection for your configuration. Ask what fields come across, at what frequency, and what happens to a line the mapping does not recognise.
And an integration count is not a coverage measure. Twenty connections to systems you do not use is worth less than one to the system holding eighty percent of your emissions. We go through how to weigh this against the rest of the shortlist in choosing carbon accounting software for SMEs.
What should you ask a vendor about integrations?
Six questions, and the last two are where the answers separate.
- Which systems do you connect to natively today, in production, with customers live on them?
- What data comes across, at what granularity, and how often?
- Who maintains the mapping when our chart of accounts changes?
- What happens to an unmapped line: does it fail, get flagged, or land in a default category?
- Can we import by file for everything else, and how good is that import?
- If the integration we need does not exist, what does the manual route actually look like?
That last question is the one worth spending the demo on, because for most buyers most sources will be manual regardless of who they choose.
Where does Hedgehog stand today?
Few integrations, as stated at the top, and a bulk import route that a customer described as the challenging part of the project. A reviewer said on G2 in August 2026 that once the data is loaded everything works perfectly, and that getting it loaded is the labour. Both of those are true and both are on a public page we cannot edit.
What exists instead is a guided route through the manual work. The platform walks you through GHG Protocol setup, inventory building, data upload and reporting with an AI assistant, carries over 20,000 spend-based and activity-based factors, and lets you add your own organisation-specific or supplier-specific data. Entity management across sites with roles for data owners, auditors and managers means the upload work can be spread across the people who own the source data rather than funnelled through one coordinator, which is the other way to reduce the same cost.
One further limit while we are being direct: product footprints, LCA, EPD, MKI and PCF, are delivered as a service. The platform does organisational footprints, and no integration changes that.
What should you do first?
Take your five largest emission sources and write down, for each, how often the data changes and who currently sends it. If four of the five are annual or quarterly, integrations are not your bottleneck and you should shortlist on something else.
If your ledger genuinely is the bottleneck, say so in the first vendor email and make it a scored requirement rather than a hope. You can start a free account to see how the manual route feels with your own data, or book a meeting and ask us the six questions above directly.
Sources: Hedgehog platform, Hedgehog on G2, ecohedge.com/compare/hedgehog. Verified 27 August 2026. Vendor integration lists change often, so re-check before relying on any of them.
Facts on this page were last verified on 2026-09-17.
