Verifactu in Dolibarr: how to connect Dolibarr with the Verifactu API

Verifacti has no official Dolibarr module: Dolibarr connects to the Verifactu API with your own module whose trigger, when an invoice is validated, sends it as JSON and stores the QR. No XML to generate, no hash to compute and no digital certificate: Verifacti sends the invoicing record to the AEAT as a colaborador social. The same pattern works for TicketBAI with the TicketBAI API.

Test environment and test NIF included
Read the documentation

Which APIs you need for Dolibarr

Your connector uses two pieces: the submission API that matches the NIF (Verifactu API in common territory; TicketBAI API in Álava, Bizkaia and Gipuzkoa) and the NIF management API, integrated once to register the NIF, manage the representation form and receive webhooks. Each NIF uses one API or the other depending on where it is taxed.

Test environment and test NIF included

How to connect Dolibarr with the API

Flow: validated invoice in Dolibarr (BILL_VALIDATE trigger) → your module → Verifactu API or TicketBAI API → AEAT or foral treasury.

  1. Register the NIF with the NIF management API and sign the representation form. Each NIF has its own API key.
  2. Create a module with a trigger and the verifactu_uuid and verifactu_qr extra fields on invoices.
  3. On BILL_VALIDATE, build the invoice and call POST /verifactu/create.
  4. Store uuid and qr in the extra fields and add the QR to the PDF model.

Do you build software and want to offer Verifactu to your customers? See ERP vendors.

Example: from the validated invoice to the record

The trigger uses the invoice's final number (newref: during BILL_VALIDATE, ref is still the provisional one), only acts on standard invoices (deposits and credit notes need their own mapping) and doesn't resend an invoice already registered. The total is base + VAT, without surcharge or withholding. If the API answers with an error, it returns -1 and Dolibarr rolls back the validation and shows the message.

core/triggers/interface_99_modVerifacti_VerifactiTriggers.class.php
<?php
// htdocs/custom/verifacti/core/triggers/interface_99_modVerifacti_VerifactiTriggers.class.php · Dolibarr 16+.
// Envía cada factura de cliente validada a la API Verifactu.
// Crea antes los atributos complementarios verifactu_uuid y verifactu_qr en las facturas.

require_once DOL_DOCUMENT_ROOT . '/core/triggers/dolibarrtriggers.class.php';

class InterfaceVerifactiTriggers extends DolibarrTriggers
{
    public function __construct($db)
    {
        parent::__construct($db);
        $this->family = 'financial';
        $this->description = 'Envía las facturas validadas a la API Verifactu';
    }

    public function runTrigger($action, $object, User $user, Translate $langs, Conf $conf)
    {
        // Solo facturas estándar; los anticipos (TYPE_DEPOSIT) y los abonos necesitan su propio mapeo
        if ($action !== 'BILL_VALIDATE' || $object->type != Facture::TYPE_STANDARD) {
            return 0;
        }
        // Ya registrada (se volvió a borrador y se valida otra vez): no se reenvía
        $object->fetch_optionals();
        if (!empty($object->array_options['options_verifactu_uuid'])) {
            return 0;
        }
        // Durante BILL_VALIDATE, ref aún es la provisional (PROV…); el número definitivo está en newref
        $ref = $object->newref ?: $object->ref;

        $porTipo = [];
        foreach ($object->lines as $linea) {
            $tipo = (string) (float) $linea->tva_tx;
            $porTipo[$tipo]['base'] = ($porTipo[$tipo]['base'] ?? 0) + $linea->total_ht;
            $porTipo[$tipo]['cuota'] = ($porTipo[$tipo]['cuota'] ?? 0) + $linea->total_tva;
        }

        $object->fetch_thirdparty();
        $nif = $object->thirdparty->idprof1 ?: preg_replace('/^ES/', '', (string) $object->thirdparty->tva_intra);
        preg_match('/^(.*?)(\d+)$/', $ref, $partes);
        $factura = [
            'serie' => $partes[1],
            'numero' => $partes[2],
            'fecha_expedicion' => dol_print_date($object->date, '%d-%m-%Y'),
            'tipo_factura' => $nif ? 'F1' : 'F2',
            'descripcion' => $object->ref_client ?: 'Factura ' . $ref,
            'lineas' => [],
            // total_ttc incluye el recargo de equivalencia y resta la retención de IRPF: el registro lleva base + IVA
            'importe_total' => price2num($object->total_ht + $object->total_tva, 'MT'),
        ];
        if ($nif) {
            $factura['nif'] = $nif;
            $factura['nombre'] = $object->thirdparty->name;
        }
        foreach ($porTipo as $tipo => $l) {
            $factura['lineas'][] = [
                'base_imponible' => price2num($l['base'], 'MT'),
                'tipo_impositivo' => $tipo,
                'cuota_repercutida' => price2num($l['cuota'], 'MT'),
            ];
        }

        $cuerpo = json_encode($factura);
        $ch = curl_init('https://api.verifacti.com/verifactu/create');
        curl_setopt_array($ch, [
            CURLOPT_POST => true,
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_TIMEOUT => 30,
            CURLOPT_HTTPHEADER => [
                'Authorization: Bearer ' . getDolGlobalString('VERIFACTI_API_KEY'),
                'Content-Type: application/json',
                'Idempotency-Key: dolibarr-' . $object->id . '-' . substr(hash('sha256', $cuerpo), 0, 12),
            ],
            CURLOPT_POSTFIELDS => $cuerpo,
        ]);
        $registro = json_decode((string) curl_exec($ch), true);
        if (curl_getinfo($ch, CURLINFO_HTTP_CODE) !== 200) {
            $this->errors[] = 'Verifactu: ' . ($registro['error'] ?? 'sin respuesta');
            return -1; // la validación de la factura se deshace
        }

        $object->array_options['options_verifactu_uuid'] = $registro['uuid'];
        $object->array_options['options_verifactu_qr'] = $registro['qr'];
        $object->insertExtraFields();
        return 1;
    }
}

The code groups the lines by VAT rate and uses F1 if the customer has a NIF and F2 otherwise. It sends the Idempotency-Key header with the invoice identifier plus a digest of the body: an identical retry never duplicates the invoice and, if you fix the data after an error, the key changes. The response carries the uuid, the state (Pendiente: the submission to the AEAT is queued), the verification URL, the QR in Base64 and the hash: store them with the invoice.

More code in the Verifactu tutorial in PHP. For TicketBAI, the call goes to POST /ticketbai/create with the foral NIF's API key: the fields, in the TicketBAI API documentation.

Special cases in Dolibarr

Special cases when invoicing from Dolibarr
CaseWhat to doRead more
NumberingEvery invoice needs a series with sequential numbering. If invoice numbers can have gaps, give the invoice its own numberVerifactu requirements
Customer without a NIFSimplified invoice (F2), without nif or nombre. The API rejects an F2 above €3,000 (vf-verifactu-f2_limite_3000)Simplified invoice
Return or refundCorrective invoice: R5 if the original was simplified; R1–R4 if it was a full invoiceCorrective invoices
Customer asks for a full invoice laterExchange invoice (F3) replacing the simplified oneExchange invoice
Canary Islands, Ceuta and MelillaIGIC or IPSI in the lines (impuesto field), not VATIGIC · IPSI
Products without VATCheck whether they are exempt (operacion_exenta) or not subject (calificacion_operacion): they are not sent at rate 0Exempt invoice
CancellationOnly for invoices that should never have been issued: POST /verifactu/cancelCancellation
Sale to another EU countryIt depends on whether the customer is a business and on the distance-selling thresholdIntra-EU examples
Equivalence surchargetipo_recargo_equivalencia and cuota_recargo_equivalencia on the VAT line, not as another lineEquivalence surcharge
IRPF withholdingNot sent: importe_total is base + tax (+ surcharge), without subtracting the withholdingDisbursements and withholding
Several companies or shopsOne NIF per company, each with its own API keyNIF management API

Dates

The first row only applies if you build the connector to sell it: then you sell invoicing software. For those who invoice, the Verifactu dates are published in the BOE and the postponement to October 2028 is announced with no rule published. In Álava, Bizkaia and Gipuzkoa, TicketBAI is in force.

Producers and resellers of invoicing softwareSince 29 Jul 2025
RDL 15/2025 did not change this date.
In force
Corporate Income Tax payers1 Jan 2027
Published in the BOE, future date
Everyone else, including the self-employed1 Jul 2027
Published in the BOE, future date
Postponement of the pending obligationsOct 2028
The note does not specify the scope for businesses invoicing over €8M.
Announced, no rule published
TicketBAI in Álava: foral taxpayersSince 1 Dec 2022
Phased from 1 April 2022; all other taxpayers since 1 December 2022.
In force
Batuz in Bizkaia (TicketBAI and LROE): all taxpayersSince 1 Jan 2026
Companies that are not SMEs since 1 January 2024; everyone else in windows on 1 July 2024, 1 January 2025, 1 July 2025 and 1 January 2026.
In force
TicketBAI in Gipuzkoa: foral taxpayersSince 1 Jun 2023
Phased by activity from 1 July 2022.
In force

This is not advice: each taxpayer determines what applies to them with their adviser.

More detail in Verifactu dates and TicketBAI.

Pricing

Public tariff of the Verifactu API and the TicketBAI API: you pay per NIF active in production, VAT excluded. Custom per-NIF pricing is available for volume.

From

€14.99

per month for the first NIF active in production, VAT excluded

See all pricing
  • The price per NIF goes down with every tier.
  • Free test environment and test NIF.
  • Annual plan with a 10% discount, no setup fees.
  • Up to 3,000 invoicing records per month per NIF.
  • Startup plan for companies under 12 months old, with under €100,000 in revenue and under €200,000 in funding.
  • Same price with the Verifactu API and the TicketBAI API: each NIF uses one or the other depending on where it is taxed.
  • Online signing of the representation form: €2.90 + VAT per signature.

Questions about Verifactu and Dolibarr

More questions about Verifactu

Is there a module or app from Verifacti for Dolibarr?

No. Verifacti is an API: Dolibarr connects to it with the code on this page, in your own development. There are third-party modules in DoliStore.

Does Dolibarr comply with Verifactu on its own?

It depends on your version and what you have installed: check with your provider. Whoever invoices needs a system that generates the invoicing records and sends them to the AEAT. Which obligation each business has depends on its case: who Verifactu applies to.

Does it work for TicketBAI too?

Yes. If the NIF is taxed in Álava, Bizkaia or Gipuzkoa, the flow is the same with the TicketBAI API: the endpoint (/ticketbai/create), the invoice fields and the API key change.

Do I need a digital certificate?

No. Verifacti is an AEAT social collaborator and submits with its own certificate once the taxpayer signs the representation form, the same one for the AEAT and the foral treasuries. It can be signed online, without a certificate.

How much does it cost?

From €14.99 per month for the first NIF active in production, VAT excluded, with the Verifactu API or the TicketBAI API. The test environment and test NIF are free. Every plan, in pricing.

Connect Dolibarr in the test environment

Create your free account and try the API with a test NIF before going to production.

Test environment and test NIF includedRead the documentation