Understanding Emissions Import Error Messages

When creating an assessment and selecting emissions databases to use you can import additional custom emission factor sets. There are templates you are prompted to use for this process, but you may still encounter some issues when importing if data isn’t in the appropriate format. Below are all the common scenarios where this will happen and suggested actions to fix the issue.

Invalid EF Start Date

Why am I seeing this message?

CSV error: Invalid value for column "EF Start Date"

This error appears when the date format in your file doesn't match the supported Day-Month-Year formats.

How to fix it:

  • Use one of these supported date formats:
    • DD/MM/YYYY (e.g., 01/01/2022)
    • DD-MM-YYYY (e.g., 01-01-2022)
    • DD MMM YYYY (e.g., 01 Jan 2022)
    • D MMMM YYYY (e.g., 1 January 2022)

Duplicate Entries Found

Why am I seeing this message?

Duplicate entries found

This error occurs when your file contains multiple rows with the same combination of key fields:

For Scope 1 & 2:

  • Category
  • SubCategory
  • InputUOM
  • Country
  • EFStartDate

For Scope 3:

  • Category
  • EmissionsSources
  • InputUOM
  • Country
  • OriginalSourceNames
  • EFStartDate

How to fix it:

  • Review your file for duplicate rows
  • Ensure each combination of these fields is unique
  • Combine or remove duplicate entries
  • If different values are needed for the same combination, consider creating a new unique identifier

Invalid Unit of Measure/Currencies

Why am I seeing this message?

Invalid unit of measure: [according_to_your_file]

This error appears when:

  1. The UOM spelling or case doesn't match the supported list
  1. You're using imperial units instead of metric
  1. You're using currency UOMs in an activity-based file
  1. You're using currency UOMs in a spend-based file

How to fix it:

  • Use exact spelling and case from the supported UOM list
  • Convert imperial measurements to metric
  • For Scope 3 spend-based files, use only valid currencies
    • AUD, BRL, CAD, EUR, GBP, NZD, RON, USD
  • For Scope 3 activity-based files, use only valid metric UOMs
    • Each, Employee Per Day, Frequency, GBP, GJ, Hour, Kg, Km, Litres, MJ, NZD, Person, Person per month, Pkm, RON, Room Per Night, Tkm, Tonnes, Tonnes of Crushed Grapes, Tonnes of Kills, Tonnes of Paper Product, USD, ha, kL, kWh, kg CO2-e, m, m2, m3, m3 of Milk

Inconsistent EF Source

Why am I seeing this message?

Inconsistent EF Source: [according_to_your_file]

This error occurs when your file contains multiple different Emission Factor sources. All entries in a single import must use the same EF source.

How to fix it:

  • Choose one EF source for all entries
  • Split your data into separate files if you need to use different sources
  • Ensure consistent spelling and capitalisation of the EF source

Country Not Supported

Why am I seeing this message?

Country not supported: [according_to_your_file]

This error appears when:

  1. The country name doesn't match our supported list exactly
  1. The country isn't in our database of supported countries with reliable CPI data
  1. The spelling or case doesn't match our requirements

How to fix it:

  • Use exact country names from the supported list
    • Malta, Turkey, Portugal, Greece, Indonesia, Sweden, United States, Slovakia, Latvia, United Kingdom, New Zealand, Lithuania, Croatia, Japan, Mexico, Taiwan (Province of China), Korea (Republic of), Wallis and Futuna, Netherlands, Norway, Switzerland, Brazil, Finland, Luxembourg, Italy, Estonia, Ireland, Czech Republic, Canada, Slovenia, Austria, Spain, Bulgaria, Russian Federation, South Africa, Hungary, Cyprus, Global, Romania, Belgium, Australia, France, Poland, Denmark, Germany, China, India
  • Check for proper case sensitivity (e.g., "New Zealand" not "NEW ZEALAND")
  • Replace unsupported countries with the closest supported alternative
  • For global factors, use "Global" as the country

Invalid Categories

Why am I seeing this message?

Category not supported: [according_to_your_file]

This error appears when category names don't exactly match the required format (case sensitive).

How to fix it:

  • Use the exact category names from the supported list:
    • Scope 1: Mobile Combustion, Stationary Combustion, Fugitive Emissions, Process Emissions
    • Scope 2: Electricity, Steam and Heat
    • Scope 3: Purchased Goods and Services, Capital Goods, Upstream Transportation and Distribution, Waste Generated in Operations, Business Travel, Employee Commuting, Upstream Leased Assets, Downstream Transportation and Distribution, Processing of Sold Products, Use of Sold Products, End-of-Life Treatment of Sold Products, Downstream Leased Assets, Franchises, Investments, Fuel and Energy Related Activities
  • Check for proper case sensitivity (e.g., "Capital Goods, not "capital goods")

Invalid value

Why am I seeing this message?

CSV error: Invalid value for column "Emission factor"

This error occurs when:

  • Emission factors contain invalid characters or formats
  • Numbers are formatted incorrectly

How to fix it:

  • Ensure emission factors are valid numbers
  • Remove any special characters or text from 'Emission Factor' field

Missing Columns

Why am I seeing this message?

CSV error: Missing column [according_to_your_file]

This error appears when mandatory columns are missing from your CSV file.

How to fix it:

  • Ensure all required columns are present:
    • For Scope 1 & 2:
      • Category*
      • SubCategory*
      • Input UOM*
      • Emission factor*
      • EF Start Date*
      • EF Source*
      • Country*
    • For Scope 3:
      • Category*
      • Emissions Sources*
      • Original Source Names*
      • Input UOM*
      • Emission Factor (kg CO2e)*
      • EF Start Date*
      • EF Source*
      • Country*
  • Use the correct template available on the Import screens

Empty File

Why am I seeing this message?

CSV error: Empty file

This occurs when uploading a file that contains no data at all.

Common Causes:

  • Accidentally uploading a blank file
  • File corruption during save/transfer
  • File creation errors
  • Incorrect file export
  • Hidden formatting issues

How to fix it:

  1. Open the file and verify the content
  1. Re-export data from source
  1. Ensure file contains:
      • Header row with required columns
      • At least one row of data
      • Proper CSV formatting
Did this answer your question?
😞
😐
🀩