fiskademy Implement Cloud TSS
Nov-2021
fiskademy
the Knowledge Platform of fiskaly.
fiskaly
Implement Cloud TSS
Implementation
On this page we have prepared an overview of how to implement the fiskaly Cloud TSS in five steps.
Here you will find what issues you need to consider. These simplify the implementation and anticipate possible errors that can be easily avoided.
First steps
Quick Start
Organizations
Implementation
Go Live
First steps
Registration at fiskaly
Go to the fiskaly Dashboard. You can register with fiskaly using your Google, LinkedIn, Microsoft account as well as your email address. Following registration, you will receive an email to activate your account.
When you log in for the first time, you will be asked to create a (test) organization. Fill in the name of the organization (step 1) and the address fields (step 2). In the last step, the address of the organization is stored by default. For testing purposes, you can also create the organization without entering the billing address.
Click on ‘Create’ to finish. Now you can test the fiskaly system for free. You find the fiskaly Dashboard User Guide at developer.fiskaly.com.
Quick Start
Testing API with Postman
Postman is a popular tool for testing APIs. An intuitive user interface and little prior programming knowledge are advantages of testing with Postman. In addition, tests that have been performed are stored and can be repeated.
This gives you the opportunity to test our APIs in detail and get a good overview of the relationships and processes. Therefore, fiskaly also provides Postman Environment and Postman Collection for testing the fiskaly API. Make sure that you always test with the current environment and collection. This ensures that the latest updates are mapped.
You can find detailed instructions on developer.fiskaly.com > Quick Start.
fiskaly API testing with Postman
Preparation
Organizations in the fiskalyversum
The design of the organizational management in the fiskaly system is an important building block in the integration of the fiskaly Cloud TSS. As a first step, consider how you can best map your organizational structure with us. Note that at this stage you determine the future management workload in operation.
Since the organizational and customer structures of our customers are very diverse, we have developed a very flexible and intuitive system that allows you to map a clean separation of customers, locations and hierarchies.
On the fiskademy page organizations in the fiskaly system we also provide best practice examples.
Organizations in the fiskaly system
Infobox
Management API
The top priority during implementation is to keep the POS system up and running! fiskaly provides comprehensive information and resources to assist you during implementation. We present the fiskaly online resources in detail on the fiskademy ressources page. It is important to understand, that apart from the technical requirements, the legal framework plays an essential role.
In the optimal case, our API is implemented in such a way that the smooth operation of the cash register can be guaranteed at all times. There are a few things to keep in mind. In general, this depends strongly on the checkout architecture, the frequency of use and the area of use of the POS system. In addition, a missing signature on the document does not mean the document is not in compliance with the law (see Punkt 7 AEAO to § 146a). However, the fiskaly API must be implemented in such a way that each transaction requests a signature. In the infobox below we have briefly summarized important information for you. We have briefly summarized important information for you in the infobox practical tips.
Hot phase
Implement into your own system
The top priority during implementation is to keep the POS system up and running! fiskaly provides comprehensive information and resources to assist you during implementation. We provide a detailed presentation of the fiskaly online resources on the fiskademy page ‘Resources’. It is important to understand, that apart from the technical requirements, the legal framework plays an essential role.
In the optimal case, our API is implemented in such a way that the smooth operation of the cash register can be guaranteed at all times. There are a few things to keep in mind. In general, this depends strongly on the checkout architecture, the frequency of use and the area of use of the POS system. In addition, a missing signature on the document does not mean the document is not in compliance with the law (see Punkt 7 AEAO to § 146a). However, the fiskaly API must be implemented in such a way that each transaction requests a signature. We have briefly summarized important information for you in the infobox practical tips.
Infobox
Practical Tips
We have compiled the following practical tips for you:
Set timeouts
These depend heavily on the frequency of the POS system As a manufacturer, you should decide for yourself which timeout length you consider reasonable. No request should ever be open long enough to jeopardize the smooth operation of the cash register.
Please note that in the event that the TSS is unavailable, the checkout process will not be disrupted.
Authorization
The authorization is initially done via API Key and API Secret. You will receive an “access token” and a “refresh token” which you can use to reauthorize yourself on an ongoing basis. If you run into a “401” response, simply reauthorize via API Key and Secret.
What to do if the TSS is not available and a receipt remains unsigned? The legislator clarifies in the AEAO to § 146a in point 7. Unfortunately we can’t provide translations for legal texts. The legislator clarifies in AEAO to § 146a in point 7*:
AEAO zu § 146a, Nr. 2.1.6
7. Ausfall der zertifizierten technischen Sicherheitseinrichtung
7.1 Ausfallzeiten und –grund einer zertifizierten technischen Sicherheitseinrichtung sind zu dokumentieren (vgl. AEAO zu § 146a, Nr. 2.1.6). Diese Dokumentation kann auch automatisiert durch das elektronische Aufzeichnungssystem erfolgen.
7.2 Kann das elektronische Aufzeichnungssystem ohne die funktionsfähige zertifizierte technische Sicherheitseinrichtung weiterbetrieben werden, muss dieser Ausfall auf dem Beleg ersichtlich sein. Dies kann durch die fehlende Transaktionsnummer oder durch eine sonstige eindeutige Kennzeichnung erfolgen.
7.3 Soweit der Ausfall lediglich die zertifizierte technische Sicherheitseinrichtung betrifft, wird es nicht beanstandet, wenn das elektronische Aufzeichnungssystem bis zur Beseitigung des Ausfallgrundes weiterhin genutzt wird. Die grundsätzliche Belegausgabepflicht bleibt von dem Ausfall unberührt, auch wenn nicht alle für den Beleg erforderlichen Werte (vgl. AEAO zu § 146a, Nr. 5.8) durch die zertifizierte technische Sicherheitseinrichtung zur Verfügung gestellt werden. Die Belegangaben zu Datum und Uhrzeit müssen in diesem Fall von dem elektronischen Aufzeichnungssystem bereitgestellt werden.
7.4 Die Belegausgabepflicht nach § 146a Abs. 2 AO entfällt lediglich bei einem vollumfänglichen Ausfall des Aufzeichnungssystems oder bei Ausfall der Druck- oder Übertragungseinheit. Bei Ausfall der Druck- oder Übertragungseinheit für den elektronischen Beleg muss das Aufzeichnungssystem i. S. d. § 146a Abs. 1 Satz 1 AO i.V.m. § 1 Satz 1 KassenSichV weiterhin genutzt werden.
7.5 Der Unternehmer hat unverzüglich die jeweilige Ausfallursache zu beheben, Maßnahmen zu deren Beseitigung zu treffen und dadurch sicherzustellen, dass die Anforderungen des § 146a AO schnellstmöglich wieder eingehalten werden.
AEAO to § 146a on the website of the BMF
Go Live
Go Live
In the fiskaly system, the default setting is test mode and the initial activation of the main organizations into live mode is done manually. To do this, follow the steps in the dashboard or contact sales@fiskaly.com. Managed organizations can be enabled to go live independently. The resources of the test and live systems are not connected to each other. Changes in the test system are thus not transferred to the live system and you can continue to use the test system as a sandbox.
When switching from V1 to V2, you do not need to create any new organizations. However, you should disable V1 resources in any case to avoid multiple billing. Of course, you can still access the data of the V1 resources. Under this link you will find more information about switching to V2.
Go live via e-mail to sales@fiskaly.com
* Disclaimer: The information contained on this website is for general information purposes and does not relate to the specific situation of any individual or legal entity. They do not constitute legal or tax advice. In specific individual cases, the present content cannot replace individual advice from experts.
KassenSichV – Blog
Blog posts on the topic
You can find articles on the topic in our blog:
