Idempotency Boundary

Summary

A unique processed-event ledger exists but no inbound Expense consumer uses it. Terminal Workflow callbacks are duplicate-tolerant; outbox identities are unique; Payroll handles duplicate/stale projection events. Receipt upload, replay, ordering, and end-to-end deduplication remain gaps.

Audience

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

Source References

• microservices/src/expense-service/Infrastructure/ExpenseDbContext.cs

Related Articles

• Technical overview
• Business documentation

See Also

• Expense module

Keywords

• Expense technical
• Infrastructure/ExpenseDbContext.cs

Revision Information

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