Contracts and models must describe the same project

Contracts and models should describe the same project. A model assumes when work completes, when service earns payment, how costs adjust, what happens during interruption and what cash remains at termination or expiry. Agreements define rights and obligations that can support or contradict those assumptions. Reconciliation should occur through a proposition-level challenge sheet rather than a broad statement that the project is contracted. The committee needs to know which model assumption has been checked, what interpretation was accepted and which conditional event still controls the cash consequence.

The technical perimeter is the first reconciliation point. A contract can procure a defined asset or service while the financial model assumes a broader performance envelope. An omitted connection, enabling facility or operating requirement can create expenditure or delay outside the headline agreement. The analyst should reconcile the scope of each delivery and operating relationship to the asset described in the cash forecast. A fixed-price promise for a limited scope does not cover every use in the financing bridge. The challenge sheet should identify who owns each interface and how completion is demonstrated.

Completion language should be connected to receipts. A physical delivery milestone, acceptance test, licence or commercial-operation definition can each determine a different obligation. The model should not assume that the final contractor payment establishes the right to invoice customers. Legal, technical and commercial reviewers should identify the event that produces usable service and collectible cash. Where the events differ, the commissioning bridge should include the interval. The contract-model reconciliation then becomes a direct test of funding adequacy, rather than a document-review exercise detached from the financial calendar.

Payment entitlement should be mapped through measurement, invoicing, acceptance and collection. An agreement can define a tariff or availability payment while retaining deductions, disputes or conditions. The model should implement the accepted mechanism and state where assumptions remain about timing or performance. It should also preserve the distinction between a claim that can eventually be pursued and cash available at a service date. A payment promise is useful evidence, but its operational path matters. The committee should know whether the forecast relies on full compliance, prompt acceptance or unresolved counterparty capacity.

Adjustment provisions require a terms bridge. A cost or currency pass-through can have a reference basis, lag, approval, cap or threshold. Applying a general index to model revenue may not implement the actual arrangement. The reviewer should identify what adjusts, when it adjusts and who bears the interval. If the provision covers only part of the cost perimeter, the residual should remain visible. A model can be mathematically precise while applying the wrong adjustment boundary. The reconciliation should therefore show a small transparent worked mechanism in the transaction record before its result is embedded in the full forecast.

Performance remedies can change cash and incentives differently. A deduction can reduce a payment; a damages claim can create a contingent receipt; a correction obligation can require expenditure; termination can change the entire horizon. The model should not treat every remedy as immediate compensation restoring the base case. The analyst should identify trigger, measurement, limit, timing and responsible party with appropriate advisers. A remedy may be legally important while offering limited short-term liquidity protection. Its financial role should be described within that boundary rather than counted as cash whenever the model experiences a loss.

Liability limits and exclusions can leave residual exposure with the project. The existence of a contractor, supplier or operator does not mean that every loss is passed to that party. The challenge sheet should identify which assumed recovery is supported, what limits apply and whether the counterparty has resources to meet it. The public paper discloses no private contract and offers no legal interpretation of actual terms. It identifies the question a financing team must resolve before treating compensation as an accepted source. A generic reference to contractual protection is insufficient for a material cash assumption.

Termination assumptions are especially prone to perimeter confusion. An agreement may define compensation under particular causes, dates and conditions. The model may contain a terminal value intended to represent asset disposal or continuing service value. Those are not automatically equivalent. The analyst should identify which event produces each assumed receipt and what obligations or deductions precede the amount available. The committee should understand whether terminal cash is a contractual source, a valuation assumption or an illustrative residual. A single closing cash-flow line should not quietly combine incompatible end states.

Operating rights and renewal should be reconciled to the forecast horizon. A model can extend cash beyond the period for which rights have been established, perhaps on an assumption about renewal or continued use. Such an assumption may be relevant, but it should retain its status and conditions. The financing calendar should identify which obligations rely on that later cash. A physical asset's remaining life does not itself establish a right to earn revenue. The transaction review should examine the actual perimeter of service, access and transfer, with appropriate legal and commercial judgment.

Counterparty performance remains a separate evidence question. An accepted obligation can establish what a party is required to do while leaving uncertainty about its ability or willingness to perform. The financing model should not collapse legal entitlement and operating availability into the same confidence statement. The relevant review includes technical capacity, resources, incentives and response options. Where the project depends on a critical counterparty, the committee should identify the fallback if performance fails. A model that continues the base cash after a counterparty interruption needs an explicit restoration or substitution mechanism.

Changes after approval require a reconciliation update. A contract amendment can alter scope, milestones, price, adjustments or remedies. A revised model can reflect a change that has not been accepted in documents. The team should maintain a bridge showing the proposition, old basis, new basis and decision effect. This avoids a situation in which the legal team and finance team each work correctly on different projects. The committee should know which edition it approved and what change requires further authority. Version labels matter because they preserve the meaning of the commitment, not merely because they organise files.

The challenge sheet should distinguish express terms, specialist interpretation and analyst assumption. A reviewer can point to a clause that expressly describes a payment event. Applying that clause to a disputed situation may require interpretation. Estimating the time to collect after that event may remain a financial assumption. These categories should be visible in the model ledger. A confident paraphrase of a clause should not convert all downstream timing into contractual fact. The practical benefit is that each unresolved question reaches the adviser or decision owner able to address it.

Public communication should retain the analytical mechanism while respecting disclosure boundaries. An illustrative contract map can explain completion, payment, adjustment and termination questions without publishing confidential terms or identifying a client. A private transaction record can contain the exact documents under appropriate controls. The public paper's source cards are public institutional guidance, and its scenarios are authored examples. Readers should not infer that a concealed executed agreement supports the illustrations. The distinction preserves both privacy and epistemic honesty: public claims should be supported by the public evidence actually available to readers.

The committee decision should close the material reconciliation gaps or condition exposure on their resolution. A document-review conclusion such as generally bankable is less useful than a list of accepted propositions and remaining cash dependencies. The recommendation should identify the model line affected, the relevant event, the owner and the evidence required. If a gap can change completion funding, service cash or maturity resources, it should have a clear decision consequence. The model then becomes an implementation of accepted assumptions and terms, while the challenge sheet preserves the reasoning that gives those inputs authority.