Fiscal subject related
Content
As a reminder, the ability to send invoice records to the AEAT is part of new strict IT, security, and tax requirements for developers and users of invoicing systems starting July 1, 2024. This includes requirements for e-invoicing software developers and solution providers to certify that their systems comply with these new standards and requirements. Invoices generated must include a QR code, and the narrative "Invoice verifiable at the electronic headquarters of the AEAT" or "VERI*FACTU" where the system sends the invoicing records directly to the AEAT.
But, it is important to state that the legislation is still in draft form, subject to change, and still needs to be formally approved (we are awaiting the opinion of the Council of State).
A short overview of the process for sending invoice records
- The submission of billing records will be made electronically through the exchange of XML messages through SOAP v1.1 web services.
- There will be two clearly defined categories of XML messages: one for the sending of "registration records" and another for the sending of "cancellation records."
- The maximum number of invoice records per individual submission is 1,000.
- Once the XML message has been sent, the AEAT will automatically carry out a validation process, validating both the XML format and applying business rules. If the message passes the XML format level validations, the business rule validation will be carried out, returning a response message, confirming whether the records have either been accepted or rejected by the AEAT. Where the XML fails the format validation, a SoapFault message will be returned containing the specific error.
- The XML response message sent back by the AEAT will contain a list of accepted and rejected invoice registration records, together with the rejection reason. In case of rejection, businesses must make the necessary corrections and re-submit the relevant records, etc.
Also, some technical details in relation to data standards and other requirements from the technical perspective have been published.
Other news from Spain
Invoicing log designs: Draft Document Update in Spain
The Spanish Tax Administration (AEAT) has recently updated an Excel document that describes sending data to the VERIFACTU system (v0.11.4). Two fields that were optional until now are now alternatives. Let's delve deeper into this subject. Read more
Fiscalization in Spain: Can SIF be Verifactu, non-verifactu, or both?
As we have introduced before, the fiscalization in Spain can be VeriFactu, where receipts and their records are sent in real-time, or non-VeriFactu. But the question arises: what needs to be supported? The confirmation came from AEAT, which states that the SIF can be only Verifactu (exclusively allowing use as VERI*FACTU) or "dual" (allowing to be used, at the taxpayer's choice, as VERI*FACTU AND... Read more
Spain submits a draft regulatory framework for e-invoicing rules to the EU Commission.
Spain submits a draft regulatory framework for Crea y Crece law to the EU Commission. Following the publication of the draft Royal Decree regarding regulatory developments for “Crea y Crece” on June 15, 2023, the Finance Ministry and the Ministry of Economy and Digital Transformation in Spain have submitted a new edited version of the previous draft Royal Decree with some changes in it. This mean... Read more
Is it allowed for taxpayers to transfer receipts (invoices) for accounting purposes to an external company, in accordance with fiscalization requirements in Spain?
The traceability of receipts or invoices is one of the main requirements of the new fiscalization system in Spain. It is materialized through the chaining that the SIF makes of the billing records. What does this actually mean? it is limited to the SIF. Once the records are duly chained and generated (and signed or sent to the AEAT), the regulation and order do not enter into what is subsequently... Read more
VERIFACTU chaining transactions, initial record
Billing record traceability refers to the process where each billing record in a series includes a reference to the previous one chronologically. This sequence of billing records ensures their traceability, particularly for those generated by the computer system. Read more in order to find out about the criteria that must be met. Read more
Does a QR code have to be present if there are no real-time receipts (invoices, no-Verifactu) in the new fiscalization system in Spain?
Yes, the QR code is a mandatory requirement for both Verifactu and non-Verifactu systems that must be presented on receipts (invoices). If the QR is scanned, the AEAT will know if it has been generated by a Verifactu (which will have sent the corresponding billing record) or a No Verifactu (which will not have sent it and must keep it locally), responding accordingly. If we consider the purpose of... Read more
Draft Royal decree about technical requirements of the new billing systems
The draft royal decree about the technical requirements of the new billing systems introduces rules for some of the requirements of the Spanish fiscalization systems. But the official Ministerial Order and some new rules are still awaiting publication. However, from the named draft, we can see more rules that must be supported when new fiscalization is applied. One of the rules is that the compute... Read more