Keep your ERP or CRM as the primary system
Kairoseth Fiscal acts as the adaptation layer. The source system keeps customers, invoices, and operations while the bridge centralizes the fiscal workflow.
VERIFACTU FOR ERP AND CRMv0.1.0 published
Connect your ERP or CRM to VeriFactu without replacing the system your company already uses.
Kairoseth Fiscal receives invoices from your existing system, applies server-side mapping and preflight, and centralizes idempotency, status, reconciliation, and presentation in the same fiscal engine.
FISCAL CONNECT
The ERP remains in charge of business operations; the bridge centralizes VeriFactu.
Integration is selected by the capabilities your system already has, not by a closed list of brands.
API or webhook according to capabilities
If the ERP exposes an API, use server-to-server integration. If it can emit HTTP events, signed webhooks decouple the flow without moving fiscal secrets into the source system.
Server-side MappingProfile
Your ERP does not need to adopt Puente field names. The profile maps source fields into the canonical contract while organization and installation identity remain server-authoritative.
Preflight before side effects
The ERP can validate structure, dates, amounts, and configuration before a fiscal record exists.
Idempotency and reconciliation
A stable key prevents duplicates and, when a remote outcome is uncertain, the bridge checks status before deciding what to do next.
Ready for additional adapters
The architecture can add system-specific connectors without duplicating AEAT rules. Database read and Local Agent routes remain roadmap items until their technical gates are completed.
HOW WE CONNECT IT
Capabilities and mapping first; activation second.
We do not activate a fiscal integration based on assumptions. We validate real samples and keep a clear boundary between ERP facts and server-side configuration.
Identify how your ERP can connect
API, webhook, or a dedicated integration depending on actual capabilities; the route is not selected by brand.
Define the MappingProfile
Map ERP fields into InvoiceIntent and keep decisions the source system must not make on the server.
Test with preflight
Validate real samples without fiscal side effects until data, numbering, and mapping are coherent.
Activate and monitor
Once opened, every operation keeps idempotency, status, reconciliation, and presentation through the same fiscal core.
WHEN THERE IS NO API
We do not promise a connector that does not exist yet.
For legacy ERP systems, the roadmap includes a Local Agent, read-only database access, watch folders, and SFTP. Those routes will only be offered after their own tests and gates; until then we assess actual system capabilities and use API/webhooks when available.
FAQ
ERP, CRM, and VeriFactu questions.
For teams that want to adapt their management software without replacing it.
Do I have to replace my ERP to use VeriFactu?
No. Kairoseth Fiscal is designed so the ERP remains the business source and connects through API, webhook, or a compatible adapter.
Does my ERP need to understand AEAT XML or services?
No. The ERP sends a neutral contract and the fiscal layer handles transformations, controls, and transport supported by Puente VeriFactu.
What if my ERP uses different field names?
A server-side MappingProfile maps your fields into InvoiceIntent so the ERP does not have to be redesigned around bridge internals.
Can a CRM that creates invoices be integrated?
Yes, when it contains the necessary commercial facts and can expose them through a supported route. Integration is capability-first, not label-first.
What if my ERP has no API?
The product is preparing additional Local Agent, read-only database, and watch-folder routes. Those remain roadmap items until their technical gates are completed.
How are duplicate invoices prevented?
Each operation uses stable idempotency and the bridge reconciles existing records before reissuing when an outcome is uncertain.
Is Kairoseth Fiscal available to integrate my ERP?
Yes. v0.1.0 is published and we can diagnose fit, define mapping, and validate preflight. AEAT production remains controlled access and requires a separate technical and regulatory gate; completing the diagnostic never enables it automatically.
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.
KAIROSETH FISCAL · ERP / CRM
Check my ERP / CRMTell us which ERP or CRM you use and, more importantly, what it can do.
We review API, events, numbering, fiscal data, and workflow to choose the integration path with the least possible change.