Review the electronic certificate requirements for your Veri*factu invoices
The electronic certificate will be mandatory to issue electronic invoices when Veri*factu comes into force, so it is advisable to sort it out in advance. With a single file, you ensure that invoices are signed validly, that communication with the AEAT is secure, and that you do not face technical blocks just when you need to activate electronic invoicing. From here, you will decide what type of certificate you need, how to obtain it, and how to connect it with VRMS.
Identify the type of electronic certificate you need
There are different types of certificate depending on who issues the invoices:
Natural person certificate: for freelancers and professionals, used to sign on your own behalf.
Representative certificate: for companies (e.g., S.L. or S.A.), links the signer’s NIF with the entity’s CIF.
Electronic seal certificate: to automate invoicing without direct human intervention in each issuance.
Choosing the right type ensures that the invoices correctly represent the person or entity that appears as the issuer.
Confirm the prerequisites to request the certificate
Before starting the electronic certificate application, make sure you have the following on hand:
Valid DNI or NIE.
Active email address.
Computer with Internet connection and an up-to-date browser.
FNMT-RCM installer (FNMT-RCM Configurator) ready to use.
Ability to generate or download the certificate in .p12 or .pfx format, issued by the FNMT.
Verifying these requirements in advance prevents errors midway through the process and saves you from repeating steps.
Apply for the electronic certificate at the FNMT-RCM
The FNMT-RCM allows you to obtain the certificate via video identification, in person, or using the DNIe. Choose the option that best fits your situation and resources.
Apply for the certificate with video identification
To complete the entire online process with video validation:
Install the FNMT-RCM Configurator on your computer.
Access the FNMT-RCM online form and fill in your details.
Pay the fee securely by following the instructions on the website.
Record the video showing your DNI or NIE and your face as requested.
Wait to receive the application code in your email.
From the same computer and the same browser, download the certificate and create a secure password to protect it.
Apply for the certificate in person
If you prefer to verify your identity at an authorized office:
Complete the certificate application on the FNMT-RCM website and obtain the application code.
Make an appointment at an authorized registration office and attend with your valid DNI or NIE.
Once your identity has been validated, download the certificate from the same computer and browser you used for the initial application.
Apply for the certificate using DNIe
If you already work with an electronic DNI and have the necessary hardware:
Connect a compatible DNIe reader to the computer and install the corresponding drivers.
On the FNMT-RCM website, choose the DNIe application option.
Enter your DNIe PIN when the system requests it.
Download the certificate directly into your browser and verify that it is correctly installed.
Common mistakes
It is easy to try to download the certificate from a different browser or from a different computer than the one you used for the application. If you do so, the download may fail or the certificate may not install correctly. Always use the same device and the same browser throughout the entire process.
Upload the electronic certificate to VRMS to activate Veri*factu
Once you have the certificate in .p12 or .pfx format, the next step is to add it to VRMS so the system can sign invoices and communicate them to the AEAT via Veri*factu.
To upload the certificate:
Log in to your VRMS account with your usual credentials.
Go to
VRMS → Accounting → Export data → Veri*factu electronic invoicing → Configurationand select "Add"In the side bar menu, upload the certificate file and select the legal entities associated to it in .p12 o .pfx format.
Add a name for the certificate if you wish. If you don't, the file name will be displayed.
Click on "Save" to complete the process.
Add more certificates as needed
If you work with various legal entities or you need to use different certificates, select "Add" and repeat the process as many times as required.
When the certificate is correctly uploaded and validated, the Veri*factu module will be ready to use it when sending your accounting documents to the AEAT.
Replace the certificate assigned to a legal entity
If you try to assign a certificate to an entity that already has one linked, the system will display a warning. You can continue and replace the previous certificate if needed.
Frequently Asked Questions
Why do I need an electronic certificate to use Veri*factu in invoicing?
Why do I need an electronic certificate to use Veri*factu in invoicing?
Because the certificate allows the issuer of the invoices to be securely identified, to electronically sign the documents, and to guarantee the legal validity required by the AEAT for electronic invoicing.
Which certificate suits me if I invoice through a company and not as a freelancer?
Which certificate suits me if I invoice through a company and not as a freelancer?
In that case, you need a representative certificate, which links your NIF as the signer with the entity’s CIF and allows the company to appear as the issuer of the invoices.
What certificate formats does VRMS accept to connect with Veri*factu?
What certificate formats does VRMS accept to connect with Veri*factu?
VRMS accepts certificates issued by the FNMT in .p12 or .pfx format. It is essential that the file you download is in one of these formats to upload it correctly.
What should I check if I have problems downloading the certificate from the FNMT-RCM website?
What should I check if I have problems downloading the certificate from the FNMT-RCM website?
Make sure you are using the same computer and the same browser you used for the initial application, that the FNMT-RCM Configurator is correctly installed, and that the browser is not blocking the download or installation of the certificate.