fis­ka­de­my

the Know­ledge Plat­form of fiskaly.

fis­ka­ly

Imple­ment Cloud TSS

Imple­men­ta­ti­on

On this page we have pre­pa­red an over­view of how to imple­ment the fis­ka­ly Cloud TSS in five steps.

Here you will find what issues you need to con­si­der. These sim­pli­fy the imple­men­ta­ti­on and anti­ci­pa­te pos­si­ble errors that can be easily avoided.

First steps

Quick Start

Orga­niz­a­ti­ons

Imple­men­ta­ti­on

Go Live

First steps

Regis­tra­ti­on at fiskaly

Go to the fis­ka­ly Dash­board. You can regis­ter with fis­ka­ly using your Google, Lin­kedIn, Micro­soft account as well as your email address. Fol­lowing regis­tra­ti­on, you will recei­ve an email to acti­va­te your account. 

When you log in for the first time, you will be asked to create a (test) orga­niz­a­ti­on. Fill in the name of the orga­niz­a­ti­on (step 1) and the address fields (step 2). In the last step, the address of the orga­niz­a­ti­on is stored by default. For tes­ting pur­po­ses, you can also create the orga­niz­a­ti­on without ent­e­ring the bil­ling address.

Click on ‘Create’ to finish. Now you can test the fis­ka­ly system for free. You find the fis­ka­ly Dash­board User Guide at developer.fiskaly.com.

Quick Start

Tes­ting API with Postman

Post­man is a popu­lar tool for tes­ting APIs. An intui­ti­ve user inter­face and little prior pro­gramming know­ledge are advan­ta­ges of tes­ting with Post­man. In addi­ti­on, tests that have been per­for­med are stored and can be repeated.

This gives you the oppor­tu­ni­ty to test our APIs in detail and get a good over­view of the rela­ti­ons­hips and pro­ces­ses. The­re­fo­re, fis­ka­ly also pro­vi­des Post­man Envi­ron­ment and Post­man Collec­tion for tes­ting the fis­ka­ly API. Make sure that you always test with the cur­rent envi­ron­ment and collec­tion. This ensu­res that the latest updates are mapped.

You can find detail­ed inst­ruc­tions on developer.fiskaly.com > Quick Start.

Pre­pa­ra­ti­on

Orga­niz­a­ti­ons in the fiskalyversum 

The design of the orga­niz­a­tio­nal manage­ment in the fis­ka­ly system is an important buil­ding block in the inte­gra­ti­on of the fis­ka­ly Cloud TSS. As a first step, con­si­der how you can best map your orga­niz­a­tio­nal struc­tu­re with us. Note that at this stage you deter­mi­ne the future manage­ment workload in operation.

Since the orga­niz­a­tio­nal and cus­to­mer struc­tures of our cus­to­mers are very diver­se, we have deve­lo­ped a very fle­xi­ble and intui­ti­ve system that allows you to map a clean sepa­ra­ti­on of cus­to­mers, loca­ti­ons and hierarchies.

On the fis­ka­de­my page orga­niz­a­ti­ons in the fis­ka­ly system we also pro­vi­de best prac­ti­ce examples.

Info­box

Manage­ment API

The top prio­ri­ty during imple­men­ta­ti­on is to keep the POS system up and run­ning! fis­ka­ly pro­vi­des com­pre­hen­si­ve infor­ma­ti­on and resour­ces to assist you during imple­men­ta­ti­on. We pre­sent the fis­ka­ly online resour­ces in detail on the fis­ka­de­my res­sour­ces page. It is important to under­stand, that apart from the tech­ni­cal requi­re­ments, the legal frame­work plays an essen­ti­al role.

In the opti­mal case, our API is imple­men­ted in such a way that the smooth ope­ra­ti­on of the cash regis­ter can be gua­ran­te­ed at all times. There are a few things to keep in mind. In gene­ral, this depends stron­gly on the check­out archi­tec­tu­re, the fre­quen­cy of use and the area of use of the POS system. In addi­ti­on, a mis­sing signa­tu­re on the docu­ment does not mean the docu­ment is not in com­pli­an­ce with the law (see Punkt 7 AEAO to § 146a). Howe­ver, the fis­ka­ly API must be imple­men­ted in such a way that each tran­sac­tion requests a signa­tu­re. In the info­box below we have brief­ly sum­ma­ri­zed important infor­ma­ti­on for you. We have brief­ly sum­ma­ri­zed important infor­ma­ti­on for you in the info­box prac­ti­cal tips.

Hot phase

Imple­ment into your own system 

The top prio­ri­ty during imple­men­ta­ti­on is to keep the POS system up and run­ning! fis­ka­ly pro­vi­des com­pre­hen­si­ve infor­ma­ti­on and resour­ces to assist you during imple­men­ta­ti­on. We pro­vi­de a detail­ed pre­sen­ta­ti­on of the fis­ka­ly online resour­ces on the fis­ka­de­my page ‘Resour­ces’. It is important to under­stand, that apart from the tech­ni­cal requi­re­ments, the legal frame­work plays an essen­ti­al role.

In the opti­mal case, our API is imple­men­ted in such a way that the smooth ope­ra­ti­on of the cash regis­ter can be gua­ran­te­ed at all times. There are a few things to keep in mind. In gene­ral, this depends stron­gly on the check­out archi­tec­tu­re, the fre­quen­cy of use and the area of use of the POS system. In addi­ti­on, a mis­sing signa­tu­re on the docu­ment does not mean the docu­ment is not in com­pli­an­ce with the law (see Punkt 7 AEAO to § 146a). Howe­ver, the fis­ka­ly API must be imple­men­ted in such a way that each tran­sac­tion requests a signa­tu­re. We have brief­ly sum­ma­ri­zed important infor­ma­ti­on for you in the info­box prac­ti­cal tips.

Info­box

Prac­ti­cal Tips

We have com­pi­led the fol­lowing prac­ti­cal tips for you:

Set time­outs
These depend hea­vi­ly on the fre­quen­cy of the POS system As a manu­fac­tu­rer, you should decide for yourself which time­out length you con­si­der rea­son­ab­le. No request should ever be open long enough to jeo­par­di­ze the smooth ope­ra­ti­on of the cash register.

Please note that in the event that the TSS is unavail­ab­le, the check­out pro­cess will not be disrupted.

Aut­ho­riz­a­ti­on
The aut­ho­riz­a­ti­on is initi­al­ly done via API Key and API Secret. You will recei­ve an “access token” and a “refresh token” which you can use to reaut­ho­ri­ze yourself on an ongo­ing basis. If you run into a “401” respon­se, simply reaut­ho­ri­ze via API Key and Secret.

What to do if the TSS is not avail­ab­le and a rece­i­pt remains unsi­gned? The legis­la­tor cla­ri­fies in the AEAO to § 146a in point 7. Unfor­tu­n­a­te­ly we can’t pro­vi­de trans­la­ti­ons for legal texts. The legis­la­tor cla­ri­fies in AEAO to § 146a in point 7*:

AEAO zu § 146a, Nr. 2.1.6

7. Aus­fall der zer­ti­fi­zier­ten tech­ni­schen Sicherheitseinrichtung

7.1 Aus­fall­zei­ten und –grund einer zer­ti­fi­zier­ten tech­ni­schen Sicher­heits­ein­rich­tung sind zu doku­men­tie­ren (vgl. AEAO zu § 146a, Nr. 2.1.6). Diese Doku­men­ta­ti­on kann auch auto­ma­ti­siert durch das elek­tro­ni­sche Auf­zeich­nungs­sys­tem erfolgen.

7.2 Kann das elek­tro­ni­sche Auf­zeich­nungs­sys­tem ohne die funk­ti­ons­fä­hi­ge zer­ti­fi­zier­te tech­ni­sche Sicher­heits­ein­rich­tung wei­ter­be­trie­ben werden, muss dieser Aus­fall auf dem Beleg ersicht­lich sein. Dies kann durch die feh­len­de Trans­ak­ti­ons­num­mer oder durch eine sons­ti­ge ein­deu­ti­ge Kenn­zeich­nung erfolgen.

7.3 Soweit der Aus­fall ledig­lich die zer­ti­fi­zier­te tech­ni­sche Sicher­heits­ein­rich­tung betrifft, wird es nicht bean­stan­det, wenn das elek­tro­ni­sche Auf­zeich­nungs­sys­tem bis zur Besei­ti­gung des Aus­fall­grun­des wei­ter­hin genutzt wird. Die grund­sätz­li­che Beleg­aus­ga­be­pflicht bleibt von dem Aus­fall unbe­rührt, auch wenn nicht alle für den Beleg erfor­der­li­chen Werte (vgl. AEAO zu § 146a, Nr. 5.8) durch die zer­ti­fi­zier­te tech­ni­sche Sicher­heits­ein­rich­tung zur Ver­fü­gung gestellt werden. Die Beleg­an­ga­ben zu Datum und Uhr­zeit müssen in diesem Fall von dem elek­tro­ni­schen Auf­zeich­nungs­sys­tem bereit­ge­stellt werden.

7.4 Die Beleg­aus­ga­be­pflicht nach § 146a Abs. 2 AO ent­fällt ledig­lich bei einem voll­um­fäng­li­chen Aus­fall des Auf­zeich­nungs­sys­tems oder bei Aus­fall der Druck- oder Über­tra­gungs­ein­heit. Bei Aus­fall der Druck- oder Über­tra­gungs­ein­heit für den elek­tro­ni­schen Beleg muss das Auf­zeich­nungs­sys­tem i. S. d. § 146a Abs. 1 Satz 1 AO i.V.m. § 1 Satz 1 Kas­sen­SichV wei­ter­hin genutzt werden.

7.5 Der Unter­neh­mer hat unver­züg­lich die jewei­li­ge Aus­fall­ur­sa­che zu behe­ben, Maß­nah­men zu deren Besei­ti­gung zu tref­fen und dadurch sicher­zu­stel­len, dass die Anfor­de­run­gen des § 146a AO schnellst­mög­lich wieder ein­ge­hal­ten werden.

Go Live

Go Live

In the fis­ka­ly system, the default set­ting is test mode and the initi­al acti­va­ti­on of the main orga­niz­a­ti­ons into live mode is done manu­al­ly. To do this, follow the steps in the dash­board or con­ta­ct sales@fiskaly.com. Mana­ged orga­niz­a­ti­ons can be enab­led to go live inde­pendent­ly. The resour­ces of the test and live sys­tems are not con­nec­ted to each other. Chan­ges in the test system are thus not trans­fer­red to the live system and you can con­ti­nue to use the test system as a sandbox.

When swit­ching from V1 to V2, you do not need to create any new orga­niz­a­ti­ons. Howe­ver, you should dis­able V1 resour­ces in any case to avoid mul­ti­ple bil­ling. Of course, you can still access the data of the V1 resour­ces. Under this link you will find more infor­ma­ti­on about swit­ching to V2.

* Dis­c­lai­mer: The infor­ma­ti­on con­tai­ned on this web­site is for gene­ral infor­ma­ti­on pur­po­ses and does not relate to the spe­ci­fic situa­ti­on of any indi­vi­du­al or legal entity. They do not con­sti­tu­te legal or tax advice. In spe­ci­fic indi­vi­du­al cases, the pre­sent con­tent cannot replace indi­vi­du­al advice from experts.

Kas­sen­SichV — Blog

Blog posts on the topic

You can find arti­cles on the topic in our blog:

Kas­sen­SichV Blog

Test fis­ka­ly for Free 

Test fis­ka­ly Dash­board Now for Free Con­vin­ce yourself of fis­ka­ly and test our dash­board now for free. Start in 3 Easy Steps 1. visit dashboard.fiskaly.com 2. Sign in

Read more» 

Con­ta­ct Sales Team

and request your con­tract with fiskaly.