Step-by-step Integration

To begin the integration process, please refer to the detailed step-by-step instructions provided here.

The accompanying diagram illustrates the workflow and highlights the essential steps necessary to successfully complete your integration, for which you will need to utilize our SIGN IT API.

Step 1: Registration

Begin by registering on the Dashboard.

Creating a fiskaly account is the first step, after which you can proceed with setting up the first organizational structure for your business and generating your API Key.

video tutorial

Take a look at our video for a step-by-step explanation on how to set up your account and first organization.

Step 2: Creating your first organization

Continue with creating your first organization using the Dashboard. This organization will represent the POS provider or retailer with its own POS system.

Step 3: API Key generation

The next step is to generate an API Key for your organization via the Dashboard. This API Key and Secret pair is required to create your first Asset of type UNIT (Step 5).

Note that API Keys generated in the TEST environment will create TEST resources, while those from the LIVE environment will create LIVE resources. For further details, refer to our article on TEST and LIVE environments.

Starting from the next step, you will be utilizing our SIGN IT API. You may download our Postman collection for SIGN IT, which could facilitate your integration moving forward with the next steps.

Step 4: MANAGEMENT - Creating a Token

Begin using the SIGN IT API through the createToken endpoint. You will need to create a token to authenticate for the next steps.

Step 5: MANAGEMENT - Creating an Asset (Organizational Structure)

Continue with creating an Asset of type UNIT through the createAsset endpoint. You will need to create one Asset UNIT for each of your taxpayer representations.

When creating your first Asset of type UNIT, ensure it is associated with the UUID of the first organization you created via the Dashboard. To do this, use the token generated from the API keys created in the first organization. This reflects the hierarchical structure where the UNIT is nested under the first organization.

Step 6: MANAGEMENT - Creating a Subject

Create a Subject of type API_KEY through the createSubject endpoint. The connection between the Asset UNIT and the API Key is established via the X-Scope-Identifier(using the id of the newly created Asset).

Step 7: MANAGEMENT - Creating a new Token

Next, create a token that will be used to create resources within the corresponding Asset UNIT.

Step 8: OPERATION - Creating an Entity (Taxpayer representation)

Now you’re ready to start creating the operational parts required for fiscalization in Italy. In order to do so, use the createEntity endpoint to create the representation of a Taxpayer as follows:

• You will need to set the Taxpayer as an Entity of type Company (business) or Individual (self-employed/sole trader). In both cases, the name and the address must be provided.
• Within the Italian fiscalization information, the following taxpayer data must be provided:
  • tax_id_number: Italian Fiscal Code (Codice fiscale),
  • vat_id_number: Italian VAT Number (Partita IVA),
  • credentials: pin and password required to access AdE’s services. For more information, please refer to our Credentials section.

Once you create an Entity, either of type Company or Individual, its state will be set to ACQUIRED. In order to be fully functional, the state has to be updated to COMMISSIONED using the updateEntity endpoint.

note

Only Fisconline credentials are valid for using SIGN IT Lite. Your credentials must be updated every 60 days.

important

The taxpayer must manually do an initial log in to the Revenue Agency’s web portal in order to ensure that the credentials work properly and to accept the terms, conditions and additional clauses provided.

Step 9: OPERATION - Creating a Location Entity

For each operating business location, you need to create an Entity of type Location via the createEntity endpoint.

When you create an Entity of type Location, its state is initially set to ACQUIRED. In order to proceed, you need to change the state to COMMISSIONED using the updateEntity endpoint.

Step 10: OPERATION - Creating a System (POS representation)

The createSystem endpoint allows you to create an abstraction of every device you use to issue receipts. This means that every cash register or point of sale needs to be provided as a new System in the SIGN IT API. For this, the System type FISCAL_DEVICE must be selected.

• A System will be connected to an already created Entity (whether it is of type Company or Individual, or a specific Location if different from the legal address).
• For each device, you will need to provide product information such as MPN, brand, and the date of usage start, along with the software name and version installed on the device. This information ensures proper tracking of which device is performing fiscal transactions.

When you create a System, its initial state is set to ACQUIRED. In order to create Records, its state must be updated to COMMISSIONED using the updateSystem endpoint.

Step 11: OPERATION - Creating a Record

tip

Creating a Record in the SIGN IT API will always require two subsequent calls:

• Part A) INTENTION - right at the beginning of the sale process
• Part B) TRANSACTION - directly after the payment process

PART A) Intention

For each business operation carried out in the cash register or POS, the use of the createRecord endpoint of SIGN IT API will be used in two calls: the first to record the intention of starting a transaction, and the second to provide the transaction data.

A Record of type Intention will contain the following information:

• Association with a System that will carry out the transaction.
• Operation of type Transaction: This means the operation the System intends to perform is recording a transaction.

Part B) Transaction

The final step to issue a compliant receipt in Italy is to make another call to the createRecord endpoint, indicating a Record of type Transaction.

Any Transaction document will be associated to the internal identifier of an already created Record of type Intention, and can contain details for training purposes (documents issued in training or test mode).

The Transaction can be used to carry out one of the following operations in Italy:

• RECEIPT: This operation contains all the required information for the creation of a Sales commercial document in Italy:
  • Document information such as number, activity code (if applicable), transaction date and total amounts of the document (including and excluding VAT)
  • Information of each entry or line item sold in the operation:
    • Identification of a Sale
    • Description
    • Indication if it’s a good or service
• CORRECTION: This operation type is used to represent any return process carried out. It contains the same data as an operation of type RECEIPT, and additionally:
  • Reference id to an already created receipt (original transaction document)
• CANCELLATION: This operation is used to invalidate an entire transaction. For this, the id of a previously created record needs to be provided.

In all cases, once the transaction is properly recorded and the commercial document information is successfully transmitted to AdE’s web portal, the compliant response of the record creation will indicate the progressive number assigned by AdE to the commercial document and the consumer’s Lottery Code (if provided in the transmitted payload).

note

All records created in the LIVE environment are transmitted to the Tax Authorities and generate valid commercial documents. Therefore, these documents must always reflect actual transactions.