What information from the API response should be printed on the invoice?

Consiglio

Ultimo aggiornamento il 2025-05-06.

In this article, we outline the key elements that must be included in issued invoices to comply with Verifactu and TicketBAI regulations.

Verifactu

Invoices issued under Verifactu must include:

• A** QR code** containing the validation URL. This must be accompanied by the label “QR tributario”, clearly indicating its purpose as a fiscal QR code.

• A** compliant text** indicating the invoice was issued in Verifactu Mode. One of the following texts must be used: “VERIFACTU”*, or “Factura verificable en la sede electrónica de la AEAT”

Additional guidelines regarding the compliant text, validation URL, and QR code, including their required dimensions and placement within the invoice, are detailed in the Verifactu Invoice Compliance section of the SIGN ES guide.

 

TicketBAI

Invoices issued under TicketBAI must include:

• A** QR code** containing the validation URL.

• A** TBAI code**, which uniquely identifies the invoice for compliance tracking. This code is shown in the tbai field of the API response when the invoice is created.

Further details about the validation URL, QR code, and identifier code, including their required dimensions and placement within the invoice, can be found in the TicketBAI Invoice Compliance section of the SIGN ES guide.

 

Offline scenarios

If invoice transmission fails due to connectivity issues, and the QR code or identifier cannot be printed, businesses are encouraged to include a message such as:

“QR code not generated due to connectivity issues.”

This informs the end customer about the reason for the missing fiscal elements and maintains transparency.

 

By adhering to these compliance requirements, businesses can ensure their invoices meet the necessary legal and fiscal regulations.