A take-or-pay clause is a contract provision under which a buyer agrees to pay for a minimum quantity of a good — cells, raw materials, energy, or processing capacity — over the term of an agreement, whether or not the buyer actually takes delivery of that quantity. The clause exists to allocate volume risk. It gives the supplier a guaranteed revenue floor against which to finance a plant or a mine, and it gives the buyer secured access to constrained supply. In a battery supply chain where lithium, separators, and finished cells have all faced periods of scarcity, take-or-pay is the mechanism that underwrites a new production line: the producer builds capacity because someone has contractually agreed to pay for the output even in a soft market.
Because a take-or-pay commitment is a fixed future cash obligation, it is disclosed in SEC filings rather than left in the contract alone. Filers report the minimum amounts as contractual obligations, typically in the purchase-obligations line of the disclosures around liquidity and commitments. FMC Corporation, a lithium and materials producer, describes the structure plainly in its Form 10-K filed with the U.S. Securities and Exchange Commission, explaining that it has entered into purchase obligations where take-or-pay arrangements apply.
"We have entered into a number of purchase obligations for the sourcing of materials and energy where take-or-pay arrangements apply."— SEC, FMC Corporation Form 10-K, source
How take-or-pay is measured and disclosed
The disclosure detail that matters most is whether the minimum is measured year by year or over the life of the contract. FMC's filing is explicit on this point: it states that the majority of its minimum obligations under these contracts are take-or-pay commitments over the life of the contract and not a year-by-year take-or-pay, and that, as a result, the obligations are presented in the earliest period in which the minimum could become payable. That distinction changes how a reader should interpret the commitment table. A life-of-contract minimum gives the buyer flexibility to under-take in any single year as long as the cumulative minimum is met by the end, while a year-by-year minimum is a harder annual obligation. The same headline dollar figure can therefore represent very different degrees of rigidity depending on which structure the filing describes.
For a battery-sector reader, the practical consequence is that a take-or-pay commitment converts a supply agreement from a flexible purchasing relationship into a fixed liability. If demand falls below the contracted minimum, the buyer still owes the minimum payment — the "pay" half of "take-or-pay" — which is why these clauses show up in risk and liquidity discussions, not just in the operations narrative. From the seller's side, the same clause is the asset that makes a new gigafactory or refining line financeable, because lenders can underwrite contracted minimum revenue rather than speculative spot sales.
The reason take-or-pay has become so prevalent in the battery supply chain specifically is the timing mismatch between when capacity is built and when it earns. A cell plant, a cathode line, or a lithium-conversion facility requires large upfront capital and years of construction before it produces at scale, and the producer needs financing to bridge that gap. A lender or equity investor evaluating that capital is exposed to the risk that, by the time the plant is running, prices have fallen or demand has softened. A take-or-pay commitment from a creditworthy buyer transfers that volume risk off the producer and onto the buyer, which is precisely what makes the project bankable. In a sector that has lived through sharp swings in lithium and cell pricing, the clause is the contractual device that lets new domestic capacity get financed despite that volatility — the buyer pays a premium in flexibility for security of supply, and the producer accepts a price ceiling in exchange for a revenue floor.
That trade has a symmetric downside disclosure: the same buyer that secures supply through a take-or-pay also books a fixed obligation it cannot escape by simply buying less. This is why the commitment surfaces in the liquidity and contractual-obligations sections of a 10-K rather than only in the operations narrative — it is a future cash outflow with the same character as a lease or a debt maturity, payable whether or not the buyer needs the product. A reader scanning a battery buyer's filing for hidden fixed costs should treat disclosed take-or-pay minimums as exactly that.
Reading a take-or-pay term in a real filing
When a take-or-pay clause appears in a 10-K, the questions that determine its significance are consistent: What is the minimum quantity or dollar amount? Over what term? Is the minimum annual or cumulative over the life of the contract? And what is the counterparty's standing? FMC's disclosure answers the structural questions — purchase obligations for materials and energy, measured over the life of the contract, presented at the earliest payable period — while the per-unit pricing typically remains inside the agreement rather than in the narrative. That boundary is normal: the filing establishes that a binding minimum-payment obligation exists and how it is measured, without necessarily revealing the contracted price.
The term is frequently confused with an offtake agreement, and the two are related but not identical. An offtake agreement is the broader long-term purchase commitment for a project's output; a take-or-pay clause is a specific provision — which may sit inside an offtake or a supply agreement — that fixes the buyer's minimum payment regardless of delivery. Put differently, take-or-pay describes the obligation's teeth: it is what makes a minimum-volume promise enforceable as a payment even when no product changes hands. In battery supply contracts, that is precisely the feature that turns a memorandum of intent into a financeable commitment, and it is why the phrase, when it appears in an SEC filing's purchase-obligations disclosure, is doing real economic work rather than serving as boilerplate.
Comments
Loading comments…