NO VERI*FACTU Onboarding Guide

Introduction

NO VERI*FACTU is one of the two compliance modalities defined by Spain’s Real Decreto 1007/2023 for Computerized Billing Systems (SIF). Unlike VERI*FACTU, where invoicing records are sent to the AEAT in real time, in NO VERI*FACTU mode records are digitally signed and stored locally — they are only submitted to the AEAT upon explicit requirement. This guide walks you through the process of registering suppliers for NO VERI*FACTU, including:

Setting up the necessary workflows.
Registering suppliers via the API.
How automatic event generation works.

NO VERI*FACTU supplier registration does not require an agreement signing process or identity verification. Registration is immediate upon execution.

Set-up

Connect the Spain and Cron apps

Go to Configuration → Apps in the Console.
Find Spain in the app list and click Connect to activate it.
Find Cron in the app list and click Connect to activate it.

No additional configuration is needed. The Cron app handles the periodic generation of summary events every 6 hours, as required by the regulation.

Create the event processing workflow

Before setting up the other workflows, you need a workflow to process event records. This workflow is used by the registration, unregistration, and summary event workflows to generate and store signed event XML records.

Template
Code
Build from scratch

NO VERI*FACTU event processing workflow

This workflow generates and stores signed event records.

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

Example NO VERI*FACTU event processing workflow

{
    "name": "NO VERI*FACTU process event",
    "description": "Generate, sign, and store a NO VERI*FACTU event record",
    "schema": "bill/status",
    "steps": [
        {
            "id": "e5f6a7b0-0005-11f1-a000-000000000004",
            "name": "Set State",
            "provider": "silo.state",
            "summary": "Set state to `processing`{.state .processing}",
            "config": {
                "state": "processing"
            }
        },
        {
            "id": "bbf19740-3a6b-11f1-9a44-6748aa5d4a91",
            "name": "Modify Silo Entry",
            "provider": "silo.modify",
            "summary": "Modifications configured",
            "config": {
                "jq": ".series //= \"NVF\"",
                "merge_type": "application/jq",
                "scope": "doc"
            }
        },
        {
            "id": "a1b2c3d0-0001-11f1-a000-000000000002",
            "name": "Add Sequential Code",
            "provider": "sequence.enumerate",
            "summary": "Dynamic · NoVerifactu · 000001",
            "config": {
                "name": "NoVerifactu",
                "padding": 6,
                "start": 1
            }
        },
        {
            "id": "e5f6a7b0-0005-11f1-a000-000000000006",
            "name": "Sign Envelope",
            "provider": "silo.close"
        },
        {
            "id": "f8df5470-3c97-11f1-8c73-6dd226144d30",
            "name": "Generate NO VERI*FACTU Event Record (Spain)",
            "provider": "gov-es.noverifactu.generate.event"
        },
        {
            "id": "050b05a0-3c98-11f1-8c73-6dd226144d30",
            "name": "Record for NO VERI*FACTU (Spain)",
            "provider": "gov-es.noverifactu.record"
        },
        {
            "id": "e5f6a7b0-0005-11f1-a000-000000000005",
            "name": "Set State",
            "provider": "silo.state",
            "summary": "Set state to `registered`{.state .registered}",
            "config": {
                "state": "registered"
            }
        }
    ],
    "rescue": [
        {
            "id": "e5f6a7b0-0005-11f1-a000-000000000003",
            "name": "Set State",
            "provider": "silo.state",
            "summary": "Set state to `error`{.state .error}",
            "config": {
                "state": "error"
            }
        }
    ]
}

Before starting, review the workflows guide to understand the general setup process.In Console, create a new workflow and choose a status document workflow as the base. Then name the workflow with a descriptive label such as “NO VERI*FACTU Process Event”.The new workflow will need the following steps:

Set State — select “Processing”.
Sign Envelope — signs the GOBL envelope.
Generate Event Record — generates and digitally signs the event XML from the bill.Status document.
Store Record — persists the signed event record in the database.
Set State — select “Registered”.

In the Error Handling area, add the Set State action and select Error.

Create the summary event workflow

The regulation requires a summary event (event type 10) to be generated every 6 hours the system has been operational. Create this workflow so that suppliers can be subscribed to it during registration.

Template
Code
Build from scratch

NO VERI*FACTU summary event workflow

This workflow generates and processes a summary event.

After adding the template, open the Process Event step and set the Workflow field to the event processing workflow created in the previous step.

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

Example NO VERI*FACTU summary event cron workflow

{
    "name": "NO VERI*FACTU summary event",
    "description": "Build and process a NO VERI*FACTU summary event every 6 hours",
    "schema": "org/party",
    "steps": [
        {
            "id": "f6a7b8c0-0006-11f1-a000-000000000001",
            "name": "Build NO VERI*FACTU Status (Spain)",
            "provider": "gov-es.noverifactu.build.status",
            "summary": "Build status: 10 - Summary event",
            "config": {
                "event_type": "10"
            }
        },
        {
            "id": "4f527c60-3a95-11f1-a472-21be9722e465",
            "name": "Create a Job",
            "provider": "transform.job.create",
            "summary": "Send to NO VERI*FACTU process event (bill/status)",
            "config": {
                "silo_entry_meta_key": "",
                "workflow_id": ""
            }
        }
    ],
    "rescue": [
        {
            "id": "f6a7b8c0-0006-11f1-a000-000000000003",
            "name": "Set State",
            "provider": "silo.state",
            "summary": "Set state to `error`{.state .error}",
            "config": {
                "state": "error"
            }
        }
    ]
}

After pasting the code, switch to the form view, open the Process Event step and set the Workflow field to the event processing workflow created in the previous step.

In Console create a new workflow and select Empty Party workflow in the template selector, then add the following steps:

Build Summary Event — configured with event type 10 (“Summary event”). Aggregates invoicing and event record counts, tax totals, and references for the period since the last summary.
Process Event — creates a job to process the summary event. Set the Workflow field to the NO VERI*FACTU event processing workflow created in the previous step.

In the Error Handling section, add the Set State action and select Error.

You won’t need to run this workflow manually. The registration workflow automatically will subscribe each supplier to periodic execution of this workflow using the Cron app. When a supplier is unregistered, the unregistration workflow will unsubscribe them.

Create a supplier registration workflow

Create a new workflow for registering suppliers. This workflow registers the supplier, generates the mandatory “Start of NO VERI*FACTU mode” event (event type 01), and subscribes the supplier to periodic summary event generation every 6 hours.

Template
Code
Build from scratch

NO VERI*FACTU supplier registration workflow

This workflow registers a supplier, generates the start-of-mode event, and subscribes to periodic summary events.

After adding the template, open the Process Event step and set the Workflow field to the event processing workflow. Then open the Subscribe to summary event cron step and set the Workflow field to the summary event workflow.

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

Example NO VERI*FACTU supplier registration

{
    "name": "NO VERI*FACTU supplier registration",
    "description": "Register a supplier for NO VERI*FACTU, generate the start-of-mode event, and subscribe to periodic summary events",
    "schema": "org/party",
    "steps": [
        {
            "id": "c21b4130-3a65-11f1-a475-db4c42dd4e99",
            "name": "Set Silo Entry State",
            "provider": "silo.state",
            "summary": "Set state to `processing`{.state .processing}",
            "config": {
                "state": "processing"
            },
            "next": []
        },
        {
            "id": "78e845e0-3ca3-11f1-90b7-0d81b4010093",
            "name": "Register for NO VERI*FACTU (Spain)",
            "provider": "gov-es.noverifactu.register",
            "next": []
        },
        {
            "id": "8857fe80-3ca3-11f1-90b7-0d81b4010093",
            "name": "Build NO VERI*FACTU Status (Spain)",
            "provider": "gov-es.noverifactu.build.status",
            "next": [],
            "summary": "Build status: 01 - Start of NO VERI*FACTU mode",
            "config": {
                "event_type": "01"
            }
        },
        {
            "id": "d16d34a0-3a91-11f1-a472-21be9722e465",
            "name": "Create a Job",
            "provider": "transform.job.create",
            "summary": "Send to NO VERI*FACTU process event (bill/status)",
            "config": {
                "silo_entry_meta_key": "",
                "workflow_id": ""
            },
            "next": []
        },
        {
            "id": "03cb3000-3a92-11f1-a472-21be9722e465",
            "name": "Subscribe to Periodic Execution",
            "provider": "cron.subscribe",
            "summary": "Every 6 hours → no workflow",
            "config": {
                "workflow_id": "",
                "interval": "hourly",
                "factor": 6
            },
            "next": []
        },
        {
            "id": "c3d4e5f0-0003-11f1-a000-000000000002",
            "name": "Set State",
            "provider": "silo.state",
            "summary": "Set state to `registered`{.state .registered}",
            "config": {
                "state": "registered"
            },
            "next": []
        }
    ],
    "rescue": [
        {
            "id": "c3d4e5f0-0003-11f1-a000-000000000005",
            "name": "Unregister supplier",
            "provider": "gov-es.noverifactu.unregister",
            "next": []
        },
        {
            "id": "c3d4e5f0-0003-11f1-a000-000000000006",
            "name": "Set State",
            "provider": "silo.state",
            "summary": "Set state to `rejected`{.state .rejected}",
            "config": {
                "state": "rejected"
            },
            "next": []
        }
    ]
}

After pasting the code, switch to the form view. Open the Process Event step and set the Workflow field to the event processing workflow. Then open the Subscribe to summary event cron step and set the Workflow field to the summary event workflow.

Before starting, review the workflows guide to understand the general setup process.In Console, create a new workflow and choose Empty Party workflow as the base. Then name the workflow with a descriptive label such as “NO VERI*FACTU Supplier Registration”.The new workflow will need to perform the following steps:

Set State — select “Processing”.
Register supplier — registers the supplier for NO VERI*FACTU mode. Registration is immediate (auto-approved).
Build Start Event — configured with event type 01 (“Start of NO VERI*FACTU mode”). Builds a bill.Status document and uploads it as a silo entry.
Process Event — creates a job to process the event. Set the Workflow field to the NO VERI*FACTU event processing workflow.
Subscribe to summary event cron — uses the Cron app to subscribe the supplier to periodic execution every 6 hours. Set the Workflow field to the NO VERI*FACTU summary event workflow.
Set State — select “Registered”.

In the Error Handling area, add the following steps:

Unregister supplier — clears the registration.
Set State — select Rejected.

Create a supplier unregistration workflow

Create a workflow for unregistering suppliers. This workflow unsubscribes the supplier from the periodic summary event cron, removes the NO VERI*FACTU registration, and generates the mandatory “End of NO VERI*FACTU mode” event (event type 02).

Template
Code
Build from scratch

NO VERI*FACTU unregister supplier

This workflow unsubscribes from summary events, unregisters a supplier, and generates the end-of-mode event.

After adding the template, open the Process Event step and set the Workflow field to the event processing workflow.

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

Example NO VERI*FACTU unregister supplier

{
    "name": "NO VERI*FACTU unregister supplier",
    "description": "Unsubscribe from summary events, unregister a NO VERI*FACTU supplier, and generate the end-of-mode event",
    "schema": "org/party",
    "steps": [
        {
            "id": "d4e5f6a0-0004-11f1-a000-000000000007",
            "name": "Set State",
            "provider": "silo.state",
            "summary": "Set state to `processing`{.state .processing}",
            "config": {
                "state": "processing"
            }
        },
        {
            "id": "3e4bd770-3a92-11f1-a472-21be9722e465",
            "name": "Unsubscribe from Periodic Execution",
            "provider": "cron.unsubscribe"
        },
        {
            "id": "f46dfa20-3ca3-11f1-90b7-0d81b4010093",
            "name": "Build NO VERI*FACTU Status (Spain)",
            "provider": "gov-es.noverifactu.build.status",
            "summary": "Build status: 02 - End of NO VERI*FACTU mode",
            "config": {
                "event_type": "02"
            }
        },
        {
            "id": "2fbe2590-3caf-11f1-ae77-65667068cb42",
            "name": "Create a Job",
            "provider": "transform.job.create",
            "summary": "Send to NO VERI*FACTU process event (bill/status)",
            "config": {
                "silo_entry_meta_key": "",
                "workflow_id": ""
            }
        },
        {
            "id": "9a9235e0-3cb0-11f1-ae77-65667068cb42",
            "name": "Unregister from NO VERI*FACTU (Spain)",
            "provider": "gov-es.noverifactu.unregister"
        },
        {
            "id": "d4e5f6a0-0004-11f1-a000-000000000004",
            "name": "Set State",
            "provider": "silo.state",
            "summary": "Set state to `void`{.state .void}",
            "config": {
                "state": "void"
            }
        }
    ],
    "rescue": [
        {
            "id": "d4e5f6a0-0004-11f1-a000-000000000006",
            "name": "Set State",
            "provider": "silo.state",
            "summary": "Set state to `error`{.state .error}",
            "config": {
                "state": "error"
            }
        }
    ]
}

After pasting the code, switch to the form view, open the Process Event step and set the Workflow field to the event processing workflow.

In Console create a new workflow and select Empty Party workflow in the template selector, then add the following steps:

Set State — select “Processing”.
Unsubscribe from summary event cron — uses the Cron app to remove the periodic summary event subscription for this supplier.
Unregister supplier — clears the NO VERI*FACTU registration state.
Build End Event — configured with event type 02 (“End of NO VERI*FACTU mode”). Builds a bill.Status document and uploads it as a silo entry.
Process Event — creates a job to process the event. Set the Workflow field to the NO VERI*FACTU event processing workflow.
Set State — select Void.

In the Error Handling section, add the Set State action and select Error.

Register a Supplier

Whether you issue invoices on behalf of third parties (white label) or under your own name, the registration process is the same.

Upload a supplier

Use the Create an entry endpoint to upload a new supplier party. Required fields are company name and tax_id.

Spanish company

To register a company supplier in Spain you must provide:

Company information: name, NIF (tax identification number), and address
Legal representative information: full name, government ID type and number (DNI, NIE, or passport), and address

The legal representative is the person authorized to sign the representation agreement on behalf of the company.

The supplier must be previously registered with the tax authority before invoices can be issued on their behalf.

{
  "$schema": "https://gobl.org/draft-0/org/party",
  "name": "Invopop S.L.",
  "tax_id": {
    "country": "ES",
    "code": "B85905495"
  },
    "people": [
        {
            "name": {
                "given": "Juan",
                "surname": "Pérez González"
            },
            "identities": [
                {
                    "key": "national",
                    "code": "123456789A"
                }
            ],
            "addresses": [
                {
                    "num": "10",
                    "street": "Calle Ejemplo",
                    "locality": "Madrid",
                    "region": "Madrid",
                    "code": "28020",
                    "country": "ES"
                }
            ]
        }
    ],
  "addresses": [
    {
      "num": "42",
      "street": "Calle Pradillo",
      "locality": "Madrid",
      "region": "Madrid",
      "code": "28002",
      "country": "ES"
    }
  ],
  "emails": [
    {
      "addr": "billing@example.com"
    }
  ]
}

Spanish autónomo

An autónomo is self-employed individuals in Spain who operate as sole proprietors. To register them, a NIF (tax id number) with the corresponding full name and address must be provided.Unlike company suppliers, autónomos do not require separate legal representative information since the individual is the authorized signatory.

The supplier must be previously registered with the tax authority before invoices can be issued on their behalf.

{
  "$schema": "https://gobl.org/draft-0/org/party",
  "name": "Juan Pérez González",
  "tax_id": {
    "country": "ES",
    "code": "B85905495"
  },
  "addresses": [
    {
      "num": "42",
      "street": "Calle Pradillo",
      "locality": "Madrid",
      "region": "Madrid",
      "code": "28002",
      "country": "ES"
    }
  ],
  "emails": [
    {
      "addr": "autonomo@example.com"
    }
  ]
}

Set the folder to suppliers to have the party appear in this section. It should appear with an Empty status unless set otherwise.

Send the supplier to the registration workflow

Via API — Send the supplier to the registration workflow using the Create a job endpoint using the IDs of the silo entry and supplier registration workflow.
Via Console — From the Silo Entry select “Run workflow” and select the NO VERI*FACTU supplier registration workflow.

The supplier’s status will change to Registered immediately upon successful completion. Unlike VERI*FACTU, there is no agreement signing step or approval waiting period.

A party can be simultaneously registered in both VERI*FACTU and NO VERI*FACTU, as each modality uses distinct meta keys to track registration state. This means integrators can offer both modalities to different suppliers within the same workspace.

Unregister a Supplier

Unregistering a supplier revokes their NO VERI*FACTU invoice issuing privileges and generates the required “End of NO VERI*FACTU mode” event. You might need to unregister a supplier because they are no longer your client, they are switching to VERI*FACTU mode, or because of a change in their Tax ID. Send the supplier’s silo entry to the NO VERI*FACTU unregister supplier workflow using the Create a job endpoint. The supplier’s status will change to Void when the workflow completes.

Automatic Event Generation

NO VERI*FACTU requires the system to automatically detect and record certain events. The following events are generated automatically by the workflows described in this guide:

Event	Type	When Generated
Start of NO VERI*FACTU mode	`01`	When a supplier is registered via the registration workflow
End of NO VERI*FACTU mode	`02`	When a supplier is unregistered via the unregistration workflow
Summary event	`10`	Every 6 hours, triggered automatically by the Cron app subscription created during registration

All event records are digitally signed and stored with the same integrity guarantees as invoicing records. The event processing workflow (generate.event → record) handles the XML generation, digital signing, and storage for all event types.

🇪🇸 Invopop resources for Spain


Compliance	Invoicing compliance in Spain Compliance timeline
Apps	Spain VERI*FACTU Spain TicketBAI Spain
Guides	Facturae Guide VERIFACTU Invoicing Guide VERIFACTU Supplier Onboarding SII Invoicing Guide SII Supplier Onboarding TicketBAI Guide
FAQ	Spain FAQ
GOBL	Spain Tax Regime VERI*FACTU Addon Facturae Addon SII Addon
GitHub	gobl.facturae gobl.verifactu gobl.ticketbai

Spain FAQ

Find answers to frequently asked questions about invoicing in Spain →

Participate in our community

Ask and answer questions about invoicing in Spain →

Networks

Countries

Set-up

GOBL

Apps

API

Features

NO VERI*FACTU Onboarding Guide

Introduction

Set-up

NO VERI*FACTU event processing workflow

NO VERI*FACTU summary event workflow

NO VERI*FACTU supplier registration workflow

NO VERI*FACTU unregister supplier

Register a Supplier

Unregister a Supplier

Automatic Event Generation

Spain FAQ

Participate in our community

Networks

Countries

Set-up

GOBL

Apps

API

Features

​Introduction

​Set-up

NO VERI*FACTU event processing workflow

NO VERI*FACTU summary event workflow

NO VERI*FACTU supplier registration workflow

NO VERI*FACTU unregister supplier

​Register a Supplier

​Unregister a Supplier

​Automatic Event Generation

Spain FAQ

Participate in our community

Introduction

Set-up

Register a Supplier

Unregister a Supplier

Automatic Event Generation