Expense Compatibility API

Summary

| Method | Compatibility path | Purpose |

Audience

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

Reference Content

Method	Compatibility path	Purpose
POST	/api/hr-operations/expenses	Create a Pending claim from the legacy shape
POST	/api/hr-operations/expenses/{legacyId}/approve	Approve after Payroll frozen-period guard
POST	/api/hr-operations/expenses/{legacyId}/reject	Reject with reason
DELETE	/api/hr-operations/expenses/{legacyId}	Delete Pending claim
GET	/api/salary/approved-expenses	Return approved monthly totals grouped for Payroll compatibility

A supplied status on create is ignored; server lifecycle remains authoritative. Compatibility may approximate missing employee linkage from legacy identity. It has no Paid or receipt operation. Shape parity is Transitional and authorization parity requires confirmation.

Source References

• microservices/src/expense-service/Api/ExpenseCompatEndpoints.cs
• microservices/src/expense-service/Application/Compatibility/ExpenseCompatService.cs

Related Articles

• Expense technical documentation
• Expense business documentation

See Also

• Expense module

Keywords

• Expense API
• Compatibility Expense

Revision Information

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