# INVOICES_HELD

Canonical page: https://docs.ovok.com/errors/invoices-held

**HTTP 502.** Problem type: [`https://docs.ovok.com/errors/invoices-held`](https://docs.ovok.com/errors/invoices-held).

## What this means [#what-this-means]

The monthly invoice run charged the invoices it could and held the rest, because a customer environment did not report its usage. Ovok holds an invoice rather than bill a month as if the customer used nothing.

## Troubleshooting [#troubleshooting]

1. Read `held` in the response. Each entry names a `customerId` and the `environment` that did not report. `charged` counts the invoices that went through.
2. Check that environment. It must be reachable, run the same version as the hub, and answer usage requests for the right customer and month.
3. Check the provisioning secret on the hub and that environment if it refuses the hub's calls. A wrong or missing secret holds invoices the same way.
4. Run the month again once the environment answers.

## Retry safely [#retry-safely]

Repeating the run is safe. An invoice is created once per customer and month, only drafts are charged, and the payment provider drops a duplicate charge. The scheduled monthly run also retries on its own.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
