Are you within scope?
Check activity, invoicing obligation, territorial regime, and whether you are registered in SII. Not every situation is treated the same.
VERIFACTU FOR FREELANCERSUpdated 2026 guide
VeriFactu for freelancers: what changes and how to prepare.
For many freelancers within RRSIF scope, the general adaptation date will be 1 July 2027. But before taking action you need to confirm whether your activity and invoicing system actually fall within scope.
The technical decision does not have to mean replacing all your software. It may mean updating it, connecting it, or replacing only the component that issues invoices.
VERIFACTU GUIDE
What a freelancer should check before changing software.
The first step is deciding whether anything actually needs replacing. Often the issue is adapting the workflow, not replacing the whole system.
Where is the invoice issued?
It may be an ERP, desktop app, WooCommerce, PrestaShop, POS, or data originating from Excel/CSV.
Can your software be updated?
If the vendor offers an adapted version, that may be the simplest route. Otherwise, an external integration may be assessed.
Do you need connection or replacement?
Kairoseth Fiscal is designed to connect existing systems where technically viable, not force an unnecessary migration.
How will you test before 2027?
Validate realistic test invoices, numbering, QR, errors, and recovery before the mandatory date.
What should you document?
Document which system issues, what data reaches the bridge, and who controls numbering, mapping, and fiscal configuration.
STEP BY STEP
A practical route for freelancers.
Start with what you already use and minimize change.
Confirm scope
Check scope and deadline with official sources and your adviser.
Inventory your tools
Identify software, ecommerce, POS, Excel, or any system that issues invoices.
Test the integration
Validate mapping and preflight before creating fiscal side effects.
Go live with margin
Do not wait until the final day to discover numbering, QR, or data problems.
DO NOT REPLACE BY DEFAULT
The goal is to adapt what is necessary, not rebuild your business.
If your system can provide the right data, an integration layer may be enough. If it cannot, then an update, connector, or replacement of the invoicing component may be necessary.
FAQ
Frequently asked questions.
Short answers grounded in official sources.
Does VeriFactu affect freelancers?
In general, taxpayers carrying out economic activities who fall within article 3.1 of the RRSIF must adapt their invoicing systems. The exact case must be checked because exclusions and out-of-scope situations exist.
What is the general deadline for freelancers?
AEAT places taxpayers other than Corporate Income Tax taxpayers on 1 July 2027, provided they fall within the scope of the regulation.
Is a freelancer in SII covered by RRSIF?
AEAT states that taxpayers registered in SII are excluded from RRSIF for their own invoicing.
Do I need to buy a new ERP?
Not necessarily. You may adapt existing software, use an already adapted application, or connect a compatible layer when the full workflow meets the applicable requirements.
Can I keep using Excel?
Excel alone does not automatically solve all invoicing-system obligations. Kairoseth Fiscal treats Excel/CSV as data input while the fiscal core applies mapping, preflight, and the supported VeriFactu workflow.
KEEP EXPLORING
Canonical VeriFactu guides.
Each guide owns a distinct intent to avoid duplication and make the path from question to solution clear.
What is VeriFactu
Open guide →Requirements
Open guide →QR VeriFactu
Open guide →Free VeriFactu / AEAT app
Open guide →Current 2027 dates
Open guide →2028 announcement and horizon
Open guide →OFFICIAL SOURCES
Always check the current official version.
This guide summarizes official rules and documentation; it does not replace tax advice or checking the exact scope that applies to each organization.
AEAT · Who is covered
Open official source →AEAT · Scope FAQ
Open official source →AEAT · VERI*FACTU and 2027 deadlines
Open official source →TRUST & CONTROL
Authority stays explicit as the platform grows.
Kairoseth separates identity, organization scope, product roles and product capabilities. A login route, browser state or AI response never becomes an authorization boundary by itself.
KAIROSETH PLATFORMCONTROL PLANE
- Identity
- Shared account
- Verified
- Organization
- Tenant scope
- Required
- Product
- RBAC assignment
- Explicit
- Sensitive actions
- Policy gate
- Controlled
Organization scope
Customer resources and access are resolved inside an active organization context rather than treated as global account state.
Product-scoped roles
Owner, Admin and Member authority is assigned per product. Organization membership alone does not automatically grant every product.
Server authority
Sensitive access, policy and capability decisions remain authoritative on the server instead of trusting client UI state or model output.
Controlled execution
Capabilities that can act are introduced behind explicit grants, staged gates and audit rather than implied autonomy.
Public trust evidence
Review the customer-facing policies that define privacy, security reporting, acceptable use and the current legal operating framework.
SOFTWARE VERIFACTU
Are you a freelancer who does not want to replace software unnecessarily?
Kairoseth Fiscal starts by reviewing how you invoice today: Excel, WooCommerce, PrestaShop, ERP, POS, or custom software.