Zeus Software/Work/Welfare app
Case studyCorporate Welfare · SaaS

An app for
welfare.
The whole cycle.

From loading credits to paying in store, from invoices to bank reconciliation — an app for workers and a platform for the people who run corporate welfare.

Sector
Corporate welfare
Integrations
12 external services
Stack
NestJS · Angular 21
01

One platform
for the entire welfare cycle.

The platform follows corporate welfare from start to finish: the company loads credits for its workers, workers spend them from the app — in store, on meal vouchers, gift cards, travel, refunds — and the system produces invoices and self-invoices, reconciles bank transactions and handles local donations.

02

Where we
started.

A welfare plan involves many parties: companies, workers, stores, business partners, non-profits, meal voucher and gift card providers, the bank. Each with its own tax documents and money flows, and all of them have to add up to the same worker's credit.

i.

The challenge

Keep the worker's credit and every way of spending it in one system — affiliated stores, meal vouchers, gift cards, travel, refunds, shared canteens — with a different provider behind almost every channel. And for every transaction, the right tax document: an invoice to the company, a store self-invoice, the partner's fee.

ii.

Our approach

One charging engine: every channel deducts credit with the same FIFO logic, oldest voucher first. Each provider has its own adapter behind the same interface. Invoices and self-invoices come from the transactions and are created in Fatture in Cloud; bank transfers go out through Qonto.

iii.

The result

One system from loading credits to accounting. Bank transactions are matched to open invoices: automatically above a confidence threshold, through a review queue below it. In production since 2026, with data migrated from the previous system.

03

Five steps,
from credit to reporting.

The same flow covers in-store spending, meal vouchers, gift cards, travel, refunds and shared canteens — only the provider underneath changes.

01

Issuance

Worker CSV upload, row-by-row validation, invoice, credits available in the app.

02

Spending

From the app: in-store QR, meal vouchers, gift cards, travel, refunds, e-commerce.

03

Invoicing

Invoices and self-invoices in Fatture in Cloud, SEPA transfers via Qonto.

04

Reconciliation

Bank transactions matched to open invoices, uncertain cases sent to a review queue.

05

Reporting

Accounting, audit log, donation receipts and CSR reports.

04

A console
for the people who configure.

Workers, services, stores, contracts, credit uploads and welfare invoices: the company's area brings together what the people running the plan need in a single view. Providers and accounting live in the platform back office, with separate roles for operators, accounting and support.

Welfare console — plan overview, spending by category and invoices
The welfare plan on one screen. Credit issued, spent and remaining, spending by category and invoice status.HR console · corporate welfare
05

Five actors,
one economy.

Context-aware permissions with CASL and dedicated portals: each actor sees its own part of the platform. External welfare platforms can load credits through an API.

i.

Companies

Load credits, manage workers and services, receive welfare invoices.

ii.

Welfare
designers

Partners who bring in client companies and build their plans; paid a fee via self-invoice.

iii.

Workers

An app with credit, QR payments, refunds, donations, cashback and gamification.

iv.

Affiliated
stores

Get paid by workers, in store or online, and are reimbursed with a self-invoice and bank transfer.

v.

Non-profit

A portal for local projects that receive donations, with receipts and tax treatment.

06

What it does,
concretely.

Eight capabilities sharing the same FIFO logic on credit: whatever the spending channel, credit is deducted from the oldest voucher first.

01

CSV credit
issuance

Upload, validation, invoice and credits in a single flow, including future start dates.

02

Multi-channel
spending

Stores, meal vouchers, gift cards, travel, refunds, discounts, shared canteens, e-commerce.

03

Electronic
invoicing

Invoices and self-invoices created in Fatture in Cloud, never duplicated. SEPA transfers via Qonto.

04

Bank
reconciliation

Payments matched to invoices by reference, number and amount. Uncertain cases go to a person.

05

Donations
3 channels

Voluntary, expired credit, store percentage. Configurable tax treatment.

06

Store
cashback

A cashback percentage set per store, credited to the worker on every purchase.

07

Worker
gamification

Experience points, levels, prizes, avatars and a leaderboard.

08

Complete
back office

Registries, signed contracts, accounting, audit log, migration from the previous system.

12
External services integrated
3
Donation channels
5
Actors with their own portal
FIFO
One charging logic
07

Twelve services,
one integration.

Every provider speaks its own language. The platform puts them behind a single interface — meal vouchers, gift cards, travel, banking, invoicing, identity.

Banking · SEPAQonto
InvoicingFatture in Cloud
Meal vouchersToduba
Meal vouchersEdenred
Meal vouchersSatispay
Gift cardGoGift
Gift cardRuna
TravelSalabam
E-commerceWooCommerce
Store mapsGoogle Maps
IdentityKeycloak
Companies · SMSOpenAPI
08

Tech stack.

TypeScript monorepo, Zod DTOs shared between backend and frontend, job queues for long-running steps. The worker app is built in Flutter.

MonorepoTurbo · pnpm
RuntimeNode 22+
BackendNestJS 11
ORMPrisma
DatabasePostgreSQL
QueueBullMQ
FrontendAngular 21
UIPrimeNG
AppFlutter
StateNgRx Signals
AuthNKeycloak · JWT
AuthZ · DTOCASL · Zod
09 One platform for the entire cycle of corporate welfare: from credit to spending, from invoice to donation.
Have a welfare program to manage?

Still reconciling providers
by hand?

We build welfare platforms that integrate providers, banking and invoicing, with local donations and credit management from start to finish. Send us a couple of lines — we reply within 48h with an initial technical response.

Images are for illustrative purposes and do not necessarily reflect the current state of the application.