Skip to main content

ContractPhase

Enumeration representing the various phases a contract can go through. Each phase indicates a specific stage in the contract's lifecycle, from the initial user input to the potential termination of the contract. Some phases may require manual intervention to proceed, while others occur automatically.

enum ContractPhase {
  USER_INPUT
  USER_AGREEMENT
  METERING_POINTS_CHECKED
  RETRIEVED_VERIFICATION
  DATE_CHECKED
  SMART_METER_CHECKED
  USAGE_CHECKED
  SMART_METER_FOUND
  FIRST_INVOICE_SEND
  FIRST_PAYMENT_DONE
  DELIVERY_PLANNED
  DELIVERY_STARTED
  DELIVERY_FAILED
  DELIVERY_STOPPED
  NEVER_DELIVERED
}

Values

`ContractPhase.USER_INPUT`

Phase where the user has initiated the contract request after using the calculation tool. In this phase, the user can submit customer details. If no input is provided, the contract is archived. This phase can remain active until the user confirms the contract terms via external input. Manual intervention is required to update this phase.

`ContractPhase.USER_AGREEMENT`

Phase where all customer data has been entered, and the user has confirmed the details. The user is now presented with the contract terms and must accept them to proceed.

`ContractPhase.METERING_POINTS_CHECKED`

System-driven phase where the metering points are checked. If there are discrepancies (e.g., too many meters), the process remains in the previous phase. No manual action is required unless metering validation fails.

`ContractPhase.RETRIEVED_VERIFICATION`

Deprecated phase where the system verified the start date. No longer in use, retained for backward compatibility.

`ContractPhase.DATE_CHECKED`

Phase where the system checks for the existence of a smart meter. If a smart meter is found, the process proceeds automatically. This phase is deprecated, but may still be triggered in legacy flows.

`ContractPhase.SMART_METER_CHECKED`

Phase where the system detects a smart meter, but consumption data may deviate from expected values.

`ContractPhase.USAGE_CHECKED`

This phase is no longer used in current flows.

`ContractPhase.SMART_METER_FOUND`

Phase where the contract has been successfully generated and sent to the user. All necessary conditions have been met for initiating service on the desired start date.

`ContractPhase.FIRST_INVOICE_SEND`

Phase where the first invoice has been generated and sent to the customer. The process moves forward automatically unless payment issues arise.

`ContractPhase.FIRST_PAYMENT_DONE`

Phase where the first invoice has been successfully paid by the customer.

`ContractPhase.DELIVERY_PLANNED`

Phase where the contract has been registered for delivery with the EDSN system. At this point, the contract cannot be canceled without first initiating the delivery process.

`ContractPhase.DELIVERY_STARTED`

Phase where service delivery has started successfully. Indicates that the customer is receiving the agreed-upon service.

`ContractPhase.DELIVERY_FAILED`

Error phase triggered if service delivery fails for any reason. The contract requires manual intervention to attempt reactivation or reconnection. Look at phaseErrorDetails for more information.

`ContractPhase.DELIVERY_STOPPED`

Phase where the contract has been terminated, either by the provider or because the customer has switched to a new provider. The system tracks the reason for termination in the customer profile.

`ContractPhase.NEVER_DELIVERED`

Phase where the contract was never fulfilled, often due to the customer canceling after the first payment but before delivery. Requires manual handling to finalize any pending refunds or adjustments.

Member Of

Contract object

Values
Member Of