Receipt Reference Model

Summary

Expense owns receipt references; Document Service owns content. Add stores content before linking metadata. Remove deletes only the reference, not stored content. Retention, access, orphan cleanup, and cascade governance require confirmation.

Audience

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

Source References

• microservices/src/expense-service/Application/Commands/ReceiptCommands.cs

Related Articles

• Technical overview
• Business documentation

See Also

• Expense module

Keywords

• Expense technical
• Application/Commands/ReceiptCommands.cs

Revision Information

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