Services delivered
What we built and ran for alven.sk
We engaged alven.sk across the services above, taking ownership of execution and reporting on measurable outcomes. To see numbers from this engagement under NDA, book a 30-min call.
Snapshot
Project: Our own product — Alven, “accounting that counts itself”: a cloud accounting system for Slovak accounting firms and payroll professionals, built from the data model up for structured documents under EN 16931.
Why it exists: from 1 January 2027, Act no. 385/2025 makes structured e-invoicing mandatory in Slovakia. Desktop accounting packages built around paper-shaped PDFs can’t natively produce or consume structured invoices — Alven treats the structured document as the source of truth from day one.
What it proves to a prospective client: our Peppol and e-invoicing expertise isn’t consulting theatre — we productized it. The same team that operates a certified Peppol Access Point wrote the VAT engine, the UBL exports and the API that Alven runs on.
The facts
| Area | Detail |
|---|---|
| VAT logic | EN 16931 semantics, Slovak rates 23/19/5/0% |
| E-invoices | UBL 2.1 exports, Peppol-ready delivery |
| Precision | integer cents everywhere — no floating-point rounding errors |
| Architecture | API-first: REST with OpenAPI docs, multi-tenant isolation |
| Registers | master data pulled from the Slovak RPO business registry |
| Documents | PDFs with PAY by square QR codes, automatic numbering per period |
| Status | early access — free during the testing phase |
What the system does
- Double-entry bookkeeping with automatic posting — routine documents book themselves; the accountant reviews instead of retypes.
- VAT returns for eDane — returns and control statements generated from the ledger, not assembled by hand.
- Saldokonto — open-item accounting with partial payments and reconciliation built in; PSD2/CAMT.053 bank feeds are in development.
- Structured outputs — every invoice exists as a valid UBL 2.1 document first and a PDF second, which is what the 2027 regime actually requires.
The engineering underneath
Alven is deliberately unspectacular where it counts: penny-precise arithmetic, strict multi-tenant data separation, and an API-first design with no vendor lock-in — everything the UI does, the documented REST API does too. Building it keeps our team fluent in exactly the compliance machinery (EN 16931, UBL, Peppol, eDane) our client projects will need over the next few years.
More work
Related case studies
Other clients using Custom software development + Automation.
Want a result like alven.sk?
Tell us about your business — we'll come back with a plan, a timeline and a number you can budget against.