# CUSTOM_FIELD_ARCHIVED

The custom field ‹value› is archived and cannot be added to an invoice

<Callout type="info">
**Category:** [Invoices](/errors/category/invoicing)
</Callout>

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

## When it happens

A `key` in `custom_fields` names a field the company has archived.

## How to fix it

Reactivate it with `"is_archived": false`, or send the list without it.

## 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}/invoices`](/invoices/createCompanyInvoice)
- [`PATCH /v1/companies/{company_id}/invoices/{invoice_id}`](/invoices/patchCompanyInvoice)

## 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/CUSTOM_FIELD_ARCHIVED",
  "title": "CUSTOM_FIELD_ARCHIVED",
  "detail": "The custom field ‹value› is archived and cannot be added to an invoice",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "CUSTOM_FIELD_ARCHIVED",
    "message": "The custom field ‹value› is archived and cannot be added to an invoice",
    "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">{"The custom field ‹value› is archived and cannot be added to an invoice"}</Tab>
  <Tab value="Spanish">{"El campo personalizado ‹value› está archivado y no se puede añadir a una factura"}</Tab>
  <Tab value="Catalan">{"El camp personalitzat ‹value› està arxivat i no es pot afegir a una factura"}</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="ATTACH_SOURCE_INVOICE_UNAVAILABLE" description="A source invoice is not available (it does not exist or you no longer have access); uncheck the source invoices attachment to send without the folder" href="/errors/ATTACH_SOURCE_INVOICE_UNAVAILABLE" />
  <Card title="ATTACH_SOURCE_INVOICES_NO_SOURCES" description="The invoice has no consolidation disbursements: there are no source invoices to attach" href="/errors/ATTACH_SOURCE_INVOICES_NO_SOURCES" />
  <Card title="ATTACH_SOURCE_INVOICES_REQUIRES_PDF" description="Attaching the source invoices also requires attaching the invoice PDF" href="/errors/ATTACH_SOURCE_INVOICES_REQUIRES_PDF" />
  <Card title="ATTACH_SOURCE_PDF_MISSING" description="These source invoices have no generated PDF: ‹value›" href="/errors/ATTACH_SOURCE_PDF_MISSING" />
  <Card title="ATTACH_SOURCE_ZIP_TOO_LARGE" description="The source invoices ZIP (‹value› MB) exceeds the maximum sendable size (‹value› MB)" href="/errors/ATTACH_SOURCE_ZIP_TOO_LARGE" />
</div>

## Keep exploring

<div className="grid grid-cols-2 gap-3 not-prose">
  <Card title="All Invoices errors" description="Every code in this category in one table." href="/errors/category/invoicing" />
  <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