> ## Documentation Index
> Fetch the complete documentation index at: https://docs.noyo.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Effective End Dates
> Unless in cases of explicit termination, the effective end date should be sent as `datemax`
When sending a member snapshot, you will need to send an `effective_end_date` for each enrolled member for a given coverage block.
## Active coverages
While `effective_end_date` is a required field, a defined end date should only be provided if the member's coverage is expected to terminate on that specific date. Otherwise, the member's `effective_end_date` should be sent as `datemax` (`9999-12-31`).
Even if the *plan year* is scheduled to end on a specific date, it's common for coverage to continue into the next plan year uninterrupted, so a member's end date should remain at `datemax`.
```json [expandable] {12} lines theme={"system"}
{
"coverages": [
{
"carrier_id": "2d370e0e-fd73-45e0-8828-796d2cacaeef",
"line_of_coverage": "dental",
"plan_id": "61b6d125-8bbf-483a-9920-f23d9442403d",
"enrolled_members": [
{
"individual_type": "employee",
"custom_individual_id": "1",
"effective_start_date": "2022-10-01",
"effective_end_date": "9999-12-31",
"latest_change_effective_date": "2022-10-01",
"event_id": "7"
}
],
}
]
}
```
For Open Enrollment elections, specifically plan switching scenarios, the member's `effective_end_date` should be sent as the plan end date and a separate coverage block should be created for the new plan.
### Splitting coverage blocks for continuous coverage
When splitting a coverage block into multiple due to a specific aspect of the configuration (e.g. benefit class), the `effective_end_date` should be set with a defined value even though the coverage is not ending. The second block takes care of signifying the open-ended nature of the coverage.
Ensure your coverage blocks do not have a gap in dates
```json [expandable] {10-11, 22-23} lines theme={"system"}
{
"coverages": [
{
"plan_id": "4655eed5-ee44-49e1-a0a9-aa3a6fd52aa5",
"carrier_config": {
"benefit_class": "511",
},
"enrolled_members": [
{
"effective_start_date": "2024-12-01",
"effective_end_date": "2024-12-31",
}
],
},
{
"plan_id": "4655eed5-ee44-49e1-a0a9-aa3a6fd52aa5",
"carrier_config": {
"benefit_class": "001",
},
"enrolled_members": [
{
"effective_start_date": "2025-01-01",
"effective_end_date": "9999-12-31",
}
],
}
],
}
```
## Waived/canceled coverages
If a coverage needs to be waived or canceled before it begins, the `effective_end_date` should be set to one day before the `effective_start_date`.
```json [expandable] {13} lines theme={"system"}
{
"coverages": [
{
"carrier_id": "2d370e0e-fd73-45e0-8828-796d2cacaeef",
"line_of_coverage": "dental",
"plan_id": "61b6d125-8bbf-483a-9920-f23d9442403d",
"enrolled_members": [
{
"custom_individual_id": "150D001",
"individual_type": "employee",
"event_id": "10002",
"effective_start_date": "2023-04-01",
"effective_end_date": "2023-03-31",
"latest_change_effective_date": "2023-03-20"
}
],
}
]
}
```
Read more
## Terminated or future-terminating coverages
When a coverage is terminated after having been active, the `effective_end_date` should be set to the last day of coverage.
If you know in advance that a coverage will terminate on a specific date (due to cessation of employment, the end of a plan, or another reason), set that date as the `effective_end_date` as soon as you know it. Future terminations are processed differently by different carriers, so these changes may exist in a `processing` state for longer as Noyo holds the change until a carrier is able to accept it.
If the coverage termination is due to an employment termination and your platform supports COBRA, this field requires special handling. Please see the [COBRA](/docs/members/complex-changes/cobra) documentation for more information.
Code example
Read more