Configuring FACTUSOL for the new invoicing software systems framework takes more than installing an update. You need to confirm the version covered by the compliance statement, decide which mode applies, review companies and series, correct tax data, test invoice creation and cancellation, verify the QR code and server responses, control user access, and rehearse contingency procedures. Final sign-off should rest on tests run against the real installation.
Checking Scope and Timeline
Following the 2025 extension, entities subject to Corporate Income Tax must adapt their invoicing software systems (SIF, from the Spanish "sistemas informáticos de facturación") before 1 January 2027; all other obliged parties, before 1 July 2027. The exact scope should be confirmed with tax advice, particularly regarding the SII, the foral regional tax regimes, and any excluded situations.
Compliance with the RRSIF (Spain's regulation on invoicing software system requirements) should not be confused with the VERI*FACTU mode, nor with B2B electronic invoicing.
Step 1. Installation Inventory
Record:
- product and edition;
- version and date;
- local, networked, or hosted installation;
- companies and financial years;
- workstations and users;
- series and warehouses;
- integrations;
- customizations;
- backups and support.
FACTUSOL's official compliance statement identifies the system and its conditions. Keep the one that matches the version in use.
Step 2. Backup and Test Environment
Before updating:
- run a full backup;
- restore it in a test environment;
- document the version and path;
- restrict access;
- avoid real submissions during testing, unless in an authorised environment;
- define the rollback procedure.
A backup that is never restored is not proof of recoverability.
Step 3. Company Data
Review:
- tax ID and legal name;
- registered address and country;
- tax regime and configuration;
- certificates and credentials;
- email and contact details;
- invoice text templates;
- branches and series.
Master-data errors multiply with every record. Fix them before issuing invoices.
Step 4. Customers, Items, and Taxes
- tax ID and identification type;
- country and address;
- business status, where relevant;
- VAT rates and exemptions;
- surcharges and withholdings;
- units and descriptions;
- rounding and discounts;
- rules by series or activity.
Test domestic, intra-EU, non-EU, and private customers according to real business operations.
Step 5. Series and Numbering
Every series should have a purpose, a branch, a document type, and an owner. Check for gaps, duplicates, year-end changeovers, and simplified invoices.
Do not create series to dodge traceability. Investigate and document any numbering gaps. Test concurrent use across multiple workstations.
Step 6. Mode and Activation
Activation should follow TeamSystem's current guidance and the approved tax decision. Before confirming:
- know whether VERI*FACTU will be used;
- understand the effect on records and submission;
- validate the certificate and connectivity;
- identify who can change the configuration;
- keep evidence of the date and the person responsible;
- check whether the mode can later be changed, and under what conditions.
Do not activate it in production out of curiosity, without understanding the consequences.
Step 7. Invoice and QR Code
Test the on-screen display, the PDF, and the printed output:
- mandatory content;
- legible QR code;
- required disclosures;
- ordinary and simplified invoices;
- multi-page documents;
- custom templates;
- copies and duplicates.
The QR code does not replace the other required data. Older templates may crop or overlap elements.
Step 8. Invoicing Scenarios
| Case | Result to validate |
|---|---|
| Ordinary | Record, number, amounts, and QR code |
| Simplified | Correct content and series |
| Corrective (rectificativa) | Reference and reason |
| Cancellation | Record and traceability, without deletion |
| Return | Coherent tax and commercial flow |
| Advance payment | Accrual and later application |
| Multiple tax rates | Taxable bases and amounts |
| Foreign currency | Conversion and rounding |
An issued invoice is not edited like a draft. Use the correction or cancellation mechanisms provided.
Step 9. Submission and Statuses
In VERI*FACTU mode, test:
- successful submission;
- rejection due to invalid data;
- retry;
- connection loss;
- pending queue;
- later reconciliation;
- response lookup.
A submission does not automatically mean acceptance. There should be a daily procedure to review errors.
Step 10. Users and Security
- individual user accounts;
- role-based privileges;
- restricted configuration access;
- export controls;
- immediate deactivation;
- backup protection;
- operating system updates;
- secure remote access;
- reviewable logs.
Do not operate day-to-day on a shared administrator account.
Integrations
If an online store, a POS system, or an external ERP generates invoices, define the master system, the identifier, the timing of issuance, and error handling. Retries must be idempotent.
Test the integration under partial outages and duplicate messages. The final result must be reconciled with FACTUSOL and, where applicable, with the AEAT (Spain's Tax Agency).
Contingency
The plan should cover:
- FACTUSOL outage;
- network loss;
- AEAT service unavailable;
- expired certificate;
- faulty update;
- corrupted backup;
- mass configuration error.
For each scenario, assign an owner, a temporary way of working, the data to record, recovery, and reconciliation. Do not improvise with uncontrolled parallel spreadsheets.
Acceptance Test
| Control | Evidence |
|---|---|
| Version | Screenshot and compliance statement |
| Company | Validated record |
| Series | Report and sequence |
| Invoices | PDF and records |
| Correction | Original and reference |
| Submission | Response and log |
| Outage | Contingency report |
| Backup | Successful restore |
| Users | Permissions matrix |
Sign-off should be given by the functional owner and, for tax matters, backed by tax validation.
Common Mistakes
- Updating without a restorable backup.
- Not checking the compliance statement.
- Activating without a mode decision.
- Leaving tax IDs and types incorrect.
- Testing only the simple invoice case.
- Editing already-issued invoices.
- Ignoring custom templates.
- Not reviewing rejections.
- Sharing the administrator account.
- Having no contingency plan.
Final Checklist
- Scope and dates confirmed.
- Version and compliance statement checked.
- Backup restored in testing.
- Companies, customers, and taxes cleaned up.
- Series and numbering reviewed.
- Mode approved.
- QR code and templates tested.
- Corrections and cancellations verified.
- Submission, rejection, and retry rehearsed.
- Users, integrations, and contingency approved.
Frequently Asked Questions
Is FACTUSOL compliant?
TeamSystem states that FACTUSOL is ready and provides its compliance statement. You should still verify the specific version and configuration of each installation.
Is updating enough?
No. You also need to configure the system, clean up data, test processes, and train users.
Can I edit an issued invoice?
Errors must be resolved through the applicable correction or cancellation mechanisms, preserving traceability.
Should I activate VERI*FACTU now?
It depends on your plan and scope. Activation should be controlled and preceded by testing.
At Summum Sistemas we review your FACTUSOL installation, set up tests for VERI*FACTU and electronic invoicing mode, and document sign-off, backed by TeamSystem as the manufacturer.