The Personal Finance Management System is a full-stack platform built to simplify shared expense tracking, automate participant-level balance computation, and provide real-time visibility into personal and group financial flow. The system is centered on clarity, ensuring users can understand who paid, who owes, and how settlement should happen without manual reconciliation.
Managing shared expenses across trips, group activities, and team events often creates confusion around contribution tracking and final settlement. In many cases, users must manually calculate balances, verify claim ownership, and reconstruct event-level spending history. This system addresses that friction with a structured, event-driven financial workflow that keeps expense data isolated, traceable, and immediately computable.
The application is designed as a full-stack system with clear separation of concerns:
- Presentation Layer: A React and TypeScript frontend delivers responsive, state-driven interfaces for event creation, participant management, and expense tracking.
- Application Layer: A Spring Boot backend in Java 21 manages business rules, claim processing, balance computation, and API orchestration.
- Data Layer: PostgreSQL provides relational persistence for events, participants, claims, and settlement-relevant financial records.
- Interaction Model: Real-time financial visibility is maintained by synchronizing user actions with deterministic balance updates.
Explore the complete architecture of the Finance Management System
The system follows a structured flow that reduces ambiguity in group finance management:
- Create Event: Define the shared financial context such as a trip, gathering, or team activity.
- Add Participants: Register the individuals involved in that expense group.
- Log Claims: Record expenses along with the claimant or paying participant.
- Compute Balances: The system derives payable and receivable positions for each participant.
- Settle Flow: Users can interpret the final state and close the event with a clear understanding of fund movement.
The financial model is structured around three core entities:
- Event: A top-level expense context that groups related transactions.
- Participant: A person associated with a given event and its financial state.
- Claim: An individual expense entry linked to an event and a contributing participant.
This structure enables consistent tracking of shared financial activity while preserving clean relationships between contributors and event-specific balances.
The balance engine is responsible for transforming raw claims into understandable financial outcomes. It supports:
- Total expense aggregation at the event level
- Participant-wise contribution tracking
- Share distribution across group members
- Net payable and receivable calculation
- Transparent settlement interpretation for each participant
By shifting the complexity of calculation into the application layer, the system removes manual effort and improves confidence in final balances.
- Event-based isolation for shared financial contexts
- Participant-level expense ownership and tracking
- Real-time balance updates across active events
- Clear payable and receivable visibility
- Streamlined claim-entry workflow
- Dashboard-oriented summaries for current financial state
The interface is built to keep financial interaction fast and readable:
- Minimal friction during event creation
- Quick onboarding for participants
- Simple expense claim entry patterns
- Visual balance indicators for immediate interpretation
- Summary-driven dashboards for active event monitoring
This keeps the product usable even when multiple participants and repeated claims are involved.
The platform surfaces the financial state through a live dashboard experience that can include:
- Total event expense summaries
- Individual payable and receivable values
- Recent claim and transaction context
- Active event overviews with computed balances
This ensures users do not need to inspect raw records to understand the current position of a group.
The following screens show the primary user journey through the application, from an empty event state to populated expense data and full event summaries.
An initial empty-state view that introduces the event workspace before any shared finance activity is recorded.
A focused event creation screen where users define a new shared expense context.
The participant onboarding step used to build the group involved in the event.
A newly created event page showing the clean state before claims and balances begin to populate.
The expense entry flow where a participant logs a claim against the active event.
An in-progress event view displaying recorded expenses, participant activity, and emerging balance information.
The completed event summary with richer financial data, clearer totals, and a more complete settlement picture.
The project demonstrates the design and implementation of a production-oriented shared finance platform that combines backend business logic, frontend interaction design, and relational data modeling into a cohesive system. It highlights strengths in full-stack development, deterministic financial computation, and system design for real-world collaborative usage.
Anand P S
Role: Firmware Systems Developer / Full-Stack Engineer
Bio: Engineer focused on backend architectures, embedded systems, firmware development, and production-grade software design, with an emphasis on scalable and maintainable systems.
Links: LinkedIn | GitHub | Email
Copyright 2026 Anand P S. All rights reserved.