ToDoIT Built a Multi-Society Financial Operations Platform for Housing Construction Teams

Overview / Snapshot

Society Financial Tracker is a responsive web platform for housing-society finance and construction-payment operations.

• Users: admin, entry_maker, white_viewer, plus QA-access users
• Timeline: November 3, 2025 to February 23, 2026
• Stack: PHP 8.2, Laravel 12, Blade, Tailwind CSS, Alpine.js, Vite, Sanctum, Chart.js, Flatpickr
• Platform: Web app + backend auth/API layer + relational DB + local/S3 storage support

Client Context

The product serves housing-society admins and finance operators managing unit-level collections and society-level IN/OUT financial activity. The import toolchain indicates legacy spreadsheet-heavy operations before centralization.

• Role-based access controls were required across modules
• Operations needed strict active-society scoping
• Legacy CSV/sheet data had inconsistent formats

Problem

Teams needed one auditable system for income, expenses, unit collections, and construction-stage receivables while enforcing strong role-based governance for financial records.

• Manual consolidation across unit-level and society-level transactions
• Strong access controls without blocking day-to-day operations
• Formula-driven stage receivable calculations and outstanding tracking
• Import duplication and mapping risk in historical datasets

Solution

ToDoIT implemented a Laravel-based financial operations platform with role-aware governance, multi-society context, and secure role-based controls.

Architecture

Blade + Alpine frontends call Laravel routes/controllers, which enforce role/context checks and use Eloquent models/services for financial calculations, imports, and storage.

• Core entities: societies, houses, transactions, users, activity_logs, construction tables, documents
• Services: FinancialCalculationService, CsvMasterImportService, SheetImportService
• Security: admin middleware, role-based access, encrypted remarks, audit events
• Reliability: indexed filters, pagination, DB transactions, dry-run workflow

Challenges

Usage & Usefulness

• Daily: operators post income/expense and update unit-stage collections
• Daily: admins monitor net totals, last IN/OUT, and house-wise balances
• Weekly/Monthly: admins run imports and review activity/audit logs

The system supports practical real-world finance workflows while preserving role boundaries and operational traceability.

Results

Quantitative outcomes: Not provided.

Qualitative outcomes: stronger governance, centralized visibility, and better traceability through role-aware workflows and activity logging.

• Recommended tracking: posting volume by mode/role, import quality, outstanding aging, governance events

What’s Unique

• Role-based governance model applied consistently across workflows
• Construction-stage receivable engine linked to booking/loan/token math
• Built-in split payment intake and entry-revert category
• Per-user/session active-society persistence for multi-project operations
• Duplicate-aware import flow with password-confirmed execution path

Deliverables / Assets

Must-have screens include login, home, societies, houses, transactions, dashboard, income, expenses, activity, documents, CSV import, sheet import, and governance workflows.

• 30-60 sec demo flow: login - houses - stage tracking - dashboard - import - activity logs
• Before/after visual set: spreadsheet-led process vs structured dashboard workflow
• Quote placeholders for admin/operator perspectives