← ALL WORKPROJECT 04 / 05

FinTech Platform

Business-critical software for revenue-management and accounting workflows, with work across backend processing, data modelling and application features.

ROLE
Software Engineer
FOCUS
Business software / Data / Correctness
STACK
C# / .NET / React / MSSQL
TYPE
Professional work
Conceptual illustration of fintech platform; not a client screenshot
Conceptual illustration of the engineering problem

THE CONTEXT

At LANACO, I developed and maintained production business software using C#/.NET, React and MSSQL. The application supported revenue-management and accounting processes with existing business rules and data-heavy workflows.

THE CHALLENGE

Correctness mattered across calculations, validation, reconciliation and status transitions. Submission, correction and approval were connected parts of the same operational process.

A change had to make sense within existing application behavior and record handling, not just work in isolation.

MY ROLE

I implemented backend processing and business rules, built end-to-end application workflows, and worked on database schemas, queries, views and stored procedures.

I worked with domain stakeholders to translate operational requirements into maintainable production software.

HOW I APPROACHED IT

I started with the operational process and the existing behavior it depended on. Requirements needed to become explicit validation, processing rules and state transitions.

Working across application code and MSSQL meant keeping the data model and the user workflow aligned as the software was maintained and extended.

CONCEPTUAL WORKFLOWA public explanation of the flow
  1. 01Submission
  2. 02Validation
  3. 03Processing
  4. 04Correction / reconciliation
  5. 05Approval

ENGINEERING DECISIONS

01

Domain rules in code

Implement calculations and validation around the actual revenue-management and accounting requirements.

02

Connected workflow states

Treat submission, correction and approval as related behaviors with deliberate status transitions.

03

Data modelling and queries

Support data-heavy workflows with schemas, queries, views and stored procedures in MSSQL.

04

Stakeholder understanding

Use domain context to turn complex requirements into maintainable application features.

OUTCOME

Delivered and maintained application features, backend processing and data workflows for production revenue-management and accounting software.

Selected identifying and implementation details are omitted because this work was completed for a client.