Console guide

The Boty Invoice console (/consola) is the despacho’s workspace: from there you register your managed clients, create their numbering series, seal rehearsal invoices, and verify the integrity of each chain.

Everything is sandbox

The entire console operates in sandbox mode (Phase 0). A non-dismissible notice reminds you on every screen. No invoice sealed here has legal or fiscal validity. See The pilot sandbox.

Access

• You need to sign in and hold an operator membership for Boty Invoice (an active subscription to a Despacho plan).
• Without a membership, the console redirects you to the pricing page.
• If your membership is revoked while you work, the console takes you to a “no access” screen that explains it — never a generic error.

Dashboard

The initial screen shows your despacho’s name, your role, and your plan, next to two real counters read from the API: active clients and sealed invoices. If the data cannot be loaded, you see an honest error state — never a fabricated zero.

Client portfolio

Route: /consola/clientes.

Lists all managed clients in your despacho. By default only active clients are shown; the “Mostrar archivados” checkbox adds archived ones, each clearly labelled “Archivado”.

• Empty state. A despacho with no clients sees “Aún no tienes clientes” and a link to register the first one — never a blank table.
• Error state. If loading fails, the screen shows an error message and invites a retry — never an empty list that could be mistaken for a genuinely empty portfolio.

Invoices

Route: /consola/facturas.

Global list of all sealed invoices across every managed client (series, number, date, client, total). Each row links to the sealed invoice’s detail. This is the entry point for invoicing when you are not starting from a specific client.

Registering a managed client

Under Cartera → Nuevo cliente you register a client with two fields: legal name and NIF/CIF/NIE.

• The NIF/NIE is validated against its control digit (mod-23) before anything is sent; the CIF is checked by format only. The server always re-validates.
• If the tax ID already exists in your despacho, the form flags it as a field error (no duplicate is created).
• If you reached your plan’s managed-client limit, a clear message says so; upgrading the plan is the only way to keep registering.

Client detail

Each managed client has its own page with:

• Numbering series — list and create series (code + kind: ordinary, rectificative, or simplified). Numbering is assigned by the server; the console never makes up a number.
• Invoice history — each row opens the sealed invoice’s detail.
• Chain verification — a button that re-verifies that client’s hash chain and shows the result: “Cadena verificada — íntegra” (intact) or “Cadena rota — no verificada” (broken), naming the invoice where the break was detected. Each client has its own chain, isolated from the others.

New invoice: preview and seal

From the client’s page, Nueva factura opens the issuance flow:

1. The issuer is the managed client itself — fixed, not editable.
2. You fill in the recipient (legal name, NIF/CIF/NIE, country), the series, the date, and the lines (concept, quantity, unit price, VAT category, and rate).
3. The fiscal engine preview computes the taxable base, VAT amount, and total on the server — the console never computes totals on its own. When you change a line, the preview refreshes automatically; the seal button stays disabled until the updated totals are ready.
4. Sellar en sandbox permanently records the invoice into that client’s chain.

A sealed invoice is immutable

There is no editing or deleting a sealed invoice — on any screen or in the API. The only possible correction is issuing a rectificativa.

Sealed invoice detail

The detail shows the full record: issuer and recipient, lines, VAT breakdown, totals, and the integrity and chain section (record hash, body hash, previous hash, SHA-256 algorithm, and chain/engine versions).

• The verification code (QR) is shown as a text link, framed “SANDBOX — sin validez legal”. No scannable image is generated in this phase.
• You can export the invoice as Facturae 3.2.2 (XML) or UBL 2.1 (XML). Both files carry a sandbox marker in their content: they are not valid as invoices.

Rectificativa

From a sealed invoice’s detail, Emitir rectificativa:

• The issuer and recipient are taken from the original invoice — not editable.
• You need a rectificative-kind series for that client; if none exists, the console asks you to create it first on the client’s page.
• The rectification reason is mandatory: without a reason, no request is sent at all.
• The rectificativa is sealed as a new document (type 381) linked to the original. The original invoice is never modified.

Conformity panel

Conformidad summarizes the real state of your issuance: environment (sandbox), chain version, the chain status of the most recent record (re-verified on every visit), and the responsible-declaration line, which today tells the truth: no responsible declaration has been issued yet. With zero sealed records, every value reads “sin registros todavía” (no records yet) instead of a fabricated figure.

Guided first-use onboarding

The ”?” button in the top bar opens the help panel: the current screen’s tour, the full list of available tours, and two explicit preferences (guided tours / sample data), each with a “Yes”/“No” toggle.

Per-screen tours. Each of the four fixed menu destinations (Panel, Cartera, Facturación, Conformidad) has its own tour. The first tour starts automatically the first time you reach the console; after that it only starts when you ask for it from the help button.

“Primeros pasos” panel. A persistent panel with four onboarding tasks: register the first client, create a numbering series, seal the first rehearsal invoice, and try a rectificativa. Each task is marked complete based on the real state of your account — never a locally stored flag.

Demo mode (Cartera, Facturas, and Panel). While the portfolio has no active clients, /consola/clientes, /consola/facturas, and the Panel show example data with a visible notice — “Estás viendo datos de ejemplo. No son datos reales de tu despacho.” — that disappears as soon as you register your first real client or press “Salir del modo de ejemplo”. The Conformidad screen never shows fabricated data.

Sample data

From /consola/clientes, the “Generar datos de ejemplo” button creates real rows through the same sealing engine: 3 managed clients and 8 sealed invoices across 4 series (7 ordinary and one rectificativa example). Sample data behaves in the sandbox exactly like real data.

• Sample marker. Each generated client shows a visible “Ejemplo” badge next to its name. This marker never appears in any exported file (Facturae/UBL).
• Plan limit. Sample clients count against your plan’s client cap. If generating them would exceed it, the console rejects the request with a clear message — it never creates a trimmed subset.
• One batch at a time. If a sample batch already exists, the console says so and points to the “Eliminar datos de ejemplo” button.
• “Eliminar datos de ejemplo” archives, never deletes. Clients move to “Archivado” status and disappear from the default view, but remain visible with “Mostrar archivados” checked, with their invoices intact. No console action deletes an already-sealed fiscal record.

Photo data capture

The “Rellenar desde una foto” button only appears when document-reading capability is configured in the platform. Without it, the forms work exactly the same with no disabled button — just fill in by hand, as always.

The AI never seals an invoice. Reading a photo can only prefill editable form fields that the gestor reviews and confirms manually.

Client registration (/consola/clientes/nuevo). The “Rellenar desde una foto (DNI/CIF)” button fills the legal name, NIF/CIF/NIE, and address as editable values in the form. The gestor still has to press “Registrar cliente”; reading the photo alone creates no record.

New invoice (/consola/clientes/:id/facturar). The “Rellenar desde una foto de la factura” button saves an editable draft with the extracted data and navigates to it. Monetary amounts are never read from the photo — they are always computed by the fiscal engine.

When the photo cannot be read. The screen shows “No se pudo leer el documento. Rellena los datos manualmente.” and the form is left exactly as it was.