When Do Carbon Credits Expire? Vintage, Registry and Claim Rules
The inspected synthetic still life shows a cream card with a circular landscape motif, blank lines and a leaf, translucent grid sheets, a closed green folder and pen, a plant and a water glass by a window. No readable calendar year, serial, price, programme endorsement or named customer is present. The image cannot establish unit validity, availability, claim eligibility or any real deadline.
Diagram text description
When do carbon credits expire? There is no single expiry clock for every voluntary carbon credit. A programme may leave an issued unit active without a calendar limit, while retirement, cancellation, a registry transition or a buyer's claim rules can still prevent a particular use. An old vintage is neither automatic invalidity nor permission to use a credit indefinitely for any purpose.
The useful question is narrower: can these identified units support this proposed statement now? Answering it requires the programme and unit type, their current registry state, and the rules for the intended claim. A recent purchase date cannot substitute for any of those checks.
This guide separates the dates that are often collapsed into “expiry”, explains real programme and transition examples, and works through a unit-specific decision. It distinguishes buying, holding and retiring units from reporting a completed use. The aim is a reasoned proceed, hold or unsuitable decision—not an invented expiry year, a promise of financial value or a guarantee that a public claim will be accepted.
Five dates and states that people call expiry
Start by identifying which date or state the speaker means. Five concepts govern different parts of the decision, even when the seller summarises all of them with one year on a quotation.
| Concept | What it describes | What it does not establish |
|---|---|---|
| Vintage | Period of the credited reduction or removal, as the programme defines it | Date the buyer paid or the programme issued units |
| Issuance | Creation of the specified units under the programme | A newer vintage or automatic permission for every claim |
| Retirement | Permanent removal from further circulation for a recorded use | A fresh unit available for resale or another incompatible use |
| Programme-unit lifespan | Any programme rule limiting how long the unit can remain usable | Every external buyer's acceptance criteria |
| Intended claim period | Period and purpose to which the company wants to relate its use | Proof that the required retirement has happened |
Table 1, shown one row at a time. Every field is retained.
Row 1
- Concept
- Vintage
- What it describes
- Period of the credited reduction or removal, as the programme defines it
- What it does not establish
- Date the buyer paid or the programme issued units
Row 2
- Concept
- Issuance
- What it describes
- Creation of the specified units under the programme
- What it does not establish
- A newer vintage or automatic permission for every claim
Row 3
- Concept
- Retirement
- What it describes
- Permanent removal from further circulation for a recorded use
- What it does not establish
- A fresh unit available for resale or another incompatible use
Row 4
- Concept
- Programme-unit lifespan
- What it describes
- Any programme rule limiting how long the unit can remain usable
- What it does not establish
- Every external buyer's acceptance criteria
Row 5
- Concept
- Intended claim period
- What it describes
- Period and purpose to which the company wants to relate its use
- What it does not establish
- Proof that the required retirement has happened
Purchase adds another event: the agreement or payment for units. A forward purchase can even precede issuance. Buying an older vintage today does not change when its underlying outcome occurred. Likewise, a recently issued batch may concern earlier monitored activity. A project crediting period belongs on a separate track: it governs eligible project generation, not simply the age of a buyer's units.
For example, imagine an expressly fictional batch with a 2021 vintage, issued in 2024 and offered to a buyer in 2026. None of those dates alone says whether it can serve the buyer's proposed 2025-period statement. A framework might restrict vintage; the registry might already show retirement; or the offer might remain incomplete. Calling it a “2026 credit” because the quotation is new hides the question the buyer needs answered.
A monitoring period can also cross calendar boundaries. Preserve the programme's actual vintage or period notation rather than choose whichever year makes a purchase fit. If one quote combines several vintages, keep the ranges distinguishable. A single project name and average year are not substitutes for batch identity. This simple separation prevents later colleagues from treating an invoice date as the date of mitigation or a planned retirement as a completed event.
Does the crediting programme impose a lifespan?
A programme's own statement can settle a specific lifespan question without settling the whole purchase. Climate Action Reserve says its Climate Reserve Tonnes, or CRTs, do not expire. Its FAQ separately describes permanent retirement. That is a useful bounded counterexample to claims that every voluntary credit must disappear after a fixed number of years; it is not a statement about every unit issued by every other programme.
For example, suppose a fictional buyer is offered an older CRT batch and receives the Reserve's non-expiry statement. The buyer can stop inventing a calendar cutoff merely from age. It cannot conclude that the units are still in the seller's control, have not been retired, meet a certification's vintage rules or satisfy its own quality criteria. Those are distinct propositions that require different evidence. The statement removes one assumed obstacle, not every remaining condition.
Define the object carefully before applying the rule. Is the offer actually for issued CRTs, an expected future delivery, another programme's units, or a derivative contractual product? A seller's use of the word “Reserve” in a project description does not identify the offered instrument. The Reserve's FAQ distinguishes verified ex-post CRT issuance from future-looking alternatives. The operational lesson is to identify what exists now rather than treat a forecast as stock with an unusually long shelf life.
There is a useful difference between “no automatic programme expiry identified” and “approved for our use”. The former records a rule finding. The latter requires the rest of the review. Keep them separate in a purchase recommendation so that a later change of claim does not inherit an approval it never received. Do not turn the absence of a programme countdown into a guarantee of resale price, future demand or permanent suitability under policies that other organisations control.
The registry status can end a unit’s availability
Availability is a current fact about identified units, not a conclusion drawn from an old certificate. Read the registry's own labels and transaction history; terminology and consequences are programme-specific. In particular, a transfer is an event that may change the holder without consuming the unit. It should not be grouped automatically with retirement and cancellation.
| Observed record | What the buyer can investigate | What must not be assumed |
|---|---|---|
| Issued and active | Current availability and authority to deliver the specified serials | Active means suitable for every claim |
| Transfer recorded | Where the units moved and whether delivery was completed | Transfer itself means the units were retired |
| Retired for a recorded use | Beneficiary, purpose, quantity and completed event | A downloadable record is reusable stock |
| Cancelled or administratively cancelled | Programme reason and affected serials | Every cancellation is a successful voluntary claim |
| Pending, restricted or unclear | Exact meaning of the label and unresolved action | Silence means unrestricted availability |
Table 2, shown one row at a time. Every field is retained.
Row 1
- Observed record
- Issued and active
- What the buyer can investigate
- Current availability and authority to deliver the specified serials
- What must not be assumed
- Active means suitable for every claim
Row 2
- Observed record
- Transfer recorded
- What the buyer can investigate
- Where the units moved and whether delivery was completed
- What must not be assumed
- Transfer itself means the units were retired
Row 3
- Observed record
- Retired for a recorded use
- What the buyer can investigate
- Beneficiary, purpose, quantity and completed event
- What must not be assumed
- A downloadable record is reusable stock
Row 4
- Observed record
- Cancelled or administratively cancelled
- What the buyer can investigate
- Programme reason and affected serials
- What must not be assumed
- Every cancellation is a successful voluntary claim
Row 5
- Observed record
- Pending, restricted or unclear
- What the buyer can investigate
- Exact meaning of the label and unresolved action
- What must not be assumed
- Silence means unrestricted availability
The public view may not prove everything about ownership. The Reserve explains that a project issuance report does not show the current project balance, while serial searches can show active or retired status; some account information is not public. A buyer therefore needs a link between public unit evidence and the seller's contractual or account authority, not a claim that every registry exposes a complete ownership ledger. Where information is limited, ask for the appropriate account-holder confirmation rather than invent it.
Consider a fictional offer assembled from two serial ranges within one project. One range is active; another has been retired. A screenshot showing the project's original total would conceal that difference. The response is not to label the whole project expired or accept the whole offer as available. Separate the ranges, reconcile the offered quantities, and investigate only the relevant remaining stock. If the seller substitutes another range, its status cannot be borrowed from the original lookup.
A quotation can also precede delivery. The seller may intend to source eligible units later, or retire them directly for the customer instead of transferring them. State that delivery model plainly. A commitment to deliver is different from a completed transfer, and a promise to retire is different from evidence of retirement. The review should identify which event is still outstanding and who controls it.
Recheck time-sensitive status at the action point. Evidence captured at quotation supports the quotation-stage assessment, not a fiction that no later transaction could occur. This is why a dated status observation belongs beside the exact serial range, with delivery and use conditions retained separately.
A project crediting period is not an issued-unit expiry date
A project crediting period and the usability of its existing stock answer different questions. The first concerns the periods for which the project can generate eligible outcomes under its governing rules. Renewal, method changes or a stop in generation can affect future supply. None should be translated automatically into deletion of an already-issued serial.
| Track | Decision governed | Evidence needed |
|---|---|---|
| Project generation | Can activity in this period generate additional units? | Applicable method, crediting-period conditions and any renewal or transition decision |
| Existing issued unit | Can this identified unit still be held or used for the proposed purpose? | Current serial status, unit-specific notices and intended-use rules |
Table 3, shown one row at a time. Every field is retained.
Row 1
- Track
- Project generation
- Decision governed
- Can activity in this period generate additional units?
- Evidence needed
- Applicable method, crediting-period conditions and any renewal or transition decision
Row 2
- Track
- Existing issued unit
- Decision governed
- Can this identified unit still be held or used for the proposed purpose?
- Evidence needed
- Current serial status, unit-specific notices and intended-use rules
Imagine a fictional project whose authorised generation window ends after outcomes from Year 10. A unit already issued for Year 4 does not vanish solely because the project reaches Year 11. Conversely, a valid future-generation window does not make an unissued Year 11 forecast into current inventory. The two directions of inference are equally unreliable. An actual programme rule could affect historical units, but that effect must be found in the rule or notice, not guessed from the window's end.
This distinction also changes contract questions. A buyer of existing issued units needs evidence about those units. A buyer contracting for later delivery needs to understand renewal dependence and what happens if future issuance is not permitted or arrives late. A supplier cannot resolve the second risk by pointing to older units unless substitution is allowed and the replacement stock also fits the buyer's requirements. Neither contract should blur a forecast with a completed issuance.
Where a project moves between programmes, preserve the method and programme that governed the offered batch. The Reserve's FAQ expressly distinguishes future registration elsewhere from previously issued CRTs remaining in its system. Do not infer that a new project registration retrospectively relabels earlier stock. The relevant file may need both the old issuance record and the later project decision, but those documents have different jobs.
A buyer framework may restrict vintage
An active unit can sit inside a programme's inventory and outside a particular buyer's permitted use. The diagram shows that containment: both branches remain active issued units, but only one matches the named use rules. Being a candidate for retirement is not yet proof of a completed or acceptable public claim. Ownership, quality and the required action still matter.
An enclosure labelled Active issued units contains two branches. Fits named use rules points to Candidate for retirement; Fails named use rules points to Not for this claim. The figure separates current programme availability from suitability for one intended use. It does not depict an actual unit, imply that retirement has happened or approve quality, ownership, certification or public wording.
Diagram text description
Change Climate's page headed 2026 Standard supplies a concrete illustration of framework-specific vintage restrictions. Its dedicated restriction text states 2019–2025 for forestry and land-use credits and 2022–2025 for other project types. The same page also repeats a block showing 2018–2024. That discrepancy is material for some boundary-year decisions and must not be concealed.
| Page evidence at the October 2026 check | Published vintage wording | Appropriate treatment |
|---|---|---|
| Dedicated 2026 restriction text | Forestry and land-use: 2019–2025; other types: 2022–2025 | Identify category, edition and applicable evaluator interpretation |
| Repeated block on that page | 2018–2024 appears again | Preserve the conflict; do not select favourable wording silently |
Table 4, shown one row at a time. Every field is retained.
Row 1
- Page evidence at the October 2026 check
- Dedicated 2026 restriction text
- Published vintage wording
- Forestry and land-use: 2019–2025; other types: 2022–2025
- Appropriate treatment
- Identify category, edition and applicable evaluator interpretation
Row 2
- Page evidence at the October 2026 check
- Repeated block on that page
- Published vintage wording
- 2018–2024 appears again
- Appropriate treatment
- Preserve the conflict; do not select favourable wording silently
The evidence establishes that a named certification uses vintage conditions. It does not justify resolving contradictory text on the publisher's behalf. A buyer whose decision depends on the inconsistent boundary should hold that decision and obtain clarification from the framework's responsible evaluator. Capture the answer and the applicable version with the purchase file. A tidy spreadsheet cannot remove an unresolved source contradiction.
Also keep different instruments separate. The page contains a distinct rule for electricity-related energy attribute certificates. It is not the carbon-credit vintage rule. Similar words, such as year, vintage and certificate, do not make the instruments interchangeable. Reading only the first date range found by a search can therefore produce a confident answer to the wrong requirement.
Even an unambiguous vintage match is only one criterion. The programme, method, project category and any exclusions must fit the selected use. Do not present the example years as a market-wide definition of valid carbon credits, or extrapolate them to another certification year. Nor does an exception for future or non-conforming instruments turn a forward commitment into a retired issued unit. Its permitted treatment would need to be established under that exception's own terms.
For procurement, the question to settle before choosing stock is the actual framework and claim, not which framework can be found afterward to accommodate an attractive price. If the organisation has not selected its use, record that uncertainty. It cannot meaningfully approve vintage eligibility for an unspecified purpose.
Match vintage and retirement to the intended claim
The reporting calendar creates another relationship: the outcome vintage, the company's emissions period and the retirement event need not be the same date. Whether a particular alignment is permitted depends on the chosen use rules. A purchase alone does not demonstrate that an action required before a statement has been completed.
For example, imagine a fictional company preparing a statement about its 2025 reporting period for publication in April 2026. Its selected policy requires the relevant retirement to be completed before that statement is released. The supplier proposes retirement in May. The practical problem is not that the units chemically expire in April; it is that a planned May event cannot support an April sentence asserting completed retirement. The team must change the timing, complete an acceptable action earlier, or revise the proposed statement so it does not assert an event that has not happened. This is an invented policy scenario, not a universal April or May deadline.
Start with the actual words the company wants to publish. “We financed future delivery”, “we hold issued units” and “we retired units for this purpose” describe different events. A report should not use the third formulation merely because procurement approved the first. Record the beneficiary and purpose required by the applicable process as well as the date. A retirement for an unrelated beneficiary is not repaired by placing a different company's logo beside the certificate.
Late reporting also needs explicit treatment. Closing an emissions inventory after year-end can be normal operationally, but it does not authorise backdating a registry event or imply that every claims system allows the same later action. Ask which edition and timing rules govern the intended disclosure, and retain the actual event date even if the claimed reporting period is earlier. If the rule is unclear, it is the use decision that is unresolved; do not invent a convenient retrospective deadline.
Keep the company's gross inventory intact while doing this reconciliation. An external unit record does not erase the physical emissions in Scope 1, 2 or 3. Separate the measured inventory, the external instrument and the permitted description of their relationship. That prevents a timing correction from quietly becoming an unsupported change to the emissions account itself.
Check for registry-transition deadlines
Some mechanisms do impose real operational deadlines. The UNFCCC CDM Registry FAQ describes winding down the CDM registry, with different dates for preparatory submissions, completion of transactions and later administrative cancellation. This concerns the affected Certified Emission Reductions and registry pathway, not every voluntary unit elsewhere.
| CDM FAQ distinction at the October 2026 check | Date or consequence | What it means for the review |
|---|---|---|
| Guaranteed-processing timeline for cancellation and other transaction requests | 25 November 2026 | Prepare submissions before the operational timeline; later processing is not guaranteed |
| End of transactions in the CDM registry | 31 December 2026 | Do not treat later administrative processing as extra time to transact |
| Administrative cancellation and registry closure arrangements | 2027, including 1 July arrangements described in the FAQ | Identify affected units and account conditions; recheck the official notice |
Table 5, shown one row at a time. Every field is retained.
Row 1
- CDM FAQ distinction at the October 2026 check
- Guaranteed-processing timeline for cancellation and other transaction requests
- Date or consequence
- 25 November 2026
- What it means for the review
- Prepare submissions before the operational timeline; later processing is not guaranteed
Row 2
- CDM FAQ distinction at the October 2026 check
- End of transactions in the CDM registry
- Date or consequence
- 31 December 2026
- What it means for the review
- Do not treat later administrative processing as extra time to transact
Row 3
- CDM FAQ distinction at the October 2026 check
- Administrative cancellation and registry closure arrangements
- Date or consequence
- 2027, including 1 July arrangements described in the FAQ
- What it means for the review
- Identify affected units and account conditions; recheck the official notice
The FAQ also gives an earlier guaranteed-processing date for transfer requests to the Article 6.4 mechanism registry: 25 October 2026. At the October check that date had passed. A broad statement that “the registry remains open until December” would therefore omit an operational constraint that matters to an account holder. Earlier rules can also apply to particular deregistered or transitioned projects. The latest date on a page is not automatically the deadline relevant to the requested action.
Scope is just as important as timing. The FAQ distinguishes eligible CERs transferred to the Article 6.4 mechanism registry from units left in the closing CDM registry, and does not impose its rules on unrelated national registries. Do not assume transfer was automatic, eligibility was universal or a seller's reference to the successor mechanism proves completion. Identify the destination and the actual serial history.
For a real transaction, the account holder should verify the current notice and operational feasibility directly. The record needs the affected unit type and location, requested action, applicable submission date, completion cutoff and evidence of the result. A promise to submit is not proof that the transaction succeeded. If the action cannot be completed under the applicable arrangements, describe the resulting limitation rather than market the units as ordinary available stock.
An administrative cancellation date and an ordinary age limit are different kinds of rule. Explaining that difference prevents two errors: assuming no real deadline can exist because some programmes have non-expiring units, and spreading one registry's closure date across the entire market. This is a current operational example, not a timeline of how carbon markets developed.
Retirement is use, not ordinary expiry
Retirement is a deliberate use-related event, not the passage of a sell-by date. For CRTs, the Reserve describes retirement as permanent: units in retirement cannot be reactivated and transferred again. A historical record can remain visible after that event. Visibility is evidence of what happened, not evidence that the same stock is still available.
Before an irreversible instruction, reconcile four practical items: the exact serials, quantity, intended beneficiary and stated purpose required by the process. Where a supplier acts for the buyer, also establish who submits the instruction and what evidence will be returned. The buyer's approval email should not be treated as the registry's completed action. An invoice may establish payment while saying nothing about which serials were ultimately retired.
For example, a fictional company holds two batches from one project. Only the second meets the policy for its present statement, but an operator selects the first batch during retirement. Matching the total number of units does not fix selection of the wrong vintage. Review the completed event against the approved batch, not merely against the payment amount. If an error has occurred, obtain the programme's actual options; do not assume a permanent retirement can be reversed or rewrite the certificate locally to conceal the mismatch.
After completion, distinguish consistent reporting of one use from a second incompatible use. The same retirement may be referenced in an annual report and the supporting evidence page if both describe the same beneficiary, period and event accurately. That does not create another unit or permit another organisation to claim a separate use of it. Repeating the evidence is not the same thing as repeating the environmental entitlement.
Similarly, the word cancellation needs context. Some systems use voluntary cancellation for an intended use, while administrative cancellation can remove units for a different reason. Read the programme's meaning and event purpose before describing a cancelled record as successful compensation. Registry terminology, not the prettiness of the downloaded document, controls what that record establishes.
Does an old vintage mean poor quality?
Age is a useful prompt for investigation, not a quality score. Vintage, issuance delay and time spent unsold describe different aspects of an offer. None independently establishes that a baseline was sound, that an activity was additional or that a buyer's proposed claim is permitted. A recent unit can have weak supporting evidence, and an older outcome can have a well-documented history.
Consider two fictional cases. Batch A concerns an older monitoring period but was issued later after a documented review process. The buyer should ask what caused the delay, which method and data were assessed, and whether any unresolved finding remains. Batch B has a recent vintage and an attractive presentation but does not identify its method version or provide the relevant verification record. Buying Batch B simply because its year looks newer would replace evidence with a cosmetic preference. Neither case is a verdict on a real project.
Unsold stock raises another question: why was it still available? Possible explanations include a long verification process, project financing arrangements, limited demand or a buyer-category mismatch. Those are hypotheses to investigate, not accusations. Ask for the actual account of issuance and availability, and compare it with source documents. A low price or long holding period alone cannot prove either poor integrity or an exceptional bargain.
Separate the historical activity's additionality from the effect of a purchase today. Whether the project outcome met its programme's test and whether buying a particular remaining unit now supports a company's chosen climate-finance objective are related but different questions. The buyer should not claim its payment newly caused an outcome that had already occurred without evidence supporting that causal assertion. Nor should it infer that every earlier outcome was non-additional because it was sold later.
Finally, keep quality and permitted use as separate findings. A unit may fail a vintage window even if the project evidence is strong. It may satisfy that window while leaving important quality concerns unresolved. A responsible recommendation can therefore say “within the stated vintage condition; technical review outstanding” rather than compress both findings into a single green age indicator. The next investigation should address the actual uncertainty, not demand an arbitrarily newer year.
What if the climate benefit is reversed?
A physical event can change the integrity assessment independently of unit age. Fire, disease or another release can matter to a storage project, while other project types have different risks and corrective processes. A reported event is a reason to investigate its scope, not proof that every unit associated with a project has automatically disappeared.
The diagram separates three reviews after a reported storage incident. First, what has the programme or registry actually done to the units? Second, what does updated technical evidence show about the physical outcome? Third, what can the company now say accurately? A registry response, an evidence review and a claims response may run together, but none should be silently substituted for the others.
A reported storage incident branches to Unit status, Physical outcome and Claim wording. Each leads respectively to Registry response, Evidence review and Claim response. Arrows indicate investigation tasks, not a mandatory administrative sequence or a quantified physical loss. The drawing assumes no universal buffer, replacement, cancellation or claim correction; actual programme rules and evidence determine the response.
Diagram text description
For example, imagine a fictional news report of a wildfire near a forestry project. The geographic proximity alone does not establish the affected project area, the amount of stored carbon released, the monitoring period or the consequences for the offered serials. The buyer needs the programme's incident record and applicable remedy decision, together with appropriate technical evidence. If a buffer or replacement mechanism applies, establish its scope and actual response; do not promise that every storage unit carries identical protection. If the programme has not yet determined the consequence, the purchase or claim may need to remain on hold even while a public status screen still appears unchanged.
The opposite shortcut is also unsafe. A current active label does not itself prove that new physical evidence has been fully assessed. Describe the unresolved question precisely: incident attribution, measured loss, programme treatment, delivery obligation or claim wording. Assign it to the party with the necessary evidence and authority. A seller's assurance that the vintage is recent cannot resolve a storage loss, just as an older vintage cannot establish that a loss occurred.
Where a programme later issues a correction or remedy, preserve its date and scope. The company may need to update a pending recommendation or revisit wording already published; those are not the same action as trading or retiring units. Follow the applicable rules and obtain qualified review where needed. Do not convert a general incident report into a universal cancellation announcement, or describe an assumed remedy as completed protection.
Run the five-field eligibility check
Use five observed fields for a named batch, then attach the programme and intended-use rules that interpret them. The fields do not produce a numerical expiry score. They make it possible to see which fact, rule or action supports the decision and which remains unresolved. The programme, unit type, project, method and serial range form the record's identity before the five-field check starts.
The following is an invented teaching case, not an actual registry entry or a real certification requirement. Policy P1, also fictional, accepts only vintages 2022–2024 for a specified 2024-period statement and requires completed retirement for the intended beneficiary before the statement is released. Batch B is the candidate; its supporting documents and dates below are assumed solely to demonstrate the decision.
| Field | Fictional Batch B observation | Interpretation for Policy P1 |
|---|---|---|
| Vintage | 2023 | Within the invented 2022–2024 window; other criteria still apply |
| Issuance | Recorded in 2025 under identified method M | Issued stock, not a future forecast; method review is separate |
| Intended claim period | Specified 2024 reporting period | Use exactly this period and the approved statement |
| Retirement | Planned for the intended beneficiary, not yet completed | Hold the completed-use statement until the required event is evidenced |
| Live serial status | Assumed active at the recorded lookup | Candidate availability at that time, not a permanent guarantee or proof of delivery |
Table 6, shown one row at a time. Every field is retained.
Row 1
- Field
- Vintage
- Fictional Batch B observation
- 2023
- Interpretation for Policy P1
- Within the invented 2022–2024 window; other criteria still apply
Row 2
- Field
- Issuance
- Fictional Batch B observation
- Recorded in 2025 under identified method M
- Interpretation for Policy P1
- Issued stock, not a future forecast; method review is separate
Row 3
- Field
- Intended claim period
- Fictional Batch B observation
- Specified 2024 reporting period
- Interpretation for Policy P1
- Use exactly this period and the approved statement
Row 4
- Field
- Retirement
- Fictional Batch B observation
- Planned for the intended beneficiary, not yet completed
- Interpretation for Policy P1
- Hold the completed-use statement until the required event is evidenced
Row 5
- Field
- Live serial status
- Fictional Batch B observation
- Assumed active at the recorded lookup
- Interpretation for Policy P1
- Candidate availability at that time, not a permanent guarantee or proof of delivery
The decision is hold, despite the matching vintage and active status. The missing item is not another year calculation; it is completed retirement under the invented policy and reconciliation of that event to the intended batch and beneficiary. A reviewer could authorise the next procurement or retirement step subject to its own controls without approving publication of a completed-use claim. Keep those approvals distinct. If delivery or quality evidence is also unresolved, closing the retirement condition alone does not close those other issues.
Now change one fact at a time. If the seller substitutes a 2021 vintage, the offer fails this invented vintage condition even if recently issued. If it substitutes units already retired for another incompatible use, they are not fresh stock for this transaction. If it offers future delivery with no issued serials yet, treat that as a forward obligation and leave the current-unit check incomplete. These cases require different decisions; none justifies announcing a universal carbon-credit expiry period.
For each real field, retain the observed value, source reference, observation date and responsible reviewer. A blank field should mean unknown, not silently pass. Where the source is inconsistent, preserve both passages and obtain clarification. The Change Climate example shows why apparent data completeness is not enough: five populated cells cannot resolve conflicting authoritative wording automatically.
The output should name the batch and use, distinguish proceed with the next step from permission to publish, and list remaining conditions with owners. Reopen the affected decision when serials, beneficiary, claim period, method eligibility or governing rule changes. Preserve the earlier version rather than overwrite it, so a later reviewer can understand why a previous recommendation differed. A repeatable check needs reproducible evidence and explicit uncertainty, not a single “not expired” tick.
Avoid two opposite mistakes
Two slogans fail in opposite directions. “Every carbon credit expires after a fixed number of years” invents a rule that does not apply across programmes. “Credits never expire, so any unit will work forever” takes a bounded non-expiry statement and turns it into permission for every claim. Both remove the exact unit and intended use from the decision.
For example, a fictional purchasing note says an offered unit is unusable because the project ended its crediting period. That reason is incomplete if the unit was already issued and no applicable rule has removed its availability. A second note says an active unit must be suitable because the programme has no age limit. That misses the buyer's separate vintage restriction. A third says a retired unit is simply an older version of available stock. That misses the completed event that ended its circulation. These are different mistakes, not competing estimates of the same deadline.
Use plain-language reasons that point to the actual remedy. “This vintage does not fit our selected policy” may lead procurement to seek another batch. “These serials are already retired for an incompatible use” means they cannot supply a fresh use in the proposed transaction. “The transfer pathway is subject to a registry deadline” calls for an operational feasibility check. “We do not yet know the applicable rule” calls for a hold, not a guess. None requires declaring every unit from the project worthless.
Reason codes also protect internal conversations. Finance may be asking whether an asset can still be sold, procurement whether delivery can occur, and communications whether a specific statement is supported. Those questions are not interchangeable. Recording the reason and decision scope helps the right team act without treating a narrow claims restriction as a global market announcement or an availability check as approval of public wording.
Keep a dated rule and decision trail
The evidence trail can be governed without pretending that recordkeeping determines validity. A structured file should join the offered serials to dated rule text, registry observations, intended claim and decision owner. It should distinguish a planned action from a completed event and keep unresolved interpretations visible. These are requirements for a record, not proof that any particular software service already performs them.
A useful change history separates three kinds of update. A source update records a revised rule or notice. A stock update records substituted serials, a different vintage or a changed status. A decision update explains what the responsible reviewer concluded for the proposed use. Linking these changes allows a colleague to see whether a new recommendation follows a new fact, a changed rule or correction of an earlier mistake. Merely replacing the displayed status loses that explanation.
For example, if the supplier replaces Batch B with another range, retain the original offer and mark the new range as requiring its own checks. If a framework clarifies inconsistent wording, preserve the clarification alongside the conflicting extract rather than erase the ambiguity from the record. If a retirement is completed, add the actual event and reconciliation; do not retrospectively change a previous planned date into a claim that completion was already known. The history should remain understandable to someone who did not participate in the transaction.
Keep the provider boundary equally clear. General product, supplier or carbon-data organisation does not establish authority to issue units, extend their life, operate a registry, sell or retire credits, or certify a company's claim. The source rules and responsible reviewers still govern those questions. A useful system can make a decision traceable; it cannot make an ineligible serial acceptable by displaying a reassuring colour or hiding an unresolved exception.
Make the use decision for the exact unit
The answer to “when do carbon credits expire?” depends on what is being limited: the unit's programme lifespan, its current availability, a registry operation or its suitability for a named use. A project generation window is another distinct matter. Do not combine them into an invented global date, or replace them with a promise of unlimited suitability.
Make the next action follow the actual unresolved condition. Obtain missing unit evidence, clarify the governing vintage rule, complete and reconcile the required action, or select a different permitted batch. If the claim or offered serials change, revisit the affected decision. Preserve the underlying emissions account and the external credit record separately.
Credit history, project quality, unit quantities and commercial value are important adjacent subjects, but none alone answers this use question. A credible conclusion identifies the exact units, proposed statement and remaining limitation. That is the difference between a useful eligibility decision and a comforting sentence about credits being either expired or not expired.
