VCU Lifecycle: After First Issuance
A VCU doesn't end at issuance
Once VCUs are deposited into a registry account, they have a defined lifecycle, they can be transferred, sold, labeled, retired, or cancelled. Meanwhile, the project must continue submitting verifications and maintaining its registry status. This lesson covers what happens to VCUs and to the project throughout its crediting life.
📍 VCU Lifecycle in Practice: Microsoft's Soil Carbon Purchase
In 2021, Microsoft purchased a tranche of soil carbon VCUs from the Soil Carbon Initiative operating under the Australian Carbon Farming Initiative (similar structure to VM0042). The VCUs were vintage 2019–2020, each with a unique serial number on the registry. Microsoft's sustainability team verified the serial numbers on the registry before paying, confirmed they were not already retired, executed the purchase via a broker, and then initiated retirement through their own Verra registry account, marking each serial number "retired for Microsoft's FY2021 Scope 1 offset claim." The retired VCUs are now permanently cancelled and publicly visible on the Verra registry. This is the standard end-to-end lifecycle for every corporate VCU purchase.
Step 5: Periodic VCU Issuance, Repeat Crediting
A registered project can continue issuing VCUs from subsequent monitoring periods throughout its crediting period (typically 20–30 years for VM0042). Each subsequent issuance follows the same core process as the first, submit monitoring report, verification report, and representations to Verra; Verra reviews; VCUs deposited after levy payment.
5-Year Maximum Verification Gap
The project proponent must submit a verification approval request within 5 years of the previous approval date. Missing this deadline triggers "late to verify" status on the registry, a public signal that the project has not been recently audited. Projects with "late to verify" status can still submit and recover, but investors and buyers treat this as a quality signal.
Step 6: VCU Retirement vs. Cancellation, A Critical Distinction
🏷️ Analogy: Concert Ticket vs. Refund
Retiring a VCU is like using your concert ticket, the credit is permanently consumed to offset a tonne of emissions, with the retirement reason recorded publicly. Cancelling a VCU is like voiding a ticket without going to the concert, it's removed from circulation without making an offsetting claim, often for technical or regulatory reasons (e.g., converting VCUs into another program's credits).
Retirement
Used when a buyer permanently claims the credit against their emissions (e.g., corporate net-zero claim, CORSIA compliance). The registry account holder initiates retirement through their Verra Registry account. The Verra Registry records all details, quantity, vintage, retirement reason, and the entity retiring.
Who initiates: Registry account holder (owner of the VCU).
Incremental retirement is permitted, holder may retire part of their holdings now and the rest later.
Cancellation
Used when VCUs are being converted into another form of GHG credit, or when Verra cancels credits due to a reversal or compliance issue. Cancellation does NOT constitute an offset claim. The registry records all cancellation details.
Who initiates: Registry account holder, the other GHG program, or Verra (in some cases).
Example: converting VCUs into ITMOs (Article 6 credits) for use in a compliance market requires cancellation + corresponding adjustment.
The AFOLU Pooled Buffer Account, Mechanics
For AFOLU projects (including all VM0042 projects), a percentage of every VCU issuance is deposited as non-tradeable buffer credits into the centrally managed AFOLU Pooled Buffer Account. These are not VCUs, they have no serial numbers and cannot be sold or traded.
Deposit
At every VCU issuance, buffer credits = buffer % × net GHG removals. Buffer contributions are set separately for reductions (typically 0%) and removals (10–20%). The non-permanence risk tool determines the %. Buffer credits are deposited simultaneously with VCU issuance.
Release (Earned Back)
Buffer credits can be released back as VCUs (into the project's account) if the project's non-permanence risk remains the same or decreases. Release conditions: first release ≥5 years after first verification; subsequent releases at most every 5 years. A 15% time release applies to total accumulated buffer credits at each eligible release event.
Cancellation (Loss Events)
If a reversal occurs (e.g., drought kills soil carbon), the project proponent must notify Verra within 30 days. Verra puts buffer credits on hold equal to the estimated loss. Upon verification confirming the loss, an equivalent number of buffer credits are cancelled, covering the reversal without impacting VCU holders. The project cannot issue new VCUs until a loss event report is submitted.
📐 Buffer Pool Worked Example, 10-year project
| Event | Buffer Credits | VCUs Issued |
|---|---|---|
| Year 5, First verification (100,000 tCO₂e removals, 15% buffer rate) | +15,000 deposited to pool | 85,000 VCUs |
| Year 10, Second verification (80,000 tCO₂e, risk same → 15% time release eligible) | +12,000 deposited; 15% × 27,000 total = 4,050 released as VCUs | 68,000 + 4,050 = 72,050 |
| Year 8 drought event (carbon loss estimated 5,000 tCO₂e) | 5,000 buffer credits cancelled from pool | No new VCUs until loss report filed |
The 9 VCU Attributes, What Makes a VCU Credible?
The VCS Program Guide (Section 3) establishes 9 attributes that every VCU must embody. These are the quality standards that underpin the entire VCS system:
| Attribute | What It Means for VM0042 |
|---|---|
| Additional | Reductions exceed what would happen without carbon market incentive (Lesson 2.3, the additionality tests) |
| Durable | Safeguards (buffer pool) are in place; reversals are accounted for, reported, and replaced where possible |
| Independently verified | Accredited VVB with AFOLU sectoral scope approval audits the project |
| Traceable and not double counted | Unique VCU serial numbers in the Verra Registry prevent double issuance, double claiming, and double use |
| Robustly quantified | VM0042 equations, uncertainty deductions, and buffer pool ensure conservative measurement (Modules 3–4) |
| Participatory-based | Stakeholder consultation, free prior and informed consent (FPIC), grievance mechanisms, required by VCS |
| Safeguarded from unmitigated harm | Negative impacts on people/environment assessed and mitigated; Indigenous Peoples' rights upheld |
| Aligned with SDGs | Project activities designed to deliver positive sustainable development outcomes |
| Aligned with net zero transition | Activities must not lock in emissions or be incompatible with mid-century net zero |
Step 7: Project Maintenance & Quality Control
Project Maintenance Obligations
- • Submit verification approval request every ≤5 years or become "late to verify"
- • Proponent may voluntarily withdraw the project via the Verra Project Hub (withdrawal form); already-verified credits are still issued before withdrawal
- • Withdrawn projects that move to another GHG program have all buffer credits cancelled
- • Projects may re-join VCS after withdrawal subject to Verra review
Quality Control Reviews
Verra may open a Quality Control (QC) review at any time if it identifies potential non-conformances, including VCUs already issued. If the QC review finds problems, Verra can require corrective actions, cancel VCUs, or reject the project. Project proponents are liable for compensating for erroneously issued VCUs (statute of limitations: 6 years from issuance, or 12 months after a subsequent verification report, whichever is later).
Key Takeaways
- 1VCUs are either retired (permanently consumed for an offset claim) or cancelled (removed for technical/regulatory reasons) - never both
- 2The AFOLU pooled buffer account is non-tradeable insurance: buffer credits are deposited at issuance and cancelled if a reversal event occurs
- 3Buffer credits can be released back as marketable VCUs every 5 years (15% of accumulated buffer per release) if no reversals have occurred
- 4Every VCU embodies 9 program attributes including additionality, durability, independent verification, and SDG alignment
- 5Project proponents must submit verification every 5 years or receive 'late to verify' status, and carry liability for erroneously issued credits for up to 6 years