How to check carbon offset certificates against registry records
An open ledger and magnifying glass sit beside blank cream paper, a pen and a green binder. The scene illustrates document review.
Diagram text description
A carbon offset certificate is useful when its details lead to the underlying record. The name on the document can mean several things. A seller may issue a purchase receipt, a programme may issue a unit into a registry, and a retirement confirmation may record the final use of identified units. Read the transaction wording and ask which event the document records.
Follow the certificate to the exact serial numbers or equivalent unit identifiers. Check their current registry status, then check the beneficiary and use where the programme records them. Only then decide what wording those facts can support. The diagram follows that chain. A missing step leaves a question to resolve before the business relies on the certificate for a claim.
Start with certificate details and locate the exact units. Check their transaction, status and any recorded beneficiary in the registry. Use only evidence that supports the specific attribution and wording.
Diagram text description
Use three separate review outcomes. First determine whether the document came from the stated source. Next confirm the unit action, including retirement where relevant. Finally assess the project and whether the credits suit the buyer's objective. Each decision needs its own evidence.
Separate programme, registry, verifier and seller roles
Start by identifying who produced the certificate and who maintains the record it refers to. A seller may buy, transfer or arrange retirement for a customer. The project developer supplies the underlying project and monitoring records. A programme defines requirements, and a registry maintains the unit and transaction records. In some arrangements one organisation carries more than one role. Ask what it is doing in this transaction.
| Role | Evidence to ask for |
|---|---|
| Seller or intermediary | Contract, invoice and the agreed transfer or retirement service |
| Project developer | Project description, applicable methodology and monitoring report |
| Crediting programme | Requirements for the unit, project and applicable method |
| Independent validation or verification body | Assessment with its scope, project and covered period |
| Registry or authorised account holder | Authoritative unit record and evidence of the relevant transaction |
Table 1, shown one row at a time. Every field is retained.
Row 1
- Role
- Seller or intermediary
- Evidence to ask for
- Contract, invoice and the agreed transfer or retirement service
Row 2
- Role
- Project developer
- Evidence to ask for
- Project description, applicable methodology and monitoring report
Row 3
- Role
- Crediting programme
- Evidence to ask for
- Requirements for the unit, project and applicable method
Row 4
- Role
- Independent validation or verification body
- Evidence to ask for
- Assessment with its scope, project and covered period
Row 5
- Role
- Registry or authorised account holder
- Evidence to ask for
- Authoritative unit record and evidence of the relevant transaction
A verifier's report can explain which design or monitored outcome was assessed. Match it to the offered vintage or period before treating it as evidence for the batch. The account holder can help retrieve an extract, while the registry or programme can explain what its statuses and fields mean.
Where a seller promises a retirement on the buyer's behalf, clarify who will request it and whose name and use should appear. An intermediary's account name may be a different field from the retirement beneficiary. Request the programme's terminology or an explanation of those fields before drawing a conclusion about either party.
Read the identifiers on the document
Read the certificate as a set of fields that must reconcile. A project number can identify the activity without identifying any particular units. A serial or batch range can identify units without showing why they were purchased. Start with the fields below and record where each can be checked.
| Field on the document | Check against |
|---|---|
| Programme, registry and project identifier | Programme and project entry reached independently |
| Methodology and version | Project and monitoring documents for the offered period |
| Vintage and unit type | Issued batch details and the programme's definition |
| Quantity and serial range | Registry block or unit details, including any split ranges |
| Holder or transaction account | Transfer record and contract for the relevant action |
| Retirement date, beneficiary and purpose | Retirement record and the buyer's instruction or agreement |
| Transaction wording and reference | The exact issuance, transfer or retirement event the document claims to show |
Table 2, shown one row at a time. Every field is retained.
Row 1
- Field on the document
- Programme, registry and project identifier
- Check against
- Programme and project entry reached independently
Row 2
- Field on the document
- Methodology and version
- Check against
- Project and monitoring documents for the offered period
Row 3
- Field on the document
- Vintage and unit type
- Check against
- Issued batch details and the programme's definition
Row 4
- Field on the document
- Quantity and serial range
- Check against
- Registry block or unit details, including any split ranges
Row 5
- Field on the document
- Holder or transaction account
- Check against
- Transfer record and contract for the relevant action
Row 6
- Field on the document
- Retirement date, beneficiary and purpose
- Check against
- Retirement record and the buyer's instruction or agreement
Row 7
- Field on the document
- Transaction wording and reference
- Check against
- The exact issuance, transfer or retirement event the document claims to show
Vintage, purchase date and retirement date answer different questions. Keep them separate in the review sheet. For a contiguous range, count the identifiers inclusively and confirm that the registry record uses the same block and unit definition. For a split range, account for each block separately. A quantity written next to a project name does not identify which units the buyer received.
If a field is missing from the public view, note what was visible and request evidence through the account holder or programme. Record the gap as unresolved while it is being investigated. The absence of a public field alone does not tell you whether the claimed action occurred.
Match the certificate to the registry
Consider this fictional example. Kelder Toolworks receives seller document KT-C72 for 25 units from project NE-231 in the fictional North Estuary programme. The document gives vintage 2024 and unit references FICT-NE-5101 through FICT-NE-5125. It says that the units were retired for Kelder on 12 February 2026. All names, records and identifiers in this example are invented.
| Field | Seller document KT-C72 | Fictional registry extract (20 February 2026) |
|---|---|---|
| Project and vintage | NE-231, vintage 2024 | Same project and vintage |
| Units | FICT-NE-5101 through FICT-NE-5125, 25 units | Same 25 issued units |
| Transaction | Retirement on 12 February 2026 | Transfer to Kelder's account on 18 February 2026 |
| Status and beneficiary | Retired for Kelder | Active in Kelder's account, with no retirement action or beneficiary shown |
Table 3, shown one row at a time. Every field is retained.
Row 1
- Field
- Project and vintage
- Seller document KT-C72
- NE-231, vintage 2024
- Fictional registry extract (20 February 2026)
- Same project and vintage
Row 2
- Field
- Units
- Seller document KT-C72
- FICT-NE-5101 through FICT-NE-5125, 25 units
- Fictional registry extract (20 February 2026)
- Same 25 issued units
Row 3
- Field
- Transaction
- Seller document KT-C72
- Retirement on 12 February 2026
- Fictional registry extract (20 February 2026)
- Transfer to Kelder's account on 18 February 2026
Row 4
- Field
- Status and beneficiary
- Seller document KT-C72
- Retired for Kelder
- Fictional registry extract (20 February 2026)
- Active in Kelder's account, with no retirement action or beneficiary shown
The quantity and identifiers reconcile, but the status and chronology do not. The later transfer is a different registry event from the earlier claimed retirement. The seller confirms it sent the PDF and supplies the paid invoice dated 10 February 2026. That supports the document's origin and the purchase. The registry extract supports transfer of the same units, and the case file still has no confirmed retirement for them.
KT-C72 says the 25 units were retired for Kelder on 12 February 2026. The same 25 identifiers appear in a transfer to Kelder on 18 February, and remain active in the 20 February extract. The file establishes the purchase and transfer and leaves retirement unresolved.
Diagram text description
Keep the original document, obtain the transaction history and ask the seller and registry account holder to explain the date and status. A corrected purchase receipt might resolve the description of the commercial transaction. A claim of retirement would need the corresponding authoritative registry evidence. Until then, the reviewer records 25 purchased and transferred units and holds the retirement claim.
Quality is a separate open issue. The seller has supplied a monitoring report for a different vintage. Even if the retirement record is later established, the buyer still needs project evidence that matches these units and its objective. The mismatch calls for clarification and a hold on the unsupported claim. It does not establish fraud or certify the project.
Check credit quality beyond authenticity
An authentic document and matching unit record help establish which transaction occurred. To decide whether the credits suit the buyer's purpose, review the project method, baseline and monitoring evidence separately. Ask what the outcome is compared with, why the activity is additional and what quantities the project measured. Check the independent assessment scope against the period and vintage of the units.
Consider whether activity could shift emissions elsewhere, how a reversal would be detected and addressed, and how the project manages harms to affected people or ecosystems. Durability questions vary by activity and storage mechanism. Request the arrangements that apply to the specific project and batch. The UK voluntary market integrity principles provide a guide to these issues, including independent validation and verification and the treatment of leakage and reversal.
Record the decision against the buyer's stated use. Accept a batch for further approval when the evidence meets the written criteria. Narrow the proposed wording when the file can support a transaction description but cannot establish a broader outcome. Hold the decision when a required record or a material assumption remains unresolved. For Kelder, the mismatched monitoring period keeps the quality review open regardless of how the seller resolves the certificate wording.
Reconcile status, exact units and beneficiary in the transaction record. Check the project’s method, baseline, additionality, measurement, leakage, durability and safeguards for the buyer’s objective. Advance a supported use for review, narrow the wording when appropriate or hold where important evidence is missing.
Diagram text description
Build a certificate review checklist
Work through the checks in order and give each result an owner. Retain the actual record or reference used, the date and the exception. Use “matched”, “mismatch” or “unresolved” for the individual check. A matched field describes the evidence reviewed for that field.
| Check | Record to retain | If it is missing or inconsistent |
|---|---|---|
| Confirm who issued the document | Original certificate, delivery record and issuer confirmation | Ask the seller to verify its origin and preserve the earlier copy |
| Reconcile the purchase | Contract, invoice and offered batch identifiers | Have procurement resolve the quantity or terms before recording delivery |
| Match units and transaction history | Dated registry extract with exact identifiers and statuses | Ask the account holder or programme for the missing history and hold the unsupported status |
| Confirm any retirement | Registry retirement action, date, beneficiary and stated use | Leave retirement unresolved for the buyer until those details reconcile |
| Assess the batch | Project method, monitoring period, verification and safeguards file | Route the evidence gap to the project reviewer |
| Review the words | Proposed statement, scope, related records and decision | Hold unsupported wording and ask the claim approver to reassess it after resolution |
Table 4, shown one row at a time. Every field is retained.
Row 1
- Check
- Confirm who issued the document
- Record to retain
- Original certificate, delivery record and issuer confirmation
- If it is missing or inconsistent
- Ask the seller to verify its origin and preserve the earlier copy
Row 2
- Check
- Reconcile the purchase
- Record to retain
- Contract, invoice and offered batch identifiers
- If it is missing or inconsistent
- Have procurement resolve the quantity or terms before recording delivery
Row 3
- Check
- Match units and transaction history
- Record to retain
- Dated registry extract with exact identifiers and statuses
- If it is missing or inconsistent
- Ask the account holder or programme for the missing history and hold the unsupported status
Row 4
- Check
- Confirm any retirement
- Record to retain
- Registry retirement action, date, beneficiary and stated use
- If it is missing or inconsistent
- Leave retirement unresolved for the buyer until those details reconcile
Row 5
- Check
- Assess the batch
- Record to retain
- Project method, monitoring period, verification and safeguards file
- If it is missing or inconsistent
- Route the evidence gap to the project reviewer
Row 6
- Check
- Review the words
- Record to retain
- Proposed statement, scope, related records and decision
- If it is missing or inconsistent
- Hold unsupported wording and ask the claim approver to reassess it after resolution
For each exception, record the question, evidence source, observed result, responsible owner, next action and resolution date when known. In the fictional file, the registry owner receives the status exception, procurement retains the seller correspondence and the claim approver keeps retirement wording on hold. If evidence changes, record what it resolves and keep the original decision with the new one.
This checklist produces a record of the checks and what remains open. It can establish that specified units and a transaction matched the available records. Assessment of the project and approval of a public claim still have their own evidence and owners.
Avoid certificate-based claim mistakes
Show gross emissions, operational changes and credit activity in separate records. The certificate belongs with the external transactions. A company or product footprint needs its own boundary, period and inputs, and any claimed reduction needs evidence of what changed within that boundary.
| Record | What it can support |
|---|---|
| Gross inventory | Emissions measured or estimated for the stated activities and period |
| Operational reduction record | Evidence of changes within that boundary and the basis for attributing the change |
| External credit record | Project, units bought, units retired where evidenced, and beneficiary and intended use |
Table 5, shown one row at a time. Every field is retained.
Row 1
- Record
- Gross inventory
- What it can support
- Emissions measured or estimated for the stated activities and period
Row 2
- Record
- Operational reduction record
- What it can support
- Evidence of changes within that boundary and the basis for attributing the change
Row 3
- Record
- External credit record
- What it can support
- Project, units bought, units retired where evidenced, and beneficiary and intended use
If the company reports Kelder's fictional transaction, it can describe the purchase and transfer of the 25 identified units within the evidence available. Keep their retirement status open in the review and make no claim that the certificate establishes a reduction in Kelder's operations. The project and use still need separate assessment.
A statement on a product page can imply more than the same transaction entry in a corporate report. Review the full impression, including its headline, images and where the limits appear. Ask the responsible reviewer to check the proposed claim against its market, audience and applicable rules. The voluntary guidance helps frame that review and leaves the actual legal assessment to the relevant context.
Trace product evidence to the inventory
Product evidence has its own traceability. Keep the product revision, bill of materials, supplier inputs and calculation method linked so a reviewer can tell which components and period a figure represents. Where data have changed, retain the earlier version and the reason for the change.
Suppose Kelder changes a metal housing. The supplier figure for the previous housing may no longer describe the material or process used in the current revision. Request matching evidence or record a bounded estimate and its uncertainty. A credit certificate offers no information about that material change. The product data owner has to resolve it before a statement relies on the revised footprint.
Keep the registry extract, project evidence and use decision with the credit record. When an external statement draws on both files, identify the role of each. The inventory supports an emissions quantity or change, while the credit file supports the external transaction and any documented retirement.
Resolve the exception before relying on the certificate
Begin with the certificate's unit references and follow them through the programme's records. Record which transaction can be matched, who it relates to and what evidence is missing. If a detail conflicts, retain both versions and assign the exception to the person who can obtain the authoritative record.
Kelder can explain what it purchased and received. A retirement claim stays unresolved until the conflicting date and status are reconciled, and a decision about quality waits for the correct monitoring evidence. Use the same order for the next certificate. First match the document and the units, then resolve the relevant status and project checks before deciding which words the evidence supports.
Carbon credits & offsetting
