A person in a green sweater reviews papers with forest, river and seedling photographs beside a folder and a pale narrow paper.
Conceptual purchase-document review, not evidence of a real project, payment, serial number or retirement.
Diagram text description

Synthetic tabletop scene showing a person in a green knitted sweater holding papers. The central page contains landscape and seedling photographs; a narrow page has faint plant symbols and unreadable lines. A folder, pen, plant, cup and glass are nearby. No legible seller, amount, unit identifier, customer name or official approval is visible.

Carbon-credit payments go first to the seller or authorised collection intermediary specified in the transaction documents. That may be a project developer, a rights-holder, a trader or a retailer. It is not necessarily the landholder or community shown in the project photographs. To establish where the money ultimately went, follow the sale agreement, settlement evidence and any onward-payment or benefit-sharing records.

Keep a second trail for the credits themselves. Project identifiers, serial numbers, transfers and retirement records concern the units and their status. They do not, by themselves, reveal the seller's margin or prove that a local beneficiary received a share of your payment.

The practical task is therefore to reconcile two trails, not find one universal recipient. Start with the counterparty you paid, identify the parties behind the project, then distinguish what is documented from what remains unknown. The fictional payment-trace record below shows how to do this without inventing a revenue split.

The first recipient is the seller on your contract

Read the legal seller's name in the contract alongside the invoice and settlement instructions. Check whether the recipient is acting for itself or collecting for another party. An intermediary may appear in the payment chain even when the underlying sale is with a developer. A different bank-account name needs an explanation and appropriate authorisation; it should not be treated as a harmless spelling variation.

For example, a seller might instruct a buyer to pay a named collection agent. The relevant question is what document authorises that agent to receive funds for this sale and whether payment discharges the buyer's contractual obligation. The buyer's finance team should reconcile the approved instruction and actual settlement rather than relying solely on a website payment button.

That establishes an immediate recipient, not an ultimate beneficiary. Project documents and benefit-sharing agreements may identify different parties with economic interests. The invoice can be correct while providing no evidence about their receipts. Ask separately whether an onward amount was payable, to whom, for which period and whether it was actually delivered. Keep the answers distinct from the simple fact that the invoice was paid.

Buying directly from a project developer

A direct purchase usually means contracting with a developer or rights-holder rather than buying inventory from a separate reseller. Check who has authority to sell the specified units, whether they already exist and what the agreement requires for delivery. The label “direct” describes the commercial relationship; it does not remove the need for documentary checks.

Imagine a fictional developer selling credits from its own project account. A buyer's payment to that developer can establish the first cash leg when the contract and settlement match. Unit delivery still needs its own registry evidence. If landholders or a community are entitled to proceeds, their agreements and onward receipts are a further inquiry. Paying the developer is not proof that every entitled party has been paid.

The development business may also have investors, operating costs, audit expenses and contractual obligations. Do not assume the whole purchase price is available for local distribution, or that every expense is an undisclosed commission. Request the relevant project-specific explanation. Where commercially sensitive terms are unavailable, describe the limit on your knowledge instead of substituting an industry-average percentage or a seller's general statement about supporting communities.

Buying through a broker or marketplace

A business described as a broker or marketplace can occupy different roles in different transactions. Establish the role for this contract before interpreting the invoice. The trading name alone does not tell you whether the intermediary owns the units, arranges someone else's sale or handles collection and retirement as a service.

Role in this saleWhat the buyer needs to establishWhat cannot be assumed
Principal resellerSeller identity, right to deliver the contracted units and agreed priceThat the buyer's entire payment is passed to the developer
Agent arranging another seller's saleNamed seller, agency authority, collection arrangements and disclosed service termsThat the agent owns the credits or receives the whole price as its fee

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

Row 1

Role in this sale
Principal reseller
What the buyer needs to establish
Seller identity, right to deliver the contracted units and agreed price
What cannot be assumed
That the buyer's entire payment is passed to the developer

Row 2

Role in this sale
Agent arranging another seller's sale
What the buyer needs to establish
Named seller, agency authority, collection arrangements and disclosed service terms
What cannot be assumed
That the agent owns the credits or receives the whole price as its fee

For a principal, an earlier purchase of inventory may have funded the project before your transaction occurred. Your later payment is then revenue for the reseller, not necessarily a new remittance to the developer. For an agent, the agreement may separate a service fee from money collected for the seller. These structures require different evidence requests.

Fees, spreads and onward payments remain contract-specific. A registry transfer may identify accounts involved, but it does not provide the financial calculation behind their commercial terms.

A registry transfer is not a payment trail

Reconcile the cash trail and unit trail through common transaction references, while recognising that they answer different questions. The contract, invoice and settlement record help establish who was owed and who received payment. Programme, project, serial, transfer and retirement records help establish what units were involved and what happened to them.

The diagram separates buyer payment and seller receipt from unit transfer and retirement. There is no connecting arrow claiming that a retirement proves a payment, or that settlement proves a credit has been issued. Transfer may be followed by holding or resale rather than retirement; any retirement must be established separately under the relevant programme's process.

Separate arrows connect buyer payment to seller receipt and unit transfer to retirement; no arrow equates the money trail with the unit trail.
Illustrative evidence map, November 2026: cash settlement and unit status require separate records. Transfer does not guarantee retirement, and neither path proves onward benefit.
Diagram text description

Four boxes form two independent horizontal relationships. Payment and receipt are reconciled through transaction and settlement evidence. Unit transfer and any subsequent retirement are checked through programme and registry records. Holding or resale can intervene. No connection claims that settlement proves issuance, retirement proves onward payment, or either authorises a public claim.

For a retailer retiring units on a buyer's behalf, reconcile the quantity, project, credited period, serial range and retirement purpose or beneficiary with the contract. Do not presume a buyer-controlled registry account is necessary in every retail arrangement, but do require evidence that matches the service purchased.

A retirement record can support the traceability of a proposed use; it is not blanket permission for any public claim. Nor does it establish what the developer received from a previous sale. If the two trails cannot be reconciled, retain the discrepancy and identify the missing evidence rather than treating one document as a substitute for all the others.

Does the standard-setter receive the credit price?

The standards body is not automatically the seller of the credits. In its VCS guidance, Verra distinguishes its framework-setting role from the carbon finance that project proponents may obtain using issued units. Its published FAQ also separates programme fees from external project-development costs. Those distinctions matter when someone asks whether a payment goes to “the certifier”.

A standards body sets programme rules. A validation or verification body performs an independent assessment under those rules. A registry records units and relevant account actions. A project developer organises project activity, while the seller is the counterparty in the particular sale. One organisation may perform more than one commercial function, but the roles should not be collapsed merely because their names appear in the same document pack.

An invoice for registration, verification or a registry service is not the same thing as the credit purchase price. Ask which service a fee covers, who charges it and whether it is already included in the seller's quote. Do not deduct a generic programme fee from the sale price and call the remainder a community benefit. The transaction and project agreements determine the relevant financial obligations.

How much reaches landholders and local communities?

Landholders, developers, investors and local communities can have different rights and different forms of benefit. A project proponent named in programme records is not necessarily the sole economic beneficiary, and a person living near a project is not automatically entitled to a fixed share of each retail sale. Establish the applicable agreements and context before describing either entitlement or receipt.

Consider a fictional forest project whose benefit-sharing plan promises support through a community fund. That plan identifies an intended mechanism, but a buyer would still need to understand the fund's beneficiaries, governance, payment basis and reporting period. A promised transfer, a deposit into the fund and a completed local activity are different events. Evidence for one should not be presented as proof of all three.

Ask for the relevant plan or agreement, how affected people were involved, what outcomes are reported and whether the reporting can be corroborated. Respect legitimate privacy and legal restrictions; a credible summary or independent report may be more appropriate than publishing personal bank details.

There is no defensible global percentage of every credit price that must reach communities. Equally, missing distribution information does not prove that no benefit occurred. It limits the statement you can support. If local benefit is central to the purchase decision, make the evidence requirement explicit before committing to the transaction.

When does the money arrive?

Payment and credit events can occur on different dates. A forward agreement may provide an advance before credits are issued, while a spot transaction may involve already-issued units and settlement linked to delivery. The precise sequence, conditions and remedies come from the contract, not the word “carbon”.

EventEvidence to retainDistinct question
Forward advanceContract and settled payment recordWhat has been funded before issuance?
IssuanceProgramme and registry recordDo the specified units exist?
Delivery or transferMatched account/serial recordWere the contracted units delivered as agreed?
SettlementInvoice and receipt reconciliationWas the amount paid to the authorised recipient?
RetirementMatched final-use recordWere those units taken out of circulation for the stated purpose?

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

Row 1

Event
Forward advance
Evidence to retain
Contract and settled payment record
Distinct question
What has been funded before issuance?

Row 2

Event
Issuance
Evidence to retain
Programme and registry record
Distinct question
Do the specified units exist?

Row 3

Event
Delivery or transfer
Evidence to retain
Matched account/serial record
Distinct question
Were the contracted units delivered as agreed?

Row 4

Event
Settlement
Evidence to retain
Invoice and receipt reconciliation
Distinct question
Was the amount paid to the authorised recipient?

Row 5

Event
Retirement
Evidence to retain
Matched final-use record
Distinct question
Were those units taken out of circulation for the stated purpose?

This table is not a mandatory order for every deal. A seller may arrange retirement on the buyer's behalf, and an advance can precede delivery by a substantial period. Keep the actual dates and conditions visible. An advance does not prove issuance, delivery or retirement; a delayed payment also does not, by itself, show that an otherwise documented registry action never occurred.

Do not confuse allowances with project credits

Identify the instrument before asking who gets paid. A voluntary project credit is connected to a crediting activity under a programme. A compliance offset is a project-based instrument whose permitted use depends on the relevant regulatory scheme. An emissions allowance is different: it is an instrument in an emissions-trading system, not automatically a credit issued to an offset project.

For allowances, a primary auction and a secondary-market purchase have different immediate counterparties and proceeds arrangements. You cannot assume that either sends the price to a forest developer. For project credits, a government role in authorisation or oversight likewise does not make the government the seller in every transaction.

Search results and sales pages sometimes use “carbon credit” loosely for several instruments. Ask for the precise programme, unit type and intended use, then follow the relevant sale and account records. A voluntary unit is not automatically acceptable for a regulatory obligation, and a scheme's eligibility rules do not establish who received the commercial proceeds. This guide explains payment tracing, not a determination of legal eligibility for a particular jurisdiction or buyer.

Documents to request before claiming where your money went

Create a payment-trace record before turning a purchase into a public story about project finance or local benefits. Keep supplied assertions separate from established receipts. Record the reviewer and review date so someone else can see both the evidence available and the questions still open.

Fictional filled payment-trace record: Northbank Components Ltd, reviewed by finance lead Leena Shah in November 2026. Every company, document identifier, amount and date below is invented.

FieldKnown transaction record
BuyerNorthbank Components Ltd
Contractual seller and invoice payeeCedar Bridge Trading Ltd
Seller rolePrincipal reseller under signed sale CB-104
Contracted quantity100 project-based voluntary credits, subject to delivery terms
InvoiceCB-104-1: US$2,500, excluding taxes
SettlementUS$2,500 received by the named seller on 20 October 2026
Supporting cash evidenceSigned CB-104, invoice and reconciled bank confirmation
Project reference suppliedSeller's description of a forest project; exact programme/project ID not reconciled

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

Row 1

Field
Buyer
Known transaction record
Northbank Components Ltd

Row 2

Field
Contractual seller and invoice payee
Known transaction record
Cedar Bridge Trading Ltd

Row 3

Field
Seller role
Known transaction record
Principal reseller under signed sale CB-104

Row 4

Field
Contracted quantity
Known transaction record
100 project-based voluntary credits, subject to delivery terms

Row 5

Field
Invoice
Known transaction record
CB-104-1: US$2,500, excluding taxes

Row 6

Field
Settlement
Known transaction record
US$2,500 received by the named seller on 20 October 2026

Row 7

Field
Supporting cash evidence
Known transaction record
Signed CB-104, invoice and reconciled bank confirmation

Row 8

Field
Project reference supplied
Known transaction record
Seller's description of a forest project; exact programme/project ID not reconciled

The agreed illustration price is US$25 per credit, obtained by dividing the invented US$2,500 invoice by 100. It is not a current market quotation or evidence of project income. The buyer can substantiate its immediate payment to the seller in this example. The same documents do not establish what the seller paid for inventory, when that earlier purchase occurred or what any subsequent beneficiary received.

FieldOnward evidence and unit status
Seller-described project recipientValley Forest Cooperative; identity and receipt unverified
Amount reaching that recipientUnknown; no onward settlement evidence supplied
Ultimate local beneficiaryNot established from the supplied documents
Community or landholder paymentUnknown; no applicable agreement or outcome report supplied
Fees, margin and deductionsNot established from the purchase invoice
Exact unit serials and credited periodNot supplied or reconciled
RetirementNot established; no matched retirement record supplied
Review decisionHold retirement/offset and local-benefit claims pending evidence

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

Row 1

Field
Seller-described project recipient
Onward evidence and unit status
Valley Forest Cooperative; identity and receipt unverified

Row 2

Field
Amount reaching that recipient
Onward evidence and unit status
Unknown; no onward settlement evidence supplied

Row 3

Field
Ultimate local beneficiary
Onward evidence and unit status
Not established from the supplied documents

Row 4

Field
Community or landholder payment
Onward evidence and unit status
Unknown; no applicable agreement or outcome report supplied

Row 5

Field
Fees, margin and deductions
Onward evidence and unit status
Not established from the purchase invoice

Row 6

Field
Exact unit serials and credited period
Onward evidence and unit status
Not supplied or reconciled

Row 7

Field
Retirement
Onward evidence and unit status
Not established; no matched retirement record supplied

Row 8

Field
Review decision
Onward evidence and unit status
Hold retirement/offset and local-benefit claims pending evidence

The unknown onward amount is not zero. Nor is the difference between the buyer's payment and an unknown developer receipt a calculable broker margin. The seller is a principal in the fictional contract, so even a verified earlier inventory purchase would need its own date, quantity and price context before it could be compared with this resale.

There are two unresolved decisions. First, do the specified units match the contract and the proposed use, and has any required retirement actually occurred? Second, is there evidence of an applicable benefit-sharing arrangement and delivery to the identified beneficiary? The consequence is to hold claims that the purchase offset emissions or delivered a stated local benefit. A settled invoice alone cannot resolve either decision.

Leena requests the programme and project identifiers, exact unit details, delivery and retirement records, the basis for the named project recipient, and any applicable benefit-sharing terms and credible outcome reporting. If the seller cannot provide distribution evidence, the record retains that limitation. It must not be replaced by a photograph, a generic sustainability statement or an assumed percentage of the invoice.

For reuse, keep the field labels and replace the fictional values with your own evidence. Add document versions, the transaction reference linking the two trails, who supplied each record and any confidentiality restriction. Mark a field unknown when it is unknown; record the consequence where the missing information changes the decision. This is a buyer review aid, not a substitute for the contract, applicable programme rules or qualified advice on an actual transaction.

Keep the evidence together without overstating it

Keep the contract, invoice, settlement and unit records traceable alongside the relevant carbon-data files, but do not confuse document organisation with verification. A structured record can reveal a mismatch or missing attachment. It cannot establish the truth of an onward-payment assertion simply because the assertion has been entered into a database.

Assign distinct responsibilities: finance reconciles the authorised payee and settlement; the buyer checks the contracted unit and delivery evidence; the appropriate reviewer assesses project or benefit-sharing information and the proposed statement. Where specialist legal, accounting or programme interpretation is needed, obtain it from a qualified adviser rather than stretching a data-preparation task into an approval.

The useful outcome is a bounded answer: who you paid, what units were documented, what onward benefit was evidenced and what remains unknown. Preserve that boundary when communicating the purchase. A complete-looking folder is valuable only if its statements remain faithful to the underlying evidence.