vkumar0303/-schoolerp-accounting

Purpose and Solution Shape

SchoolERP is an early-stage .NET school ERP focused on a double-entry accounting module. The implemented core is a domain-driven accounting model with Entity Framework Core persistence; API, application, contracts, and UI projects are present but largely scaffolding. The solution root is SchoolERP.slnx.

Runtime Entry Points

Two executable hosts exist:

• ASP.NET Core API: src/SchoolERP.Api/Program.cs, configured through src/SchoolERP.Api/appsettings.json.

• Blazor web host: src/SchoolERP.Web/Program.cs, with root routing/UI in src/SchoolERP.Web/Components/App.razor and src/SchoolERP.Web/Components/Routes.razor.

The web project currently contains template pages and layout rather than accounting workflows. The API’s exposed endpoint surface cannot be inferred beyond its host bootstrap.

Accounting Domain Core

The authoritative business layer is src/SchoolERP.Domain/Accounting. It models organizational scope and chart-of-accounts hierarchy:

• Organization and branch ownership: Organization.cs, Branch.cs.

• Account classification and balances: LedgerAccount.cs, AccountGroup.cs, AccountType.cs.

• A proposed school-specific seed chart: DefaultSchoolChartOfAccounts.cs.

Domain entities inherit shared identity/error primitives in src/SchoolERP.Domain/Shared/Entity.cs and DomainException.cs, keeping accounting invariant enforcement independent of transport and database concerns.

Financial Calendar and Posting Lifecycle

Financial control is represented by fiscal years and accounting periods:

• FinancialYear.cs and FinancialYearStatus.cs

• AccountingPeriod.cs and AccountingPeriodStatus.cs

Transaction processing centers on vouchers and journal entries:

• Source/approval-facing voucher lifecycle: Voucher.cs, VoucherStatus.cs, VoucherType.cs.

• Double-entry representation and lifecycle: JournalEntry.cs, JournalEntryLine.cs, JournalEntryStatus.cs.

• Posting and reversal orchestration: AccountingPostingService.cs, AccountingReversalService.cs.

The intended control flow is voucher/journal creation → validation of accounts, balances, period/year status, and entry state → posting via the domain service → reversal through a dedicated domain service rather than editing posted records.

Persistence Boundary

SchoolERP.Infrastructure owns the EF Core boundary. src/SchoolERP.Infrastructure/Persistence/SchoolErpDbContext.cs maps domain entities to relational storage, while the per-aggregate configurations under Persistence/Configurations define schema and relationships. SchoolErpDbContextFactory.cs supports design-time context creation.

The initial durable schema is captured in:

• src/SchoolERP.Infrastructure/Migrations/20260805083641_InitialAccountingPersistence.cs

• src/SchoolERP.Infrastructure/Migrations/SchoolErpDbContextModelSnapshot.cs

Database provider and connection details are not visible from the supplied tree; configuration is expected to come from host appsettings files.

Application and Contract Boundary

src/SchoolERP.Application and src/SchoolERP.Contracts establish intended boundaries for use cases and transport DTOs, but each currently has only Class1.cs. Consequently, hosts should not yet depend on a mature application-command/query layer; the concrete implemented behavior resides in the domain and infrastructure projects.

Legacy Discovery and Migration Context

Repository-root reports and scripts support discovery of legacy financial data rather than runtime operation. Key artifacts include sql/legacy_financial_discovery.sql, financial_data_source_map.md, receipt_reconciliation_report.md, and the accounting migration proposal in docs/legacy_accounting_mapping_proposal.md. Python scripts such as process_schema.py and generate_reports.py appear to profile and document source data for future migration planning.

Infrastructure and External Dependencies

Material runtime technologies are .NET/ASP.NET Core, Blazor, and EF Core migrations. No deployed infrastructure, identity provider, messaging system, payment gateway, or external SaaS integration is evidenced in the tree. Bootstrap is bundled under src/SchoolERP.Web/wwwroot/lib/bootstrap for the web host’s presentation layer.