01
Choose mode before brand
A SIF may be VERI*FACTU-only or dual. It cannot offer only non-verifiable operation: every SIF must be capable of VERI*FACTU.
For many small autónomos, sending records is operationally simpler, but connectivity, locations, users and gestor access matter.
- Who invoices and on which devices.
- Whether offline work is needed.
- Who handles AEAT rejections.
- What the gestor must access.
02
Request the declaration of responsibility
The producer must declare compliance for the system and specific version. It should be visible in or supplied with the product, not remain a sales claim.
Match product, version, producer, modes and date. Users remain responsible for running obsolete, unsupported software.
- Download before paying.
- Match the covered version.
- Retain updated declarations.
- Archive with contract and terms.
03
Do not migrate blindly
Move business data, clients, items, VAT, withholding, series, payment methods and required drafts. Preserve issued legacy invoices as a separate archive instead of recreating them.
Clean duplicates, validate tax IDs and document the last old and first new invoice. A new series can make the boundary clearer.
- Export invoices and ledgers.
- Save reusable client data.
- Record last numbering.
- Resolve drafts and recurring invoices.
- Check currencies, reverse charge and exemptions.
04
Test errors, not a perfect invoice
A clean demo proves little. Test wrong tax ID, VAT rate, refund, later discount, duplicate, lost connection and AEAT rejection.
Demand to see alta, chaining, status, corrective invoice, cancellation, audit history and export.
- Spanish B2B.
- EU reverse charge.
- Foreign currency.
- Partial correction.
- Duplicate cancellation.
- Offline queue and retry.
05
Rehearse before the deadline
Before mandatory dates, a VERI*FACTU test can be stopped in favour of another SIF. Once effective sending starts in the mandatory period, that mode must remain at least until year end.
Rehearse early and never mix live and test series without a documented plan.
- T−60: configure data and tax.
- T−30: test with gestor.
- T−7: repeat export and backup.
- T−1: close drafts and record numbers.
- T: issue a control invoice.
- T+7: review queues and errors.
06
Plan your exit
Ask what you receive on closure: PDFs, clients, alta and cancellation records, events and AEAT responses.
Check retention, cost, formats and gestor handoff. Screenshots are not a structured archive.
- Export after cancellation.
- Machine-readable records.
- AEAT acknowledgements.
- Documented retention and deletion.
- Transfer to another provider.
07
Decision protocol
Compare two finalists with identical scenarios. Prefer the product that handles errors correctly and proves history later.
- Scope confirmed.
- Declaration obtained.
- Mode understood.
- Six tests passed.
- Migration dated.
- Export verified.