BFI Kumanovë

BFI Kumanovë is an AbaSoft application for the administration of mosque and household membership contributions. It brings community records, invoices, payments and reporting into a shared system for authorized staff.

The platform combines an ASP.NET Core API, SQL Server persistence, Angular administration and an Angular/Capacitor mobile application. The focus is reliable operational workflows and controlled access to community and financial records.

Context

BFI Kumanovë manages community membership contributions associated with mosques and households. The application digitizes record keeping, collection and administrative reporting while keeping personal and financial information behind authorized workflows.

My role

I developed the application as an AbaSoft project, working across architecture, the backend, the Angular administration interface and the mobile experience. The case study concerns software delivery; it does not disclose individual household or payment data.

Core workflows

Authorized staff manage mosque and household records, record contributions and work with invoices and payments. Administration and collector responsibilities are represented by separate authorization rules. Reporting provides an operational view of stored records rather than relying on manually assembled spreadsheets.

Technical approach

The backend follows Clean Architecture and vertical slices, separating API, Application, Domain and Infrastructure responsibilities. ASP.NET Core, Entity Framework Core and SQL Server provide the core platform. Mediator and FluentValidation organize use cases and validation, while structured ProblemDetails responses support consistent client error handling.

Angular supplies the administrative interface. The mobile application uses Angular and Capacitor while reusing the API as the source of business rules. Client screens reflect the user role, but sensitive operations are still checked on the server.

Data integrity and access

Financial maintenance is an authorized administrative operation with audit history rather than an unrestricted edit to historical records. Community and payment information remains private; this portfolio entry uses only a high-level description of the implemented system.

Outcome

The implemented platform connects administration, contribution records and mobile workflows around a common backend. The focus is functional coverage and traceable record handling across administrative workflows.