01
1. Scope and deadline
I confirmed whether RRSIF applies and checked relevant exclusions.
I recorded my actual deadline rather than the deadline for companies.
I chose VERI*FACTU or a system without immediate reporting.
02
2. Provider and declaration
I have the responsible declaration for the exact version I will use.
It identifies the producer, product, version and operating mode.
Support, incident and update ownership is clear.
03
3. Data and archive
I can export customers, products, taxes, series and invoices.
The historic archive and its retention location are defined.
The last old and first new invoice numbers will be documented.
04
4. Invoice lifecycle
Draft, issue, QR and alta record have been tested.
Wrong ID, corrective invoice, cancellation and refund have been tested.
The original remains preserved and cannot be silently overwritten.
05
5. AEAT and connectivity
I understand sent, accepted, accepted-with-errors and rejected states.
I know what happens offline and how retries work.
An outage does not automatically create another invoice.
06
6. People and process
Cutover date, owner and support channel are assigned.
Invoice users distinguish editing a draft from correcting an issued invoice.
The business and gestor share rules for series, close and corrections.
07
7. Final evidence
Test results and the responsible declaration are retained.
I can obtain a full export without vendor lock-in.
A review is scheduled seven days after cutover.
