How FPOs Can Negotiate Fair Benefit-Sharing in Carbon Projects

Every carbon project developer who approaches an FPO will tell the FPO it is getting a good deal. That is not because carbon project developers are uniformly dishonest, most are not. It is because 'good' is a relative term, and in the absence of a reference point, FPO leadership cannot evaluate whether what is being offered is genuinely fair.

This article is intended to be that reference point. It is written specifically for FPO secretaries, chairpersons, and board members who are evaluating a carbon project proposal, whether from Karimam or from any other developer. The principles here apply regardless of who is offering the deal.

Start With the Revenue Question

The single most important number in any carbon project contract is the farmer revenue share: the percentage of gross or net credit revenue that flows back to the FPO and its member farmers.

There is no industry-mandated minimum. This means that an unscrupulous developer can legally offer 10% to farmers and keep 90%, if the FPO agrees. We have seen contracts structured this way. They should not be signed.

A reasonable benchmark for fair revenue distribution in a well-structured agricultural carbon project, based on Karimam's own project economics and the comparative analysis of projects internationally, looks something like this:

• Farmers and landowners: 55–70% of net credit revenue

• FPO institutional fund (administration, record-keeping, coordination): 5–15%

• NGO implementation partner (training, monitoring, community support): 5–10%

• Carbon development company: 15–25%

• Verification and compliance reserve: 3–8%

Note that these are ranges, not fixed numbers. The exact split depends on the scale of the project (larger projects have lower per-unit costs, allowing more to flow to farmers), the complexity of the monitoring required, the methodology used, and the upfront investment the developer has made.

A reasonable benchmark: 55–70% of net credit revenue to farmers. If a developer is offering less than half the net revenue to the farming community, ask detailed questions before proceeding.

Gross vs. Net: The Definition That Changes Everything

One of the most important contractual distinctions in carbon project benefit-sharing is whether the farmer's percentage is calculated on gross credit revenue (the total amount received from credit sales before any costs are deducted) or net credit revenue (the amount remaining after verification costs, registry fees, and other project expenses are deducted).

A developer who offers 60% of gross revenue is being genuinely generous: that means the farmer gets 60 rupees out of every 100 rupees of credit sales, regardless of the developer's costs.

A developer who offers 60% of net revenue, where 'net' is defined as what remains after the developer has deducted all of its costs, including a generous management fee, travel costs, and other expenses it decides to classify as project costs, may actually be offering the farmer much less than 60% of gross. The devil is entirely in the definition of 'net.'

When reviewing any carbon project contract, the FPO should ask for a worked example: given a specific credit price (e.g., ₹1,000 per CCC) and a specific credit volume (e.g., 3,000 CCCs), what is the projected gross revenue, what are the specific costs that are deducted to arrive at net revenue, and what is the resulting rupee amount the farmer actually receives?

If a developer cannot provide this worked example, that is itself a red flag.

The Non-Negotiables: What Every Fair Contract Must Include

Beyond the revenue share percentage, there are several provisions that every fair carbon project contract should include, and whose absence should prompt hard questions.

Transparent Cost Accounting

The contract should specify which cost categories can be deducted from gross revenue to arrive at the figure on which the farmer's percentage is calculated. 'Reasonable costs' is not a sufficient definition. The contract should list specific categories: ACVA verification fees, registry issuance fees, buffer pool contribution, PDD development cost amortisation. Any cost category not specified in the contract should not be deductable.

Annual Reporting to the FPO

The developer should be contractually required to provide the FPO with an annual statement showing: total credits generated, total credits sold, price per credit, gross revenue, costs deducted, and net amount due to the FPO. This should be in language the FPO can verify, ideally audited by an independent party.

Payment Timeline

The contract should specify when payments are made to the FPO following credit sales, not 'within a reasonable time,' but within a specific number of days. Thirty to ninety days from the date of credit sale is a typical and reasonable range.

Early Exit Provisions

The contract should specify what happens if the FPO or its members want to exit the project before the crediting period ends. Exit provisions should be fair: they may require the FPO to repay credits already issued for activities it no longer intends to maintain, but they should not impose penalties that effectively trap the FPO in a project indefinitely.

Governing Law and Dispute Resolution

The contract should specify that it is governed by Indian law, and that disputes are resolved in an Indian jurisdiction accessible to the FPO, not in a distant city or through an arbitration process the FPO cannot afford to participate in.

Red Flags: Walk Away From These

There are specific contract provisions and developer behaviours that should cause an FPO to pause negotiations and seek independent advice before proceeding.

• Revenue share below 50% of net revenue to farmers and FPO combined, without a detailed and credible justification based on specific project costs.

• Vague or undefined cost deduction clauses, particularly any clause that allows the developer to deduct 'any other reasonable costs' without listing them.

• Contracts that assign the developer perpetual or very long-term rights over the FPO's land or carbon rights, beyond the specific crediting period of the project.

• Developers who are unable or unwilling to provide a worked numerical example of projected revenue distribution.

• Significant time pressure, 'sign this week or we lose the registration slot', which is a sales tactic, not a genuine constraint. Carbon project registration timelines are measured in months, not days.

• Absence of any reference to community consent processes or prior informed consent of individual farmer members.

• Contracts written only in English, with no Tamil translation available, presented to farmer members who are not English-literate.

Karimam's Own Commitment

We are writing this article with the awareness that some readers may be evaluating Karimam as a project partner. We welcome that scrutiny, and we apply the same standards to our own contracts that we describe here.

Karimam's founding principle is that the farmer's revenue share is set first: it is not a residual after all other costs are covered. In our project structures, farmers and FPO institutions together receive the majority of net credit revenue. We provide worked numerical examples during the negotiation process. Our contracts are available in Tamil. We do not impose early exit penalties beyond the repayment of credits issued for activities no longer being maintained.

If we do not meet these standards in a specific proposal, an FPO should ask us why, and should not sign until they are satisfied with the answer.

The carbon market is still being shaped. The norms for fair benefit-sharing are still being established. FPOs that demand fair treatment now, and walk away when it is not offered, are not just protecting themselves. They are raising the standard for the whole sector.

Priyan Rangith is the Founder and Managing Director of Karimam Global Ventures. Karimam's project revenue sharing frameworks are available in plain-language Tamil and English summaries upon request.