Expense API Overview

Summary

Native APIs use a typed claim identifier and expose claims, decisions, Paid-state recording, receipts, workflow completion, and limited evidence/diagnostic reads. Compatibility APIs preserve legacy numeric identity and response shapes for existing clients.

Audience

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

Reference Content

Native APIs use a typed claim identifier and expose claims, decisions, Paid-state recording, receipts, workflow completion, and limited evidence/diagnostic reads. Compatibility APIs preserve legacy numeric identity and response shapes for existing clients.

Area	Native capability	Compatibility capability
Claims	List, retrieve, create, delete Pending	Create and delete Pending
Decisions	Approve and reject	Approve with Payroll freeze guard; reject
Paid state	Mark Approved claim Paid	Not confirmed
Receipts	Upload, list, download, remove reference	Not implemented
Workflow	Completion callback	Not confirmed
Evidence	Audit, timeline, outbox reads	Workspace claim bundle
Payroll	Event-driven relationship	Approved-expense monthly aggregation

Endpoint authorization parity requires confirmation; tenant context remains mandatory for tenant-scoped operations.

Source References

• microservices/src/expense-service/Api/ExpenseEndpoints.cs
• microservices/src/expense-service/Api/ExpenseCompatEndpoints.cs

Related Articles

• Expense technical documentation
• Expense business documentation

See Also

• Expense module

Keywords

• Expense API
• API Overview

Revision Information

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