Bas Stokmans · Software Developer · AI & Robotics

Archiving payroll data

Software engineering internship · Teal Partners, Antwerp · Feb – May 2025

The assignment

Teal Partners builds an established payroll product: payslips, gross-to-net, employer cost. My job was to move historical payroll calculations out of the live database into long-term storage, without losing the ability to read them later. It had to fit an existing .NET and Angular codebase, its domain model and its conventions.

The flow I built

1. SQL Serverpayroll data
2. NHibernatenamed queries
3. Archive modelsstable JSON contract
4. Azure Blobdeterministic paths
5. Reader API.NET · Swagger
6. Angular viewerpayslip-style view

Full stack, in someone else's codebase. One feature that touched the database, the ORM, backend services, cloud storage, an API and a new frontend.

No screenshots: the code is proprietary. So here is the architecture.

How it came together

What I took from it

1. Prototype, then fit in. The SQL proof showed the idea worked. The real work was rebuilding it in the codebase's own patterns.
2. An archive is a contract. Exporting database entities directly would tie history to today's schema. Dedicated archive models keep it readable later.
3. Learn the domain first. Gross-to-net, employer cost and employment relations decided what belonged in the archive.
4. Interfaces pay off. Storage and reading sit behind abstractions, so the infrastructure can change without rewriting the logic.

Built with

• .NET / C#
• Angular
• SQL Server
• NHibernate
• Azure Blob Storage
• MediatR
• Swagger / OpenAPI
• Docker
• Git