Establish derivative scope and fair-value measurement

A derivative analysis does not begin with “hedge.” Begin with the contract. Identify the underlying, notional amount or payment provision, settlement terms, initial net investment, and whether net settlement is available directly, through a market mechanism, or by delivery of an asset readily convertible to cash. Then test the applicable scope exceptions.

For example, if the supplied copper forward requires the parties to settle the change in copper price with a cash payment rather than deliver metal, it has a direct net-settlement term. A different contract may require delivery of a standardized quantity that can be sold quickly in an active market; that is the separate readily-convertible-to-cash route. A market-mechanism route exists when an established arrangement, such as an exchange's offsetting-contract process, lets either party settle net even though the contract itself does not require a net cash payment. The facts must establish the route; active spot prices alone do not.

Create a feature table for the copper forward and for any host contract with an indexed, optional, contingent, conversion, call, put, or foreign-currency term. For each feature, cite the clause and record whether it is part of the host, clearly outside Topic 815, within a scope exception, or unresolved. Do not infer terms from a confirmation summary when the executed contract differs.

Once a supplied conclusion places the instrument in derivative accounting, recognize the derivative at its supplied fair value. The period change is ending fair value minus opening fair value. That recomputation proves the movement, not the valuation. Preserve the valuation date, source, hierarchy level, method owner, and any collateral or credit adjustments.

Without qualifying hedge accounting, the supplied change follows the applicable earnings route. A risk-management designation in treasury software does not alter that result. The entry file should therefore have separate columns for economic purpose, Topic 815 scope, accounting designation, measurement source, and statement location.

Embedded features remain an escalation boundary. The learner should be able to explain why a feature matters and request the complete host terms without pretending to make a separation or valuation conclusion that the packet does not support.