Mechanisms and worked studies
A revenue mechanism map and transparent scenario fixtures
How service becomes collectible receipts
Revenue stress should describe how the service loses collectible cash. A single reduction in a headline revenue line can be useful for a transparent screening calculation, but it cannot explain every failure mechanism. Fewer units delivered, a lower tariff, reduced availability, delayed collection and a disputed adjustment can produce similar cash totals through different paths. They imply different remedies and different parties able to act. The financing analyst should preserve this mechanism map before aggregating it into a cash schedule. Otherwise the downside becomes a number whose meaning cannot guide a decision.
Volume begins with the distinction between capacity and use. Technical capacity defines a possible operating envelope under stated conditions. Demand defines what users want and are willing to pay for. Accessible demand depends on connections, competing services, eligibility and commercial arrangements. Delivered volume adds actual operational performance. A forecast can therefore fail even when the engineering capacity is correct. The analyst should identify which transition the revenue model assumes and what evidence supports it. Financing based on theoretical capacity alone can expose the project to a commercial gap that additional equipment does not solve.
The value of customer commitment depends on its scope. An expression of interest can indicate engagement without requiring purchase. A volume commitment can contain conditions about availability, quality, access or price. An enforceable payment obligation can still depend on the payer's resources and the process for dispute resolution. The financial model should represent the cash mechanism supported by the arrangement, while legal advisers assess the obligation itself. Calling revenue contracted does not answer every demand, performance or collection question. The committee should know precisely which uncertainty the contract reduces and which uncertainty remains.
Tariff stress can affect cash directly or through changes in use. A higher price can improve receipts per delivered unit while reducing uptake or causing customers to seek alternatives. A lower price can support demand while leaving insufficient contribution to cover required costs. The analyst should not assume that price and volume change independently if the commercial mechanism links them. In a preliminary scenario, independence can be stated as a simplifying assumption. A financing case that materially relies on customer response requires evidence about the relationship and a sensitivity range consistent with the service and customer context.
Indexation should be examined as a mechanism with timing, conditions and limits. A tariff may adjust to a cost or inflation measure after a lag, at specified dates or subject to approval. It may compensate only part of the operating perimeter. The project can therefore face higher payments before receipts adjust. The model should identify the index, frequency, lag, caps and the party controlling approval, without assuming that a contractual reference guarantees immediate cash recovery. Where indexation is material, an adverse case should test both the amount of adjustment and the period over which the project funds the mismatch.
Availability-based revenue changes the source of demand exposure but can create performance exposure. A payment linked to service availability may reduce dependence on actual user uptake while requiring compliance with measurable standards. Deductions, acceptance, reporting and dispute processes can affect the amount and timing of collection. The project should therefore map the operational actions needed to earn the payment. Financing analysis should not replace demand uncertainty with an assumption that availability payments are automatically collected in full. The relevant evidence moves from customer use toward performance, measurement and payer obligations.
The time-resolution boundary appears in the calculation dictionary. The interface test here is conditional use: can protection be drawn for the actual shortfall mechanism under the agreed purpose and account terms? A source that is large enough but reserved for technical completion cannot be assumed available for operating service. The completed case keeps source capacity, permitted use and timed access as separate evidence objects so the failure of one is visible.
Concentration affects the response available to the project. A service dependent on a narrow customer or payer base can lose a large part of receipts when a single relationship deteriorates. Diversification can reduce that exposure, but it may require different service specifications, commercial expenditure or working capital. The model should not assume replacement customers can appear immediately after a lost commitment. A commercial mitigation plan needs an operating path, lead time and evidence. A broad addressable market is not automatically a funded substitute for a specific payer whose cash is missing at the debt-service date.
Revenue can also depend on a chain of performance outside the project's direct control. A logistics asset may need connecting infrastructure; a service facility may need a customer's upstream activity; an energy asset may need transmission or purchase acceptance. A revenue stress should identify whether the project can restore the dependency or merely wait for another party. Contractual risk allocation can alter who bears the financial effect, but the service interruption can remain. The committee should examine both the compensation mechanism and its collection timing. An eventual entitlement may not meet a near-term operating or lender payment.
The ramp should connect commercial readiness to operational readiness. An asset can be technically available before customers complete their own preparations, and customers can be ready before the asset passes acceptance tests. A forecast that assumes full use from the first operating period may require coordination evidence rather than a general market growth argument. The illustrative delayed-ramp study changes early cash while preserving later cash and service. It does not identify a measured demand trajectory. Its purpose is to demonstrate how an otherwise attractive long-horizon series can encounter a financing gap when early receipts arrive differently from the assumed calendar.
Pass-through should be assessed from both sides of the contract. A cost that can be charged to a customer may still be subject to verification, approval, caps or disagreement. A customer may be legally obliged to pay but economically unable or commercially unwilling to continue using the service on revised terms. The analyst should therefore separate entitlement, invoicing and collection. This is not a presumption that pass-through fails. It is a requirement to identify what would make it work and which delay or limit the cash schedule must absorb. A label such as reimbursable cost is not a complete cash mechanism.
Stress combinations should be economically coherent. A demand decline can reduce variable operating expenditure while leaving fixed obligations intact. A price adjustment can change volume. An outage can reduce delivered units and trigger deductions simultaneously, but some deductions may overlap with the lost payment. The analyst should document these links and avoid counting the same lost receipt repeatedly under different names. A combined stress can be severe without being arbitrary. Its usefulness depends on explaining the joint event and how each affected cash line follows from that event.
Mitigation should change the mechanism causing the shortfall. Commercial diversification can address customer dependence; improved collection administration can address avoidable delay; performance investment can address availability deductions; restructured tariff terms can address a mismatch between costs and receipts. A reserve can fund an interval while these actions occur, but it does not replace them. The committee should ask who owns each action, what cash or time it consumes and what evidence would demonstrate success. A mitigation described only as management attention cannot be included as an assured cash improvement.
The revenue decision should retain an affordability perspective when users or public payers bear the consequence of adjustment. A financing structure can restore project coverage by raising charges or securing compensation while transferring pressure to another party. That may be a legitimate policy or commercial choice, but it should be explicit. The asset's collectible revenue depends in part on the sustainability of that party's obligation. The analytical perimeter therefore includes incidence as well as project receipts. A financier should not treat contractual protection as the end of the analysis when the protected revenue mechanism undermines the service's continued use or payer capacity.
The practical output is a revenue mechanism map linked to the cash schedule. Each material source of receipts has a quantity, pricing, performance, invoicing and collection path. Each stress has a causal event, affected link and response owner. The simplified model can then receive a coherent cash schedule with clear assumptions and sensitivity. When a downside result is presented, the committee can ask what changed in the project and what decision follows. This preserves the explanatory power that a blanket revenue cut cannot provide on its own.
Evidence and scope
The World Bank risk-identification guidance distinguishes demand, construction, operating and financial mechanisms. This paper adapts that separation into an original revenue map. The source does not provide measured probabilities, forecast receipts or customer evidence for the illustrative schedules.
Evidence: Identifying Risks
Revenue mechanism and response map
This original conceptual map helps a committee identify which link needs evidence and which action can affect it.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Revenue mechanism and response map | |||
|---|---|---|---|
| Mechanism | Cash effect | Evidence to seek | Response boundary |
| Demand or access | Fewer wanted or reachable units | Customer readiness, commitment and alternatives | Capacity expansion does not create willingness to pay |
| Tariff or adjustment | Changed receipts per delivered unit | Pricing terms, approval and customer response | An entitlement is distinct from collection |
| Availability or quality | Lost service and possible deductions | Acceptance and performance measurement | Operational remedy must preserve the service envelope |
| Collection delay | Receipts move after required payments | Invoice, acceptance, dispute and collection dates | Liquidity protection buys time; it does not resolve disputes |
| External interface | Service cannot produce planned receipts | Control, completion and compensation mechanism | The project may lack authority to restore the dependency |
Revenue stress specification
Complete a coherent scenario before entering changed cash into the app. This conceptual record shows a delayed customer-readiness mechanism, without claiming actual volumes or payment terms.
Scroll for all columns. With the table focused, use the left and right arrow keys.
| Revenue stress specification | ||
|---|---|---|
| Specification | Illustrative conceptual case | Required evidence before actual use |
| Event | Customers become ready later than the asset | Readiness milestones and controlling parties |
| Held constant | The stated mature operating cash expectation | Evidence that the delay does not destroy later demand |
| Changed link | The path from available service to collected receipts | A dated collection and operating-cost bridge |
| Response | Stage commercial mobilisation and fund the interval | Funding source, timing and measurable milestones |
| Failure boundary | Later uptake remains unsupported | Reappraise mature receipts; do not call the case merely delayed |
A broad cut can be enough for screening
A blanket reduction is transparent and can quickly reveal whether a preliminary financing structure has little margin. That is useful when mechanism detail is not yet available. The result should remain a screening stress. It cannot identify a probability, choose a remedy or establish that an actual revenue mechanism has been modelled correctly.
No demand or tariff estimator is supplied
The app accepts net cash and cash available; it does not estimate customer demand, willingness to pay, tariffs, indexation, payment deductions or collections. Those mechanisms require evidence and a separately defined commercial model. The public cases are explicit cash-schedule assumptions.