Compliance: RVTC and Verifactu

RVTC: reporting every service to the Registry

What it requires

Royal Decree 785/2021 requires holders of VTC authorisations to report the data of every service to the Ministry of Transport's VTC Services Communications Registry before it starts. Changes and cancellations are reported too.

What TransfersManager does

• Reports each service to the Registry once a vehicle is assigned, and the start of the trip when the driver begins it.
• Sends on your behalf the destination or vehicle changes and the cancellations the Registry accepts.
• Stores every communication with its identifier, so you have the full trail if you are asked for it.
• Only reports bookings of fleets with a VTC authorisation that have switched the option on in their dashboard.

Where it stands

We have the registration in the Ministry's integration environment and the system is built against its integration manual (version 2.4, October 2024). To go to production, the Ministry requires at least one real VTC holder to authorise us as an intermediary platform. Until that happens, communications are simulated in production and do not reach the real Registry. If you are obliged today, keep reporting the way you do now: we do not promise the real connection until it is live.

What you have to do

1. 1Sign in to the Ministry of Transport's electronic office (the VTC Registry application) with Cl@ve or a digital certificate.
2. 2Open "Autorizar comunicaciones" (authorise communications) and look up Codelabs Studio S.L. by its tax ID B88708797.
3. 3Choose the relationship "Intermediario o plataforma" and assign your authorisations, or tick "Gestionar todas mis autorizaciones" so new ones are covered without repeating the step.
4. 4In your TransfersManager dashboard, under company settings, set that you are a VTC holder, fill in your authorisation number and confirm that you gave that authorisation at the electronic office.
5. 5Switch on "Authorise the platform to report for me". From then on every booking with an assigned vehicle is reported automatically.

A plate you have not assigned at the electronic office will be rejected by the Registry. When you add new vehicles, assign them there too.

Verifactu: invoices that cannot be tampered with

What it requires

The Verifactu system requires invoicing software to prevent invoices from being altered and to record each one with a chained hash. It is mandatory for companies from 1 January 2027 and for self-employed people from 1 July 2027 (Royal Decree-law 15/2025).

What is already integrated

• A legal invoice series with correlative numbering, with no gaps or duplicates, per issuer and year.
• Immutable invoices: once issued, they cannot be edited or deleted. Mistakes are fixed with a rectifying invoice; an invoice issued by mistake is voided and its number is never reused.
• A record for every invoice issued or voided, with a hash chained to the previous one, following the AEAT specification.
• Tax QR code, printed on the invoice only when sending to the AEAT is active (a QR the customer could not verify would be misleading).

What is not active yet

Sending the records to the AEAT is built but switched off: to date we have not sent a single invoice, not even to the AEAT test environment. Our plan is to test it there and switch it on before the obligation takes effect, but that is a plan, not a fact. To send on your behalf we will also need your signed representation.

What you have to do

1. 1Issue your invoices from TransfersManager instead of by hand: that way they land in the legal series with their record.
2. 2Check in your dashboard that your company's tax details (legal name and tax ID) are correct: they are what appears on every invoice.
3. 3When sending is available, you will sign the authorisation for TransfersManager to send your records to the AEAT on your behalf and switch it on in your dashboard. We will let you know.
4. 4If you already invoice with another program, that program has to meet Verifactu on its own. Ask your accountant which one suits you.