Expense Receipt Management API

Summary

| Method | Path | Purpose |

Audience

API consumers, backend and frontend developers, QA, architects, implementation partners, and support.

Reference Content

Method	Path	Purpose
POST	/expense/claims/{claimId}/receipts	Store receipt content through Document Service and create a reference
GET	/expense/claims/{claimId}/receipts	List receipt references
GET	/expense/claims/{claimId}/receipts/{receiptId}/download	Stream Document-managed content
DELETE	/expense/claims/{claimId}/receipts/{receiptId}	Remove only the Expense reference

Upload requires file name and non-empty encoded content; document type/content type are supported metadata. Dependency failure is surfaced as unavailable. A metadata-only reference cannot be downloaded. Deleting the reference does not delete stored content. No compatibility receipt API, receipt-required policy, or confirmed receipt authorization policy exists.

Source References

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

Related Articles

• Expense technical documentation
• Expense business documentation

See Also

• Expense module

Keywords

• Expense API
• Receipt Management

Revision Information

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