Skip to main content

​
Introduction

Invopop’s Smart Receipts provider allows you to generate and issue electronic tickets (documento commerciale/scontrino elettronico) in Italy. The documento commerciale is a digital fiscal document that records sales transactions and transmits them to the Agenzia delle Entrate (AdE). This digital receipt replaces traditional paper receipts while maintaining full fiscal compliance and serves as official proof of purchase for your customers. Italian law requires businesses to transmit sales data digitally through either a certified Registratore Telematico (RT) or the AdE’s online portal. Smart Receipts streamlines this process by providing a secure interface to relay your sales data to the AdE through a local provider. Important distinctions for the Documento Commerciale:
  • It is not an invoice (fattura) - invoices require detailed buyer information and follow different tax rules.
  • It does not replace transport documents (documento di trasporto).
  • It is not a simple internal receipt - it serves an official fiscal function requiring AdE transmission.
  • It must include VAT at the time of sale - deferred VAT payment is not permitted.
The AdE portal provides functionality to create tickets, void them entirely, and process refunds at the item level. Invopop’s Smart Receipts implementation supports all these operations, allowing you to manage your electronic tickets programmatically through our API or manually via the Console.
-SandboxLive
SupplierTest data acceptedReal Partita IVA and AdE credentials required

​
Prerequisites

Before you begin, ensure you have:
  • An Italian tax ID (Partita IVA) for the supplier.
  • Invoice line items that include:
    • quantity,
    • name ,
    • price (including VAT),
    • VAT rate,
    • item type (specified in extension).

​
Setup

There are five key processes to prepare:
  1. Create a supplier post-registration workflow.
  2. Connect the Italian Smart Receipts app.
  3. Configure a supplier registration workflow.
  4. Prepare an invoicing workflow.
  5. Prepare a voiding 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.
1

Create Supplier post-registration workflow

Smart Receipts supplier post-registration workflow

This workflow marks suppliers as Registered. You will select this workflow in the Italian Smart Receipts app configuration later.
2

Connect the Italian Smart Receipts app

  1. Navigate to Configuration → Apps.
  2. Find Italian Smart Receipts in the app discovery list.
  3. Click Connect to activate.
Smart Receipts App
Click the Configure button on the app, and choose the “Post-registration workflow” we created in the previous step.Click the Save button.
3

Configure the supplier registration workflow

Smart receipts supplier registration workflow

This workflow will issue a registration request for a supplier to complete in order to issue receipts through SDI.
4

Prepare Invoice Workflow

Smart Receipts issue receipt workflow

This workflow will issue a Smart Receipt through Italy’s AdE.
5

Prepare Void Workflow

Smart Receipts void receipt workflow

This workflow will void Smart Receipts from the AdE.

​
Running

Each company who will issue e-receipts must first register as a supplier in Invopop. In this section we’ll first explain how to register a supplier using the registration workflow we setup, and then how to issue and void invoices on behalf of that supplier, with the corresponding workflows. As usual, the recommended approach for running jobs is to perform two steps; first upload the document to the silo, second create a job.

​
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.
  1. Navigate to Parties → Suppliers in the sidebar
  2. Click + New Supplier
  3. In the editor, enter the supplier details
Here’s an example using test data (only valid for sandbox environments): 
{
    "$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:
Supplier 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.
Issuer Registration Form
The details from this form are sent securely to 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.

​
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.
1

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.
2

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.
3

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.
4

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"
}
FieldRequiredDescription
fiscal_idYesThe supplier’s Partita IVA, without the IT country prefix.
codice_fiscaleYesThe supplier’s codice fiscale. It will be stored in the supplier party for future use.
passwordYesThe supplier’s AdE portal password.
pinYesThe supplier’s AdE portal PIN.
emailNoEmail 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.

​
Send an Invoice

Use these GOBL document examples as templates in the Invopop Console or when creating silo entries via the API. For proper validation and normalization, set these properties in your GOBL Invoices: While Invopop attempts to set these automatically based on other invoice fields, we recommend defining them explicitly.
This example shows a simple B2C invoice from an Italian supplier (Documento Commerciale). Key points to note:
  • The minimal version (ticket-b2c.min.mdx) contains only the essential fields required to create the invoice
  • The it-ticket-v1 addon ensures validation using AdE CF v1 rules built into GOBL
  • Extensions (ext) fields specify values that cannot be determined otherwise:
    • Items have an extension identifying them as goods or services
    • VAT exemptions require an Italian exemption code
  • The prices_include field indicates that item prices include VAT
  • When running gobl build, the system automatically calculates totals, line item sums, IVA breakdowns, and normalizes the document according to Smart Receipts requirements
  • The built version (ticket-b2c.mdx) shows the normalized document with all calculated fields including line indices, sums, and total amounts
{
  "$schema": "https://gobl.org/draft-0/bill/invoice",
  "$addons": ["it-ticket-v1"],
  "series": "XXIT",
  "code": "001",
  "currency": "EUR",
  "tax": {
    "prices_include": "VAT"
  },
  "type": "standard",
  "supplier": {
    "name": "Cleaning SRL",
    "tax_id": {
      "country": "IT",
      "code": "74230430451"
    }
  },
  "lines": [
    {
      "quantity": "1",
      "item": {
        "name": "Cleaning services",
        "price": "125.00",
        "ext": {
          "it-ticket-product": "services"
        }
      },
      "taxes": [
        {
          "cat": "VAT",
          "ext": {
            "it-ticket-exempt": "N3"
          }
        }
      ]
    },
    {
      "quantity": "3",
      "item": {
        "name": "Cleaning products",
        "price": "137.50",
        "ext": {
          "it-ticket-product": "goods"
        }
      },
      "taxes": [
        {
          "cat": "VAT",
          "rate": "standard"
        }
      ]
    }
  ]
}
After the AdE (Agenzia delle Entrate) accepts the invoice, they add a reference to each line item. This reference, stored in the it-ticket-line-ref extension, is essential for processing refunds.Notice:
  • This example shows a complete invoice with line references added by the AdE after acceptance
  • The minimal version contains the basic invoice structure before AdE processing
  • When running gobl build, the system calculates all totals and normalizes the document
  • The built version shows the complete document with AdE-assigned line references, calculated totals, and all automatically generated fields
  • These line references are required for creating corrective invoices and processing refunds
  • The complete invoice represents the final state after successful submission to and acceptance by the AdE
{
  "$schema": "https://gobl.org/draft-0/bill/invoice",
  "$regime": "IT",
  "$addons": [
    "it-ticket-v1"
  ],
  "uuid": "0196ed2c-3ca6-7000-b87f-8fb532b45250",
  "type": "standard",
  "series": "XXIT",
  "code": "001",
  "issue_date": "2025-05-20",
  "currency": "EUR",
  "tax": {
    "prices_include": "VAT"
  },
  "supplier": {
    "name": "Cleaning SRL",
    "tax_id": {
      "country": "IT",
      "code": "74230430451"
    }
  },
  "lines": [
    {
      "quantity": "1",
      "item": {
        "name": "Cleaning services",
        "price": "125.00",
        "ext": {
          "it-ticket-product": "services"
        }
      },
      "taxes": [
        {
          "cat": "VAT",
          "ext": {
            "it-ticket-exempt": "N3"
          }
        }
      ],
      "ext": {
        "it-ticket-line-ref": "557647"
      }
    },
    {
      "quantity": "3",
      "item": {
        "name": "Cleaning products",
        "price": "137.50",
        "ext": {
          "it-ticket-product": "goods"
        }
      },
      "taxes": [
        {
          "cat": "VAT",
          "rate": "standard"
        }
      ],
      "ext": {
        "it-ticket-line-ref": "557647"
      }
    }
  ]
}
When a customer requests a refund for specific items, you can process it by issuing a corrective invoice. Since this is still considered sending an invoice, you can use the same workflow as before.To create a corrective invoice, take the original GOBL Invoice and:
  1. Set the type field to corrective
  2. Add a reference to the original invoice using the preceding object
  3. Include the original document number stamp from the first invoice
  4. Keep the lines and quantities you want to refund
Notice:
  • The minimal version (ticket-b2c-corrective.min.mdx) contains only essential correction details including references to the original invoice
  • The corrective invoice preserves the it-ticket-line-ref extension from the original invoice for proper tracking
  • When running gobl build, the system automatically calculates negative amounts for refunds, validates the corrective structure, and applies AdE rules
  • The built version (ticket-b2c-corrective.mdx) shows the normalized document with calculated negative totals, tax refunds, and all automatically generated fields
  • The corrective invoice references the original invoice using the preceding object and maintains line item references for accurate tracking
  • This example shows a corrective invoice that refunds two units of “Cleaning Products” from the original invoice
{
  "$schema": "https://gobl.org/draft-0/bill/invoice",
  "$regime": "IT",
  "$addons": [
    "it-ticket-v1"
  ],
  "type": "corrective",
  "series": "REFUND",
  "code": "001",
  "issue_date": "2025-05-20",
  "currency": "EUR",
  "preceding": [
    {
      "uuid": "0196ed2c-3ca6-7000-b87f-8fb532b45250",
      "type": "standard",
      "issue_date": "2025-05-20",
      "series": "XXIT",
      "code": "001",
      "stamps": [
        {
          "prv": "ade-ref",
          "val": "ACUBE2025/0000-7816"
        }
      ]
    }
  ],
  "tax": {
    "prices_include": "VAT"
  },
  "supplier": {
    "name": "Cleaning SRL",
    "tax_id": {
      "country": "IT",
      "code": "74230430451"
    }
  },
  "lines": [
    {
      "quantity": "2",
      "item": {
        "name": "Cleaning products",
        "price": "137.50",
        "ext": {
          "it-ticket-product": "goods"
        }
      },
      "taxes": [
        {
          "cat": "VAT",
          "rate": "standard"
        }
      ],
      "ext": {
        "it-ticket-line-ref": "557647"
      }
    }
  ]
}
The AdE will automatically generate a document number for the invoice. Once the invoice is sent, you will find the document number in a stamp inside the document header.
Invoice Stamp

​
Refund an Invoice

Refund processing is handled through corrective invoices, which you can issue using the same workflow as regular invoices. See the “Corrective Invoice” accordion above for details and examples.

​
Void an Invoice

You can void an invoice if it was issued in error, such as when a receipt is accidentally sent twice. To void an invoice:
  1. Locate the silo entry uuid of the invoice
  2. Run the “Void AdE CF Invoices” workflow with this uuid
You can only void invoices that were originally sent through this app during the same business day.

​
FAQ

Install the SDI Italy app for B2B/B2G/B2C structured invoicing, or the Smart Receipts app for B2C-only AdE CF receipts. Run invoices through the Generate FatturaPA + Send to SDI workflow.
See the Italy tax regime in GOBL for tax categories, codice fiscale rules, and SDI-specific extensions. The it-sdi-v1 addon documents required FatturaPA fields.
You cannot modify an AdE CF invoice after issuing it. Instead you must:
  1. Void the incorrect invoice using the “Void AdE CF Invoices” workflow
  2. Issue a new invoice with the correct information
We recommend adding a series and code to the invoice so that you can keep track internally even though the AdE will generate a document number.
AdE CF is not a substitute for SDI. Invopop works with SDI to issue electronic invoices using the FatturaPA and is the main tool available to issue electronic invoices in Italy. AdE CF should only be used when customer information is not available, like in online B2C scenarios.
Use the standard GOBL invoice with the simplified tag. No customer tax ID is required. The it-ticket-v1 addon handles the AdE CF-specific fields. Each receipt gets a unique Lottery Code if the lottery functionality is enabled.
More available in our Italy FAQ section

Participate in our community

Ask and answer questions about invoicing in Italy →