Skip to main content

Roadmap

This page records the current product status and areas under consideration. It is intentionally short: no dates and no delivery promises.

If you want to help prioritise or contribute, open an issue or a pull request on GitHub.


Current status

Community Edition REST API (available)

The Community Edition provides an organization-scoped REST API at /api/v1. The current API includes bearer-token authentication, contacts, invoices, expenses, journal entries, idempotent mutations, and CAMT.053 imports. The OpenAPI and endpoint documentation is published with the project.

Core accounting and banking (available)

Gäld includes Swiss QR-bill PDF generation, ISO 20022 CAMT.053/054 imports, financial reports, VAT workflows, fiscal-year closing, and organization data export. The web application remains the primary product experience.

Recently shipped

Receipt scanning with OCR

Upload a receipt photo or PDF — Gäld extracts date, amount, supplier, and VAT via built-in OCR. Available from the Dashboard quick-receipt button or when creating an expense.

In-app notifications

Notification bell in the top bar with per-user preferences. Covers OCR scan results, billing alerts, and system messages.

Progressive Web App

Service worker for offline access, install-to-home-screen on mobile, and native share/print support.


Under consideration

API integration follow-up

A small follow-up may add first-token bootstrapping, bank-account creation through the API, and token-authenticated invoice PDF downloads. These items are being evaluated as focused integration improvements and have no committed release date.

Broader API coverage, including report endpoints, chart-of-accounts write access, bank transaction reconciliation, and per-line invoice revenue accounts, remains under consideration. It is not currently a commitment to turn Gäld into a fully headless accounting backend.

Gäld already speaks ISO 20022 (CAMT.053/054 import) and the EE cloud edition has an early integration with the SIX bLink open-banking gateway for automatic transaction retrieval. The goal is to make the same flow available to self-hosters.

Current limitation — connecting to the SIX bLink API requires a paid business contract with SIX Payment Services. The fees are significant enough that we cannot absorb the cost and offer it for free in the community edition at this time. We are actively looking at alternatives (direct-bank APIs, FinTech middleware that is more affordable) and welcome sponsorships or contributions that would make this viable sooner.

In the meantime, manual CAMT file import remains fully supported in the CE.


Better installer & packaging

The current setup uses the ./gaeld setup helper and published release artifacts. Further improvements under consideration include:

  • Official Docker Hub image with a one-liner docker run install
  • Pre-built release archive (no composer install needed)
  • Potential Helm chart for Kubernetes self-hosters
  • Improved gaeld:install wizard with health checks and first-run validation

Coming later

e-Invoicing — Factur-X / Peppol / ZUGFeRD

Swiss and European regulations are moving toward structured electronic invoicing. Planned additions:

  • Embed Factur-X / ZUGFeRD XML inside generated PDFs
  • Peppol BIS Billing 3.0 export
  • Receive and parse incoming e-invoices

Fiduciary & accountant portal

A read-only (or limited-write) access mode for external accountants and fiduciaries:

  • Invite your accountant to a shared view without giving them full admin rights
  • Export packages ready for your fiduciary (already partially available via the export module)
  • Collaboration comments on journal entries and closing tasks

Mobile & PWA — continued improvements

The core PWA shipped in v2.8.0. Planned next steps:

  • Full responsive polish on remaining pages (complex tables and modals)
  • Offline write queue for creating expenses and invoices without connectivity

Hardware security keys (FIDO2)

Gäld already supports passkeys and hardware security keys via WebAuthn — any FIDO2-compatible authenticator (YubiKey, Titan, etc.) works today for two-factor authentication. Planned improvements:

  • Multiple hardware key registration per account
  • FIDO2 as a standalone second factor (separate from passkey login)
  • Recovery code improvements for lost-key scenarios

Contribute or sponsor

All of the above takes time and money. If you or your company relies on Gäld, consider:

  • Opening an issue to discuss a feature or share feedback
  • Submitting a pull request — see CONTRIBUTING.md
  • Sponsoring the project to help fund integrations like SIX bLink

Thank you for using Gäld. 🙏