fiskaly SIGN ES

Introduction

fiskaly SIGN ES is a cloud-based fiscalization solution for the Spanish market, provided as Software as a Service (SaaS). It enables POS providers (CUSTOMER) and their merchants (END CUSTOMER) to comply with Spanish fiscalization regulations, covering Verifactu, TicketBAI, SII, and the associated B2B e-invoicing framework — all through a single API. The service also supports the Customer’s role in relation to the AEAT (Spanish Tax Authority) as a social collaborator for the telematic submission of invoicing records. fiskaly SIGN ES is accessed via a RESTful API and managed through the fiskaly HUB.

Service Description

fiskaly makes fiskaly SIGN ES available to the CUSTOMER as SaaS. The CUSTOMER obtains access via the API and may sublicense its use to END CUSTOMERS through an authorisation system. Key aspects include:

• Compliance with TicketBAI, Verifactu, SII and applicable Spanish fiscalization regulations.
• Non-exclusive, non-transferable right of use, limited to the contract term and the territory of the Kingdom of Spain, sublicensable only to END CUSTOMERS.
• Data generated by the END CUSTOMER is stored for a three (3) month period.
• Provision of the current version of fiskaly SIGN ES, including updates at irregular intervals.
• Access to a TEST SYSTEM.
• Social collaboration with AEAT: fiskaly makes available its electronic certificate as a social collaborator for the telematic remission of invoicing records, subject to the formalization of a legally signed representation agreement between fiskaly and the END CUSTOMER.

📘Note

fiskaly’s scope of services does not include: integration into recording systems; individual solutions or adaptations; training; internal documentation (except via workspace.fiskaly.com); data transfer services; storage beyond the contract validity and term; or support not expressly specified.

Functionalities

• Cryptographic transaction signing: Transactions are signed in compliance with TicketBAI and/or Verifactu requirements.
• Signature chaining: Each record is cryptographically linked to the preceding one, preventing deletion, alteration, or back-dating.
• Telematic submission to AEAT: Supports submission of invoicing records to the AEAT electronic site, subject to a valid representation agreement.
• Authorisation system: The CUSTOMER manages END CUSTOMER access via user credentials or other approved procedures.
• Management via fiskaly HUB: Administration and configuration of fiskaly SIGN ES instances.
• Continuous monitoring: fiskaly monitors functionality up to the API and eliminates malfunctions.
• Update management: Updates are announced at least two weeks in advance (e.g., via workspace.fiskaly.com) and deployed during defined maintenance periods.

System Requirements

• A valid contractual relationship with fiskaly.
• An internet connection for integration and operation.
• Integration of the fiskaly SIGN ES API into the CUSTOMER’s recording system.
• Non-blocking or asynchronous integration to ensure uninterrupted operation.
• The CUSTOMER must ensure the recording system’s operation is not limited in case of a potential outage.
• For AEAT submission: a legally signed representation agreement between fiskaly and the END CUSTOMER (in Spanish), with valid consent accredited by a reliable record of authorization — required for Verifactu and SII.
• For TicketBAI submission: must register/accept the fiskaly device certificate with their tax authority before or shortly after the device starts issuing Ticket BAI files in their name, depending on the province:
  • Gipuzkoa: Once the device is issuing in the name of the taxpayer, the device will appear in the system and must be accepted within one month.
  • Araba: The device certificate must be registered before the device starts issuing Ticket BAI files in the name of the taxpayer.
  • Bizkaia: The device certificate must be registered before the device starts issuing Ticket BAI files in the name of the taxpayer.

Maintenance and Support

fiskaly is committed to maintaining and updating fiskaly SIGN ES. fiskaly undertakes to maintain and update the Service with a view to supporting its security, availability, and ongoing alignment with applicable technical and reporting requirements; however, the Customer remains responsible for implementing required updates, migrations, and integration changes on its side. The service is versioned according to semantic versioning; significant changes resulting in new major releases will be documented. Maintenance activities may result in the temporary outage of the service. As far as possible, these activities shall be announced at least two (2) weeks in advance; emergency maintenance activities may deviate from this. fiskaly provides assistance to customers via the fiskaly support portal (support.fiskaly.com).

Testing

fiskaly provides a TEST SYSTEM for fiskaly SIGN ES, which is a fully functional sandbox environment. The CUSTOMER can validate integration before going live. fiskaly is not responsible if real data is used in the TEST environment.

Service Limitations

• Functionality outside the API (particularly on recording systems) is not warranted.
• No warranty for proper integration into the CUSTOMER’s recording system.
• No warranty for requirements for itemised billing, document splitting, or cash register obligations beyond TicketBAI and/or Verifactu obligations.
• No warranty for other requirements for proper recording system operation (e.g., archiving).
• No binding resolution times for malfunctions.
• Fault reports from END CUSTOMERS directly are not accepted or processed.

Customer Obligations

• Responsible for integrating fiskaly SIGN ES into recording systems at own expense, meeting all framework criteria.
• Must ensure the recording system’s operation is not limited in case of a potential outage.
• Must support fiskaly in the provision of its contractual services to a reasonable extent and must not engage in any conduct that makes it more difficult for fiskaly to provide its services. Such conduct includes, but is not limited to:
  • Unusually high demand on fiskaly SIGN ES or its essential components, such as transaction volume or storage (e.g., where fiskaly can attribute unusually high demand to non-real business cases of the CUSTOMER or its END CUSTOMER).
  • Abusive use of services via support channels, such as multiple incorrectly categorised P1–P2 fault reports, thereby causing incident management costs on the part of fiskaly.
• Must not misuse the service or negatively affect availability for other customers; data must be free of harmful components.
• Acknowledges that the END CUSTOMER is responsible for compliance with all statutory obligations of TicketBAI, Verifactu and SII.
• Must notify fiskaly of any changes to company data in good time.
• For AEAT submission: must integrate the representation agreement process as indicated by fiskaly, ensure valid END CUSTOMER consent, and verify and preserve evidence of such consent — required for Verifactu and SII.
• For TicketBAI submission: must register/accept the fiskaly device certificate with their tax authority before or shortly after the device starts issuing Ticket BAI files in their name, depending on the province:
  • Gipuzkoa: Once the device is issuing in the name of the taxpayer, the device will appear in the system and must be accepted within one month.
  • Araba: The device certificate must be registered before the device starts issuing Ticket BAI files in the name of the taxpayer.
  • Bizkaia: The device certificate must be registered before the device starts issuing Ticket BAI files in the name of the taxpayer.
• Must provide truthful and complete information and ensure that END CUSTOMER personal data is processed solely for the purpose of regulatory compliance, in accordance with GDPR and applicable Spanish data protection law.

---

Version: v.1 | Last updated: 2026/03/24