Auto-submit policy

Whether an invoice reaches AEAT is a fact of the taxpayer, resolved when the invoice is issued. If the NIF is under the VeriFactu regime, every invoice it issues is registered; if it is not, none is. There is nothing to set per invoice, and no request can opt one document in or out.

BeeL. works this way because the VERI*FACTU modality is chosen by the taxpayer, not per document: under article 16.1 of the RD 1007/2023 it covers «todos los registros de facturación generados». A per-invoice switch allowed a mixed ledger — two invoices from the same NIF on the same day, one registered and one not.

What decides it

Two conditions, both read at issue time:

A proforma is never submitted, whatever the NIF's regime: it is not an invoice yet. It gets a fiscal record when you convert it.

How it reads on the invoice

The invoice resource carries a nested verifactu object. enabled tells you which side of the axis the invoice is on, and it is decided once, at issue time:

{
  "id": "...",
  "status": "ISSUED",
  "verifactu": {
    "enabled": true,
    "submission_status": "PENDING",
    "registration_number": "094365f5-9637-40e9-851a-4e964a939b0b",
    "registered_at": "2026-09-19T09:27:44Z",
    "invoice_hash": "1863E77D540083E4259F4AF44322E16B962CB5D72C2F949AB2B30FA83E93FF84",
    "qr_url": "https://www2.agenciatributaria.gob.es/wlpl/TIKE-CONT/ValidarQR?nif=B27534239&numserie=S-2026-0001&fecha=19-09-2026&importe=121.00",
    "qr_base64": "iVBORw0KGgoAAAANSUhEUgAAAMgAAADI...",
    "skip_reason": null
  }
}

The hash, the QR and the BeeL. registration_number are already there while AEAT has not answered — they belong to the record as submitted, not to AEAT's verdict. See QR code and the invoice PDF.

An invoice from a NIF outside the regime has enabled: false and no submission_status at all — it is outside the axis, not failing on it:

{
  "id": "...",
  "status": "ISSUED",
  "verifactu": {
    "enabled": false
  }
}

To select those over the API, filter with ?verifactu_enabled=false. No value of verifactu_status matches them, because they have no submission to describe. See Submission states for what submission_status does next, including NOT_SUBMITTED — an invoice that should have reached AEAT and has no live record.

Issuing a wave you don't want registered

There is no way to exclude individual invoices. The NIF's enabled flag is all-or-nothing for that taxpayer, and it is not a tool for leaving invoices unregistered: see the rules on timing.

There's no public "submit now" endpoint

The public API does not expose a way to trigger a submission by hand. What to do depends on what you are looking at:

Related