The fiskaly Dashboard gives you insight into your booked products at fiskaly and it gives you an overview of what is happening in the fiskaly system.
Unternehmer, Finanz & Technik-Experte
The fiskaly Dashboard gives you insight into your booked products at fiskaly. Via the dashboard you can create and manage organizations and user profiles, get insights into your transactions, created clients, and technical security devices (TSS). It visualizes your data and gives you an overview of what is happening in the fiskaly system.
To use the fiskaly Dashboard you need a separate account. You can sign up for a test account at fiskaly for free. All organizations that you create in the test account can go live after you signed a contract with fiskaly.
Click here to go to the Dashboard.
Info: An organization must be created the first time you log in. Then, you have the option to create your organizations and managed organization via the dashboard or via the Management API.
Via the Management API you can use all functions of the dashboard programmatically. Only the first organization must be created via the dashboard. The detailed documentation of the interface with their functions can be found on the fiskaly website for developers.
! In the Management API the term organization is used for main organizations and managed organization for sub-organizations.
An organization is a significant unit in the fiscaly system. It usually represents a holding, business or branch office. Organizations can be created free of charge via the dashboard. Managed organizations can be attached to it and can be administered through the parent organization.
In the menu item organization management you can create more organizations, have access to information, switch to live mode, add a logo to your organization, organize user authorizations, create API keys for your organization and create API keys for your managed organizations.
An organization cannot be a managed organization of another organization!
Users of the organization, and persons invited to the organization, have access to all information displayed in the dashboard of the organization and all the information of the attached managed organization(s) of this parent organization. I.e. overview of the dashboard, TSS number(s), client(s), transactions, exports, integrations etc. are displayed to the user.
A managed organization is dependent on its parent organization and can never be used on its own. It must always be secondary to an organization. Managed organizations are marked with the badge “managed”. They can also be created via the dashboard.
Users who are authorized for a managed organisation have only access to the information of the respective managed organization. These users have no access to information of the parent organization. Within a managed organization, users have access to the dashboard and all information stored there.
In the Dashboard under menu item Settings > Organization Management, click on the button Create New Organization and select the checkbox Create Managed Organization. > Then select which organization this managed organization is secondary to.
The following link shows how to create the managed organization using the Management API:
Make sure to check the box CreateManaged Organization.
The fiskaly system distinguishes between organizations and managed organizations. Managed organizations are dependent on the parent organization and cannot contain any further managed organizations themselves. An organization cannot be a manged organization of another organization. Note that the user authorizations of organizations and managed organizations differ.
Users of organizations or managed organizations have access to the information of the respective (managed) organization displayed in the dashboard. User authorizations within organizations and managed organizations differ in that users of organizations also have access to the information of the respective connected managed organizations. However, users of managed organizations do not have access to the information of the parent organization.
At least one API key must be created at the organizational level.
Via the dashboard in the menu itemDevelopers > API Key click on the button Create API Key and choose a name for your new API Key. Then select Create.> Then select Create.
Attention! The API Secret is only displayed immediately after the creation of a new API Key!
API Keys can also be created via the Management API.
With the API key of an organization, the managed organizations can be administered. A separate API key must be created for each managed organization in order to create a TSS for it and to use the other functionalities of the fiskaly SIGN API.
API keys for organizations must be generated via the dashboard or the management API. For managed organizations API keys can be generated automatically.
An API Key is bound to an organization and to the selected mode (Test/Live). Therefore each API Key can only be used for its own organization. Exception: API Keys of an organization can be used for the related managed organizations.
If the API key was created in test mode, entities can be created only(!) for test purposes. With a key created in live mode, only(!) live entities can be produced. I.e. in a live organization further managed organizations can be created with the Live API Key, so it is not necessary to go live with each managed organization.
On the fiskaly developer website allinformation about the API Keys can be found.
On the fiskaly developer website all information about the API Keys can be found.
There are two ways to set up the billing options:
The option Bill_to_Organization sends the invoice to the organization and can also be viewed via the dashboard.
If the option Withhold Billing is selected, the invoice is not sent to this managed organization and cannot be viewed from the dashboard. For example, the fiskaly TSS can be sold as part of a POS package without your customer seeing the price of the fiskaly TSS.
On the fiskaly developer Website, all information about billing options can be found.
A POS manufacturer uses the fiskaly Cloud TSS for its POS software. They offer three solutions to their customers. Point 1 is a typical best practice for large POS providers. Points 2 and 3 are designed for more complex models.
Please contact our sales team: sales@fiskaly.com.
1. Individual Customers — Best Practice
Under the main organization of the POS manufacturer, individual customers are created and administered as managed organizations. The API key of the managed organization is created via the main organisation. The billing option was set to Withhold Billing, because the price of the fiskaly Cloud TSS is included in the total invoice of the POS manufacturer to its customer.
2. Enterprise Customers
The cash register manufacturer creates an organization for the holding of the enterprise customer. The branches of the Enterprise Customer are created as managed organizations. The organization of the Enterprise Customer is created with the API key of the organization of the POS manufacturer. It is up to the POS manufacturer to decide whether the Enterprise Customer manages its own organizations or whether it is managed by the POS provider. The billing options are set to Withhold Billing for the organizations of the Enterprise Customer.
3. White Label Partner
The cash register manufacturer creates an organization for the White Label Partner. The White Label Partner’s customers are organized as managed organizations. The organization of the White Label Partner is created by the API key of the main organization of the POS manufacturer. The White Label Partner manages his customers (managed organizations) on its own. The billing options are set to Withhold Billing for the organizations of the White Label Partner.
For other models or special cases please contact our sales team: sales@fiskaly.com.
Here you can download the article fiskaly Dashboard and Management API as PDF document.
Data storage fiskaly Cloud — Server Site Germany At fiskaly we take a thorough interest in data protection and data security, because our customers’ data
How is the Technical Security System (TSS) Certified? The requirements for the components SMAERS (Security Module Application for Electronic Record Keeping System) and CSP (Cryptographic
German KassenSichV and the decrees of the states: How you are able to continue working in compliance with the law from 1st October 2020
Copyright fiskaly GmbH 2019
