Smart Receipts supplier registration guide

Introduction

Before a company can issue electronic tickets (documento commerciale/scontrino elettronico) in Italy, they must be registered as a supplier in Invopop with the credentials they use on the Agenzia delle Entrate (AdE) portal, so that receipts can be relayed to the AdE on their behalf. In this guide you’ll learn how to register a supplier using the Smart Receipts Italy app. Once a supplier is registered, continue with the companion guide: Italy: Issuing receipts.

-	Sandbox	Live
Supplier	Test data accepted	Real Partita IVA and AdE credentials required

Prerequisites

To register a supplier for Smart Receipts, you will need:

An Italian tax ID (Partita IVA) for the supplier.
The supplier’s codice fiscale.
The supplier’s AdE portal credentials (password and PIN).

Setup

There are three key processes to prepare:

Create a supplier post-registration workflow.
Connect the Italian Smart Receipts app.
Configure a supplier registration workflow.

These instructions work in both sandbox and live environments. The only differences are in supplier data and registration details when using test environments.

Follow these steps in the Invopop Console.

Create Supplier post-registration workflow

Smart Receipts supplier post-registration workflow

Add to my workspace →

Workflow
Code

Copy and paste into a new Empty Party workflow code view.

SDI supplier post-registration workflow

{
    "name": "SDI supplier post-registration",
    "description": "Mark an SDI customer as registered",
    "schema": "org/party",
    "steps": [
        {
            "id": "7e8d8070-3870-11ef-af29-4533d56cea03",
            "name": "Set state",
            "config": {
                "state": "registered"
            },
            "summary": "Set state to `registered`{.state .registered}",
            "provider": "silo.state"
        }
    ],
    "rescue": []
}

Connect the Italian Smart Receipts app

Navigate to Configuration → Apps.
Find Italian Smart Receipts in the app discovery list.
Click Connect to activate.

Click the Configure button on the app, and choose the “Post-registration workflow” we created in the previous step.Click the Save button.

Configure the supplier registration workflow

Smart receipts supplier registration workflow

Add to my workspace →

Workflow
Code

Copy and paste into a new Empty Party workflow code view.

Smart Receipts register supplier workflow

{
    "name": "Smart Receipts register supplier",
    "description": "Register a supplier with AdE",
    "schema": "org/party",
    "steps": [
        {
            "id": "1a1be400-2b32-11f0-984e-0542d5f28f0b",
            "name": "Sign envelope",
            "provider": "silo.close"
        },
        {
            "id": "de116bb0-25b4-11f0-864a-193f213df097",
            "name": "Register supplier with AdE",
            "provider": "ticket-it.register"
        },
        {
            "id": "e0a1b380-25b4-11f0-864a-193f213df097",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `processing`{.state .processing}",
            "config": {
                "state": "processing"
            }
        }
    ],
    "rescue": [
        {
            "id": "1deb1470-2b32-11f0-984e-0542d5f28f0b",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `error`{.state .error}",
            "config": {
                "state": "error"
            }
        }
    ]
}

Register a supplier

You can register suppliers either manually via the Invopop Console or programmatically via the API. The process is essentially the same. We’ll demonstrate the manual process first, followed by the API flow.

Suppliers in Italy using this system must generate and provide their AdE credentials so that invoices can be processed on their behalf. This is not an automated service and can only be performed manually by a representative of the supplier.

Navigate to Parties → Suppliers in the sidebar
Click + New Supplier
In the editor, enter the supplier details

Here’s an example using test data (only valid for sandbox environments):

View supplier Data for sandbox

{
    "$schema": "https://gobl.org/draft-0/org/party",
    "uuid": "018fbeda-bc61-7000-b66d-398ce3e21c43",
    "name": "Milano Pizza",
    "tax_id": {
        "country": "IT",
        "code": "48220010093"
    },
    "identities": [
        {
            "key": "it-fiscal-code",
            "code": "MRTMTT91D08F205J"
        }
    ]
}

You may notice that we included the Italian fiscal code in the supplier, this is not necessary at the moment but will be asked for, if not provided, during the registration process.

Tap Build, ensure there are no errors, and click Save. We should now see the document. Find and click the Select Workflow button. Select the Register Supplier workflow created during setup, and click Run Workflow. The execution should be successful, and the silo entry will now be in the Processing state. Tap the Meta tab to see the registration link:

You can access the registration link via the API by fetching the silo entry and reading the meta row where the key is set to registration-link.

Tap the registration link and a new browser window will be presented with a form to upload the credentials for the supplier. Note that this form can be shared directly with the supplier if required.

The details from this form are sent securely to our local partner who will be responsible for sending them to the AdE. We will update the supplier with the provided codice fiscale for future use but will not store any type of credentials.

These credentials will expire every 90 days. You must first update your credentials on the official AdE web portal, then enter these new credentials in our registration form. You can use the same registration link to update your credentials.

At this point, you’re ready to start issuing receipts on behalf of the supplier. Head over to the Smart Receipts issuing guide to continue.

Register a supplier via the API

The whole registration process can also be completed programmatically. This is useful in white-label setups where you want to collect the supplier’s credentials inside your own product instead of sharing Invopop’s hosted form.

Upload the supplier

Use the Create an entry endpoint to upload the supplier party, like the example in the previous section. The party must include the company name and an Italian tax_id (Partita IVA). Optionally include the it-fiscal-code identity and an email address to pre-fill the registration form.

Run the registration workflow

Send the supplier to the registration workflow using the Create a job endpoint with the IDs of the silo entry and the supplier registration workflow created during setup.

Fetch the registration link

Fetch the silo entry and read the meta row where the key is registration-link. The link_url will look like this:

https://ticket-it.invopop.com/register/{owner_id}/{entry_id}?exp={expiry}&sig={signature}

The URL is signed: the exp and sig query parameters are validated on every request, so always use the link_url exactly as returned. Requests with missing or modified parameters are rejected.

Submit the credentials

Opening the link in a browser presents the hosted registration form. To submit the credentials from your own product instead, send a PUT request to the link_url (keeping the query parameters intact) with the following JSON body:

{
  "fiscal_id": "48220010093",
  "codice_fiscale": "MRTMTT91D08F205J",
  "email": "supplier@example.com",
  "password": "supplier-ade-password",
  "pin": "12345678"
}

Field	Required	Description
`fiscal_id`	Yes	The supplier’s Partita IVA, without the `IT` country prefix.
`codice_fiscale`	Yes	The supplier’s codice fiscale. It will be stored in the supplier party for future use.
`password`	Yes	The supplier’s AdE portal password.
`pin`	Yes	The supplier’s AdE portal PIN.
`email`	No	Email address to receive AdE notifications. Updates the supplier party if changed.

A 200 response means the registration is complete and the post-registration workflow configured in the app will be launched. Errors are returned as {"error": "<message>"} with a 400 status for client errors (invalid or expired link, missing fields) or 500 for server errors.The same endpoint can be called again with the same link to update the supplier’s credentials when they expire.

Unregister a supplier

Unregistering a supplier revokes their receipt issuing privileges. You might need to unregister a supplier because they are no longer your client or because of a change in their Partita IVA. Unregistering disables receipt issuance for the supplier with our local partner and removes the registration link and codice fiscale stored with the supplier. To do so, use the following workflow template:

Smart Receipts unregister supplier

Add to my workspace →

Workflow
Code

Copy and paste into a new Empty Party workflow code view.

Smart Receipts unregister supplier workflow

{
    "name": "Smart Receipts unregister supplier",
    "description": "Unregister a supplier from AdE to stop issuing receipts",
    "schema": "org/party",
    "steps": [
        {
            "id": "8c00e272-ded1-4600-8e86-24e0ffb8c0b2",
            "name": "Unregister supplier from AdE",
            "provider": "ticket-it.deregister",
            "summary": "Stop issuing receipts for this supplier"
        },
        {
            "id": "c8a3aa22-4f06-48a8-9a81-f89b281de700",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `void`{.state .void}",
            "config": {
                "state": "void"
            }
        }
    ],
    "rescue": [
        {
            "id": "26ff28ea-3a4a-4c04-b415-4ed6d8bb8cad",
            "name": "Set state",
            "provider": "silo.state",
            "summary": "Set state to `error`{.state .error}",
            "config": {
                "state": "error"
            }
        }
    ]
}

Run the workflow on the supplier’s silo entry, the same one you registered earlier. On success, the entry moves to the Void state. If the supplier was never registered, the step is skipped without error. To issue receipts for the supplier again, run the registration workflow and submit their AdE credentials once more.

FAQ

How do I onboard a new supplier in Italy?

Provide the supplier’s Partita IVA and Codice Fiscale (where different) in their party configuration. No certificate upload is needed — Invopop transmits to SDI over its own accredited channel.

How are supplier credentials stored in Invopop for Italy?

No supplier certificates are required. Invopop exchanges documents with SDI over its own accredited channel; only the Partita IVA and routing metadata are stored.

How do I register a supplier with Smart Receipts?

Create the supplier party with its Partita IVA and run the Smart Receipts Register Supplier workflow. The workflow returns a signed registration link in the silo entry’s meta. Open the link (or share it with the supplier) and submit the supplier’s AdE credentials. Once the form is accepted, the post-registration workflow runs and the supplier can start issuing receipts. See the supplier registration guide for the full steps.

What credentials does Smart Receipts require to authenticate a supplier?

The supplier’s own Agenzia delle Entrate portal credentials: the password and PIN they use at ivaservizi.agenziaentrate.gov.it, together with their Partita IVA and codice fiscale. Only a representative of the supplier can generate these. They are submitted through the registration link and passed securely to our local partner, who uses them to transmit receipts to the AdE on the supplier’s behalf. Invopop stores the codice fiscale on the party but never stores the password or PIN.

How often do the supplier's AdE credentials need to be renewed?

Every 90 days. The supplier must first renew the credentials on the AdE portal, then resubmit them through the same registration link (or via the API PUT to the link) so receipt issuance is not interrupted.

More available in our Italy FAQ section

🇮🇹 Invopop resources for Italy


Compliance	Invoicing compliance in Italy Compliance timeline
Apps	Italy SDI Italy Smart Receipts Italy
Guides	SDI — Issuing invoices · Status · Receiving invoices · Archiving SDI sending guide (legacy) SDI receiving guide (legacy) Smart Receipts supplier registration Smart Receipts issuing guide
FAQ	Italy FAQ
GOBL	Italy Tax Regime Italy SDI FatturaPA Addon Italy AdE Ticket Addon
GitHub	gobl.fatturapa

Participate in our community

Ask and answer questions about invoicing in Italy →

Networks

Countries

Set-up

GOBL

Apps

API

Features

Smart Receipts supplier registration guide

Introduction

Prerequisites

Setup

Smart Receipts supplier post-registration workflow

Smart receipts supplier registration workflow

Register a supplier

Register a supplier via the API

Unregister a supplier

Smart Receipts unregister supplier

FAQ

Participate in our community

​Introduction

​Prerequisites

​Setup

Smart Receipts supplier post-registration workflow

Smart receipts supplier registration workflow

​Register a supplier

​Register a supplier via the API

​Unregister a supplier

Smart Receipts unregister supplier

​FAQ

Participate in our community

Introduction

Prerequisites

Setup

Register a supplier

Register a supplier via the API

Unregister a supplier

FAQ