> ## Documentation Index
> Fetch the complete documentation index at: https://docs.isometric.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GHG Entries

> Create GHG entries containing all CO₂e fluxes from project operation plus allocated project establishment and end-of-life emissions

GHG entries contain all CO₂e fluxes incurred in project operation, as specified by the schema in the project's [LCA builder](/user-guides/certify/lca), as well as an allocated portion of the [project establishment and end-of-life emissions](/user-guides/certify/project-emissions).
GHG entries are verified once submitted in a [GHG Statement](/user-guides/certify/ghg-statement).

## GHG entry definition

There are no fixed requirements for how you define the boundaries of a GHG entry, however all project flux data (sequestrations, losses, counterfactuals, activities and reductions) must be allocated to a GHG entry to be accounted for.

<Tip>
  Examples:

  * A CDR process with a product injection stage might report data per injection
  * A continuous process might report daily or weekly totals as individual GHG entries
  * A project with multiple sequestration sites might separate GHG entries geographically and temporally
</Tip>

A GHG statement can contain multiple GHG entries: data across all GHG entries will be provided to a verifier once the statement is submitted.

## Create a GHG entry

Draft GHG entries are shown in the GHG entries section of Certify. If a GHG entry has been allocated to a draft [GHG statement](/user-guides/certify/ghg-statement) it will also be visible there.

GHG entries that are part of verified GHG statements are not shown in the GHG entries section and should be accessed via the relevant verified GHG statement.

To create a new GHG entry:

<Steps>
  <Step title="Add a GHG entry">
    In an existing [GHG Statement](/user-guides/certify/ghg-statement), or in the **GHG Entries** section of your project on Certify, click the **Add GHG entry** button.

    <Tip>
      GHG entries can be created before or after GHG statements.
      We recommend that non-API users create [GHG statements](/user-guides/certify/ghg-statement) first as this ensures that [Project emissions](/user-guides/certify/project-emissions) are calculated and shown on any included GHG entries.
    </Tip>
  </Step>

  <Step title="Load template ">
    Select a [template](/user-guides/certify/lca#verification-and-templating) to pre-populate the GHG entry with the components, fixed inputs (such as emission factors) and component descriptions required for calculations.
  </Step>

  <Step title="Set reporting period">
    Provide a start and end date for your GHG entry.
  </Step>

  <Step title="Edit components">
    If your specific GHG entry doesn't match your regular template schema, you can add, delete or update components as needed to match your reporting requirements.

    <Info>
      If a component is accounted for over multiple GHG entries, an [attribution factor](/user-guides/certify/attribution) can be assigned accordingly. For example, if a single transport leg transported feedstock for two production batches, an attribution factor of `0.5` can be assigned to the component on each GHG entry.
    </Info>
  </Step>

  <Step title="Enter input values">
    For each datapoint input, add measurements relevant to your current reporting period.

    If multiple units (e.g. `kg` and `tonnes`) are supported for the given input, you can select your preferred unit from the dropdown.
  </Step>

  <Step title="Define measurement uncertainty">
    Where there is material uncertainty for the value of a given input, the standard deviation for the measurement should be entered in the **+/-** column. This could be due to:

    * Known uncertainty for a measurement device
    * Use of values from a probability distribution with a known variance
  </Step>

  <Step title="Upload sources">
    Measurements should be evidenced with source files. These may include:

    * Documentation such as bills of landing
    * Spreadsheets containing data behind aggregate calculations
    * Scientific citations for use of given approaches or emission factors
  </Step>
</Steps>

The net CO₂e result is recalculated and the GHG entry is saved automatically each time an input is updated.

## API users

GHG entries can also be automated via API integration. Prefer the [Post GHG Entry](/api-reference/certify/post-ghg-entry) endpoint reference and the [Creating Your First GHG Entry](/api-reference/certify/your-first-ghg-entry) tutorial when building a new integration.

<Info>
  The older `removal*` and `removal_template*` API endpoints remain available as deprecated
  compatibility aliases while existing integrations migrate.
</Info>

<Tip>
  If creating GHG entries via an API integration, the GHG entry template schema can
  be queried from [GET GHG entry templates](/api-reference/certify/get-ghg-entry-templates)
  or set in the API request, allowing you to define your LCA structure in your
  local stack or via an MRV partner platform.
</Tip>