07 / Chain stage
What is revenue recognition?
The point at which the operator may record income from the capacity — which happens once the contract's conditions are met, and which the company must disclose before it can be treated as fact.
(In simple terms: the operator can finally record the money.)
Why AI needs it
This is the end of the chain and the only stage that pays for all the others. It is also the stage most frequently assumed rather than evidenced: a signed contract is read as revenue, and acceptance is read as billing. Neither follows.
How it works
- Capacity is accepted under the customer agreement.
- The contract's conditions for billing are met, which may lag acceptance.
- The operator begins billing and discloses that it has done so.
- Revenue is recognised in the accounts under the applicable standard, which may differ again from both billing and cash receipt.
Inputs and outputs
- Made of
- A contract, delivered capacity, and an accounting policy.
- Takes in
- Accepted capacity and satisfied contractual conditions.
- Produces
- Disclosed billing, and eventually recognised revenue and cash.
Where it gets stuck
Billing, GAAP recognition and cash receipt are three different events that companies disclose with varying precision, and T2C never assumes one from another. A contract does not imply acceptance, and acceptance does not imply billing.
A general statement about the technology. It is not a claim about any named project — where T2C can evidence a specific delay, it appears in the intelligence ledger with its source.
Where it sits in the chain
Who sells to whom. The operator is finally paid for the megawatts.
T2C tracks the delivery end of this chain. An upstream stage is shown as having happened — capacity cannot be billing unless the parts were made — and simultaneously as untracked, because no supplier, order or shipment record sits behind it.
Public companies in this area
T2C holds no sourced supplier record for this component yet.