For software developers and vendors looking to ensure their systems are in line with Italian fiscal law, we bring exciting news—the launch of SIGN IT! This new solution offers streamlined and effective compliance for Italy, and the documentation and guides are now available on our developer site.

What is SIGN IT?​

SIGN IT offers a cloud fiscalization solution for Italy, with an API designed to simplify the complexities of fiscal compliance. It provides developers with the tools needed to integrate compliance features into their software effortlessly. This service is crucial for ensuring that digital transactions meet all necessary fiscal requirements, thereby reducing the risk of non-compliance penalties, and guaranteeing top-tier performance and reliability at every step of the compliance process.

Navigating Italian regulations made easy​

The Italian government mandates strict regulations that businesses must adhere to, particularly concerning electronic transactions and fiscal receipts. These laws ensure transparency and fairness in financial dealings, crucial for maintaining both business integrity and consumer trust.

Italy has embraced cloud-based fiscalization solutions, and we’re excited to provide our expert software for complete compliance: SIGN IT. It interprets and implements the necessary legal frameworks into an easy-to-use API, allowing developers to integrate fiscal compliance into their systems seamlessly.

Now available: SIGN IT API Documentation & Guides​

The SIGN IT API documentation and guides are live on our developer site. IT is designed to walk you through every aspect of SIGN IT. You'll find step-by-step guides, code samples, and best practice tips to integrate SIGN IT into your applications swiftly.

• SIGN IT API documentation
• SIGN IT Integration guide

Scheduled Maintenance: Authentication Server​

Date: Sunday, 01.09.2024
Time: 9:00 - 9:30 CEST (7:00 - 7:30 UTC)

In preparation for a necessary infrastructure update, please be advised that our authentication services will experience periods of unavailability during the scheduled maintenance window on September 1, 2024, from 9:00 to 9:30 CEST (7:00 to 7:30 UTC).

Impact​

• User Management:
  Creation, updating, and deletion of users, API keys, and organizations (including managed organizations) may not be possible during this time.

• Token Generation:
  Generating new authentication tokens may be temporarily unavailable.

• Token Invalidation:
  Existing access and refresh tokens may be invalidated post-maintenance.

Token Handling Advisory​

If a refresh token is invalidated, it cannot be reused for re-authentication. To generate a new token, please use the relevant authentication endpoint along with your API key and API secret.

Implementation Notice​

Ensure your implementation falls back to ApiKeyAuthentication if RefreshTokenAuthentication returns a 401 HTTP status code.

Cheers,
Hannah from fiskaly

Expansion to Austria: Webinar Simplifying RKSV Fiscalization​

Are you a developer or a POS provider looking to expand your operations to Austria? Navigating the complex legal requirements of the Cash Register Security Regulation (RKSV) can be daunting. However, with the right tools, guidance, and fiskaly, you can ensure a smooth transition and compliance with Austrian fiscal laws.

What is the RKSV?​

The RKSV is Austria's Cash Register Security Regulation, designed to protect against tampering with electronic records of sales. Compliance with the RKSV is mandatory for all POS systems used in Austria. This regulation requires every transaction to be signed electronically, ensuring data integrity and traceability.

SIGN AT is fiskaly’s cloud-based fiscalization solution specifically designed to meet the stringent requirements of the RKSV. Here’s how SIGN AT can benefit your business:

By utilizing cloud-based signature creation, SIGN AT eliminates the need for physical signature devices, making the implementation process straightforward and reducing ongoing maintenance efforts.

SIGN AT is adaptable to businesses of any size, ensuring that as your business grows, your fiscalization process remains efficient and compliant.

Our solution uses state-of-the-art encryption technologies to ensure the highest level of security for your transaction data, safeguarding your business against fraud and data breaches.

Without the need for costly hardware, SIGN AT offers a cost-effective solution that lets you focus on expanding your business rather than managing compliance issues.

In the Webinar, You Will Learn:​

• The fundamentals of the RKSV and why compliance is critical.
• The features and benefits of SIGN AT, our cloud-based fiscalization solution.
• Practical examples of successful implementations in various industries.

Whether you're just starting your expansion journey or looking to enhance your existing operations, this webinar is packed with valuable insights to help you succeed in Austria.

Watch the Webinar​

Don't miss out! The webinar is available in both English and German to cater to your language preference.

• Watch the Webinar in English
• Watch the Webinar in German

We are pleased to inform our developer community that fiskaly has not been impacted by the recent global outage experienced by CrowdStrike. Our systems continue to operate seamlessly, ensuring no disruption in performance or availability.

Our decision to leverage Google Cloud Platform (GCP) has proven to be a wise choice, further reinforcing the robustness of our infrastructure. However, it's not just about the platforms we choose; it's about the meticulous processes we have in place.

At fiskaly, we understand the importance of a comprehensive tool evaluation process. This process ensures we are fully aware of the capabilities and potential risks associated with every tool on our devices. It’s about proactive prevention, not reactive solutions.

Moreover, our infrastructure is designed to be largely independent of any specific operating system. By building on cloud services, we ensure that as long as the cloud is operational, fiskaly can perform.

In essence, our approach combines the best of technology with robust operational processes to deliver uninterrupted, reliable service to our users, regardless of external disruptions.

Rest assured, fiskaly remains committed to providing seamless and secure services at all times. For further updates and insights, sign up to our Developer Newsletter and stay tuned to our Status Page.

SIGN DE​

Important Update: Changes to Export Behavior in the fiskaly SIGN DE v2 API​

Scheduled for calendar week 29 (July 15-21, 2024)

In the course of the upcoming deployment scheduled for calendar week 29, we are introducing an important change to the export functionality in the fiskaly SIGN DE v2 API which may impact your current integration. Moving forward, when an export is in the state PENDING or WORKING, additional export attempts of the same TSS using identical parameters will temporarily be blocked until the initial export is completed. Attempts to initiate a duplicate export will result in a 429 Too Many Requests error with the code E_EXPORT_DUPLICATE_RATE_LIMITED. Introducing this measure ensures system reliability and efficiency.

Please adjust your processes accordingly.

DSFinV-K​

Update to fiskaly DSFinV-K API: Changes to insertCashPointClosing Endpoint​

Scheduled for calendar week 30 (July 22-28, 2024)

In calendar week 30, an update to the fiskaly DSFinV-K API is scheduled for deployment. Starting with version 1.25, the insertCashPointClosing endpoint requires that the cash_statement.payment.payment_types[] array contains at least one item.

Previously, Cash Point Closings with an empty cash_statement.payment.payment_types[] array changed asynchronously the state to ERROR. As a result of the upcoming deployment and as part of the enhanced schema validation, the system will immediately return a validation error, if this requirement is not met.

Please make sure that your systems are updated to comply with this new validation process.

New DSFinV-K Implementation Guide​

We are happy to announce that a new and comprehensive DSFinV-K Guide aiming to enable an easy and fast integration is now available on our Developer Page.

Check out the DSFinV-K Guide ­

Essential Authentication Server Update​

We are announcing scheduled maintenance in July for the fiskaly Authentication Server:

July 2, 2024, from 05:00 to 07:00 CEST (03:00-05:00 UTC)​

During the essential infrastructure update aimed at enhancing service reliability, anticipate restricted access to functionalities such as user management, API Key alterations, and organization management features within the scheduled maintenance period. The creation of new authentication tokens will be temporarily halted, and there's a possibility that existing tokens will be invalidated.

Impact:

• Creating, updating, and deleting users, API Keys, and (managed-) organizations may be temporarily unavailable during the scheduled maintenance.
• Generating new authentication tokens may be temporarily unavailable during the scheduled maintenance.
• Existing access and refresh tokens may be invalidated following the maintenance.

Token Information:Invalidated refresh tokens cannot be used for re-authenticating. To generate a new token, please use the corresponding Authentication endpoint with your API Key and API Secret.

Implementation Notice:Please make sure your implementation uses ApiKeyAuthentication if RefreshTokenAuthentication fails with a 401 HTTP status code response.

For the latest updates on the status of fiskaly systems, please visit our Status Page.

Go to fiskaly Status Page

Upcoming Scheduled Maintenance​

We're scheduling a key maintenance session on April 7 to update our infrastructure, ensuring the continued delivery of high-quality service across our system's components.

April 7, 2024, from 7:00 to 10:00 CEST (5:00-8:00 UTC)​

We have planned a necessary infrastructure update to improve the overall performance and reliability of our services. The following services will be affected during the maintenance window:

• SIGN DE API V2 + V1
• DSFinV-K API
• Management API
• Dashboard
• Authentication Server

During this period, some services may not be available. Our team is committed to minimizing the impact of this maintenance and ensuring that services are restored promptly after the update.

For more detailed information regarding these maintenance periods, please visit our status page.

Go to fiskaly Status Page

Essential Infrastructure Maintenance​

We are announcing a short-term maintenance event for today:

🇩🇪 Germany​

SIGN DE API V2​

March 29, 2024, from 20:30 CET (19:30 UTC) to 23:00 CET (22:00 UTC)

Due to a necessary essential infrastructure update on the side of our hosting provider to ensure safe & stable operations, there will be a time window of 5 - 15 minutes in which the system will not allow any connection.

Visit our status page to stay up to date.

Go to fiskaly Status Page

Upcoming Scheduled Maintenance Events​

We are announcing two upcoming scheduled maintenance activities in March:

fiskaly Authentication Server​

March 24, 2024, from 6:00 to 7:00 CET (5:00-6:00 UTC)

During the essential infrastructure update aimed at enhancing service reliability, anticipate restricted access to functionalities such as user management, API key alterations, and organization management features within the scheduled maintenance period. The creation of new authentication tokens will be temporarily halted, and there's a possibility that existing tokens will be invalidated. In the event that refresh tokens are invalidated, it will be necessary to undergo re-authentication using the Authentication endpoint along with your API Key and Secret.

Developer Tip: As a precautionary measure, developers are advised to employ ApiKeyAuthentication as an alternative strategy if RefreshTokenAuthentication encounters a 401 error response.

🇩🇪 Germany​

SIGN DE API V2 + DSFinV-K​

March 17, 2024, from 6:00 to 8:00 CET (5:00-7:00 UTC)

As part of our ongoing commitment to quality and reliability, the necessary infrastructure upgrades will result in the temporary unavailability of SIGN DE V2. Additionally, users can expect prolonged processing times for DSFinV-K Cash Point Closings and Exports during this maintenance window.

For more detailed information regarding these maintenance periods, please visit our status page.

Go to fiskaly Status Page

Upcoming Scheduled Maintenance Events​

We are announcing two upcoming scheduled maintenance activities:

fiskaly Authentication Server​

February 13, 2024, 5:30 to 7:00 CET (4:30-6:00 UTC)

During the scheduled maintenance window, expect limited functionality on the fiskaly Dashboard and Management API, temporary suspension of token generation, and potential brief downtimes. Be aware that existing tokens may also be invalidated.

TLS Certificate Update​

February 7, 2024, 7:00 to 8:00 CET (6:00-7:00 UTC)

This routine update only affects intermediate certificates and is designed to ensure seamless service without major disruptions expected. Most systems will automatically adapt to this change, though a brief check post-update is advised.

Note: This update does not involve a change of the root certificate.

For comprehensive information about these maintenance events, please visit our status page.

Go to fiskaly Status Page

Keep Up-to-Date: Subscribe to Our Status Page​

We'd love for you to stay in the loop with us! Subscribing to our status page is a great way to keep yourself updated. While our developer newsletter brings you the fiskaly highlights for developers, it might not cover everything. Subscribing to our status page means you'll ensure that you're always up-to-date with all the essential news.

On our support site, you can find the guide on 'How to subscribe to the fiskaly status page'. This article is available in ENGLISH, GERMAN or SPANISH.

🇪🇸 Spain​

Automatic BATUZ Submission for Companies​

Effective February 1st, 2024, POS vendors with our SIGN ES API integration can offer their business clients a streamlined BATUZ submission process. This update automatically sends the BATUZ LROE book, Subchapter 1.1, for issued invoices directly to tax authorities in real-time. This feature is currently exclusive to companies, ensuring hassle-free compliance and enhanced efficiency.

Note: This automation does not extend to individual taxpayers, and manual BATUZ submissions are required for January invoices in Bizkaia. This integration significantly eases the tax reporting process for your business clients.

🇩🇪 Germany​

Updates on KassenSichV 2024​

Effective January 1, 2024, KassenSichV regulations require receipts in Germany to include serial numbers for both the electronic record-keeping system (ERS) and the security module (TSS). Details are outlined in our blog post "KassenSichV in 2024 – What will change" summarizes all the important information for you.

If you're already using QR codes on receipts, no further action is needed.
If you use plain text on receipts, ensure they now include these serial numbers. We recommend switching to QR codes for streamlined compliance.

Technical Integration of SIGN ES​

Fiscalization in Spain, Webinar #4​

Join us for the fourth part of our series Fiscalization in Spain, exploring the integration of the fiskaly SIGN ES API. Get insights:

• into Spanish fiscalization,
• understand the technology behind SIGN ES,
• and familiarize yourself with the onboarding process, daily operations, and more.

Don't miss out and register here:

Technical Integration: SIGN ES​

Date: 31.10.2023
Time: 4 pm CEST
Language: English Register now

Integración Técnica de SIGN ES​

Fecha: 02.11.2023
Hora: 16 hs (hora Madrid)
Idioma: Español Regístrate ahora

Missed previous sessions?​

For those who missed our past sessions, revisit the knowledge shared by visiting our YouTube channel, where we archive each enlightening discussion.

Webinar: Integrate SIGN ES​

We are pleased to announce the fourth part of our webinar series Fiscalization in Spain. The fourth session provides essential knowledge for the effective integration of the fiskaly SIGN ES API for fiscalization in Spain. It is designed especially for integration developers, and is available for Spanish and English-speaking audiences.

You will gain the following insights:

• Understanding Fiscalization in Spain & SIGN ES API: Familiarize yourself with the foundational concepts and role of the SIGN ES API within the framework of Spanish fiscalization.
• Technical Deep Dive: Gain an understanding of the underlying technology of the SIGN ES to leverage its full capabilities.
• Guided Onboarding Process: Receive step-by-step guidance during the onboarding phase, acquainting you with the dashboard and API navigation.
• Essential Setup Procedures: See the steps required for the effective setup and implementation of SIGN ES.
• Daily Operation Insights: Familiarize yourself with the daily operational functionalities and procedures associated with the solution.
• Compliance: Understand the necessary compliance measures and regulatory requirements pertinent to the solution.
• Validation Processes: Learn the techniques for accurate data validation with SIGN ES. Data Transmission: Understand the mechanisms for secure and efficient data transmission with SIGN ES.
  
  

Register to the Webinar:

English Webinar: “Fiscalization in Spain – Technical Integration SIGN ES”
Date & Time: Tuesday, October 31, 2023, 16:00 CEST. Register Here

Spanish Webinar: “Fiscalización en España – Integración Técnica de SIGN ES”
Date & Time: Thursday, November 2, 2023, 16:00 CEST. Register Here

Previously in Our Series:

• Webinar 1: TicketBAI & Veri*factu
• Webinar 2: Legal Requirements
• Webinar 3: Invoices and Digital Receipts in Spain
  
  

Upcoming in the Series:

• Webinar 5 (on-demand, available from November 6): Detailed Overview of SIGN ES Integration for SIGN DE Customers Register to access the webinar in English or in German
  
  

Stay connected!
Subscribe to our newsletter to stay up-to-date. We are committed to supporting you through every step of the integration process.

Cheers,
Hannah from fiskaly

We're excited to share some important updates and resources with you regarding fiscalization in Spain and our new product SIGN ES!

SIGN ES Integration and Testing​

Our product is now fully ready for integration and testing. We have extensively worked on enhancing its functionality and performance to meet your requirements and ensure compliance. Our Production Test environment is already available for you to try and it’s a matter of days until we enable Production Live. Stay tuned and subscribe to our change log for more updates.

How to get started?​

To get started, you can find detailed integration guides for new customers, but also for current SIGN DE customers on our developer website. These guides provide instructions on how to integrate our services effectively.

Postman Environment and Collection​

We have prepared a Postman environment and collection specifically designed for testing and providing a quick start to the integration of our API. With these resources, you can easily explore the capabilities of SIGN ES! You can access the Postman environment and collection on our developer website.

API Documentation​

In addition to the Postman environment and collection, we have prepared all the API documentation, including code samples ready for you. You can find these on our developer website.

We value your feedback and want to ensure you have a smooth integration experience. If you encounter any issues or have questions, our dedicated support team is here to assist you. Feel free to reach out to us at dev-support@fiskaly.com.

Cheers,
Hannah from fiskaly

fiskaly eReceipt API Update​

A major version change to eReceipt API version 2.0.0 and updates are planned for our eReceipt API on Thursday, 23rd March 2023 starting from 2 pm. The new version will be even better, with bugs fixed and improved consistency in our API.

Change log​

• Removal of default values for various schema fields in the CreateReceipt endpoint:
  For a list of properties (see Table 1 below) the default value 0 will be removed in the CreateReceipt endpoint. For mandatory fields, a value now needs to be sent explicitly. Invalid requests with missing mandatory fields will be answered with the error-code 400 and a corresponding error-message.
  
  
• Removal of the possibility to send additional fields in the CreateReceipt endpoint:
  The option to send additional properties in various Objects in the CreateReceipt endpoint will be removed. Until now, additional fields with any name and any type could be sent to the CreateReceipt endpoint. This option will be removed to improve clarity and improve consistency. See Table 2 below for a list of affected Objects.
  Exception: optional fields were retained for all Objects contained in the EkabsSecurity Object to allow for flexibility when providing the response from various fiscalization endpoints.

Table 1: Affected schema fields​

Table 2: Affected schema objects​

fiskaly website for developers: developer.fiskaly.com.
fiskaly status page: status.fiskaly.com.
fiskaly support website: support.fiskaly.com.

You can contact our support at dev-support@fiskaly.com.

­

­

­

SIGN DE​

As part of the ongoing SMAERS recertification, we are planning tests in our TEST environment starting from 25.7.2022 and until the end of the recertification process. This testing phase is expected to last until the end of September but may be extended depending on the test results. The tests will include trial upgrades to provisional versions, so don't worry if you see unfamiliar version numbers appearing in your exports. These upgrades may break some TSS instances or reveal some bugs. If you experience errors, please report them to our team at dev-support@fiskaly.com.

­

­ ­

DSFinV-K ​

v1.6.1 deployment 2022-07-12

• Fixed InterneTransaktion when used within the same Cash Point Closing.
• Fixed wrong sign_api_version when creating Cash Point Closings.
• Fixed postman links.
• Performance improvements for listing all Cash Point Closings.

We are preparing fiskaly DSFinV-K for OpenAPI 3.1, which will be rolled out in the next update.

­ ­

Cheers,

Hannah from fiskaly

fiskaly website for developers: developer.fiskaly.com.
fiskaly status page: status.fiskaly.com.
fiskaly support website: support.fiskaly.com.

You can contact our support at dev-support@fiskaly.com.

­

­

­

SIGN DE​

To give you a better understanding of fiskaly SIGN DE's system architecture, we have compiled all the relevant information about our system.
In the first part of our article, you can read more about the components of fiskaly SIGN DE and their functions within the system. In the second part, we explain our system in a legal context. Our article is only available in German.

fiskaly SIGN DE Architecture

­

Seminar fiskaly SIGN DE Architecture​

To give the best possible insight, we additionally invite you to our next online seminar:

fiskaly SIGN DE System Architecture

When: Tuesday, 12.07.2022 - 11 a.m. CEST

Seminar language: German

After the seminar, you will be familiar with the architecture of fiskaly SIGN DE, and know everything about the compliant operation of the fiskaly Cloud TSS as well as the environment protection concept of the fiskaly SMAERS.

Register for the seminar

­ ­

DSFinV-K ​

fiskaly DSFinV-K is updated to DSFinV-K 2.3 as required as of July 1, 2022.

v1.6 - deployment 2022-06-30

• Implements DSFinV-K 2.3 and DFKA taxonomy 2.3.

Note: Some changes must be addressed when using the DSFinV-K. Please have a look at the DSFinV-K legal text for more information.

• Added a new format field for `Trigger an Export` making it possible to export Cash Point Closings into a ZIP instead of TAR.
• Added new filters for `Trigger an Export` to export Cash Point Closings by their business_date (or export_creation_date as its fallback).
• Added Guthabenkarte (with a lowercase k) to payment types.
• Fixed exporting GuthabenKarte defined in the DFKA taxonomy and turning it into the corresponding Guthabenkarte as defined in DSFinV-K.
• Fixed potential race condition when exporting Cash Point Closings.
  Clarifying the date field of a Transaktion reference.

­

­

Cheers,

Hannah from fiskaly

fiskaly website for developers: developer.fiskaly.com.
fiskaly status page: status.fiskaly.com.
fiskaly support website: support.fiskaly.com.

You can contact our support at dev-support@fiskaly.com.

­

­

­

SIGN DE​

The previously announced update of the SIGN DE API on Sunday, June 5, 2022 is postponed.

We found an issue that was only detectable in large-scale and highly dynamic environments. As we need to address this bug correctly, we need to postpone the update. Therefore, the scheduled maintenance is no longer necessary and is canceled.

You as our customers feel no impact by this. The presently running certified TSS version (1.0.5-1.2.0) is stable and works reliably. Our SIGN DE Team put detailed information together in our blog post Postponed Update.

Big shout out to you!​

Without your help in intensively testing our system, we wouldn’t have been able to detect the issue. So thank you for testing our API! 

­

­

­

Hello support.fiskaly.com! ​

As part of our continuous effort to provide you with the best possible support, we are pleased to announce the launch of our new support website.

support.fiskaly.com

The new fiskaly support website will improve the service we offer to our customers by facilitating access to information. While we are working on providing more and more information on this site, we welcome suggestions on the content and overall feedback.

­

Postman + fiskaly ​

We now provide postman environments and collections for all our services. With Postman, APIs can be tested quickly and in a user-friendly way. Our Postman collections allow you to step through the most important functions of our APIs.

Try it out with our latest API, the eReceipt API, and implement it into your system. Bonus: The eReceipt is free of charge. ­

eReceipt + Postman

­

fiskaly SIGN DE​

Test fiskaly SIGN DE API with Postman for KassenSichV compliant TSS integration. ­

SIGN DE + Postman

­

fiskaly DSFinV-K​

Test fiskaly DSFinV-K API with Postman for KassenSichV compliant DSFinV-K Exports.

DSFinV-K + Postman

­

­

fiskaly SIGN AT​

Test fiskaly SIGN AT API with Postman for RKSV compliance in Austria.

SIGN AT + Postman

­

­

eReceipt ​

eReceipt API is now available in our TEST environment and our LIVE environment. 

­

­

DSFinV-K ​

v1.4.0 - deployment 2022-05-20

• Making it possible to use non-fiskaly TSS with fiskaly DSFinV-K.
  • We recommend exporting Cash Point Closings separately for each client_id for now when using non-fiskaly TSS.
• Added new historic VAT definitions.
• Added missing TSE_ZERTIFIKAT_V to tse.csv.
• Fixed a problem when using historic vat definitions.
• Fixed an error when sending larger quantity_factor.
• Fixed query parameters for listCashPointClosings.
• Fixed problem when vat_definition_export_id is being reused in another environment.

LEARN​

• Read our blog post Postponed Update, which provides detailed information and FAQ on the postponed TSS update and the canceled maintenance on June 5, 2022.

­

­

Cheers,

Hannah from fiskaly

fiskaly website for developers: developer.fiskaly.com.
fiskaly status page: status.fiskaly.com.
fiskaly support website: support.fiskaly.com.

You can contact our support at dev-support@fiskaly.com. ­

­

­

TSS Update Postponed​

The reason is an bug discovered during testing that can cause updated TSS instances to transition to a permanent secure state. In consequence, the announced actions for 5.6.2022 and 6.6.2022 will not take place. We are analyzing the reason for the problem, and will proceed with fixing it. This will require a recertification of the SMAERS. A new update date will be announced in advance once the process is complete.

FAQ of Postponed Update​

Below you can find answers to some questions you may have on the postponed TSS update.

Does the postponed update affect my operation of SIGN DE?​

Customers will feel no impact from the postponement of the update. The presently running certified TSS version (1.0.5-1.2.0) is stable and works reliably.

The changes in the updated versions concern further improvements in stability, but are not critical for the normal operation of the SIGN DE API.

Why was the update postponed?​

During the extensive testing in our TEST environment, a bug was detected. Under certain circumstances, this bug results in some of the SMAERS instances that were updated from version 1.0.5 to version 1.0.6 entering an unrecoverable secure state.

‘New’ SMAERS instances, that were created in version 1.0.6, are not affected by this bug. No problems have been detected with the new CSPL version 1.3.0.

Fixing this problem is only possible by changing the implementation of our SMAERS, which means that it has to undergo a recertification process before it can be deployed to production. As a result, the planned update has to be postponed until that process is completed.

What is the impact of the postponed update?​

The postponement affects the update of the TSS in the LIVE environment. In TEST, which has already been updated, the TSS version 1.0.6-1.3.0 will continue to run for testing purposes. This means that:

• In LIVE environment, the TSS version will remain at 1.0.5-1.2.0 (the ‘old’ version). This means that for the customers, nothing will change compared to now.

• In TEST environment, the TSS version will remain at 1.0.6-1.3.0 (the ‘updated’ version). As the environment is set up to create new TSS instances only in this version, the bug will not affect customers' TSS instances in the TEST environment. The behaviour of this version from a customer perspective is indistinguishable from the previous version, meaning that the ‘updated’ TSS instances will behave the same as the ‘old’ ones. No tests or other customer-side integration will be affected, apart from the presence of the updated TSS version in the info.csv file of TSS exports.

Why was the problem not detected earlier?​

Despite extensive automated and manual testing, the bug was not detected during development or certification because the specific circumstances that triggered it were difficult to anticipate and test for in advance. The complexity of the TSS is such that some behaviors are rare and will only be detectable in large-scale and highly dynamic environments.

However, this was precisely why an extended period of testing in TEST environment, which more closely approximates the conditions and behavior of our LIVE environment, was planned for before the update in LIVE environment took place.

Will the update still take place in the future?​

The changes incorporated in TSS version 1.0.6-1.3.0 will be part of the next update, which will take place once the SMAERS recertification is complete, leading to a new SMAERS version (1.0.x). The update will then upgrade the TSS version in TEST environment and LIVE environment to version 1.0.x-1.3.0.

It is difficult to estimate how much time the development and recertification effort will require, but the anticipated delay is in the order of at least a few months. Should an update date be decided upon, we will notify customers in advance in the same manner as we did for this update.

Why not update the CSPL, if it has no problems?​

The TSS certification process requires the separate certification of both the individual component versions (SMAERS and CSPL) as well as their combination (i.e., the TSS as a whole). Hence we are not allowed to update only the CSPL, as this would lead to the TSS instances in LIVE environment being in an uncertified version (1.0.5-1.3.0).

Best, the fiskaly SIGN DE Team

­

SIGN DE​

The following is for information, you do not need to take action!

Successful deployment of SMAERS v1.0.6 on TEST environment on May 2, 2022

• All new SMAERS instances are created with version 1.0.6.
• All existing UNINITIALIZED/INITIALIZED SMAERS instances migrated to v1.0.6.
• All existing DISABLED SMAERS instances are not affected (i.e. are still v1.0.5).

We will test the SMAERS deployment in the TEST environment until the update in the LIVE environment

• I.e., SMAERS update will be reverted and re-deployed several times.
• You can help by running a lot of load in the TEST environment.

Scheduled Maintenance Sunday, June 5, 2022, 08:00-16:00 CET​

SIGN DE API will undergo scheduled maintenance on Sunday, June 5, 2022, between 08:00 and 16:00 (CET)

The maintenance will involve a rolling update of LIVE TSS instances from version 1.0.5-1.2.0 to version 1.0.6-1.3.0 (where the former is the SMAERS version and the latter is the CSPL version).

During the maintenance window, the following restrictions apply:

• Data Exports are disabled.
• TSS state transitions to DISABLED are not possible.
• API calls may take longer than usual or run into timeouts.
• Service interruptions may occur.

You find more information and FAQ in our blog post scheduled maintenance.

­

­

DSFinV-K ​

v1.3.0 - deployment 2022-04-13

• Fixed missing error messages for Cash Point Closings.
• Fixed triggering exports with Cash Point Closings that were created before 2021-12-24.
• Note: Old exports in the TEST environment might get removed in the future. Please trigger a new export with the old Cash Point Closings in the TEST environment.
• Fixed spelling.

­

­

LEARN​

• Read our blog post scheduled maintenance, which provides detailed information and FAQ on the TSS update on June 5, 2022.

­

­

­

Cheers,

Hannah from fiskaly

fiskaly website for developers: developer.fiskaly.com.
fiskaly status page: status.fiskaly.com.
fiskaly support website: support.fiskaly.com.

You can contact our support at dev-support@fiskaly.com.

­

­

­

­

TSS Update on June 5, 2022​

Here you find more information on our scheduled maintenance on June 5, 2022. We will update our system to make it even better.

SIGN DE - TSS Update Announcement​

The maintenance will involve a rolling update of LIVE TSS instances from version 1.0.5-1.2.0 to version 1.0.6-1.3.0 (where the former is the SMAERS version and the latter is the CSPL version).

During the maintenance window, the following restrictions apply:

• Data Exports are disabled.
• TSS state transitions to DISABLED are not possible.
• API calls may take longer than usual or run into timeouts.
• Service interruptions may occur.

Note for June 6, 2022​

FAQ of TSS Update​

Below you can find answers to some questions you may have on the TSS update on June 5, 2022.

What does the update entail?​

The update concerns the deployment of the new certified versions for the SMAERS (from version 1.0.5 to 1.0.6) and CSPL (from version 1.2.0 to 1.3.0), together representing an update of the entire TSS to version 1.0.6-1.3.0.

The TSS update will also represent the deployment of version 2.1.0 of SIGN DE API.

You can find the certification documents for the new versions at Certification | fiskaly.developer.

What are the effects of the update?​

The new versions of SMAERS and CSPL include bugfixes and stability improvements. Customers' operations should not be affected, as there are no changes to the API. The only visible differences are in the exports triggered after the update: the exports will include the update logs, and the TSS version in the info.csv will be incremented to 1.0.6-1.3.0. Old exports, i.e. exports triggered before the update, will not be affected by it.

Only TSS instances that are in the states UNINITIALIZED or INITIALIZED will be updated. All existing and new TSS instances in the state CREATED will be in the new version once they are transitioned into the UNINITIALIZED state. An update of DEFECTIVE and DISABLED instances is not possible due to technical reasons.

Customers may experience some temporarily increased latency in the handling of their first post-update requests due to the need to re-establish communication between SMAERS and CSPL, and synchronize the update logs across all components.

What do I need to do?​

Customers do not need to do anything on their side. As mentioned above, there are no effects on customer operations apart from some restrictions and the inevitable interruptions during the update process.

We recommend to follow our guide on how to deal with service interruptions and timeouts at Error and Timeout-Handling | fiskaly.developer.

After the update is completed, you can verify the update by checking your info.csv files in the data exports of INITIALIZED TSS instances for the correct TSS version.

Can I continue to use SIGN DE API during the update timeframe?​

In principle, yes. During the maintenance window, individual calls may fail, time out or take longer than usual.

Data Exports and the TSS state transition to state DISABLED will also be temporarily disabled during the maintenance window. HTTP endpoints regarding these operations will respond with HTTP status code 503.

Otherwise SIGN DE API will remain available and functional throughout the maintenance window.

When will the update take place?​

The update will take place as a rolling update over longer periods of time during the announced maintenance window. It does not mean that it will start at exactly 8:00 or last until exactly 16:00, but during that period different parts of SIGN DE API will be updated at various times.

What does it mean that the data exports are disabled?​

During the maintenance window the export endpoints will return HTTP status 503.

How long will the data exports be disabled?​

The data exports may be disabled and re-enabled for longer periods of time at various points during the announced maintenance window. We recommend avoiding data exports during the maintenance window entirely.

How long will the TSS disabling functionality be disabled?​

The TSS disabling functionality may be disabled and re-enabled for longer periods of time at various points during the announced maintenance window. We recommend avoiding setting TSS instances to state DISABLED during the maintenance window entirely.

What does it mean that service interruptions can occur?​

In addition to the disabled functionality, during the rolling update process, individual TSS instances may be temporarily unreachable or busy as their components are being updated.

Some TSS instances may temporarily display increased latency in the handling of their first post-update requests due to the need to re-establish communication between SMAERS and CSPL, and synchronize the update logs across all components.

Happy updating, the fiskaly SIGN DE Team

SIGN DE​

• Deployed improvements to our backend component (bug fixes, more informative errors). ­

DSFinV-K ​

v1.2.0 - deployment 2022-02-24

• Added order_by and order query parameters to the List all vat definitions endpoint.
• Fixed a problem with Cash Point Closings that contained transactions that were not signed by the SIGN API.
• Fixed number validation for big numbers.

v1.1.1 - deployment 2022-02-21

• Fixed a problem with creating exports of cash point closings with a specific client_id.

v1.1.0 - deployment 2022-02-17

• Increased performance of insertCashPointClosing.
• Added possibility to filter results of listExports by business date.
• Making transaction IDs case-insensitive for cash point closings.
• Fixed duplicate API specs.
• Fixed duplicate Cash Point Closings on the listCashPointClosings endpoint.
• Fixed a problem when using multiple cash registers with multiple revisions.
• Fixed a bug in the exported lines.csv.

­

SIGN AT​

• Improved Docs: FAQ.
• More descriptions etc. available and working on more detailed information.
• Extended response from signing endpoint by legal texts that are required to be placed in the receipts depending on the signing outcome and receipt type.

­

­

­

LEARN​

• We strive to improve our systems, but as in all software projects, there will be issues. For a faster workflow read our article on How to raise an issue.
• How do you achieve a smooth-running system with fiskaly? Read our article on Error and timeout handling.

­

­­

Info​

We are constantly working on the security aspects of our system and the data entrusted to us. That is why we have changed our newsletter tool. We work from now on with Sendinblue and their privacy policy. 
Switching to a European service provider for managing newsletters we improve the security of processing your data. You can change your preferences or unsubscribe from our mailing list at any time. If you have unsubscribed during the migration of our newsletter and have received this news. Please unsubscribe from our list again. We apologize for the inconvenience.

­

Cheers,

Hannah from fiskaly

fiskaly website for developers: developer.fiskaly.com.
fiskaly status page: status.fiskaly.com.
fiskaly support website: support.fiskaly.com.

You can contact our support at dev-support@fiskaly.com.

­

SIGN DE v2.0​

For upcoming deployments, you do NOT need to take action. This is only for information.

• SMAERS v1.0.6 deployment is upcoming.
• Log Synchronization deployment is upcoming:
  • 2022-02-15 on TEST environment
  • 2022-02-18 activation on LIVE environment

LEARN​

• Errors and Status Codes
  The fiskaly SIGN API uses standard HTTP status codes to indicate the sucess or failure of requests. Here you find detailed descriptions of the codes. Make sure to unfold arrow sections ▶️ 🔽 to read all information!

SEMINAR:​

RKSV Compliance - easy with fiskaly SIGN AT

• German: Monday, February 21, 2022 – at 10 a.m. CET
• English: Wednesday, February 23, 2022 – at 10 a.m. CET

Here are the topics of our seminar:

• What do I need to know about fiscalization in Austria?
• Differences to fiscalization in Germany
• Information on the integration of fiskaly SIGN AT
• Current fiskaly updates
• Advantages of cloud fiscalization with fiskaly

After the seminar, you will have a sound overview of fiscalization in Austria, know the legal requirements, and know how to integrate fiskaly SIGN AT as quickly as possible.

Cheers,
Hannah from fiskaly

You can contact our support at dev-support@fiskaly.com.
Website for developers: developer.fiskaly.com
fiskaly status page: status.fiskaly.com

Hi!

Check out our latest updates:

SIGN DE v2.0​

• Recertification of the new TSS / TSE is complete.
• The new TSS / TSE will first be rolled out in the TEST environment: We'll inform you in our developer newsletter (Q1/2022).
• The LIVE environment will follow a month later.

DSFinV-K v1.0​

• Deployed 2022-02-02.
• Improved performance of exports.
  Note: Cash Point Closings that were created before 2021-12-24 and would be included in an export will be postponed as that data is currently being migrated. We update the changelog once older data was migrated. See changelog.
• Multiple bugfixes on various CSV files.
• Fixed documented response types of list endpoints.

DSFinV-K v0.14​

• Deployed 2021-12-06.
• Improved description for exports and added a new cash_point_closings field in the response to show which are included.
• Improved performance of Retrieve details of a cash point closing.
• Added order by and order for List all purchaser agencies endpoint.
• Fixed multiple exported field values.
• Fixed endpoints for retrieving metadata when no metadata is available.

SIGN AT v1.0-beta​

• Welcome Austria to our solutions portfolio!
• First feature-complete and stable API.

fiskalcheck v2.0.1​

• Fixed allows no payments when sum of VAT rate is 0.

fiskalcheck available on Android and iOS.

log4j + fiskaly​

• fiskaly Sign API v2 is not affected by the critical vulnerability of log4j

How to deal with timeouts / system problems
Check out our new guide on how to deal with timeouts / system problems:
We talk about - How to:

• Set timeouts correctly
• Handle missing signatures
• DSFinV-K and transactions
• Authorization

How to deal with timeouts / system problems

Cheers,
Hannah from fiskaly

You can contact our support at dev-support@fiskaly.com.
Website for developers: developer.fiskaly.com
fiskaly status page: status.fiskaly.com

Hi!

Check out our latest updates:

fiskaly is NOT affected by Log4j exploit​

As you all know, a zero-day exploit for the Java logging tool Log4j has been discovered and classified as critical by the BSI (German Federal Office for Information Security).

fiskalys production systems, reading all systems, services, APIs that are listed on developer.fiskaly.com/api, and the fiskaly Dashboard are NOT vulnerable.

Online Seminar

• Most common errors in integration
• Learnings from the regular exchange with tax administrations
• Best practices system vendors
• After the seminar you will be well prepared for the operation as well as the smooth process of a tax audit.

Here you can register for the seminar:

German: Thursday, December 16, 2021 - 10:00 to 10:45 am CET

English: Friday, December 17, 2021 - 10:00 to 10:45 am CET

How to deal with timeouts
Check out our new guide on how to deal with timeouts / system problems.
You'll learn: How to ...

• ... set timeouts correctly
• ... handle missing signatures
• ... DSFinV-K and transactions
• ... handle Authorization correctly

Go to guid: How to deal with timeouts / system problems

Cheers,
Hannah from fiskaly

You can contact our support at dev-support@fiskaly.com.
Website for developers: developer.fiskaly.com
fiskaly status page: status.fiskaly.com

Hi!

Check out our latest updates, as we start another round of technology seminars: This time we talk about V2 technical details.

Latest Updates:​

KassenSichV API V2 is live​

On Friday we went live with V2. Please make sure to use the correct production URLs. Here is an overview of the URLs and the V2 guide to read:

KassenSichV API V2.0​

• 🚀 Deployed.

Dashboard V2.0​

We've deployed the V2 Dashboard, being able to display and populate V1 and V2 resources.

New:​

• Integration of Sign V2 (KassenSichV V2).
• "DSFinV-K Exports" moved to a sole menu (currently available for V1 only).
• Moved "API Keys" to the "Settings" menu.
• "Status" moved to a sole menu.

Fixed:​

• Fixed metadata display issue.

Seminar: Technical Details V2​

In this seminar we will focus on the technical details of the fiskaly Cloud TSS V2. We will address, among other things, the scenarios of migration from V1 to V2 and the direct implementation of V2. As usual, you can send us your questions in advance or ask them live in the seminar. We look forward to receiving numerous questions via sales@fiskaly.com.

Register now

• German: Wednesday, July 28, 2021, 4:30 - 5:30 pm CEST
• English: Thursday, July 29, 2021, 4:30 - 5:30 pm CEST

Cheers, Hannah from fiskaly

Hi!

Technology, technology, and technology: that's the focus in our next online seminar this week.

Technical Details fiskaly Cloud TSS​

We invite you to our next online seminar this week with a focus on technology. To answer all your questions thoroughly, one of our senior developers will be present. We are looking forward to your attendance.

Register now

• German: Thursday, July 15, 2021, 10:00-10:45 am CEST
• English: Friday, July 16, 2021, 10:00-10:45 am CEST

Cheers, Hannah from fiskaly

Hi!

Today I have a very short Update for you. We reached another milestone:

Reminder online Seminars​

Our online Seminars on Certified Operation fiskaly Cloud TSS are coming up this week. Additionally we'll discuss the decision of the Bundesrat (German Federal Council) on the KassenSichV and the changes it brings.

Register here:

• German: Thursday, July 8, 2021, 10:00-10:45 am CEST
• English: Friday, July 9, 2021, 10:00-10:45 am CEST

Cheers, Hannah from fiskaly

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Latest Updates​

Roadmap to V2​

We published our Roadmap to V2, and it is available at: developer.fiskaly.com/v2-roadmap

We finished phase 1...​

… of our Roadmap successfully. This means following is done:

• TSS Initialization
• Client Handling
• Authentication
• Test only Environment
• Documentation Update
• Base-Url: sign.fiskaly.dev
• TX-Handling ~End-of-Week

Phase 2 is nearly complete! This implementation generates certified TSSs, thus clearing the hurdle of fiscalization for many years to come. From now on, we will be in a continuous process of improvement with each new deployment.

Postman​

For a quick first demo, you may use Postman. We prepared a Postman collection that allows you to step through the most important functions of this API.

FAQ’s V2​

We’ll soon push a new FAQ’s section: If you want to place some questions there, please reach out to sales@fiskaly.com.

QR Code replaces readable TSS Signature​

On June 25, 2021, the German Bundesrat approved the ordinance amending the KassenSichV. The addition to § 6 sentence 2 KassenSichV makes it possible to omit printing certain information in plain text on a receipt, and instead display it in a QR code. Source: Bundesrat (TOP 86) or read our Blogpost.

Online Seminars​

In our next online seminars we talk about the law amendment and give you updates on our system. Join us and register here:

• German: Thursday, July 8, 2021, 10:00-10:45 am CEST
• English: Friday, July 9, 2021, 10:00-10:45 am CEST

Cheers, Hannah from fiskaly

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Latest Deployment Notes​

fiskaly Dashboard v0.14​

• Show metadata of entities.
• Fixed duplicates of organizations in the organization list.
• Fixed DSFinV-K download button.

Management API v0.8​

• Fixed duplicate listing of organizations in rare cases.

DSFinV-K v0.8​

• Fixed TSE_SERIAL field in tse.csv.
• Fixed UST_SCHLUESSEL field in business_cases.csv.
• Fixed inserting Cash Point Closing with coupons.
• Fixed count field on responses of list endpoints.
• Performance improvements.

Cheers, Hannah from fiskaly

Hi there,

"More than two years of planning, postponements, hurdles and changes, as well as improvements in requirements are behind us. Now the time has finally come! The certified fiskaly Cloud TSS is the first Cloud TSS to be certified for the entire duration! I am very proud of fiskaly and the incredible team effort over the last months." Johannes Ferner, CEO fiskaly GmbH

fiskaly is thus the only cloud TSS to accomplish the full certificate duration and is certified until 2029. The fiskaly Cloud TSS is 100% software-based and can be integrated into all systems and POS architectures.

Download Certificates​

You can find the official certificates below:

• CSP-L - “Signature Server”
• SMAERS - “Connector”
• TR - “end2end Check”

Download

IGZTK - Become a member​

We recommend you to join the IGZTK - Interest Group of Future-Oriented Technology Manufacturers for POS Systems: igztk.com

Thank you very much for your trust and loyalty!

Your fiskaly Team Johannes Ferner (CEO), Simon Tragatschnig (COO) & Patrick Gaubatz (CTO)

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Current Changelog:​

fiskaly Client v.1.2.200​

• Re-implemented HTTP client configuration to fix problems with proxies and certificates.
• Fixed number formatting & validation.
• Fixed ARM builds.
• Extended health check function.

This is the last planned update for version 1 - if you're experiencing any issues, make sure to install the latest version.

DSFinV-K v0.7.0 is deployed.​

• Translated documentation into English.
• Fixed missing businesscases.csv in exports.
• Fixed missing itemamounts.csv in exports.
• Fixed missing subitems.csv in exports.
• Fixed order of CSV columns in multiple exported files.
• Fixed the use of historic VAT definitions ("Historische Steuersätze") in a Cash Point Closing.
• Fixed inconsistent revisions for Cash Registries.
• Fixed response of upsertCashRegister to include the processing_flag and software field.
• Wording improvements in the documentation.

Upcoming Online Seminar: Certification​

We invite you to join our next online seminar: Certification

Topics:​

• Certification and all around certification Other important topics for providers of digital POS systems
• The seminar is offered in German and English. Register now:

German: Thursday, May 27, 2021 - 3:00-3:45 pm CEST English: Friday, May 28, 2021 - 10:30-11:15 am CEST

links removed

Cheers, Hannah from fiskaly

Hi!

We have been carrying out some maintenance on our system during the last week.

Brand new: status.fiskaly.com

Our system is busier than ever before. In order to continue to give the best service and planning reliability we set up a status website for the fiskaly system:

status.fiskaly.com

Information about maintenance windows, as well as new functionalities in the respective services, will be sent out here in our Developer Newsletter.

Alternatively, you can find information about maintenance windows and status information at status.fiskaly.com.

Cheers, Hannah from fiskaly

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Current Changelog:​

DSFinV-K v0.6.0​

• Added linked dtd file to export.
• Better error handling on invalid time formats.
• Fixed export_creation_date time format in listCashPointClosings.
• Fixed MAX_PARAMETERS_EXCEEDED error for Cash Point Closings.
• Fixed misleading E_CLIENT_NOT_FOUND error for Cash Point Closings.
• Fixed input of incl_vat, excl_vat and vat and allowing up to 5 decimal places.

Management API v0.9.0​

• Added possibility to create main organizations in LIVE mode if the billing_options.bill_to_organization is set, the set organization is also in LIVE mode and a token with env:LIVE is present.
• Added created_by_user field on multiple responses.
• Fixed edge case where setting the billing_options.bill_to_organization for a MANAGED_ORGANIZATION raised an error.

Cheers, Hannah from fiskaly

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Current Changelog:​

Management API (0.8.0)​

• Added new endpoint to remove a user from an organization.
• Fixed the invite endpoint to invite new users to an organization.
• Fix: Managed organizations could have had further managed organizations

Dashboard (0.12.0)​

• Managed organizations can be set to LIVE mode when the main organization is already in LIVE
• The display name is now displayed over the real name of an organization
• Users can now be removed from an organization
• Fixed sorting for multiple tables
• Fixed 'an unknown error' when new users were invited to an organization
• Managed organization count fixed on the Dashboard
• Typo fixes

DSFinV-K API (0.5.1-alpha)​

• Fixed E_TX_NOT_FOUND on cash point closings - with an empty transaction list or only transactions that contain errors
• Fixed listExport with a client_id filter

Cheers, Hannah from fiskaly

Hi, welcome to our dev newsletter. Check the changelog for our latest changes in the fiskaly dashboard.

Latest Changelog:​

• Fixed DE/EN translations
• More consistent way of showing the display_name
• Enable the Country Dropdown (non-germany) when creating new organizations
• Added a new Count Widget to display the managed organizations
• Added managed organization list to Settings > Organization Management
• Fixed filter for state field
• Fixed test banner when the organization is already set to LIVE
• Fixed displaying empty fields of organization data

Cheers, Hannah from fiskaly