Case study · Financial Management SaaS
MoneyGence
MoneyGence is a financial management SaaS for service businesses. It brings client finances, invoicing, collections and receivables into one view.
- React.js
- Node.js
- Express.js
- PostgreSQL
01
Problem & context
Service businesses need to see what they have billed, what they are owed and what has been collected, without stitching it together from separate spreadsheets and tools.
02
My role and contribution
My work
- Owned three modules within the development team: invoicing, receivables and reports.
- Implemented the frontend functionality, backend APIs and database-backed workflows for those modules.
Scope
MoneyGence was built by a development team. The rest of the platform, outside the three modules above, was not my work and is not described here.
03
Technical implementation
Frontend
React screens for the invoicing, receivables and reports modules.
APIs
Express.js endpoints serving those modules to the frontend.
Data
PostgreSQL-backed workflows that persist invoices, receivable status and report data.
04
Workflow
- Invoice raised
- Receivable tracked
- Payment collected
- Report generated
Simplified illustration of the flow, not the production schema or architecture.
05
Engineering decisions
One record, three modules
Invoices, receivables and reports describe the same money, so the modules work from shared database-backed records instead of keeping separate copies.
Clear contracts inside a team
Owning specific modules in a shared codebase means agreeing explicit API contracts, so my modules and the rest of the platform can change independently.
06
Technologies used
- React.js
- Node.js
- Express.js
- PostgreSQL
The interface shown above is an original mock-up with placeholder data, not a product screenshot.