The pilot sandbox
Boty Invoice is in Phase 0: all issuance happens in a sandbox environment. Every console screen shows this notice, which cannot be closed or hidden (the product script is Spanish-only, quoted verbatim):
Esto es un sandbox. Ninguna factura aquí tiene validez legal ni fiscal. Es un ensayo con los datos reales de tu cartera para validar el flujo antes de la primera factura de producción.
(“This is a sandbox. No invoice here has legal or fiscal validity. It is a rehearsal with your portfolio’s real data to validate the flow before the first production invoice.”)
What the sandbox is
Section titled “What the sandbox is”A rehearsal with real data: you register your real portfolio of managed clients, create their series, and seal test invoices to validate the complete flow — registration, per-series numbering, fiscal engine preview, sealing, rectificativa, export, and chain verification — before issuing the first production invoice.
What happens inside the sandbox is real mechanics, not stage dressing:
- Every sealed invoice enters a per-client hash chain (SHA-256), verifiable from the console.
- Numbering is assigned by the server per series, with no invented gaps.
- Totals are computed by the fiscal engine on the server, never by the browser.
- The Facturae and UBL exports are real XML — with a sandbox marker flagging them as not valid.
What the sandbox does NOT claim
Section titled “What the sandbox does NOT claim”What it is for, then
Section titled “What it is for, then”So that the despacho reaches its first production invoice with the flow already rehearsed on its own portfolio: series created, team trained, and chain verified — instead of premiering the process on an invoice that counts.
The real conformity status and the Verifactu roadmap are published on the product’s conformance page and in the console’s Conformity panel.
Última verificación: