Using Verifactu with Mangobeds

If you issue invoices in Spain, VeriFactu is coming for you sooner or later. Mangobeds already supports it, so you can start using it now and be fully ready when it becomes mandatory.

This guide walks you through what Veri*Factu is, how it works inside Mangobeds, and how to handle invoices, rectificativas, and anulaciones.


1. Veri*Factu in a nutshell

Veri*Factu is the system where your invoicing software sends invoice data in real time to the Spanish tax agency (AEAT).

If you don’t know about it, you can find all the information including dates about it here


2. Before we talk cancellations: when to rectify vs when to cancel

Important mindset:

  • If an invoice has an error (wrong guest, wrong VAT, wrong amount, etc.) → you must issue a rectification invoice (rectificativa).
  • Cancellation via Veri*Factu “cancel” endpoint is only for invoices that should never have existed (issued by mistake, duplicate, wrong flow, etc.).

AEAT is quite strict here, so please follow these rules to avoid issues with your Tax Reports:

  • Rectifications are for fixing invoices (changing taxable data, recipient, amounts, etc.).
  • Cancellations are for deleting invoices that were emitted by accident.

Mangobeds follows this logic in the product and in what we allow you to do.

Remember. You can edit an invoice as much as you want before emitting it


3. How to activate Veri*Factu in Mangobeds

Step 1 – Enable Veri*Factu in your invoicing app settings

  1. Go to Apps → Invoicing.
  2. Find the Veri*Factu / AEAT section in the settings.
  3. Activate “Use Veri*Factu for this property”.
  4. Make sure you’ve set:
    • Property Tax ID (NIF)
    • Legal name and address that match AEAT records

If the NIF doesn’t match AEAT, invoices will be rejected.

Important. At the moment, to avoid issues with the AEAT, once Verifactu is enabled, there is no way to disable it.


Step 2 – Sign the representation model

To send invoices to AEAT through Verifacti, AEAT wants you to authorise us as your technical representative.

  1. Once Veri*Factu is activated, you’ll see an option to download the representation model in the invoicing settings.
  2. Download the PDF, sign it, and follow the instructions on the doc:
  3. Upload the signed document back into Mangobeds (same section).
  4. When we confirm everything, your connection is ready.

Until this step is completed correctly, AEAT won’t accept your invoices.


4. What changes once Veri*Factu is active

When Veri*Factu is enabled and correctly configured:

  • Invoices generated for that property can be emitted to the AEAT which means:
    • Are sent to AEAT in real time.
    • They get a QR / URL from AEAT once they’re validated.
  • The system stops showing any “proforma / not valid for tax purposes” warnings for those invoices.
  • The invoice type is now “real” tax invoice in Spain, subject to the Verifactu rules.

Because AEAT receives a signed record each time, invoices become harder to modify. Many operations that used to be an “edit” are now done via rectification invoice.

Remember, you can edit an invoice as much as you want before emitting it. Once emited it will not be editable.


5. Working with invoices under Veri*Factu

5.1. Emitting invoices

When you generate an invoice:

  1. Mangobeds calculates the amounts (rates, discounts, taxes) as usual.
  2. A correlative invoice number is assigned using:
    • The number pattern and series you configured in the Invoicing App settings, or
    • A manual edit if you override it.
  3. When you click Emit to AEAT / Send via Veri*Factu:
    • We build the Veri*Factu register.
    • We send it to AEAT.
    • AEAT returns:
      • Initial status → usually “Pending”.
      • Then, given how Verifactu works, within a short time (up to a few minutes), it will turn into “Correct” or an error.

Remember. You can edit an invoice as much as you want before emitting it

Timing and QR

  • The invoice can be generated in Mangobeds.
  • The QR and validation URL from AEAT only become valid once AEAT has processed and accepted the record.
  • In the verifactu view and invoice you’ll see:
    • Status of the Veri*Factu register (Pending / Correct / etc.).
    • The QR and link once available.

If there’s an error, you’ll see it in the invoice’s Veri*Factu section.


5.2. Rectification invoices (rectificativas)

Whenever you need to correct an invoice that has already been sent (or should have been sent) to AEAT, you must emit a rectification invoice, not edit the original.

Typical cases:

  • Wrong recipient details (NIF, name, country).
  • Wrong taxable base or VAT percentage.
  • Wrong amounts (overcharges, undercharges).
  • Need to change the description in a way that has fiscal impact.

How rectificativas work in Mangobeds

In Mangobeds, you don’t start from the original invoice.
You create a new invoice with the correct data, and only when emitting it you tell the system which invoice it rectifies.

Flow:

  1. Create the new invoice
    • From the booking or from the Invoices section, create a new invoice as usual.
    • Fill in all the correct data: guest, lines, VAT, totals, etc.
    • Save it. At this point it’s not sent to AEAT yet.
  2. Emit it as a rectification
    • Open this new invoice.
    • Click “Emit to AEAT / Send via Veri*Factu”.
    • In the Veri*Factu dialog, choose “Rectification invoice (rectificativa)”.
    • Select the original invoice Number that this new one is rectifying.
  3. What Mangobeds does in the background
    • Sends this new invoice to AEAT as a rectificative type (R1, R2, etc., depending on the case).
    • Links it internally to the selected original invoice.
    • Includes, in the AEAT register:
      • Original invoice number
      • Original invoice date
    • Stores the encadenamiento (chain) returned by AEAT so both invoices are tied together.

The original invoice never changes. You’ll see:

  • The original invoice with its status and a note that it has been rectified.
  • The rectification invoice with its own number, QR, and reference to the original.

If AEAT marked the original invoice as “Accepted with errors”, the fix is still a rectification, not a cancellation.


5.3. Cancellations (anulaciones)

Use cancellation only when the invoice should never have existed.

Typical valid cancellation scenarios:

  • Invoice emitted to the wrong booking / wrong customer.
  • Duplicate invoice caused by a bug or user error.

If you have doubts about your case, please contact us before.

How cancellation works conceptually:

  • AEAT marks it as annulled.
  • You cannot reuse the same series + number.
  • If you need a new, correct invoice, you must emit:
    • A new high (new invoice) with a different number.

In Mangobeds we will:

  • Allow cancellation actions only when:
    • The invoice is not already rectified, and
    • It matches the AEAT conditions for cancellation.
  • Prevent cancellation for:
    • Invoices already involved in rectifications (as base or as rectifying).
    • Rectification invoices themselves (these should not be cancelled; they should be replaced by new rectifications if needed).

We also follow AEAT’s rule:

“Un registro de alta enviado previamente y que no procede se dará de baja mediante un registro de facturación de anulación identificando el número de la factura original. […] La anulación no debe usarse para cancelar facturas emitidas con errores, sino para facturas emitidas por error.”


6. Pricing and alternatives

Implementing Veri*Factu isn’t just “switching on a switch”. It’s a full legal and technical integration:

  • Real-time communication with AEAT via Verifacti.
  • Multiple invoice types (F1, rectificativas R1, etc.).
  • Hash chains, encadenamiento, and status handling.
  • Model of representation, NIF validations, and error management.

Because of this, Veri*Factu support will have an extra cost on top of your standard Mangobeds plan.

  • If you don’t want to pay for Veri*Factu, no problem:
    • You can still use standard invoicing and booking exports and work manually with your accountant or another tool.
  • If you want fully compliant, real-time Spanish electronic invoicing through AEAT, you’ll need to:
    • Activate Veri*Factu in Mangobeds.
    • Accept the additional monthly fee (we’ll detail pricing clearly in the app).

7. Summary and more

  • Mangobeds integrates with Veri*Factu so your invoices can be reported to AEAT in real time.
  • You activate Veri*Factu in Invoicing settings, sign and upload the representation model, and then invoices start going to AEAT.
  • Once active:
    • Invoices are real tax invoices, not proformas.
    • You fix errors via rectification invoices, not “edit”.
    • Cancellations are reserved for invoices that never should have existed, not for normal corrections.
  • The Veri*Factu module will come with an additional fee, reflecting the legal + technical complexity. If you don’t want it, you can still work with exports and external accounting.
  • Our Declaracion Responsable can be found here


You may also like

How Booking Prices Are Calculated in Mangobeds

How Booking Prices Are Calculated in Mangobeds

Understanding how Mangobeds calculates prices helps you predict totals accurately—especially when seasonal rates and long-stay discounts overlap. Here’s a clear breakdown of how it all works behind the scenes. 1. How the system calculates the nightly price When you...

Give Your Guests Superpowers with The Mangobeds Guest Portal

Give Your Guests Superpowers with The Mangobeds Guest Portal

Make life easy for your guests and your team. The Guest Portal puts everything in one place, so guests help themselves instead of pinging you for basics. What guests can do See booking details: dates, unit, totals, house rules, and add-ons. Manage payments: view...