Bulk Retirement for Compliance Teams: WattSwap's New Institutional Workflow

Compliance leads in mid-market and enterprise companies increasingly carry the responsibility for environmental attribute retirement and the documentation burden that comes with it. The Q3 2026 disclosure cycle has compressed timelines for many teams — CSRD audit windows, CDP Climate C11 assurance, and internal ESG sign-offs all stack against the same quarter, and the credits you retire need to land cleanly inside that window.

Today, WattSwap is shipping bulk retirement — a dedicated workflow that lets compliance and procurement leads retire RECs, GHECs, I-RECs, and voluntary carbon credits at scale in a single intake. From the buyer's side, it looks like one form, one confirmation, and an audit-ready retirement certificate at the end. Behind it sits the same WATT settlement layer that runs the public exchange, with manual institutional outreach added in front to confirm vintage, registry, and beneficiary details before settlement.

Why Bulk Retirement, Why Now

The retirement problem has not changed — environmental claims still require registry-issued retirement certificates, beneficiary designation, and serial-number traceability. What has changed is the cadence. Three forces are converging on compliance teams in 2026:

• CSRD and ESRS E1 deadlines. Wave 1 reporters filed in 2025; wave 2 is filing in 2026 with retrospective Scope 2 coverage that requires clean retirement trails for every MWh claimed. Mid-market filers under voluntary adoption are now being pulled in by their parent companies and supply-chain partners.
• CDP Climate C11 assurance. Limited assurance on retirement documentation has moved from a "nice to have" to a scored indicator. Providers that can't produce a serial-number cert per tranche within the request window get flagged for follow-up.
• Framework vintage recency. RE100 updated guidance in late 2025; ICVCM published its core carbon credit assessment criteria the same year. Auditors are now asking for vintage recency language in contract deliverables, pushing buyers toward newer-vintage credits sourced closer to the reporting period.

If your team is still buying credits one retail order at a time, the documentation cycle tends to run 4–8 weeks longer than the framework deadline. The new WattSwap workflow condenses that to a single intake call plus a settlement cycle. Read our carbon credits vs RECs primer for the conceptual backgrounder, and our corporate carbon offsets procurement checklist for the broader buying motion. For teams whose reporting falls under CSRD or RE100, our /compliance overview explains how WattSwap structures documentation to align with each framework.

How WattSwap Bulk Retirement Works

The workflow is built around a single intake. A compliance or procurement lead fills in the credit family, quantity, beneficiary legal entity, and contact email. WattSwap's institutional team does the manual outreach. Settlement then completes on the existing WATT rails. Four distinct stages:

1. Intake form

On /institutional, under the "Bulk retirement" form section, your team enters:

• Credit family — one of REC, VCC (voluntary carbon credit), GHEC, IREC, or CCC (compliance-grade). The form validates this against the same set WattSwap supports on the public exchange, so you cannot mistakenly request a credit class the platform doesn't trade.
• Quantity in MWh — integer and positive. There is no explicit minimum, but most institutional inquiries come in above 5,000 MWh, so the form is sized for that volume.
• Beneficiary name — exact legal entity as written in the issuing registry. This string lands on the retirement certificate verbatim, so it matters.
• Contact email — for the confirmation email and follow-up outreach.

Submitting the form posts to POST /api/institutional/bulk-retirement, returns a success message immediately, and fires a confirmation email through the Polsia email proxy to the address entered. The endpoint validates the credit family and quantity server-side; you get a 400 response with a human-readable error if either is malformed.

2. Confirmation email

Within seconds of submission, a confirmation lands in the contact inbox. The email restates the recorded request (credit family, MWh, beneficiary) and tells the contact that a member of the institutional team will reach out to confirm vintage, registry, and settlement before processing the bulk retirement. This is the artifact your team files in the inbound ticketing system — it's proof that the request was logged with a timestamp.

3. Manual outreach

The institutional team personally takes the request from there. The typical outreach covers four checkpoints:

• Vintage window. Which reporting period are you retiring into? Current calendar year, prior calendar year, or a multi-year spread?
• Registry or standard. M-RETS, PJM GATS, NEPOOL GIS, NAR, I-REC Standard, Verra, Gold Standard, ICVCM-correlated?
• Settlement. WATT-denominated payment against a quoted price, or fiat invoice through your AP system?
• Beneficiary format. Confirm the exact registry-side string for the retirement record — sometimes legal entity names diverge from common usage, and the registry is unforgiving.

This is where human + exchange is the model: the speed of an order-book platform with the procurement discipline a compliance team needs. There is no ambiguity at settlement, because every parameter is in writing before the credits move.

4. Execution on WATT settlement

Once the parameters are confirmed, the institutional team sources the credits on the public exchange, executes the matching portion of the trade against the platform's order book, and retires them through the issuing registry with the beneficiary designation on file. Each retirement emits a registry-issued certificate with serial numbers that trace back to WattSwap's settlement hash.

What the Workflow Delivers

For a compliance team, the output is what matters. Three artifacts come out of every WattSwap bulk retirement:

• Retirement certificate. Registry-issued, beneficiary = your legal entity, signed and dated. This is the document your auditor wants for the Scope 2 or Scope 3 claim.
• Record of trade fee. The 0.4% transparent fee structure that runs on the public exchange applies here as well. You'll see exactly what the trade cost in WATT or fiat terms, and how the fee broke down.
• Audit-trail timestamp. Settlement on WATT produces an immutable record linking the wallet, the trade ID, the registry serial numbers, and the retirement certificate. Pull this into your audit pack and your assurance partner has the timing chain they need.

Frequently Asked Questions

Which credit families are supported?

US RECs, I-RECs, GHECs, voluntary carbon credits (VCC), and compliance-grade carbon credits (CCC). The intake form validates against this exact set; unsupported families return a clear error before any record is created. If your reporting needs something WattSwap doesn't currently list — EU GOs, for instance — flag it in the outreach call and we'll quote an off-flow path.

Is there a minimum volume?

There is no hard minimum on the form, but the institutional pathway is designed for multi-thousand MWh retirements. Below 1,000 MWh it usually makes more sense to transact on the public exchange directly or through your existing procurement counterparty.

How long does settlement take from form submit?

Confirmation is instant; outreach happens within one business day; settlement depends on registry-side processing time but typically completes within 5–10 business days of confirmation. Your team will get a settlement-completion notification with the certificate attached.

Can the retirement naming be anything I want?

The beneficiary string must match a legal entity the issuing registry accepts. Most registries accept your company name or a specific subsidiary name with the exact spelling and corporate suffix (Inc., LLC, GmbH, etc.). WattSwap's outreach will sanity-check the string before any retirement is filed, so your audit file always lands with a clean beneficiary record.

What about documentation for our audit file?

Every bulk retirement ships with a documentation pack: the registry certificate, the trade receipt, the fee breakdown, and the settlement hash. If your reporting framework needs anything beyond the standard pack — assurance-ready verification statements, project metadata, vintage certificates — flag it during the outreach call and the institutional team will line it up.

What does it cost?

Pricing is sourced from the live order book on the public exchange plus the standard 0.4% platform fee. There are no surcharges for using the bulk-retirement pathway — you're paying the same fee structure as if you'd executed the trade yourself, with the institutional team handling settlement on your behalf.