BUSINESS SYSTEMS · BILLING
From property records to explainable bills.
Built property, unit, member, and billing workflows in a separate PHP application. Itemized charges and reusable templates support the complexity of society billing.
Workflow at a glance
- Property
- Charge rules
- Itemized bill
- Payment
The problem
Society billing combines property and member records with reusable charge rules, itemized bills, and payments. Calculations need to remain understandable after a bill is generated or a receipt is reversed.
What I built
- Built administration, property, unit, and member workflows in the CodeIgniter application.
- Built billing masters, itemized charges, reusable billing templates, and related payment functionality.
- Worked across frontend workflows, backend logic, and relational data for the society management application.
Platform capabilities
Described at platform level, separately from my individual contributions above.
Traceable billing calculations
Area-based charges and proration use integer-money calculations with preserved calculation snapshots.
Reversals with history
Payment reversals retain receipt and audit history instead of losing the previous financial record.
Reusable billing workflows
Billing masters and templates connect recurring charge rules with itemized bills and related payment workflows.
How this is supported
The billing and payment-history capabilities are supported by repository review. Advanced safeguards are described at platform level. This PHP/MySQL application is distinct from the Next.js/NestJS/PostgreSQL platform.
This is company work at Finovel Fintech Private Limited. The source code, integrations, and customer data are private, so there is no public repository or screenshot for this project.
Takeaway
A practical business application connecting society records, billing rules, and payment history.