Known Limitations

Summary

No Draft/Submitted, editing, item lines, policy engine, cancellation/resubmission, payment execution/reconciliation/reversal, or content cascade delete. Manager authority and authorization parity are unclear. Workflow/routing are Transitional. Health, metrics, caching, tests, reporting, correction, and replay governance have gaps.

Audience

Backend and frontend developers, QA, architects, DevOps, support, and new engineers.

Source References

• microservices/src/expense-service/Domain/Expense/ExpenseClaim.cs

Related Articles

• Technical overview
• Business documentation

See Also

• Expense module

Keywords

• Expense technical
• Domain/Expense/ExpenseClaim.cs

Revision Information

• Status: Draft
• Last reviewed: 2026-07-16
• Review cycle: Quarterly