Glossary of Terms
SIF
The Billing IT System (SIF) is the Information System that issues invoices including their tax QR code, while "simultaneously" generating, sending and storing their corresponding chained Billing Records (RF).
It is composed of:
- The corresponding Billing Software, which generates invoices, prints them with their tax QR, and stores the billing records.
- SDH, which generates the tax QR for each new invoice, performs the Chaining, and "simultaneously" sends the billing record.
Glossary Used in SDH
| Term | Description |
|---|---|
| Company | The taxpayer (Corporate Name and TIN/NIF) that sends its invoices using SDH. The company must sign a contract with SDH with an annual invoice plan, and upon registration in SDH it is assigned a Company Identifier. |
| Installation | Normally, a company issues invoices from a single location or installation, and upon registration in SDH it is assigned an Installation Identifier. SDH allows managing multiple installations for a company, each with its own Installation Identifier. For example, if a company issues invoices with the same NIF from a location in Madrid and another in the Canary Islands, two installations are required in SDH, marking the timezone adjustment for the Canary Islands installation. |
| Customer | A multi-company environment or customer is supported. This Customer (a group of companies) must have a certificate for authentication in the SDH API. |
| Request | A request is the operation performed from the Billing Software to the SDH platform. |
| Container | Each request is recorded in a container, and its input and output data may also be stored. For example, there are containers for invoice status queries or for sending invoice books to the Tax Administration. |
| Document | Documents are the containers corresponding to fiscal reports that are sent to the Tax Agency (Administration). |
| Invoice | An invoice normally consists only of its issuance, but it also includes possible corrections or its cancellation. |

Certificates Managed in SDH
| Certificate Type | Description |
|---|---|
| For Authentication in SDH | Persistent in the Billing Software. Required for API security, as it is an element that the API consumer must possess. In a multi-company environment (the Customer corresponds to this group of companies), the certificate is the same for all companies. More information in the role Customer Administrator. |
| For delivering documents to the Administration | Configured in SDH. Required by the Administration. If the collaboration agreement with the AEAT is signed, then Zucchetti Spain’s seal certificate is used. More information in the role Company Administrator. |
Document Signatures for Each Company in SDH
More information in the role Company Administrator.
| Signing of | Description |
|---|---|
| Contract with SDH | Mandatory, so that SDH can process the invoices received from the Billing Software. |
| Collaboration agreement with AEAT | Optional but highly recommended, allowing SDH to sign document submissions to the Administration with Zucchetti Spain’s seal certificate. Otherwise, the company must manage its own seal certificate. |