Three illustrative airline-office staff review route maps and aviation graphics beside an airport window
A synthetic airline-office scene illustrates evidence review, not a real operator or a compliance finding.
Diagram text description

Three people look at two screens and paper maps in an airport-side office; an aeroplane and control tower appear outside. The synthetic scene does not prove actual route coverage, unit eligibility, measured emissions or operator compliance.

CORSIA carbon credits are useful to an airline only when the particular emissions units meet the applicable scheme conditions and their cancellation is evidenced for the intended use. A recognised programme name or a quoted price cannot establish that result. Begin with the operator, its attributed State and the compliance period, then connect the offered lot to the current eligibility scope.

Three questions must stay separate: what obligation the operator has, whether the units qualify, and whether the required cancellation and reporting have occurred. Confusing them can leave a buyer with genuine credits but an unresolved compliance file. An ordinary company buying voluntary credits or staff travel is not thereby meeting an airline's CORSIA obligation.

This guide follows those distinctions from route coverage through procurement and cancellation evidence. It focuses on the 2024–2026 first phase while explaining why phase, reporting year and unit vintage must not be exchanged. It provides a review framework, not approval of a named project, lot or operator.

What is CORSIA and who has an obligation?

CORSIA is the Carbon Offsetting and Reduction Scheme for International Aviation. It addresses covered international aviation CO₂ through an aviation-specific framework. It is not a general requirement for every company to buy carbon credits, nor a certificate that makes an airline's entire environmental impact disappear. Domestic aviation is outside CORSIA's international-flight scope.

Keep the responsibilities separate:

  • ICAO: establishes the scheme framework and, through Council decisions, the eligible emissions-unit programme and unit scopes. It does not turn a seller's marketing description into a finding about a particular offered lot.
  • Attributed State: administers the relevant operator requirements and calculates the operator's final offsetting requirement under the scheme. The operator needs to know which State is responsible for its case.
  • Aeroplane operator: maintains the applicable emissions evidence, obtains the necessary verification, addresses its requirement with eligible units and reports the cancellation evidence.
  • Supplier or intermediary: offers and delivers units under a commercial arrangement. A supplier can provide documents, but cannot replace the applicable ICAO eligibility conditions or the operator's State process with a sales assurance.

The buyer's identity therefore matters. An airline procurement team acting for a covered operator faces a different task from a manufacturer buying voluntary credits or arranging staff travel. The latter does not become a CORSIA operator through that purchase. Establish the responsible entity and the intended use before assessing any offer described as “CORSIA carbon credits”. This prevents a technically valid description of a programme from being used to justify the wrong buyer claim.

Which flights and phases are covered?

CORSIA offsetting coverage is route-based. Under that approach, a route between two participating States is covered for offsetting; if one or both do not participate, the route is not covered for that purpose. Use the participation information applicable to the relevant year, not an old route list or the airline's country of registration alone.

Scheme phaseYearsParticipation distinction
Pilot2021–2023State participation in offsetting was voluntary.
First2024–2026State participation in offsetting remains voluntary.
Second2027–2035Participation follows the scheme's criteria and exemptions, with voluntary participation also possible.

Table 1, shown one row at a time. Every field is retained.

Row 1

Scheme phase
Pilot
Years
2021–2023
Participation distinction
State participation in offsetting was voluntary.

Row 2

Scheme phase
First
Years
2024–2026
Participation distinction
State participation in offsetting remains voluntary.

Row 3

Scheme phase
Second
Years
2027–2035
Participation distinction
Participation follows the scheme's criteria and exemptions, with voluntary participation also possible.

A phase and a compliance period are related but are not always the same length. The second phase contains separate three-year compliance periods; an approval for 2027–2029 is not automatically approval for every later year through 2035. Match the procurement purpose to the precise period for which units may be used.

Route coverage can change as State participation changes. An operator from a non-participating State can still fly between two participating States and have offsetting exposure on that route. Conversely, belonging to an airline based in a participating State does not mean every international flight has the same offsetting treatment.

These route statements do not remove the need to assess operator and flight exemptions or national implementation. They also do not settle monitoring and reporting: an offsetting-exempt route can still carry reporting requirements. The practical output is a year-specific coverage assessment connected to the operator, not a blanket “international flights are covered” label.

Is reporting the same as offsetting?

Monitoring, reporting and verification, often shortened to MRV, establish an emissions record. They are distinct from determining how many units must be cancelled and proving that the cancellation occurred. An emissions report can be complete without an invoice proving anything about units, and a purchase invoice cannot repair missing flight or fuel data.

The emissions trail begins with the applicable monitoring arrangements, flight and fuel information, estimates where permitted, and verification of the reported emissions. It supports the data used in the scheme's process. Whether a flight attracts an offsetting requirement is a separate coverage question; not being subject to offsetting does not by itself eliminate reporting duties.

The unit trail identifies the eligible units used to address the final requirement, their cancellation and the associated verified reporting. It answers a different question: which units were permanently removed for the relevant use? The parallel illustration separates those trails rather than showing one as a replacement for the other.

Verified emissions reporting and verified unit-cancellation reporting establish different facts; neither substitutes for the other.
Verified emissions reporting and verified unit-cancellation reporting establish different facts; neither substitutes for the other.
Diagram text description

Two parallel evidence paths connect fuel and flight records to a verified Emissions Report, and cancelled eligible units to a verified Emissions Unit Cancellation Report. The paths do not depict a complete compliance approval or imply that an invoice establishes cancellation.

For a reporting team, the operational consequence is ownership of both evidence sets. Flight-data staff may hold the emissions basis while procurement or a registry account administrator holds the unit records. Connect them through the operator and compliance period, but retain their different meanings. A single folder marked “carbon compliant” obscures which fact each document actually establishes. Missing evidence should be identified by its role, not covered with an unrelated report bearing a verification label.

How is an airline offsetting requirement determined?

The attributed State determines the operator's requirement using the applicable CORSIA rules and verified information. During 2024–2026, the allocation approach is sectoral: the relevant sector growth factor is applied to the operator's annual emissions covered by offsetting. This is not a universal formula that a passenger or ordinary company can apply to a ticket, a total travel footprint or all of an airline's activities.

Annual offsetting requirements are brought together for the compliance period. The State also accounts for eligible, verified reductions claimed from CORSIA Eligible Fuels when determining the total final requirement. Fuel claims have their own eligibility and evidence framework; an ordinary fuel purchase or an unsupported sustainable-fuel label is not automatically such a reduction.

Procurement forecasts can help an operator prepare, but a forecast should remain labelled as a forecast. Reconcile it with the State-determined final quantity for the period. Otherwise a buyer may purchase against an estimate without knowing whether later changes arise from coverage, verified emissions, the applicable growth factor or accepted eligible-fuel claims.

An operator can acquire and cancel eligible units before receiving its final notification; it need not treat notification as permission to start every purchase. Early action nevertheless leaves a reconciliation task. The evidence must ultimately show that the eligible quantity cancelled addresses the actual final requirement, with any remaining shortfall or discrepancy resolved through the applicable process. An early contract does not freeze the regulatory calculation.

What counts as a CORSIA-eligible emissions unit?

As checked on 30 October 2026, ICAO's eligible-units page identifies the April 2026 document as its current edition. Start with the detailed section for the intended compliance period, then read the programme entry, scope and footnotes. The accompanying summary table is informational: its short programme listing does not reproduce every condition.

CheckEvidence to matchReason to pause
Compliance periodThe entry permitting use for the intended periodApproval cited for a different period
Programme and unit typeThe named programme and exact eligible unit classA programme badge without the offered unit class
Activity datesThe project's first crediting-period startA project date that cannot be reconciled with the scope
Reduction vintageWhen the credited reductions or removals occurredAn issuance date presented as the only date test
Scope exclusionsActivity, methodology and any applicable exceptions or thresholdsAn excluded activity or an unexplained exception
Host-Party conditionsRequired authorization and double-claim evidenceA generic letter with no connection to the lot
Registry and identityDesignated registry, applicable registry conditions and serialsUnits or cancellation route that cannot be traced

Table 2, shown one row at a time. Every field is retained.

Row 1

Check
Compliance period
Evidence to match
The entry permitting use for the intended period
Reason to pause
Approval cited for a different period

Row 2

Check
Programme and unit type
Evidence to match
The named programme and exact eligible unit class
Reason to pause
A programme badge without the offered unit class

Row 3

Check
Activity dates
Evidence to match
The project's first crediting-period start
Reason to pause
A project date that cannot be reconciled with the scope

Row 4

Check
Reduction vintage
Evidence to match
When the credited reductions or removals occurred
Reason to pause
An issuance date presented as the only date test

Row 5

Check
Scope exclusions
Evidence to match
Activity, methodology and any applicable exceptions or thresholds
Reason to pause
An excluded activity or an unexplained exception

Row 6

Check
Host-Party conditions
Evidence to match
Required authorization and double-claim evidence
Reason to pause
A generic letter with no connection to the lot

Row 7

Check
Registry and identity
Evidence to match
Designated registry, applicable registry conditions and serials
Reason to pause
Units or cancellation route that cannot be traced

For the 2024–2026 entries reviewed, the date conditions include activities beginning their first crediting period from 1 January 2016 and reductions occurring from 1 January 2021 through 31 December 2026. These are different tests. They do not establish that every unit inside the date window qualifies, or that all future output within that window has already been issued.

Read the host-country and double-claim provisions for the actual programme. Some scopes require programme verification of corresponding adjustments or an approved guarantee arrangement in addition to authorization. Do not transfer one programme's alternatives to another. Also inspect the designated-registry conditions and any outstanding registry-attestation notes. If a live ICAO note and an older downloaded document identify different cancellation arrangements, resolve the discrepancy with the relevant programme and State before acting; do not guess a destination.

Why is an approved programme name not enough?

Programme approval describes the assessed scope, not an unrestricted promise about every credit issued under that brand. The detailed document can distinguish compliance periods, dates, activity types, methodologies and other conditions within the same programme. “Issued by an approved programme” therefore answers only part of the procurement question.

Imagine two offers citing the same programme. One has a traceable project, the required dates, an applicable methodology and documented host-country conditions. The other supplies a programme logo but cannot explain an exclusion or connect authorization to the proposed units. The second offer has an unresolved evidential problem even though the programme name matches. The illustration shows these hypothetical states; it does not approve either real project or certify a lot.

One programme-level assessment does not settle the evidence for every offered lot; these two lot states are hypothetical.
One programme-level assessment does not settle the evidence for every offered lot; these two lot states are hypothetical.
Diagram text description

A programme-level assessment branches to illustrative lot A, whose conditions are evidenced, and lot B, whose conditions remain unresolved. The diagram is not a real unit eligibility finding and does not grant supplier approval authority.

Conditional eligibility also needs to be read as conditional. A pending programme action is not a completed condition, and a statement that approval is expected cannot be treated as current eligibility. Separate the supplier's prediction from the status evidenced by the applicable ICAO material.

Keep the assessment at the offered-lot level. If the supplier substitutes another project, methodology, vintage or unit type, repeat the checks affected by that substitution. A contract covering the same headline quantity and programme can still deliver a materially different eligibility position. The useful question is whether the delivered serials meet the required scope, not whether their marketing label looks familiar.

What should a buyer verify before contracting?

Define what the contract must deliver before negotiating only price. A purchase specification should connect an operator's intended compliance period to identifiable units and an achievable cancellation process. It is prudent procurement guidance, not a replacement for the operator's legal or regulatory advice.

  1. Establish the buyer, attributed State, compliance period and quantity basis. Distinguish a planning estimate from the final requirement and state how reconciliation will occur.
  2. Define the proposed lot: programme, unit type, project or activity identifier, methodology, vintage, quantity and registry. If serials are not yet available, make that limitation and the later identification step explicit.
  3. Match the applicable ICAO scope and conditions to that lot, including exclusions, authorization and registry arrangements. Identify which evidence is already available and which remains a condition of delivery.
  4. Assign responsibility for transfer, cancellation and production of the required records. Clarify whether the supplier acts on the operator's behalf or merely transfers units to an account.
  5. Agree how non-conforming delivery, missing evidence and substitutions will be addressed. Any replacement still needs the relevant eligibility assessment; a replacement promise is not the assessment itself.

Do not present a forward-delivery contract as a completed cancellation. A supplier can promise future units while issuance, documentation or transfer remains outstanding. Retain those dependencies in the purchase file so commercial certainty is not confused with registry status or compliance evidence. The same discipline applies when an intermediary aggregates units from several underlying activities.

What changes when an eligible unit is cancelled?

Cancellation permanently removes a unit for a single use; holding a unit keeps it available rather than demonstrating that use. An offer, a purchase and an account balance establish different things from a cancellation entry. Follow the unit identity through the relevant registry records, not merely through the amount paid.

The status sequence is conceptual. A commercial offer may lead to acquisition and holding, but the final transition requires an actual cancellation action and evidence of it. The arrows do not mean that a purchase automatically cancels units or that a cancelled unit is automatically acceptable for the operator's intended CORSIA period.

Offered, acquired, held and cancelled are distinct states; reaching cancellation requires an evidenced registry action.
Offered, acquired, held and cancelled are distinct states; reaching cancellation requires an evidenced registry action.
Diagram text description

A conceptual sequence separates a commercial offer, acquisition, holding and cancellation for single use. Each transition requires its own action or evidence. The arrows do not promise that purchase automatically cancels units or that cancellation alone proves CORSIA eligibility.

Eligibility and cancellation must both be demonstrated. Cancelling a unit outside the applicable scope does not turn it into an eligible one. Conversely, a fully eligible unit still being held does not prove cancellation. A cancellation made for a different stated purpose or beneficiary must not be casually relabelled to satisfy another use.

When reconciling a completed action, retain its date, quantity, identifying serial range, programme-designated registry and the use it records. Link those facts to the operator and period, then to the verified cancellation reporting. A screenshot without enough identity to recover the record is weaker evidence than the traceable registry trail it should represent.

How does the 2024–2026 first phase baseline work?

For the first phase, 2024–2026, the reference is sectoral: 85% of the CO₂ emissions covered by CORSIA in 2019. ICAO's current explanation applies that reference to the first and second phases, 2024–2035. It is not a universal baseline of 85% of every company's emissions, every airline's entire footprint or the emissions of a particular passenger's journey.

Coverage is part of the reference's meaning. ICAO recalculates the sectoral baseline when the routes included in CORSIA change, reflecting State participation. The current-year covered population and the corresponding covered 2019 reference must therefore be treated consistently. Mixing all international emissions with a differently scoped baseline would not reproduce the scheme calculation.

The sector growth factor is also not an ordinary percentage-growth headline. The scheme defines it using the applicable covered emissions and reference, and the State applies the relevant calculation to the operator's covered emissions. Use the published factor and State process rather than estimating an obligation from a news article saying aviation has grown since 2019.

This explains a potentially surprising outcome: an operator's own efficiency improvement does not alone establish that it has no offsetting requirement under a sectoral allocation approach. Its emissions still affect the calculation, but the shared sectoral factor matters too. Keep operational progress, the regulatory calculation and unit cancellation as separate statements. This guide does not calculate a real operator's requirement or replace its State's determination.

What records prove a compliant cancellation?

A cancellation file needs to connect the regulatory quantity with the units actually used. Retain enough evidence for someone other than the buyer to reconcile that connection and identify a mismatch. A large volume of correspondence is not a substitute for the few records that establish the essential facts.

  • Requirement: operator identity, attributed State, compliance period and final quantity, with the relevant notification or calculation record and treatment of accepted eligible-fuel claims.
  • Eligibility: the applicable ICAO document and programme scope, the assessment date, unit-date evidence, activity and methodology checks, exclusions and required host-country documentation.
  • Identity and action: programme-designated registry, project identifier, unit type, quantity, serial information, cancellation date and the recorded purpose or beneficiary as applicable.
  • Reporting and verification: the Emissions Unit Cancellation Report and associated Verification Report, together with the submission trail required by the attributed State.

Check totals and identities together. A cancellation receipt matching the required quantity can still concern the wrong vintage or purpose; a suitable lot can still leave a quantity shortfall. Keep separate lots separately identifiable even if a final reconciliation sums them.

ICAO describes submission of verified cancellation reporting to the State. A supplier's voluntary retirement certificate is not automatically the same document or process. Obtain the current State instructions and retain the submission evidence. The file should show what was done, what it was intended to satisfy and how that conclusion was verified, without relying on an internal label such as “finished”.

What should a non-airline business take from CORSIA?

A non-airline business can learn from CORSIA's evidence discipline without adopting its compliance claim. A company purchasing staff flights has a business-travel accounting question. A company purchasing voluntary credits has a separate credit-use and claims question. Neither transaction alone makes the company an aeroplane operator with a CORSIA obligation.

Do not assume that an airline's cancellation gives the passenger's employer the same units to use again. A single-use cancellation cannot simply be shared as another organisation's independent credit retirement. Ask precisely what an airline or travel supplier's environmental statement covers, and distinguish a statement about the operator's regulatory compliance from one about a customer's own inventory or voluntary action.

The transferable practice is to define the user, purpose, boundary and evidence before accepting a carbon claim. Programme status, unit identity and cancellation records can be useful information, but a CORSIA-eligible label does not automatically satisfy every voluntary claims framework or settle a company's Scope 3 reporting treatment.

Use wording proportionate to the action evidenced. A traveller's company should not say it has met an airline compliance requirement simply because it bought a credit described as CORSIA eligible. That would confuse the characteristics of a unit with the legal identity and reporting responsibilities of the person using it.

CORSIA carbon-credit buyer checklist

Use the checklist at the point where a procurement decision becomes an action. It joins the evidence already developed; it does not create eligibility or a State approval. Name an owner for an unresolved answer so that the process has an explicit hold point rather than a silent assumption.

  1. Confirm the obligation: match the operator, attributed State, precise compliance period and quantity basis. Reconcile a forecast to the final requirement when available.
  2. Confirm the scope: identify the current applicable ICAO entry and footnotes for the programme, unit type, activity, dates, exclusions and host-country conditions. Preserve the version used.
  3. Confirm the lot: connect those conditions to actual project and registry identifiers and the delivered serials. Reassess an allowed substitution instead of inheriting the previous lot's conclusion.
  4. Confirm the action: establish who will cancel, through which designated registry and for what recorded use. A holding statement or purchase invoice does not close this step.
  5. Confirm the reconciliation: join the eligible cancelled quantity to the State requirement and retain the verified cancellation report, associated verification and required submission trail.

Stop when a material identity, eligibility or cancellation condition cannot be supported. Do not compensate for it with a lower price, a recognised programme name or an unrelated verification report. When the gap is resolved, the evidence should explain why the hold changed, allowing the same decision to be understood later without reconstructing the sales conversation.

Keep the evidence trail distinct from an eligibility decision

A useful carbon-data record keeps the source, applicable boundary, decision and responsible person connected. That organisation helps a colleague understand what a figure or unit claim means; it does not itself make a unit CORSIA eligible, issue credits, certify an airline or replace the attributed State's process. No document-management tool should be assumed to perform those roles merely because it stores the evidence.

For the airline buyer, the conclusion is specific: establish the correct requirement, match the delivered lot to the applicable ICAO scope, and retain the cancellation and verified reporting trail. For a non-airline business, preserve the boundary between its own action and the operator's compliance. The same unit should not be presented as independently used twice.

Take one actual proposed lot and ask whether its identity can be followed from the offer to the applicable scope and eventual registry action. If one connection is missing, name the missing evidence and hold that conclusion open. A traceable unresolved question is safer and more useful than a broad compliance label that the records cannot support.