# SERIES_FORMAT_OVERLAPS

This series' format can produce the same numbers as series '‹value›'. An invoice number must be unique per issuer: change the code or the format.

<Callout type="info">
**Category:** [Account settings](/errors/category/configuracion)
</Callout>

| | |
|---|---|
| HTTP status | `409` Conflict |
| Retry | After fixing the cause |

## When it happens

The series' `code` and `format` could print a number that another series of the company, in the same environment and active or not, can also print. An invoice number must be unique per issuer.

## How to fix it

Put `{CODIGO}`, or a literal of its own, in the format so the numbers of both series differ. The error names the other series.

## Retry

Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new `Idempotency-Key` if the body changed.

## Returned by

The operations where this code is most likely. The list is not exhaustive.

- [`POST /v1/companies/{company_id}/series`](/invoice-series/createCompanySeries)
- [`PATCH /v1/companies/{company_id}/series/{series_id}`](/invoice-series/patchCompanySeries)

## Rules that cite this code

- [NUM-002 · An issued number is never reused, even when the invoice is voided](/rules/numbering#num-002)

## Example response

When this error occurs, the API answers `409` Conflict with a JSON body of this shape:

```json
{
  "type": "https://docs.beel.es/errors/SERIES_FORMAT_OVERLAPS",
  "title": "SERIES_FORMAT_OVERLAPS",
  "detail": "This series' format can produce the same numbers as series '‹value›'. An invoice number must be unique per issuer: change the code or the format.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "SERIES_FORMAT_OVERLAPS",
    "message": "This series' format can produce the same numbers as series '‹value›'. An invoice number must be unique per issuer: change the code or the format.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}
```

The `type` URI is stable and always resolves to this page.

## Message

<Tabs items={["English", "Spanish", "Catalan"]}>
  <Tab value="English">{"This series' format can produce the same numbers as series '‹value›'. An invoice number must be unique per issuer: change the code or the format."}</Tab>
  <Tab value="Spanish">{"El formato de esta serie puede generar los mismos números que la serie '‹value›'. El número de factura debe ser único por emisor: cambia el código o el formato."}</Tab>
  <Tab value="Catalan">{"El format d'aquesta sèrie pot generar els mateixos números que la sèrie '‹value›'. El número de factura ha de ser únic per emissor: canvia el codi o el format."}</Tab>
</Tabs>

Send the request with `Accept-Language: <es|en|ca>` to receive the message in your preferred language.

> Placeholders like `‹value›` are filled in at runtime with the actual values of your request.

## Other errors in this category

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="ACTIVE_CANNOT_DELETE" description="Cannot delete an active series. Deactivate it first" href="/errors/ACTIVE_CANNOT_DELETE" />
  <Card title="DEFAULT_CANNOT_BE_UNMARKED" description="Cannot unmark the default series. Set another series as default first" href="/errors/DEFAULT_CANNOT_BE_UNMARKED" />
  <Card title="DEFAULT_CANNOT_DEACTIVATE" description="Cannot deactivate the default series. Set another series as default first" href="/errors/DEFAULT_CANNOT_DEACTIVATE" />
  <Card title="DEFAULT_CANNOT_DELETE" description="Cannot delete the default series. Set another series as default first" href="/errors/DEFAULT_CANNOT_DELETE" />
  <Card title="ENTITY_TYPE_INCONSISTENT_WITH_NIF" description="The entity type ‹value› does not match the NIF ‹value›: an individual is identified by a DNI or NIE, and a company or entity by a NIF that starts with a legal-form letter" href="/errors/ENTITY_TYPE_INCONSISTENT_WITH_NIF" />
</div>

## Keep exploring

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="All Account settings errors" description="Every code in this category in one table." href="/errors/category/configuracion" />
  <Card title="Error reference home" description="Browse every category or jump to the handling guide." href="/errors" />
</div>

---

Full OpenAPI spec: https://docs.beel.es/api/openapi