Backend – Spring Boot microservice
ms-financial-statement (Financial Statement)
Objective
Centralise the business logic for preparing and generating financial statements (trial balances, chart of accounts, exercises, sheets and notes) via a REST API and automated Excel exports.
Role
Backend developer responsible for the Spring Boot microservice ms‑financial‑statement.
Impact
Automation of the production of financial statements, normalisation of accounting processes and easy deployment thanks to Docker, improving team productivity.
Key technologies
Java 17, Spring Boot 3.2, Spring Web (REST), MongoDB, Apache POI, JEXL, ANTLR, Docker.
Context:
Contribution as a backend developer to the ms-financial-statement microservice, a Spring Boot service dedicated to the management and production of financial statements (trial balances, chart of accounts, exercises, spreadsheets, notes, forms, consistency checks) for a finance/accounting environment.
Project description
The ms-financial-statement service exposes a REST API allowing accounting teams to prepare, manipulate and validate normalised financial statements. It integrates with a MongoDB database and generates Excel files from templates. The aim is to centralise the business logic (exercises, balances, formulas, checks) in a unique microservice that is industrialisable and easily deployable via Docker / Docker Compose.
Client
ASMA Software
Role
Backend Developer – Spring Boot microservice
Technologies
Java 17, Spring Boot 3.2, Spring Web (REST), MongoDB, Apache POI (Excel), Apache Commons JEXL, ANTLR, Maven, Docker, Docker Compose.
Features & responsibilities
- Balances & chart of accounts: endpoints to load, view and exploit trial balances and the chart of accounts.
- Management of exercises: creation, update and consultation of accounting exercises associated with financial statements.
- Spreadsheets & Excel: initialisation and manipulation of spreadsheets linked to exercises, generation and modification of Excel files via Apache POI.
- Forms & notes: management of form templates, their records and the notes attached to financial statements.
- Consistency checks: implementation of business rules (formulas, expressions) via JEXL to verify the consistency of statements, and exposition of results by control rule.
-
Architecture & structuring: clear separation between API (
web/api), controllers (web/controller), models & repositories (data) and business services (service). -
Configuration & execution: multi-profile configuration via
application.ymland environment variables, local orchestration with Docker / Docker Compose (backend + MongoDB).