> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engrate.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Handle a mismatch

> Find out why a series does not match your counterparty's, and fix it before the market decides for you.

When your series and your counterparty's do not agree, the market decides the value after its deadline: in Germany by its matching rules, in the Netherlands by setting the series to zero, or, between two BRPs with a priority nomination, by using the values of the BRP with priority. Fix the mismatch before that, and you keep control of the value.

**1. Find the series that do not match**

```bash theme={null}
curl --request GET \
  --url "https://api.engrate.io/schedule-management/v1/schedules/$SCHEDULE_UID/series-state" \
  --header "authorization: $API_KEY"
```

Look for series whose `match_status` is not `matched` or `not_checked`:

* `inconsistent`: you and the counterparty sent different values.
* `counterpart_missing`: the counterparty sent nothing for this trade.
* `counterpart_only`: the counterparty sent a series that names you, and you did not.

**2. Read the findings**

`findings` gives the market's reasons, with its codes, and per affected quarter-hour your value and the counterparty's:

```json theme={null}
{
  "match_status": "inconsistent",
  "findings": {
    "reasons": [{ "code": "A09", "text": "Time series not matching" }],
    "positions": [
      { "position": 8, "ours": 2.0, "counterparty": 1.0 }
    ]
  }
}
```

`position` counts quarter-hours from local midnight, starting at 0: position 8 is 02:00 to 02:15.

The console shows the same findings on the schedule's page, with a chart of both sides.

**3. Agree on the values**

Contact the counterparty and agree which values are right. The market does not decide who is right before its deadline: one of you changes the series.

**4. Send the corrected values**

If your side changes, post the whole day again with the corrected values. Engrate sends a new revision. For a `counterpart_only` series, add the series the counterparty expects.

When the counterparty's side changes, you do not need to do anything. The market matches again and reports the new result.

**5. Check the result**

Read the series state again. The series turns `matched`, and its confirmation shows your values. If the deadline passed first, the confirmation shows the value the market chose, and why. See [Why a value changed](https://docs.engrate.io/market-communication/schedules/matching-and-confirmation.md#why-a-value-changed).

## Deadlines

* **Germany**: in the day-ahead process, until 15:30 on D-1. In the intraday process, until the gate closure of each quarter-hour.
* **Netherlands**: until 10:00 on D+1.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.