WOOCOMMERCEFiscal Connect
I use WooCommerce
Native connector, HPOS support, and order/refund workflows on the same fiscal core.
View this solution →VERIFACTU SOFTWAREv0.1.0 released
VeriFactu without replacing your software.
We connect the invoicing system your business already uses to the required fiscal layer, from WooCommerce or PrestaShop to ERP, Excel, custom software, or legacy systems.
You keep your tools. Software VeriFactu centralizes preflight, idempotency, status, reconciliation, and presentation on one technical core.
START WITH WHAT YOU ALREADY USE
Where do you invoice today?
You do not need to understand our architecture. Choose your current system and we will take you to the most appropriate adaptation route.
PRESTASHOPFiscal Connect
I use PrestaShop
Native module validated across multiple versions while keeping the store as the source system.
View this solution →ERP / CRMFiscal Connect / Custom
I invoice from an ERP or CRM
We integrate around the system's actual capabilities without forcing an ERP rebuild.
View this solution →CUSTOM SOFTWARE / SAASFiscal API
I have custom software
Your application keeps its UX while VeriFactu Software centralizes fiscal workflows, status, and reconciliation.
View this solution →EXCEL / CSVFiscal Web
I work with Excel or CSV
Upload, assisted mapping, and preflight so you can start without a large integration project.
View this solution →API / BACKENDFiscal API
My system already has an API
REST, starter kits, and webhooks for integrators, SaaS products, and technical teams.
View this solution →LEGACY SOFTWARE / POSFiscal Custom
I use local or legacy software
We assess read-only databases, files, SFTP, watch folders, or a local agent depending on the system.
View this solution →I'M NOT SUREAssisted assessment
I do not know which integration I need
Tell us how you invoice today and we will identify the simplest path before changing your system.
Help me identify it →ONE PRODUCT · FOUR IMPLEMENTATION MODES
The implementation mode changes. The fiscal core does not.
We do not sell seven different products. We choose the mode according to the system, complexity, and support each organization needs.
Fiscal Web
For straightforward businesses that need a guided path without a complex integration project.
Fiscal Connect
For existing systems connected through maintained plugins, modules, and adapters on the same fiscal engine.
Fiscal API
For technical teams that want VeriFactu without embedding AEAT logic inside their own backend.
Fiscal Custom
For integrations that need assessment, managed adaptation, and a tailored continuity plan.
Pricing is not public yet: we are first finalizing unit economics, support, and setup costs by modality. Until then, we use an assisted assessment and proposal flow.
REAL TECHNICAL EVIDENCE
We are not starting from a sales promise: we are starting from a tested release.
Public evidence remains sanitized and contains no certificates, tax IDs, raw XML/SOAP, or infrastructure secrets.
v0.1.0 released
The technical release is tagged and the WooCommerce, PrestaShop, and Local Agent artifacts were reproduced and checksum-verified.
5/5 AEAT TEST pilot
Five controlled operations completed the TEST delivery flow: accepted, one attempt each, with no duplicates or pending reconciliation.
Ecommerce tested
WooCommerce and PrestaShop passed real installation and smoke tests across the release compatibility matrix.
Legacy connectivity tested
The portable agent passed smoke tests on Linux, Windows, and macOS plus read-only database and SFTP connectivity checks.
HOW WE START
First we understand your system. Then we choose the technology.
The customer buys a solution to the adaptation problem; APIs, mapping, plugins, or local agents are implementation decisions that come later.
Identify your current system
Choose where you invoice today. You do not need to know whether the implementation uses an API, plugin, mapping, or local agent.
Validate before issuing
Preflight and server-side configuration catch incomplete data or incompatibilities before fiscal side effects are created.
Integrate without replacing your tools
Your system keeps its role while VeriFactu Software centralizes idempotency, status, reconciliation, and presentation.
VERIFACTU / AEAT
A published release does not mean automatic AEAT production activation.
Software VeriFactu v0.1.0 has technical evidence and a controlled pilot in the AEAT TEST environment. Fiscal production activation remains separate and requires its own technical, regulatory, and authorization gates.
FAQ
Questions to answer before adapting your system.
The first step is understanding what you use today, what it can do, and how much implementation support you need.
What is Software VeriFactu?
It is the commercial layer of Puente VeriFactu inside Kairoseth. Its purpose is to adapt the system you already use to the supported fiscal workflow without turning each store, ERP, or application into its own fiscal engine.
Do I have to replace my ERP, ecommerce platform, or current software?
No. We first identify the system's capabilities and choose the simplest integration route: connector, API, Excel/CSV, or managed adaptation.
Are WooCommerce and PrestaShop connectors already available?
Yes. Release v0.1.0 publishes WooCommerce and PrestaShop artifacts and both channels have installation and smoke evidence in the validated technical matrix.
What if my software is old and has no API?
That does not automatically mean you must migrate. We assess exports, read-only database access, files, SFTP, or a local agent before recommending the route.
Is Software VeriFactu officially certified by the AEAT?
We do not present the release as an official AEAT certification. We have technical evidence and an AEAT TEST pilot, while each organization's fiscal responsibilities and production gates remain separate.
Does v0.1.0 automatically enable AEAT production?
No. Publishing, purchasing, or installing Software VeriFactu does not by itself enable the fiscal production environment. Production activation remains a separate technical and authorization gate.
How much does it cost?
We are finalizing unit economics and commercial packaging before publishing prices. The planned model combines setup where needed with a recurring fee based on modality, support, and complexity.
VERIFACTU RESOURCES
Useful information without mixing it into the buying decision.
Regulatory guides remain separate from the product and must be reviewed against official sources whenever requirements or timelines change.
What is VeriFactu?
Core concepts, the general workflow, and the difference between the system and software that implements it.
Read guide →VeriFactu requirements
Records, integrity, traceability, submission, and technical controls for invoicing systems.
Read guide →VeriFactu QR
What the tax QR represents and how it fits into presentation and checking workflows.
Read guide →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.
VERIFACTU SOFTWARE · START WITH YOUR SYSTEM
Tell us where you invoice today and we will identify the right adaptation path.
WooCommerce, PrestaShop, ERP, CRM, Excel, APIs, custom software, or a legacy application: you do not need to choose the technical architecture before you start.