Data → CO2 transfers records the CO2 that a Scope 1 source captured and sent out of the site in a month instead of emitting it.
Record a transfer
- Choose Record transfer, then the Asset and the Scope 1 Source whose CO2 was captured (for example the amine unit or the flare).
- Enter the Month and the Quantity with its Unit:
- a mass (t or kg) is CO2 mass;
- a gas volume (Sm3, Nm3, scf …) also needs the CO2 mole fraction of the gas (0.95 for 95 mol%). Leave the reference temperature and pressure empty to use the asset’s reference conditions.
- Choose the Destination type (geological storage, enhanced oil or gas recovery, utilisation, another installation or other) and name the destination. When the receiving site is one of your assets, choose it as Receiving asset.
- Give a Reference (meter, delivery note or permit) and attach the document with Evidence.
Several transfers per source and month are allowed, for example to two destinations. A locked month cannot be changed, as for any other activity data.
How it is calculated
The calculation adds the month’s transfers to the source as CO2 transferred (method CO2_TRANSFER_V1): the mass as entered, or volume ÷ molar volume at the reference conditions × CO2 mole fraction × 44.009 kg/kmol. When the source has no result for the month (for example missing activity data), the transfer is not recorded and the calculation run lists the warning W-TRANSFER-NOT-WRITTEN.
Where it appears
- Totals, dashboards, targets, budgets and regulatory checks stay gross: transferred CO2 is never subtracted from them.
- The analytics totals, the GHG inventory report, the GHG tables and the disclosure tables show CO2 captured and transferred and net Scope 1 (gross minus transferred) beside gross Scope 1.
- Whether a programme lets you deduct transferred CO2, and for which destinations, depends on its rules.
- A CCUS project in Decarbonisation compares its planned annual abatement with the CO2 its asset actually transferred each year.
See Decarbonisation and Evidence files.