# Compliance and responsibilities

What BeeL. does for each invoice, who signs its declaración responsable, the rules that apply to software built on the API and to the issuing business, the VERI*FACTU modality, and what BeeL. keeps for each record.

When an invoice is issued through the BeeL. API, three parties are involved: the business whose NIF is on the invoice, the software that calls the API, and BeeL. This page describes what BeeL. does for each of them and quotes the rules that apply: the RD 1007/2023 (*Reglamento de sistemas informáticos de facturación*), the Orden HAC/1177/2024, the RD 1619/2012 (*Reglamento de facturación*) and the criteria AEAT has published.

BeeL.'s own position is stated in the **VeriFactu section of its [Terms](https://beel.es/terminos#verifactu)** and in its **[*declaración responsable*](https://beel.es/declaraciones-responsables)** (the producer's signed statement that the system complies with the rules). Where this page mentions that position it links there; if this page and those texts ever differ, those texts prevail.

> **Not legal or tax advice.** This page describes how BeeL. works. It is not legal or tax advice: confirm your own obligations, and those of the businesses you invoice for, with your tax advisor.

## Who is who

| Role | Who | What it does in BeeL. |
|---|---|---|
| **Issuer** (*obligado tributario*, *expedidor*) | The business whose NIF is on the invoice | Issues its invoices through BeeL. and provides the data they contain |
| **Integrator** | Your software, calling the API | Sends data to BeeL. and shows the result |
| **Billing system** (*SIF*, *sistema informático de facturación*) | **BeeL.**, as stated in its [*declaración responsable*](https://beel.es/declaraciones-responsables) | Numbers the invoice, builds its billing record, computes and chains its hash, produces the QR and submits the record to AEAT |
| **Producer** (*productor*) of BeeL. | **Honey Solutions, S.L.** | Signs BeeL.'s *declaración responsable* |

## What BeeL. does for each invoice

The RD 1007/2023 defines a SIF as «el conjunto de hardware y software utilizado para expedir facturas» that admits, keeps and processes billing information (article 1.2). For every invoice issued through BeeL. — from the dashboard, through the API or through the Stripe integration — BeeL.:

- assigns its number from one of the issuer's series;
- generates its billing record (*registro de facturación de alta*, article 9 of the RD 1007/2023), and a cancellation record when it is voided (article 11);
- computes the record's hash and chains it to the previous record of the same issuer (article 12 of the RD 1007/2023, article 7 of the Orden HAC/1177/2024);
- produces the QR data (`qr_url`, `qr_base64`) and, when BeeL. renders the PDF, prints the QR and its legend on it;
- submits the record to AEAT.

The API does not register an invoice numbered or hashed somewhere else: see [Who generates the record, the hash and the chain](/guides/erp-integration#who-generates-the-record-the-hash-and-the-chain).

> **Rules that apply here:** [REC-001 · Each issued invoice gets a billing record built from its data](/rules/records#rec-001)

## The *declaración responsable* [#declaracion-responsable]

Article 13.1 of the RD 1007/2023 reads: «Corresponderá a la persona o entidad productora del sistema informático certificar, mediante una declaración responsable, que el sistema informático cumple con lo dispuesto en el artículo 29.2.j) de la Ley 58/2003 […] así como con lo dispuesto en este Reglamento».

For BeeL., that declaration is signed by **Honey Solutions, S.L.** It is published, with every version, at **[beel.es/declaraciones-responsables](https://beel.es/declaraciones-responsables)**, where anyone can download it.

The declaration is the producer's own. AEAT's published FAQ on VERI\*FACTU describes it as an «"auto-certificación" del propio productor del producto SIF realizada como Declaración Responsable», and states that no certification by independent bodies and no prior registration of the product is required. BeeL. is therefore **not certified, homologated or approved by AEAT** or by any other body: what exists is its producer's *declaración responsable*.

## Software built on the API [#software-built-on-the-api]

Whether software that uses BeeL. is itself part of a billing system depends on what that software does. These are the rules and criteria that apply:

- A SIF can be made of several components. Article 15.4 of the Orden HAC/1177/2024: when the system «esté formado por varios componentes […] producidos por diferentes personas o entidades, todas ellas deberán aportar las correspondientes declaraciones responsables de sus componentes».
- AEAT's FAQ for developers (version 1.3, section 5) states that every component of such a system needs a *declaración responsable*, and exempts only the components whose functions are irrelevant to the rules: «fundamentalmente, las que no afecten a la generación del RF, a su encadenamiento, a la impresión de facturas, a la generación del QR, al envío a sede electrónica, al enlace indefectible entre componentes, a la conservación inalterada ni al registro de eventos».
- AEAT's FAQ also states that when a user extends a SIF with its own means, «el responsable de la ampliación será el usuario del SIF, que como productor de la misma deberá certificarla».

Under that criterion, **printing the invoice and generating its QR are among the functions that make a component relevant**. Software that renders its own invoice document, even with the number and QR data BeeL. returns, may be treated as a component of the billing system with its own *declaración responsable*. BeeL.'s declaration covers BeeL.; it does not extend to software that others build on the API.

What BeeL. does and does not let your software do:

- the number, the billing record, the hash, the chain and the submission are always produced in BeeL., and no request accepts them from outside;
- corrections and cancellations are made through BeeL. ([corrective invoices](/verifactu/corrective-invoices), [voids](/verifactu/cancel-and-fix));
- BeeL. renders a PDF with the QR and its legend for every invoice it registers — see [QR code and the invoice PDF](/verifactu/qr-and-pdf);
- the QR data is also returned, so software can print it on a document it renders itself — see [Rendering your own PDF](/verifactu/qr-and-pdf#rendering-your-own-pdf).

Whether your architecture needs its own *declaración responsable* is a question to settle with your tax advisor before you go live, with the rules above in hand.

## The issuing business [#the-issuing-business]

A business that issues its invoices with BeeL. signs **one** document: the [representation](#representation-not-a-certificate) that lets BeeL. submit its billing records to AEAT on its behalf, once per NIF.

It does not sign a *declaración responsable*. That declaration is the software producer's, not the user's: BeeL.'s is signed by its producer, Honey Solutions, S.L., and it covers every business that invoices with BeeL. Using a billing system whose producer has signed one is what the rules ask of the user.

Signing the representation does not move the issuer's obligations to BeeL. They remain the issuer's, among them:

- those of the RD 1619/2012: the duty to issue invoices, their content (articles 6 and 7) and keeping copies of them (article 19);
- article 29.2.j of the Ley General Tributaria, which places on «los productores, comercializadores y usuarios» the duty that billing systems «garanticen la integridad, conservación, accesibilidad, legibilidad, trazabilidad e inalterabilidad de los registros».

BeeL. builds each record from the data it receives: the issuer's fiscal data, its series, the tax rates and the classification of each operation. BeeL. validates the format and some consistency rules of that data, but it cannot know whether the data is true. How responsibility is allocated between BeeL. and its users is set out in the [Terms](https://beel.es/terminos).

> **Rules that apply here:** [CNT-004 · Every invoice shows the issuer's NIF](/rules/contents#cnt-004)

## VERI\*FACTU modality [#verifactu-modality-only]

BeeL. submits billing records only in the **VERI\*FACTU** modality (article 16 of the RD 1007/2023), at the time each invoice is issued. It does not offer the "no VERI\*FACTU" modality, in which records are kept by the system and signed instead of being submitted.

VeriFactu is enabled per issuing NIF. For each NIF it includes signing the representation that authorises BeeL. to submit on the taxpayer's behalf. **Invoices a NIF issues while VeriFactu is not enabled for it generate no billing record and are not submitted**: they carry `verifactu.enabled: false` — see [Auto-submit policy](/verifactu/auto-submit).

The rules on timing:

- The RD 1007/2023, as amended by the RD-ley 15/2025, requires Corporate Tax payers to have their billing systems adapted «antes del 1 de enero de 2027», and the other taxpayers of its article 3.1 «antes del 1 de julio de 2027».
- Article 16.5 of the RD 1007/2023: the choice of VERI\*FACTU «se prolongará, al menos, hasta la finalización del año natural en el que se haya producido, de forma efectiva, el primer envío de los registros de facturación». Article 17 of the Orden HAC/1177/2024 sets the same until 31 December of that year.

Before turning VeriFactu off for a NIF, or issuing from a NIF for which it is not enabled, confirm with the taxpayer's advisor how these rules apply on that date.

BeeL. is used by several taxpayers, each with separate billing records, numbering, series and chain. Article 7.a of the RD 1007/2023 allows «un mismo sistema informático […] por parte de diversos obligados tributarios […] siempre que los registros de facturación de cada obligado tributario se encuentren diferenciados».

> **Rules that apply here:** [REC-003 · VERI*FACTU is kept until the end of the year](/rules/records#rec-003)

## Representation, not a certificate

BeeL. submits each record to AEAT **on the taxpayer's behalf**, under a representation that the NIF's holder signs once. Article 5 of the Orden HAC/1177/2024 allows the submission to be made «por el propio obligado tributario o por un tercero que actúe en su representación». No digital certificate is handed to BeeL. for the submissions, by the taxpayer or by the integrator.

The holder signs the representation document BeeL. generates, electronically and with their own certificate, once. Generating it, downloading it, uploading the signed copy and checking its status are all API calls; only the signing is done by the holder. The steps are in [Signing the VeriFactu representation](/multi-nif/companies#signing-the-verifactu-representation) and [Enabling VeriFactu for a NIF](/verifactu/enabling-verifactu). In sandbox there is no representation to sign.

> **Rules that apply here:** [REC-006 · No certificate is needed to sign records](/rules/records#rec-006) · [REC-011 · The NIF holder signs the AEAT representation first](/rules/records#rec-011)

## What BeeL. keeps for each invoice

For each invoice, BeeL. stores its billing record, its hash and AEAT's answer, and returns them through the API:

- the invoice's `verifactu` block — `submission_status`, `invoice_hash`, `qr_url`, `error_code` / `error_message` — see [Submission states](/verifactu/submission-states#reading-the-aeat-response);
- every record of the invoice, registration and cancellation, each with its own status — [List the VeriFactu records of an invoice](/invoices/listCompanyInvoiceVerifactuRecords);
- what the record sent to AEAT contains — [What AEAT receives](/verifactu/what-aeat-receives).

On keeping records, article 3 of the Orden HAC/1177/2024 exempts systems acting as VERI\*FACTU from its articles 8 (conservation of records) and 9 (event log). The duty to keep copies of the invoices themselves, in article 19 of the RD 1619/2012, belongs to the issuer; article 19.3 allows a third party to carry it out materially, with the issuer remaining responsible. BeeL.'s commitments on how long it keeps data are the ones in its [Terms](https://beel.es/terminos) and [privacy policy](https://beel.es/privacidad); this page adds none.

> **Rules that apply here:** [CON-001 · Keep copies of issued invoices for the limitation period](/rules/conservation#con-001) · [CON-002 · AEAT keeps the records, not your invoices](/rules/conservation#con-002)

## Related

<Related>

- [Terms, VeriFactu section](https://beel.es/terminos#verifactu) — BeeL.'s binding position
- [Declaraciones responsables](https://beel.es/declaraciones-responsables) — every published version
- [Integrating BeeL. into your ERP](/guides/erp-integration) — who numbers, who renders, who sends
- [Multi-NIF](/multi-nif) — one integration, many issuers
- [FAQ](/faq#compliance) — the short answers

</Related>

---

Full OpenAPI spec: https://docs.beel.es/api/openapi