Full invoice (F1) in Verifactu: API example
F1 is the AEAT list L2 code for a full invoice. In the Verifactu API, the recipient’s nif and nombre are checked against the AEAT census before the record is generated.
| Field | Value |
|---|---|
| API | Verifactu API |
| Invoice type or key | F1 |
| Endpoint | /verifactu/create |
| When to use it | Invoice with the recipient’s tax details. |
What changes in this case
The standard invoice entails greater information obligations than the simplified invoice, as it is mandatory to specify the fiscal data of the recipient. This type of invoice is generated using the field tipo_factura equal to F1.
When the recipient is a Spanish citizen or company, we can identify them using the fields nif and nombre. The field nif must be a valid NIF (of an individual, an NIE or of an entity). The field nombre corresponds to the full name for individuals and the company name for businesses. Below is an example of such an invoice.
JSON request
{
"serie": "Ejemplos",
"numero": "1",
"fecha_expedicion": "19-11-2026",
"tipo_factura": "F1",
"descripcion": "Factura normal",
"nif": "A15022510",
"nombre": "Nombre destinatario",
"lineas": [
{
"base_imponible": "200",
"tipo_impositivo": "21",
"cuota_repercutida": "42"
}
],
"importe_total": "242"
}When the recipient is a company, it is sufficient for the NIF to be correct. However, when the recipient is an individual, the name must also be close enough to the one in the census.
Our API performs this validation automatically and rejects the invoice if it does not pass. This prevents generating an invoicing record that the AEAT will reject. In the NIF management API we have a specific endpoint to query the AEAT census.
Try this case in the test environment
Create your free account, copy the request and send it with the test API key of your test NIF.