NewThe SII in Live, under contract
BeeL
Get startedMulti-NIFVeriFactuSIIRulesStripeAPI referenceChangelog

Companies in the SII

How a company in the SII issues its invoices with BeeL.: scope, activation, what changes on the invoice and in the API, the deadline, rejections and SII-only rules.


The SII (Suministro Inmediato de Información) is the AEAT ledger where some companies keep their VAT books, submitting a record of each invoice within days. For a company in the SII, BeeL. sends its issued invoices to the SII instead of registering them under VERI*FACTU. The invoice is issued the same way, through the same endpoints; what changes is where it is reported, what the invoice carries and a handful of checks before it is numbered.

The SII is available under contract: talk to sales. In Sandbox it can be tried without one.

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.

What BeeL. covers

CoveredThe invoices the company issues through BeeL.: standard, simplified, corrective and exchange invoices, and their voids
Not coveredReceived invoices (the ledger of invoices received from suppliers), and the SII of the foral tax administrations or of the Canary Islands tax agency
TicketBAINot covered

The company keeps its other SII ledgers through its own means. BeeL. only reports the invoices it issues, and only those issued on or after the date the SII applies to the company.

SII or VERI*FACTU

A company that keeps its VAT books through the SII is outside the billing-systems regulation (RD 1007/2023), so it does not use VERI*FACTU (DAT-011 Adapted billing systems are mandatory from 1 January 2027 or 1 July 2027). In BeeL. the two never apply on the same day: a company reports through one system or the other, and activating one ends the other on the same date.

Which system applies is decided once, when the invoice is issued, from the system that applies to the company on its issue date. It is a fact of the company, never a choice per invoice or per series.

Activating the SII

The compliance systems of a company are read and changed with three operations:

To activate the SII, send effective_from, the settings (periodicity and reason, both required) and acknowledge_responsibility: true, with an Idempotency-Key:

POST /v1/companies/{company_id}/compliance/systems/SII/activate
{
  "effective_from": "2027-01-01",
  "settings": {
    "periodicity": "MONTHLY",
    "reason": "MANDATORY_LARGE_COMPANY"
  },
  "acknowledge_responsibility": true
}
  • reason says why the company is in the SII: MANDATORY_LARGE_COMPANY, REDEME, VAT_GROUP or VOLUNTARY.
  • periodicity is how often the company files its VAT returns: MONTHLY, or QUARTERLY only with reason VOLUNTARY (otherwise SII_QUARTERLY_REQUIRES_VOLUNTARY).
  • acknowledge_responsibility confirms that the company is subject to the SII for that reason and that the data it reports is its responsibility. Without it: SII_ACKNOWLEDGEMENT_REQUIRED.
  • The AEAT census. Activating the SII registers the company's NIF for SII submission, so the company needs a NIF. Its option for the SII must be in force in the AEAT tax census by effective_from; otherwise the AEAT rejects the submissions.
  • The other system. If VERI*FACTU applies, it ends on effective_from in the same call, and the response shows how the company is left. When that is not possible, the request answers COMPLIANCE_SYSTEMS_INCOMPATIBLE and nothing changes.
  • The environment. A system that cannot be activated in the environment of the request answers COMPLIANCE_SYSTEM_NOT_AVAILABLE.

The full order in which these checks run is in the reference of the activate operation.

In Live

In Sandbox

No contract is needed, and the company can enter and leave the SII and change its settings on any date from today. A company in Sandbox always reports through VERI*FACTU or the SII: deactivating the one that applies without activating the other answers COMPLIANCE_REQUIRED_IN_SANDBOX.

Tax address in the common territory

The SII of the AEAT is the one of the common territory. It can only be activated for a company whose tax address is in Spain and in the common territory, and with the SII active each invoice is checked against the company's tax address as it stands when the invoice is issued (TAX-030 With the SII, the company's tax address must be in the common territory). On activation, an address in the Basque Country, Navarre, the Canary Islands, Ceuta or Melilla, or outside Spain, answers SII_TERRITORY_NOT_SUPPORTED; on issue, a Spanish address in one of those territories answers SII_ISSUER_TERRITORY_NOT_SUPPORTED.

What changes on the invoice

An invoice reported through the SII is not registered under VERI*FACTU:

  • it carries no VERI*FACTU QR code;
  • its verifactu block has enabled: false, which only means it was not registered under VERI*FACTU, not that it was not reported to the AEAT.

Numbering, series and totals work as usual. The checks of Rules that apply only with the SII run before the invoice is numbered, so an invoice the SII would not accept takes no number.

What changes in the API

The compliance array

Every issued invoice carries compliance: one entry per tax system it is owed to, in the same shape for every system. It is the source of truth for whether the invoice reached the AEAT; read it instead of the verifactu block, which only covers VERI*FACTU. For a company in the SII, the entry has type: SII.

FieldWhat it says
typeThe system: SII
statusWhere the invoice stands, in a vocabulary shared by every system: NOT_SUBMITTED, IN_PROGRESS, FULFILLED, FULFILLED_NEEDS_FIX, REJECTED or CANCELLED. Branch on this
system_statusThe status as the SII states it, as sii:<CODE>. Informational only
stampsThe values the SII returned that have to be kept or printed
updated_atWhen status, system_status or stamps last changed

The SII stamps are:

  • sii-csv: the secure verification code (CSV) the AEAT returned for the submission that recorded the invoice in the SII.
  • sii-reconciliation: the reconciliation status (EstadoCuadre) the AEAT reports for the invoice in the SII ledger, when there is one.

More keys may be added: keep or ignore one you do not know.

Submissions

List the compliance submissions of an invoice returns every submission of the invoice, each with its operation (ISSUE, CORRECT or CANCEL), its own status, and the error_code and error_message of the outcome. The invoice's compliance summarises where it stands; this resource lists what was sent to get there. When an invoice is voided, BeeL. sends its cancellation, and the entry moves to CANCELLED once the SII accepts it.

The invoice.compliance.updated webhook

invoice.compliance.updated is delivered when the status, system_status or stamps of an entry change, and carries the entry as it is after the change. Route on compliance.type, branch on compliance.status, and ignore a type you do not know. verifactu.status.updated only covers VERI*FACTU: subscribe to invoice.compliance.updated for the SII.

Submission deadline

The deadline is set by the law, and it is the company's. For issued invoices, article 69 bis.1.a) of the VAT Regulation (RD 1624/1992, added by the RD 596/2016) requires the record within 4 days from the issue of the invoice, and in any case before day 16 of the month after the one in which the VAT accrued:

«La información correspondiente a las facturas expedidas, en el plazo de cuatro días naturales desde la expedición de la factura [...]. En ambos supuestos el suministro deberá realizarse antes del día 16 del mes siguiente a aquel en que se hubiera producido el devengo del Impuesto correspondiente a la operación que debe registrarse.»

Corrective invoices follow the same 4 days from their issue (article 69 bis.1.d). Saturdays, Sundays and national public holidays are not counted.

BeeL. reports each invoice issued through it; the SII entry of compliance tells you whether it has been sent and what the AEAT answered.

Rejected invoices

With the SII, a REJECTED invoice does not need anything from you: BeeL. sends it again.

  • invoice.compliance.updated is delivered when the status changes.
  • The submission in compliance-submissions gives the reason in error_code.
  • If the customer's NIF or name is not in the AEAT census, sending it again leaves the status in FULFILLED_NEEDS_FIX: the SII accepted it but reported errors in the data. Review them and tell the user.
  • If the cause is in data that only you can correct, BeeL. contacts you.

This is different from VERI*FACTU, where a rejected invoice has to be sent again once the cause is fixed (Handling AEAT rejections).

Rules that apply only with the SII

These checks run only for a company with the SII active, and they run before the invoice is numbered: an invoice that fails them takes no number. The same invoice remains valid for a company under VERI*FACTU. The tax-address rule is in Tax address in the common territory.

Regime keys

Taxes and the VAT breakdown

Recipients identified abroad

Permanent establishments

Corrective invoices