Veri*factu
Veri*factu is not just a submission to the Spanish tax authority. It also affects invoicing software requirements, record integrity, and traceability.
What it means in practice
- The Spanish tax authority uses Veri*factu to refer to the mode where invoicing records are sent at the same time they are produced.
- The regulation distinguishes between the invoicing system itself and the specific transmission mode.
- For a SaaS product, this affects how records are generated, chained, stored, and potentially transmitted.
What to review before enabling it
- Clear issuer tax ID and business data.
- Stable numbering and clear locking rules after invoice issuance.
- Traceability: events, changes, and exports that allow reconstruction of what happened.
- System ability to preserve and chain records without uncontrolled alteration.
What users expect from the UI
- A visible status: off, prepared, shadow mode, or active transmission.
- A configuration checklist before enabling the strictest mode.
- Messages that separate blocking issues, warnings, and accepted-with-observations outcomes.
- Record history and, when applicable, transmission references and verification QR.
What not to overpromise
- Do not present activation as a one-click switch if configuration is incomplete.
- Do not treat rejected records as if they were harmless informational notices.
- Do not mix marketing claims with compliance language: public documentation should stay precise and cautious.