Do not rebuild your spreadsheet for the bridge
The assistant inspects existing columns and proposes how to map them into the fiscal contract. Ambiguous mappings require explicit confirmation.
VERIFACTU WITH EXCEL AND CSVv0.1.0 published
VeriFactu from Excel or CSV without rebuilding the way you work.
Upload your file, let Kairoseth Fiscal inspect columns, confirm only what needs review, and run a no-effect preflight before fiscal activation.
CHAMELEON PRINCIPLE
Your spreadsheet is adapted through mapping, not the other way around.
The goal is to reduce the technical jump for spreadsheet-based invoicing without hiding errors or silently making ambiguous fiscal decisions.
CSV and XLSX share one workflow
Both formats end in the same MappingProfile, preflight, and fiscal engine. File format does not create a different VeriFactu implementation.
No-effect preflight
Check structure, required fields, dates, amounts, and mappings before creating any fiscal record.
Reusable mapping
Once a profile is confirmed, equivalent future uploads do not require deciding every column again.
Defensive XLSX processing
The reader is read-only, applies size and structure limits, does not extract files to the filesystem, and rejects dangerous XML constructs.
Designed for small businesses
The file route exists for businesses without an API, modern ERP, or technical team to build their own integration.
HOW IT WORKS
From your spreadsheet to a verifiable preflight in four steps.
Import is first used to understand and validate your data. Fiscal activation is never a silent consequence of uploading a file.
Upload your CSV or XLSX
Choose the file and, for XLSX, the sheet and header row when needed.
Review suggested mapping
Kairoseth detects strong matches, flags uncertain mappings for review, and identifies missing fixed configuration.
Run preflight
Each row is validated without fiscal side effects. Errors point to the file, mapping, or configuration that needs correction.
Activate when the flow is ready
The validated MappingProfile is reused when sending is enabled. AEAT production activation is a separate gate and never happens merely because a file was uploaded or validated.
VALIDATE BEFORE SENDING
Uploading a spreadsheet does not mean sending it to AEAT.
Inspection and preflight are deliberately no-effect operations. They identify columns, missing fields, amount errors, and pending decisions before any fiscal operation exists.
FAQ
Excel, CSV, and VeriFactu questions.
For businesses that need a simple route before considering a technical integration.
Can I use VeriFactu if I currently invoice in Excel?
Kairoseth Fiscal includes a CSV/XLSX import route for businesses without an API. You can inspect columns, confirm mapping, and validate every row before fiscal activation.
Do I have to rename my spreadsheet columns?
Not necessarily. Mapping Assistant proposes matches between your headers and the canonical contract. Uncertain matches stay pending until you confirm them.
Is XLSX supported as well as CSV?
Yes. The read-only XLSX reader supports multiple sheets, shared strings, inline strings, numbers, cached formula values, and Excel dates within defensive limits.
Is old .xls supported?
Not directly. Legacy .xls files must first be converted to .xlsx or CSV.
Does uploading the file immediately send invoices to AEAT?
No. Inspection and preflight do not send anything or create fiscal side effects. Activation is a separate explicit step.
Is the original spreadsheet binary stored?
The onboarding flow keeps parsed data required for preflight; the import contract does not require retaining the original binary file.
Is the Excel/CSV route available?
Yes. Kairoseth Fiscal v0.1.0 is published and the Excel/CSV route can be diagnosed, prepared, and validated. AEAT production remains controlled access and requires its own technical and regulatory gate.
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 · EXCEL / CSV
Check my Excel / CSVStart with the file you already use.
We review your data structure and define the required mapping without asking you to redesign your business around another tool.