Hela

What's new in 3.0

Version 3.0 opens Hela to the outside. Everything described in this documentation ships with it.

3.0.1

  • The API applies the platform schema's migrations itself at start-up, under a lock; a deploy no longer leaves the new pages without their tables.
  • Each company can register its own OAuth application (client id and secret) for Google, Microsoft, Dropbox, QuickBooks, Xero, Yuki, Exact, Pennylane, Sage, Zoho Books and DocuSign; no connector is "unavailable on this server" any more.
  • When the API does not respond, the Integrations, Developers, Compliance and Hours pages say so once, plainly, instead of marking every partner "coming soon".
  • The Developers page lists the connected services, each leading to its page.
  • The Hours page is the team's timesheet: totals per employee, a filter by employee, the client only on billable hours.
  • The OAuth callback address is on the web app's domain (…/integrations/callback/<connector>), the one a company declares with the partner.
  • The point of sale collects online: link or QR (Stripe, PayPal, Square, SumUp, Mollie…) or a request on the customer's phone (M-Pesa, MTN MoMo, Airtel, Orange, Wave…); the sale waits, the confirmation settles it.
  • The treasury shows the connected payment providers and the wallet each credits; in a connector's settings the wallet and the location are picked from a list.
  • Connect with Stripe: one button, Stripe's consent screen, the webhook registered by Hela on the account; the key still works without a Connect platform. The same path for Mollie, Square, SumUp and Slack.
  • The Connecting a partner page says, family by family, what goes by itself after an operation and what waits for a gesture.
  • To the sheet: on Sales, Purchases, Partners, Catalogue, Treasury and Hours, the table on screen is written into Google Sheets or Excel Online.
  • Pay online on the invoice the customer receives: the portal page leads to the connected provider's payment page, and the payment records itself.
  • invoice.overdue is emitted (hourly sweep, once per invoice) and stock.movement on every adjustment, loss, return or count; Shopify and WooCommerce rewrite stock on every sale, cancellation or credit note.

Public API

  • Per-company API keys, with scopes and test mode; per-key rate limit.
  • OpenAPI 3.1 schema served by the server, browsable UI at /docs.
  • Cursor pagination on new collections, idempotency on every write.
  • TypeScript SDK @hela/sdk.

Events and webhooks

  • One event journal per company (43 types), written inside the business transaction.
  • Signed webhooks, retries over six steps, replay, test, secret rotation; protection against private addresses.
  • Zapier, Make, n8n apps; Power Automate recipe; MCP server.

Integrations

  • Accounting: Odoo, QuickBooks Online, Xero, Yuki, Exact Online, Pennylane, Sage Business Cloud, Zoho Books; CSV, FEC, DATEV exports on the SYSCOHADA, PCMN, PCG charts.
  • Payments: Stripe, Mollie, PayPal, Square, SumUp; MTN MoMo, M-Pesa, Airtel Money, Orange Money, Wave, Flutterwave, Paystack. Payment links and phone requests from the invoice.
  • Banking: CAMT.053, MT940, CSV statement import; GoCardless, Ponto, Plaid feeds; reconciliation with suggestions.
  • Commerce: Shopify, WooCommerce — orders as sales, stock written to the shop.
  • Calendar: iCal both ways (Booking.com, Airbnb, Vrbo), Google Calendar.
  • Identity: Google, Microsoft, Apple sign-in.
  • Documents: Google Drive, OneDrive, Dropbox; Google Sheets, Excel Online.
  • Signature: Yousign, DocuSign.
  • Time: Clockify, Toggl Track, and the Hours page with billing.
  • Messaging: WhatsApp Business, Slack, Teams, Telegram, Twilio, Africa's Talking.
  • Exchange rates: ECB, Open Exchange Rates.

E-invoicing and compliance

  • UBL 2.1 (EN 16931, Peppol BIS 3.0) and CII formats on every sale.
  • Regimes: Peppol, France (PDP), Germany (XRechnung), Kenya (eTIMS), Rwanda (EBM), Tanzania (VFD), Uganda (EFRIS), Côte d'Ivoire (FNE), Benin (e-MECeF), and the device regimes of the DRC, Senegal, Burkina Faso and Cameroon.
  • Sealed journal by hash chain, verifiable.

In the app

  • New pages: Integrations, Developers, Compliance, Hours, Bank reconciliation.
  • Back office: Integrations and keys — OAuth clients, public addresses and sign-in keys set without a redeploy.
  • Partners card on invoices and quotes.
  • New permissions integrations:manage and developers:manage; new plan ceilings integrations, apiKeys, webhooks.

Public site

  • Partners page, with the catalogue and the marks.
  • This documentation.

Next version (3.1)

German TSE; certified Power Automate; OAuth for third-party applications; SCIM; Python SDK.

Something wrong or missing? Write to us.