An identified source
Which event creates the invoice, which data is involved and who maintains that process.
KeneaFactu · Operational product
Your software already invoices.
Now consider the connections.
KeneaFactu is our product for working on the integration between your invoicing software and Spain's VeriFactu system. Request a demonstration to understand the available scope and how it fits your setup.
Request a demo Explore the workflow
Operational product. Access, integrations and terms are agreed with Kenea after reviewing your case. The demonstration on this page is illustrative and uses fictional data.
Kenea visual study
The mechanism
The source, the response
and what happens between them.
This diagram explains six parts of an integration: your software, the adapter, tax reporting, results, review and evidence. It illustrates the workflow using fictional data; a product demonstration establishes what each implementation covers.
KeneaFactu / operating modelDEMO · SAMPLE DATA
View more sample records · 3 scenarios
Example environment3 synthetic records · not connected
Record / sourceIllustrative stateNext decision
DEMO-001Example ERPResponse receivedReview evidence
DEMO-002Example industry softwareData to checkHuman review
DEMO-003Example custom softwareUnconfirmedCheck before resubmitting
DEMO-001 / Example ERP
One invoice.
Three scenarios.
Example source and context
- Document
- DEMO-001
- Source
- Example ERP
- Latest event
- 10:42 · simulated time
- Owner
- Demo operator
Select a scenario to see how the review changes. Nothing is submitted.
Record reviewSuccessful response
- Source
- Record
- Submission
- Review
DEMO-001 / EXAMPLE, NOT AN AEAT CODEResponse received. Evidence linked.
Example of an accepted record. The result is retained with its source for review.
Illustrative demonstration. This page does not connect to the AEAT or process real data. Read the state model.
The integration point
Your application
knows the business.
Before proposing an adapter, we review the version, customisations and the point at which an invoice is issued. We also check what the current software provider covers.
A meaningful result
Which information would distinguish a received response from an error or an unconfirmed submission.
Linked evidence
Which records, responses and decisions your team needs to retain, and how to check them within the agreed scope.
Who may need this workflow
Different software.
A specific decision.
ERP integrators
Assess a shared source and check what could be reused across versions and customisations.
Industry software vendors
Define integration within the product and the responsibilities of each component.
Businesses with custom software
Identify the dependencies that affect adaptation and the available alternatives.
Tax and accounting advisers
Organise software details and provider responses to coordinate technical decisions with tax advice.
Choosing an approach
The assessment may recommend another solution.
A vendor module, a tax reporting API or a change of application may address the need. We compare version coverage, customisations, dependencies, maintenance and cost before defining an integration.
KeneaFactu focuses on the workflow from source to review. Compatibility, applicable features and implementation are established for each system before an engagement begins.
The software producer's responsible declaration and integration responsibilities are reviewed against the relevant system and applicable rules.
Available today
See KeneaFactu in the context of your work.
Tell us which software you use and request access or a demonstration. We review the source, provider coverage and next steps, then agree on scope, price and schedule before implementation.