> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invopop.com/llms.txt
> Use this file to discover all available pages before exploring further.
# NO VERI*FACTU Onboarding Guide
> Register and manage suppliers in Spain with NO VERI*FACTU.
## 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:
1. Setting up the necessary workflows.
2. Registering suppliers via the API.
3. 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
1. Go to **Configuration** → **Apps** in the [Console](https://console.invopop.com).
2. Find **Spain** in the app list and click **Connect** to activate it.
3. Find **Cron** in the app list and click **Connect** to activate it.
No additional configuration is needed. The [Cron app](/apps/cron) handles the periodic generation of summary events every 6 hours, as required by the regulation.
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.
This workflow generates and stores signed event records.
Copy and paste into a new [Empty Status workflow](https://console.invopop.com/redirect/workflows/new?template=empty-status) code view.
```json Example NO VERI*FACTU event processing workflow expandable theme={"system"}
{
"name": "NO VERI*FACTU process event",
"description": "Generate 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": "Default series to \"NVF\"",
"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 · NO VERI*FACTU · 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 event for NO VERI*FACTU",
"provider": "gov-es.noverifactu.generate.event"
},
{
"id": "050b05a0-3c98-11f1-8c73-6dd226144d30",
"name": "Record for NO VERI*FACTU",
"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](/guides/features/workflows) to understand the general setup process.
In [Console](https://console.invopop.com), 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:
1. **Set state** — select "Processing".
2. **Sign envelope** — signs the GOBL envelope.
3. **Generate Event Record** — generates and digitally signs the event XML from the `bill.Status` document.
4. **Store Record** — persists the signed event record in the database.
5. **Set state** — select "Registered".
In the Error Handling area, add the **Set state** action and select `Error`.
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.
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](https://console.invopop.com/redirect/workflows/new?template=empty-party) code view.
```json Example NO VERI*FACTU summary event cron workflow expandable theme={"system"}
{
"name": "NO VERI*FACTU summary event",
"description": "Build a NO VERI*FACTU summary event (cron-driven)",
"schema": "org/party",
"steps": [
{
"id": "f6a7b8c0-0006-11f1-a000-000000000001",
"name": "Build status for NO VERI*FACTU",
"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](https://console.invopop.com) create a new workflow and select [Empty Party workflow](https://console.invopop.com/redirect/workflows/new?template=empty-party) in the template selector, then add the following steps:
1. **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.
2. **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](/apps/cron). When a supplier is unregistered, the unregistration workflow will unsubscribe them.
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.
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](https://console.invopop.com/redirect/workflows/new?template=empty-party) code view.
```json Example NO VERI*FACTU register supplier workflow expandable theme={"system"}
{
"name": "NO VERI*FACTU register supplier",
"description": "Register a supplier with NO VERI*FACTU, generate the start-of-mode event, and subscribe to summary events",
"schema": "org/party",
"steps": [
{
"id": "c21b4130-3a65-11f1-a475-db4c42dd4e99",
"name": "Set state",
"provider": "silo.state",
"summary": "Set state to `processing`{.state .processing}",
"config": {
"state": "processing"
},
"next": []
},
{
"id": "78e845e0-3ca3-11f1-90b7-0d81b4010093",
"name": "Register supplier with NO VERI*FACTU",
"provider": "gov-es.noverifactu.register",
"next": []
},
{
"id": "8857fe80-3ca3-11f1-90b7-0d81b4010093",
"name": "Build status for NO VERI*FACTU",
"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",
"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 from NO VERI*FACTU",
"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](/guides/features/workflows) to understand the general setup process.
In [Console](https://console.invopop.com), create a new workflow and choose [Empty Party workflow](https://console.invopop.com/redirect/workflows/new?template=empty-party) 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:
1. **Set state** — select "Processing".
2. **Register supplier** — registers the supplier for NO VERI\*FACTU mode. Registration is immediate (auto-approved).
3. **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.
4. **Process Event** — creates a job to process the event. Set the **Workflow** field to the **NO VERI\*FACTU event processing** workflow.
5. **Subscribe to summary event cron** — uses the [Cron app](/apps/cron) to subscribe the supplier to periodic execution every 6 hours. Set the **Workflow** field to the **NO VERI\*FACTU summary event** workflow.
6. **Set state** — select "Registered".
In the Error Handling area, add the following steps:
1. **Unregister supplier** — clears the registration.
2. **Set state** — select `Rejected`.
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`).
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](https://console.invopop.com/redirect/workflows/new?template=empty-party) code view.
```json Example NO VERI*FACTU unregister supplier workflow expandable theme={"system"}
{
"name": "NO VERI*FACTU unregister supplier",
"description": "Unregister a supplier from NO VERI*FACTU 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 status for NO VERI*FACTU",
"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 supplier from NO VERI*FACTU",
"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](https://console.invopop.com) create a new workflow and select [Empty Party workflow](https://console.invopop.com/redirect/workflows/new?template=empty-party) in the template selector, then add the following steps:
1. **Set state** — select "Processing".
2. **Unsubscribe from summary event cron** — uses the [Cron app](/apps/cron) to remove the periodic summary event subscription for this supplier.
3. **Unregister supplier** — clears the NO VERI\*FACTU registration state.
4. **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.
5. **Process Event** — creates a job to process the event. Set the **Workflow** field to the **NO VERI\*FACTU event processing** workflow.
6. **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](/guides/white-label)) or under your own name, the registration process is the same.
Use the [Create an entry](/api-ref/silo/entries/create-an-entry-put) endpoint to upload a new supplier [party](https://docs.gobl.org/draft-0/org/party). Required fields are company `name` and `tax_id`.
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](https://docs.invopop.com/guides/es-verifactu-supplier#create-a-supplier-entry) with the tax authority before invoices can be issued on their behalf.
```json Spain supplier example theme={"system"}
{
"$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"
}
]
}
```
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](https://docs.invopop.com/guides/es-verifactu-supplier#create-a-supplier-entry) with the tax authority before invoices can be issued on their behalf.
```json Spain autónomo supplier example theme={"system"}
{
"$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.
* **Via API** — Send the supplier to the registration workflow using the [Create a job](/api-ref/transform/jobs/create-a-job-post) endpoint using the `ID`s 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](/api-ref/transform/jobs/create-a-job-post) 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](/apps/cron) 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.
***
| | |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Compliance | [Invoicing compliance in Spain](/compliance/spain)
[Compliance timeline](/timelines/spain) |
| Apps | [Spain](/apps/spain)
[VERI\*FACTU Spain](/apps/verifactu-spain)
[TicketBAI Spain](/apps/ticketbai-spain) |
| Guides | [Facturae Guide](/guides/es-facturae)
[VERI\*FACTU Invoicing Guide](/guides/es-verifactu)
[VERI\*FACTU Supplier Onboarding](/guides/es-verifactu-supplier)
[SII Invoicing Guide](/guides/es-sii)
[SII Supplier Onboarding](/guides/es-sii-supplier)
[TicketBAI Guide](/guides/es-ticketbai) |
| FAQ | [Spain FAQ](/faq/spain) |
| GOBL | [Spain Tax Regime](https://docs.gobl.org/regimes/es)
[VERI\*FACTU Addon](https://docs.gobl.org/addons/es-verifactu-v1)
[Facturae Addon](https://docs.gobl.org/addons/es-facturae-v3)
[SII Addon](https://docs.gobl.org/addons/es-sii-v1) |
| GitHub | [gobl.facturae](https://github.com/invopop/gobl.facturae)
[gobl.verifactu](https://github.com/invopop/gobl.verifactu)
[gobl.ticketbai](https://github.com/invopop/gobl.ticketbai) |
Find answers to frequently asked questions about invoicing in Spain →
Ask and answer questions about invoicing in Spain →