3 min read
Fakturia Team

How to Manage the Event Log in a VeriFactu System

Discover what the VeriFactu event log is, why it's crucial for complying with the AEAT, and how to manage it correctly in your invoicing software.

With the implementation of VeriFactu invoicing systems drawing closer—let's remember the deadline is July 1, 2027, for freelancers and micro-SMEs—it's essential to understand its key components. One of the most important, though it often operates in the background, is the event log.

This log is the heart of the traceability and integrity required by the new anti-fraud regulations. But what is it exactly, and how should you manage it?

What is the VeriFactu Event Log?

The event log is a computer file that every VeriFactu system must generate automatically. It acts as a black box for your invoicing, chronologically recording every relevant action that occurs in the software. Its main feature is that it is unalterable and non-manipulable.

Every time you create, modify, or void an invoice, the system notes this event in the log. Other high and low-level events, such as user logins or configuration changes, are also recorded. The goal is to provide the Spanish Tax Agency (AEAT) with a complete audit trail that ensures no invoices have been improperly deleted or altered.

The most common events recorded are:

* Invoice creation: Creation of a new full or simplified invoice.

* Invoice voiding: Cancellation of an issued invoice (which will be marked as voided, not deleted).

* Credit/Debit note: Issuance of an invoice that corrects a previous one.

* System events: System start-up and shutdown, configuration changes, etc.

Why is this log so important?

The importance of the event log lies in it being the primary proof that your invoicing complies with the principles of integrity, conservation, accessibility, legibility, traceability, and inalterability of records required by the regulation. In essence, it proves that there is no dual-use software or parallel accounting. To better understand the general framework of these obligations, you can consult our complete guide on What is VeriFactu? Guide for Freelancers in Spain.

In the event of an inspection, the AEAT can request this log to verify the consistency and truthfulness of all your invoicing. An incomplete log or one with signs of tampering could lead to significant penalties.

How is the event log managed?

Here's the good news: as a freelancer or SME, your direct management of the event log is minimal. The main responsibility falls on the invoicing software you use. Your only obligation is to ensure that your program meets VeriFactu requirements.

Management can be summarized in these points:

1. Automatic generation: The software creates and updates the log without you having to do anything. Every time you issue an invoice, the system adds a new line to the log with its digital fingerprint (hash) and that of the previous record, securely chaining them together.

2. Consultation: Although you cannot edit it, you must be able to consult the log. Your software should offer an option to view or export this file, usually in XML format, in case you need to review it or submit it to the AEAT.

3. Conservation: The software must ensure the log is kept for the legally required period, which coincides with the tax prescription period (currently, 4 years).

Your role is to choose a reliable, certified tool. The quality of your program will determine your peace of mind. Therefore, it's key to research The Best VeriFactu Software for Freelancers: Comparison that suits your needs.

In short, the event log is a pillar of security and automatic compliance in the VeriFactu era. Understanding its function will give you the confidence that, by using the right software, your business is perfectly aligned with the new tax requirements.

Share X LinkedIn
Back to newsMore on VeriFactu