Three linked checkpoints distinguish project registration, registered reductions and registry status. Intended use is checked separately.
Follow the records from the project to the specific units before assessing their intended use.
Diagram text description

The featured diagram has three ordered record checkpoints: project registration, registered reductions and registry status. The arrows show the order in which a buyer can trace evidence, not automatic issuance or transfer. A final note separates the intended-use check from those records. The graphic shows no actual registry entry, quantity, approval or eligibility determination.

A seller sends you a project registration record and asks whether your company can buy and use its carbon credits. The record may identify a registered project, but it does not tell you whether any of its reductions have been registered, whether the seller holds the units being offered, or whether those units can be used for your stated purpose. In China's voluntary carbon market, those are separate questions. Ask for evidence for each one before treating the offer as ready to approve.

China Certified Emission Reductions (CCERs) are project reductions registered under the interim measures for voluntary greenhouse gas emission reduction trading. Article 22 expresses the quantity in tonnes of carbon dioxide equivalent (tCO2e). That is a measure of the greenhouse gas reduction or removal, expressed in a common unit. It is not tonnes of elemental carbon, a count of projects or a measure of the buyer's own emissions. A CCER is also distinct from an emissions trading system allowance: one represents registered project reductions; the other is a unit in an allowance system. The measures contemplate certain uses of CCERs against allowance obligations under applicable national rules. That does not make the instruments interchangeable.

Start with the particular project and reduction period. Then trace the registered quantity to the holder and current status. Article 6 makes the registry record the final basis for determining attribution and status; Article 28 calls for cancellation in the registry when the credits are used for the specified purposes under applicable rules. Neither tells you, on its own, that a proposed purchase or public statement is suitable. The practical test below is whether a reviewer could follow your evidence from the project to the exact units and from those units to the stated use.

The ministry’s consolidated text records an amendment under the decision of 20 September 2026. The ministry’s consolidated text was accessed on 9 November 2026 (UTC). This guide explains the provisions shown in that text and the notices discussed below. It does not verify every current implementation rule or determine whether a particular project, buyer or proposed use is eligible.

What a CCER record does and does not establish

Read the heading on the record before reading the number. A project registration record concerns the project. A reduction registration record concerns a quantity produced by the project. A holding and status record concerns who holds the units and what their current registry status is. The same project name can appear in all three without making the documents equivalent.

RecordWhat it can establishWhat you still need
Project registrationThe identified project was registered under the project procedure.A matching reduction registration, including the relevant period and quantity.
Reduction registrationThe registry registered reductions for the identified project and period.Current registry evidence of the holder, available quantity and status for the units offered.
Holding and statusThe attribution and status the registry records for those units at the point checked.A separate basis for the intended use, and the cancellation record when that use requires it.

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

Row 1

Record
Project registration
What it can establish
The identified project was registered under the project procedure.
What you still need
A matching reduction registration, including the relevant period and quantity.

Row 2

Record
Reduction registration
What it can establish
The registry registered reductions for the identified project and period.
What you still need
Current registry evidence of the holder, available quantity and status for the units offered.

Row 3

Record
Holding and status
What it can establish
The attribution and status the registry records for those units at the point checked.
What you still need
A separate basis for the intended use, and the cancellation record when that use requires it.

When an offer arrives as a single PDF, separate its attachments by what they prove. Put the project identifier beside the reduction registration identifier and period. Match the registered quantity to the record of the units offered; the quantity registered for a period need not equal the quantity the seller holds today. If the seller is presenting an intermediary's confirmation, identify the actual holder rather than assuming the two entities are the same.

Date the holding evidence you relied on and note when it needs to be checked again. That date belongs to the evidence review, not to the reduction period. A technically valid older record can still be insufficient to answer a present-tense question about who holds the units. Leave that question open if you cannot match the current record to the offer.

Check the methodology, version and applicable dates

Ask the project team for the exact methodology code and version used in the project design and reduction accounting documents. Article 8 requires project methodologies to specify applicability, quantification and monitoring methods, validation and verification requirements, and the period within which reduction registration can be sought. The ministry's January 2026 Q&A described the methods issued in 2025 as an expansion of the areas the market could support. It explained how methodology requirements guide project development; it did not establish that any particular project had met them.

Next, read the signed notice and the clause governing its effect. The mangrove establishment notice for CCER—14—002—V02 is signed 8 October 2026. The afforestation notice for CCER—14—001—V02 is signed 9 October 2026. The notices appear on pages dated 10 October, but each says it takes effect 30 days after issuance. That is why recording the date at the top of the webpage is not a substitute for recording the signed notice and its operative clause.

Each notice also preserves the previous method for the projects described in its transition clause: projects registered under the named prior version in the national registration system and platform before the new notice takes effect. The notice for one method does not establish the transition for the other, and an application started before a change is not the same as a project already registered under the prior method. The project team's file should show which of those states it actually reached.

For the two methodology notices, a signed notice starts a 30-day interval before effect. Check prior registration against each notice’s transition clause.
Use the signed issuance and transition provision, not just the webpage date.
Diagram text description

The timeline moves from the signed notice through a 30-day interval to effect. Below it is the separate transition check for prior project registration. The interval is specific to the two methodology notices discussed in the text. Match each notice and prior version to the actual project registration record; the timeline does not establish eligibility for any project or any other methodology.

In the review record, keep the method and version, signed notice, effective provision, project registration date and reduction period in separate fields. Then write one sentence explaining why the version in the project documents applies to that project and period. If the timing or transition cannot be reconciled, request the actual method text and supporting project records before relying on the version. These notices illustrate how to make the check; they are not a complete list of eligible activities, a decision about another version, or evidence that any particular reductions were accepted.

Separate project registration from registered reductions

Project registration and reduction registration are decisions on different applications. Under Articles 14–15, the project owner submits the project application, design document and validation report, along with the required undertaking. The registry reviews completeness and conformity of the materials and registers a project that passes. That record does not determine how much the project later reduces or removes.

Under Articles 21–22, the project owner submits a reduction application with an accounting report and a verification report, and the quantity submitted must agree with the verified quantity. The registry reviews the reduction materials separately. Reductions registered through this procedure are the CCERs described by Article 22. A verified report and a registered quantity are therefore also distinct: the report supports the application, while the reduction registration records its outcome.

ApplicationMain evidence in the fileOutcome to check
Project, Articles 14–15Project application, design and validation report, with the project undertaking.Project registration and its identifier.
Reductions, Articles 21–22Reduction application, accounting and verification reports, with the accounting undertaking.Reduction registration for the stated project, period and quantity.

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

Row 1

Application
Project, Articles 14–15
Main evidence in the file
Project application, design and validation report, with the project undertaking.
Outcome to check
Project registration and its identifier.

Row 2

Application
Reductions, Articles 21–22
Main evidence in the file
Reduction application, accounting and verification reports, with the accounting undertaking.
Outcome to check
Reduction registration for the stated project, period and quantity.

This difference matters when an offer cites a project design forecast. A forecast belongs with the design; it may explain what the project is expected to achieve but is not the quantity registered for a past period. Ask for the reduction registration and link it back to the same project. If the name matches but the identifier or period does not, resolve that mismatch instead of copying the larger or more recent figure into the purchase file. Even after the amounts reconcile, the seller's current registry holding remains a separate check.

Project design, validation and registration

Project registration begins with a design tied to the applicable methodology. Under Article 11 the project owner prepares the design document and commissions a qualified validation and verification institution to validate the project. In a project team's file, the design should make it possible to connect the activity, the methodology and the monitoring approach. A reader should be able to see what will be measured and which records will be retained when the team later accounts for the reductions.

Article 12 requires public disclosure of the design document and the institution's name through the registry before the application. Article 13 calls for a validation report with an affirmative or negative conclusion and an account of how the owner dealt with public comments. When reviewing the record, identify the report that corresponds to the design being relied on. If the file contains several versions, a report for an older design does not explain a later change simply because the project title is unchanged.

Articles 14–15 take the project from those documents to a registration application. The project owner provides the application and supporting files, and undertakes responsibility for project uniqueness and the authenticity, completeness and validity of its materials. The registry checks the submission. Record the project registration result and the validation institution's name; both will be useful later, but for different reasons. The project identifier connects the eventual reduction record to its project. The institution's identity lets you check who may verify the reductions.

For a buyer, the useful outcome at this stage is a traceable project, not a figure to put in the purchase agreement. The project owner can share a registration record and a design estimate while the period-specific reductions remain unregistered. If all you have is the project file, say so plainly. Ask next for the reduction accounting period and registration, and separately for the seller's current holding. Do not describe the project file as evidence that either already exists.

Reduction accounting, verification and registration

After project registration, the team still has to account for the reductions it is applying to register. Article 18 requires a reduction accounting report prepared under the applicable method and technical rules. The project owner monitors implementation and retains the underlying records. For a review, connect the quantity in the report to the project identifier, the period and the monitoring records that support that period. Avoid substituting a design-stage estimate for the measured and calculated basis of the later application.

Commission reduction verification separately. Article 18 bars the institution that validated the project from verifying that project's reductions. This is a project-wide separation, not a rule confined to one issuance cycle or one member of staff. Compare the institution identified in the original validation report with the institution identified in the reduction verification report. A different signature or team name is not enough if the institution itself is the same.

Under Articles 19–20, the accounting report and the name of the institution commissioned for verification are disclosed through the registry before the application. The verification report determines the verified quantity and explains how public comments were handled. This report gives the reviewer a quantity and a basis to examine; it is not the registry's registration decision. Under Articles 21–22, the project owner applies using the quantity determined in the verification report, and the registry registers reductions after the separate materials review.

Reduction accounting leads to verification and then registration. The institution that validated the project cannot verify its reductions.
The verified quantity supports a separate application for reduction registration.
Diagram text description

Three vertically connected stages distinguish the project owner’s reduction account, the verifier’s report and the registry decision. A note alongside verification states that the institution that validated the project cannot verify these reductions. This applies to the project, not just a single issuance cycle. The registered quantity is not a record of a buyer’s holdings.

To reconcile the records, compare the reporting period and quantity on the application with the verification result and the eventual reduction registration. Express registered quantities in tCO2e. If the accounting report claims more than the verifier accepted, the higher claim does not belong in the purchase file. If the verified and registered records disagree, resolve which period and records are being compared before using either figure. A discrepancy is an evidence problem, not a reason to average the figures.

The sequence ends with registered reductions, not with a transfer to your account. Save the final registration alongside the earlier reports so another reviewer can reconstruct how the recorded quantity was reached. Then start a different check: whether the holder offering the units has the relevant quantity and status in the registry.

Check holdings, transfer and cancellation separately

A trade confirmation records a transaction; a registry holding record shows the resulting attribution and status. Under Article 26 the registry updates quantities and holding status based on the transaction results supplied by the trading institution. Under Article 6 its records are the final basis for judging attribution and status. When the two records serve different purposes, keep both rather than treating the exchange confirmation as a substitute for the registry entry.

Point in the transactionRecord to inspectLimit of that record
Before the tradeCurrent registry holding and status for the seller or actual holder.Does not establish that the buyer already holds or has used the units.
After the tradeTransaction confirmation plus the corresponding registry change.Does not show cancellation or establish permission for a use.
For a use requiring cancellationRegistry cancellation record linked to the relevant units and stated use.Does not by itself substantiate every part of a public claim.

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

Row 1

Point in the transaction
Before the trade
Record to inspect
Current registry holding and status for the seller or actual holder.
Limit of that record
Does not establish that the buyer already holds or has used the units.

Row 2

Point in the transaction
After the trade
Record to inspect
Transaction confirmation plus the corresponding registry change.
Limit of that record
Does not show cancellation or establish permission for a use.

Row 3

Point in the transaction
For a use requiring cancellation
Record to inspect
Registry cancellation record linked to the relevant units and stated use.
Limit of that record
Does not by itself substantiate every part of a public claim.

Make the matches explicit. Check that the buyer and seller named in your records are the parties whose status matters, that the quantity reconciles, and that the registry update concerns the same units as the trade. An invoice or payment receipt can show that money moved. It cannot answer whether registry records changed, which units moved, or whether the buyer may use them as proposed.

Cancellation is another action. Article 28 requires it for the specified uses under applicable national rules; it also encourages voluntary cancellation for public-interest purposes. Do not infer cancellation from a change in the holder's balance. Save the relevant cancellation record when the intended use requires it. If the supporting record is absent, describe the confirmed state without upgrading it: traded, held and cancelled answer different questions.

Confirm the intended use before making a claim

Define the intended use in writing before you ask whether a CCER qualifies. A compliance team assessing an allowance obligation, an event organiser evaluating a neutrality statement and a company considering a statement about its greenhouse gas emissions have different questions. Article 28 identifies those types of uses under national rules and requires registry cancellation when units are used for them. It does not give this buyer a general permission or a universal percentage limit.

For an allowance obligation, identify the scheme and compliance period, then have the responsible reviewer check the rules that apply to the particular entity, units and purpose. For a public statement, keep the emissions boundary, calculation and proposed wording with the evidence for the credit use. A cancellation record may support a narrow statement about the units cancelled. It does not establish that a corporate inventory is complete, that reductions occurred within the company's own operations, or that the full wording is supportable.

Cross-border questions need their own review. Article 29 says the specific rules for cross-border trading and use are to be formulated separately by the ministry with relevant departments. A CCER registration record is not proof of universal foreign buyer eligibility, permission to use the credits abroad or authorization under Article 6 of the Paris Agreement. Nor does Article 29 by itself tell you that a particular transaction is permitted or prohibited. Confirm the relevant rules and any required authorization for the actual parties and use before drawing a conclusion.

Write the reviewer’s decision against the exact use proposed. If the company changes that use, for example from a procurement holding to a public statement, check it again rather than inheriting the earlier sign-off. Keep the procurement evidence and the intended-use decision in separate files or fields. That way a well-documented holding does not accidentally appear in a board paper or a customer-facing statement as proof of an approved claim.

Work through an incomplete buyer file

Consider a fictional buyer file. A manufacturer receives an offer from a seller that attaches a project registration record. The buyer wants to know whether it can acquire the units and refer to them in a public statement. The four rows below show what the file actually contains.

Evidence requiredStatus in this fictional fileDecision and next action
Project registrationPresent. The record identifies the project named in the offer.Retain the record and its identifier. It establishes the project step only.
Reduction registration identifier and periodMissing. No separate registry record shows the reductions being offered.Request the identifier, period and registered quantity. Do not infer units from project registration.
Seller's registry holding and statusMissing. The offer names the seller but supplies no current holding evidence.Request a matching registry record for the actual holder and offered units. Do not assume the seller holds them.
Basis for the intended useMissing. The proposed statement is not tied to an applicable rule or approval.Send the exact use and wording for separate review. Do not issue the statement.

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

Row 1

Evidence required
Project registration
Status in this fictional file
Present. The record identifies the project named in the offer.
Decision and next action
Retain the record and its identifier. It establishes the project step only.

Row 2

Evidence required
Reduction registration identifier and period
Status in this fictional file
Missing. No separate registry record shows the reductions being offered.
Decision and next action
Request the identifier, period and registered quantity. Do not infer units from project registration.

Row 3

Evidence required
Seller's registry holding and status
Status in this fictional file
Missing. The offer names the seller but supplies no current holding evidence.
Decision and next action
Request a matching registry record for the actual holder and offered units. Do not assume the seller holds them.

Row 4

Evidence required
Basis for the intended use
Status in this fictional file
Missing. The proposed statement is not tied to an applicable rule or approval.
Decision and next action
Send the exact use and wording for separate review. Do not issue the statement.

The buyer has enough evidence to identify the project but not enough to conclude that the units exist in the offered quantity, that the seller holds them, or that the stated use is allowed. A project registration may be genuine and still leave all three questions unanswered. Record the missing evidence against the actual decision, rather than writing a general request for more information.

The buyer must obtain the reduction registration identifier and period, the seller's current holding evidence and the applicable basis for the intended use. Until those questions are resolved, the evidence is insufficient: do not approve a purchase or make a public claim. A new accounting report alone would close none of the registry holding or use questions.

If the seller supplies a later record, match it back to the original project before changing the status of that row. The buyer might resolve the registered quantity and still have an open holding or use question. Record that partial result explicitly. It is more useful to the next reviewer than labelling the entire file either approved or rejected.

Request the missing evidence before the decision

Start with the record that is missing, not with a conclusion about the credit. For the fictional file, ask the project owner or seller to produce the reduction registration identifier, covered period and registered quantity that match the project. Ask the actual holder for current registry evidence for the offered units. Have the intended-use reviewer identify the applicable rule and check the exact statement or use proposed. Keep both holdings and intended use marked unresolved until those records support a decision.

If the trade later goes ahead, reconcile its result with the registry update under Article 26 rather than relying on payment evidence. If the applicable use requires cancellation under Article 28, keep the matching registry cancellation evidence. Neither payment nor a trade confirmation can stand in for that status or demonstrate that the wording of a claim is permissible. For a cross-border proposal, Article 29 points to separate rules; do not infer foreign buyer eligibility, Article 6 authorization or claims compliance from domestic registration.

Give each outstanding item a named owner and a decision consequence. Without the reduction registration, there is no basis in the file for the offered registered tonnes. Without the current holding record, there is no basis for confirming that the seller can supply those units. Without the use basis, there is no decision to make the proposed statement. The fictional file has all three gaps, so request the records and withhold purchase and claim approval. That conclusion does not label the project invalid. It keeps the decision no stronger than the evidence, which is the point of following a CCER from project to use.