Veridico
Invoicing infrastructure built for VeriFactu compliance, not around it.
Spanish freelancers and small businesses face a hard regulatory deadline: VeriFactu requires invoicing systems to guarantee data integrity, traceability, and auditability, with real penalties for non-compliance. Most existing invoicing tools were retrofitted to comply after the fact — Veridico was designed around the requirement from line one.
VeriFactu isn't a feature, it's a constraint that shapes the entire data layer: every invoice record needs a verifiable chain (no silent edits, no deletion, exportable audit trail), and the system has to work for non-technical solo business owners, not accountants.
Regulatory correctness cannot be "close enough" — an invoicing system either satisfies the traceability requirement or it's a liability. Built as a desktop-first application (Electron) to give offline reliability and local data ownership, which added its own sync/architecture tradeoffs.
The invoice ledger is treated as an append-only log, not a mutable table — corrections happen via compensating entries, never edits, which is what makes the audit trail real instead of cosmetic.
Client (Electron) → append-only invoice ledger → export/audit layer → multi-device sync service (planned).
Electron (desktop shell + offline-first reliability), JavaScript/HTML/CSS for the interface layer, with the data layer designed to be swappable toward a hosted backend as the product moves from local tool to SaaS.
Discovery started from the regulation text, not from a feature list — mapped every VeriFactu requirement to a concrete data-integrity guarantee before writing UI. Prototype validated the ledger model before any interface work began.
Harder to build, but the only model that survives an audit.
Prioritized data ownership and offline reliability for solo operators over the convenience of a hosted app, with cloud sync planned as an additive layer, not a replacement.
Underestimated how much UX work "boring" compliance software needs — a system can be perfectly correct and still fail if a non-technical user can't trust what they're looking at. Re-scoped the interface layer mid-build to prioritize clarity over feature breadth.
Compliance-driven products reward getting the data model right before anything else — every later feature is downstream of whether the ledger design is trustworthy.
First pilot business, first real invoice issued through the system, and first completed VeriFactu audit trail export will be added here as soon as they exist. There's nothing to show yet — and I'd rather say that than invent a number.
Hosted/SaaS version with multi-device sync, accountant-facing export tools, expansion beyond invoicing into broader fiscal record-keeping for small businesses.