Expense Technical Documentation
Summary
Technical scope covers architecture, ownership, domain/application/infrastructure, persistence, integrations, messaging, security, observability, quality, and limitations. Expense is a .NET 8 ASP.NET Core Minimal API service with domain-oriented layers, EF Core/PostgreSQL, transactional outbox, optional Workflow, Document receipts, Payroll/Notification outcomes, and Gateway-controlled compatibility. Native and compatibility behavior makes it Transitional. Every child page below is linked by sidebar; Business remains authoritative for business meaning, while API/Database/Events/UI/Operations/Reference/Troubleshooting remain future foundation sections.
Audience
Backend and frontend developers, QA, architects, DevOps, support, and new engineers.
Overview
Use the ordered Technical sidebar for every architectural area. Related Business, future API, Database, Events, UI, Operations, Reference, and Troubleshooting sections preserve separation of concerns.
Technical pages
- architecture
- service responsibilities
- project structure
- layered architecture
- domain model
- expense claim aggregate
- value objects
- receipt reference model
- application layer
- infrastructure layer
- repository and unit of work
- cqrs and dispatch
- command flow
- query flow
- validation
- tenant context
- workflow integration
- payroll integration
- notification integration
- document integration
- identity boundary
- gateway interaction
- messaging and outbox
- idempotency boundary
- dependency injection
- configuration
- security boundaries
- observability
- health checks
- performance
- testing architecture
- known limitations
- future evolution
Source References
microservices/src/expense-service/Program.cs
Related Articles
See Also
Keywords
- Expense technical
- Technical Overview
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly