# 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](https://beel.es/ventas). 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 [#what-it-covers]

| | |
|---|---|
| **Covered** | The invoices the company issues through BeeL.: standard, simplified, corrective and exchange invoices, and their voids |
| **Not covered** | Received invoices (the ledger of invoices received from suppliers), and the SII of the foral tax administrations or of the Canary Islands tax agency |
| **TicketBAI** | Not 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 [#sii-or-verifactu]

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](/rules/dates#dat-011)). 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 [#activating-the-sii]

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

- [Get the compliance systems of a company](/compliance/getCompanyCompliance): the systems that apply today (`ACTIVE`) and the ones scheduled for a later date (`SCHEDULED`), each with its period and `settings`.
- [Activate a compliance system](/compliance/activateCompanyComplianceSystem), with `SII` in the path.
- [Deactivate a compliance system](/compliance/deactivateCompanyComplianceSystem).

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

```json title="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`](/errors/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`](/errors/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`](/errors/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`](/errors/COMPLIANCE_SYSTEM_NOT_AVAILABLE).

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

### In Live [#in-live]

- **Contract.** The account needs the SII contracted; without it the request answers [`SII_NOT_CONTRACTED`](/errors/SII_NOT_CONTRACTED), and an account whose billing is not set up or not paid answers `402`.
- **From tomorrow.** Every change of the SII takes effect tomorrow at the earliest ([`SII_CHANGE_ONLY_FROM_TOMORROW`](/errors/SII_CHANGE_ONLY_FROM_TOMORROW)).
- **Entering.** A company enters the SII on 1 January ([DAT-016 · In Live, a company enters the SII on 1 January, unless it is already in the SII and has not used VeriFactu that year](/rules/dates#dat-016)). To enter on another date it declares `settings.already_in_sii: true`: it is already registered for the SII in the AEAT tax census, and the records of that year before `effective_from` are submitted by the company or its previous provider, not by BeeL. Even with that declaration, the entry is rejected with [`SII_ENTRY_ONLY_FROM_JANUARY_FIRST`](/errors/SII_ENTRY_ONLY_FROM_JANUARY_FIRST) when VERI\*FACTU applies to the company on any day from today until the day before `effective_from`, or when the company has issued invoices in Live through VERI\*FACTU dated from 1 January of that year to the day before `effective_from`.
- **Leaving and changing.** When the company can leave the SII, or change its `reason` or `periodicity`, depends on the `reason` of the period in force ([DAT-015 · In Live, a company leaves the SII or changes how it reports only on the dates its reason allows](/rules/dates#dat-015)).

### In Sandbox [#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`](/errors/COMPLIANCE_REQUIRED_IN_SANDBOX).

### Tax address in the common territory [#tax-address]

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](/rules/taxes#tax-030)). On activation, an address in the Basque Country, Navarre, the Canary Islands, Ceuta or Melilla, or outside Spain, answers [`SII_TERRITORY_NOT_SUPPORTED`](/errors/SII_TERRITORY_NOT_SUPPORTED); on issue, a Spanish address in one of those territories answers [`SII_ISSUER_TERRITORY_NOT_SUPPORTED`](/errors/SII_ISSUER_TERRITORY_NOT_SUPPORTED).

## What changes on the invoice [#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](#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 [#what-changes-in-the-api]

### The `compliance` array [#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`.

| Field | What it says |
|---|---|
| `type` | The system: `SII` |
| `status` | Where 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_status` | The status as the SII states it, as `sii:<CODE>`. Informational only |
| `stamps` | The values the SII returned that have to be kept or printed |
| `updated_at` | When `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 [#submissions]

[List the compliance submissions of an invoice](/invoices/listCompanyInvoiceComplianceSubmissions) 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 [#webhook]

[`invoice.compliance.updated`](/webhook-events/onInvoiceComplianceUpdated) 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 [#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 [#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](/verifactu/handling-rejections)).

## Rules that apply only with the SII [#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](#tax-address).

### Regime keys [#regime-keys]

- [TAX-025 · With the SII, regime keys 07, 11, 19 and 20 are not accepted](/rules/taxes#tax-025): keys `07`, `11`, `19` and `20` answer [`SII_REGIME_KEY_NOT_SUPPORTED`](/errors/SII_REGIME_KEY_NOT_SUPPORTED).
- [TAX-027 · With the SII, the regime keys of an invoice form a combination the SII accepts](/rules/taxes#tax-027): the SII declares one regime key per invoice and up to two additional ones, only in the combinations the AEAT lists; any other combination answers [`SII_REGIME_KEYS_COMBINATION_NOT_VALID`](/errors/SII_REGIME_KEYS_COMBINATION_NOT_VALID).

### Taxes and the VAT breakdown [#taxes-and-breakdown]

- [TAX-026 · With the SII, every line is taxed with IVA, IGIC or IPSI](/rules/taxes#tax-026): every line is taxed with IVA, IGIC or IPSI; a line with `main_tax.type: OTHER` answers [`SII_TAX_NOT_SUPPORTED`](/errors/SII_TAX_NOT_SUPPORTED).
- [TAX-028 · With the SII, subject and non-exempt lines with and without reverse charge are declared together](/rules/taxes#tax-028): lines with and without reverse charge are declared together, within the limits of the SII breakdown; an invoice outside them answers [`SII_BREAKDOWN_NOT_SUPPORTED`](/errors/SII_BREAKDOWN_NOT_SUPPORTED).

### Recipients identified abroad [#recipients-identified-abroad]

- [CNT-029 · With the SII, a recipient identified abroad needs the nature of each line](/rules/contents#cnt-029): an invoice to a recipient identified with `alternative_id`, or with a Spanish NIF that starts with `N`, carries `nature` (`GOODS` or `SERVICES`) on every line; without it: [`SII_NATURE_REQUIRED`](/errors/SII_NATURE_REQUIRED).
- [CNT-028 · With the SII, a United Kingdom VAT number is accepted only as Northern Ireland and for goods](/rules/contents#cnt-028): a United Kingdom VAT number is accepted only as Northern Ireland (`XI`) and for goods; otherwise: [`SII_UK_VAT_ID_NOT_ACCEPTED`](/errors/SII_UK_VAT_ID_NOT_ACCEPTED).

### Permanent establishments [#permanent-establishments]

- [TAX-029 · With the SII, do not issue operations made through a permanent establishment in the Canary Islands, Ceuta or Melilla](/rules/taxes#tax-029): with the SII active, every IGIC or IPSI line is recorded as an operation made from the territory of application of IVA. The AEAT never takes in the SII an operation made through a permanent establishment in the Canary Islands, Ceuta or Melilla, and the request carries no field that identifies it, so do not issue such an operation from a company with the SII active.

### Corrective invoices [#corrective-invoices]

- [COR-025 · With the SII, an R4 or R5 corrective that raises the VAT goes to the original invoice's period](/rules/corrective#cor-025): a corrective with `rectification_code` `R4` or `R5` that raises the VAT is recorded in the SII in the tax period of the original invoice. For that period, the business files a supplementary VAT return with its tax adviser.

## Related

- [Compliance and responsibilities](/verifactu/compliance-and-responsibilities)
- [Handling AEAT rejections](/verifactu/handling-rejections)
- [Fiscal rules](/rules)

---

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