Custom billing & VERI*FACTU specialists
Custom invoicing software that fits the way you work, with VERI*FACTU compliance built into the process.
CostaWeb brings together billing workflows, invoice records, QR generation and AEAT integration. From adapting an existing system to building a complete billing platform, we handle the technical detail and give your team a clear way to operate.
Your business
Factura
Illustration only · not a valid invoice or QR
The rules, explained clearly
Spain’s SIF rules govern how billing software creates and safeguards invoice records. VERI*FACTU is the operating mode that sends those records to AEAT as invoices are issued. AEAT overview
Our service focuses on implementing that workflow in software your business can use day to day. We confirm your business’s position with your tax adviser before defining the technical scope.
SII participants and businesses subject to the relevant Basque or Navarre foral rules need a separate applicability review. The dates here concern affected users of invoicing software. Scope and exclusions
Current adaptation timetable
1 January 2027
Affected taxpayers subject to Spanish corporation tax.
1 July 2027
Other affected taxpayers, including autónomos carrying on economic activities.
Reviewed 12 September 2026. Royal Decree 1007/2023, current text. We recheck the applicable rules when scoping your project.
What we build
Customer records, quotes, invoice series, recurring billing, payment tracking and accountant exports. We design the workflows around your services, team and approval process, with the tax treatment agreed with your adviser.
Add billing to your CRM, booking platform, job-management software or online store. We assess your existing architecture and data, then scope an integration or replacement that avoids unnecessary re-entry.
Implement the required record structure, invoice output, QR content and VERI*FACTU wording for the agreed operating mode. We check the whole issue-and-record workflow, rather than treating the QR as a cosmetic addition.
Connect the billing workflow to AEAT services with the appropriate certificate or authorised representation. Submission queues, retries and response visibility help your team identify and resolve records that need attention.
Design record chaining, access permissions and correction workflows into the system. Issued records remain traceable, with the appropriate subsequent records used to correct or cancel information.
Test the agreed scenarios, document the delivered system and establish a release process. Where CostaWeb is the system producer, we provide the required version-specific declaración responsable before release. Updates and support are scoped in your proposal.
Implementation is scoped against the applicable technical specification and producer declaration requirements.
Three ways we can help
01
Understand the changes your current billing process needs.
02
Connect an existing platform to the required billing workflow.
03
Build invoicing into the way your business operates.
Every project is quoted to its scope. We set out delivery stages, producer responsibilities, third-party costs and maintenance arrangements before work starts.
From review to working software
01
Map your legal entities, invoice types, software, integrations and adviser’s requirements.
02
Build the agreed workflows, record handling and connections, with working previews for your team.
03
Test ordinary invoices, corrections, rejected submissions, connection failures and recovery in the appropriate test environment.
04
Complete the documentation, plan the switch, train your users and agree how updates and incidents will be handled.
Questions worth asking
The invoicing-software rules apply to defined taxpayers and operations, with exclusions. VERI*FACTU is one permitted operating mode; a compliant non-VERI*FACTU mode is also provided for. We check the scope with your tax adviser, including SII participation and the relevant foral tax regime, before recommending a solution.
Read the official guidanceNo. The QR is one part of the invoice requirements. The system must also meet the applicable record-generation, integrity and traceability rules. In VERI*FACTU mode it sends invoice records to AEAT. Scanning the QR is a customer verification mechanism, not the issuer’s submission process. Structured electronic invoices carry the required URL content instead of a printed QR image.
Read the official guidanceNo. Spain’s business-to-business electronic invoicing framework, developed by Royal Decree 238/2026, is distinct from the SIF/VERI*FACTU rules. A VERI*FACTU integration does not by itself cover all electronic invoice exchange obligations. We identify any additional formats, exchange services and requirements as a separate part of the project.
Read the official guidanceAEAT does not require prior product registration or independent certification for this purpose. The producer certifies the software through a declaración responsable for the relevant version. We define the producer’s responsibility for the delivered system and any third-party components, and provide the required documentation. This is not an AEAT endorsement.
Read the official guidanceYes, where the existing software and access rights make a sound integration possible. We first review the source or available interfaces, invoice workflows and producer documentation. We then recommend a targeted adaptation, a compliant billing component, or a replacement, with a clear scope and ownership of responsibilities.
We build visible pending and error states, controlled retries and an exception workflow. AEAT guidance provides for continued invoicing and later submission during transmission incidents. The implementation must distinguish a transport problem from a rejected record and preserve the information needed to resolve it.
Read the official guidanceWe quote after reviewing your billing process, invoice volume, integrations and support needs. Your proposal separates discovery, implementation, migration, hosting, any third-party fees and ongoing maintenance. A standard product may be more suitable for straightforward invoicing; custom development is most useful when the workflow or integration requirements justify it.
No. Invoice-record submission does not remove your separate bookkeeping and tax-filing obligations. We handle the agreed software implementation and work with your accountant or gestor on the business’s tax treatment and reporting needs.
Read the official guidanceLet’s talk billing
Tell us how you invoice today and what needs to change. We’ll help you define the right project, from a focused VERI*FACTU integration to a complete custom billing platform.
Prefer email? hello@costaweb.co
Explore our wider business software services