---
title: "Submit invoice to FACe"
method: POST
path: "/companies/{company}/invoices/{invoice}/face-submissions"
tags: ["FacturaE"]
---

# Submit invoice to FACe

`POST /companies/{company}/invoices/{invoice}/face-submissions`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/invoices/{invoice}/face-submissions`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Submit an issued invoice to FACe (the Spanish B2G entry point). Requires the client's three DIR3 codes and an active signing certificate; the FacturaE 3.2.2 XML is signed XAdES-EPES and presented to FACe, returning the registry number. No request body — the DIR3 codes are read from the client. Test keys simulate the submission without contacting FACe.

## Path parameters

- `company` string, uuid, required
- `invoice` string, uuid, required

## Headers

- `Idempotency-Key` string, required
- `Factuarea-Version` string, date

## Response `201`

- object
  - `data` FaceSubmission, required: A submission of an invoice to FACe (the Spanish B2G general entry point). Tracks the FACe registry number and the processing status reported by the FACe web service.
    - `id` string, required: UUID v7 of the FACe submission.
    - `object` 'face_submission', required
    - `invoice_id` string, required: UUID v7 of the submitted invoice.
    - `status` string, required: FACe processing status (`submitted`, `registered_rcf`, `accounted`, `paid`, `rejected`, `cancellation_requested`, `cancelled`, `error`). Kept up to date by the system polling — there is no refresh endpoint in v1.
    - `registry_number` string, nullable, required: Registry number assigned by FACe on presentation. Synthetic `FACE-SANDBOX-*` for sandbox (test key) submissions.
    - `dir3_accounting_office` string, required: DIR3 code of the accounting office (oficina contable, role 01) snapshotted at submission time.
    - `dir3_managing_body` string, required: DIR3 code of the managing body (órgano gestor, role 02) snapshotted at submission time.
    - `dir3_processing_unit` string, required: DIR3 code of the processing unit (unidad tramitadora, role 03) snapshotted at submission time.
    - `error_code` string, nullable, required: Local transmission error code, `null` unless the submission is in `error` state.
    - `error_message` string, nullable, required: Human-readable transmission error message (in Spanish), `null` unless the submission is in `error` state.
    - `status_updated_at` string, date-time, required: When the processing status last changed (ISO 8601).
    - `last_polled_at` string, date-time, nullable, required: When the system last polled FACe for this submission, or `null` if never polled yet.
    - `created_at` string, date-time, required

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `409`: The request conflicts with data that already exists or with a request running at the same time. `resource_already_exists` with `subcode` `face_submission_already_exists`: the invoice already has an active FACe submission. `resource_conflict`: another request was reserving identifiers for the same kind of record at that moment and this one could not complete its reservation. Nothing was written; send the request again after a few seconds.
- `422`: Validation failed, or the invoice cannot undergo the requested state transition (e.g. marking an already-paid invoice as paid, or editing an issued invoice — use a corrective instead). The `error.param` field identifies which input is invalid, if any. Issuing or annulling an invoice can also be rejected with `verifactu_not_eligible`: either a field of the invoice does not fit its billing record, or — only when the company has VeriFactu enabled in NO VERI*FACTU mode — it has no usable signing certificate (`error.subcode: signing_certificate_unavailable`; `error.param` is `certificate`, `representation` or `system_certificate`, depending on what is missing); in both cases the invoice stays exactly as it was.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)