Expense Data Consistency and Reconciliation

Summary

Reconciliation spans several independently owned states and must remain read-only until the owning team approves a corrective action.

Comparison	Safe evidence
Native vs compatibility claim	Parity/backfill validator and service responses
Expense reference vs receipt content	Reference metadata and Document-owned existence evidence
Claim vs Workflow	Workflow linkage, terminal state, callback/audit evidence
Claim vs Payroll	lifecycle outcome, outbox, processed identity, projection state
Claim vs Notification	outbox publication, consumer processing, message/delivery evidence
Routing state vs system of record	gateway route source and cutover evidence

Routing rollback does not remove migrated rows or undo downstream projections. Do not edit persistence directly, copy sensitive payloads, or infer delivery from publication alone.

Requires confirmation

Correction authority, reconciliation cadence, canonical evidence sources, and cross-team sign-off require confirmation.

Source References

• microservices/src/expense-service/Application/Compatibility/ExpenseCompatService.cs
• microservices/src/expense-service/Backfill/ExpenseBackfillValidator.cs
• microservices/src/expense-service/Application/Commands/ReceiptCommands.cs
• microservices/src/payroll-service/Messaging/PayrollReadModelConsumer.cs
• microservices/src/notification-service/Application/NotificationDispatcher.cs

Related Articles

• Expense operations documentation
• Expense troubleshooting
• Expense technical documentation

See Also

• Expense events
• Expense module

Keywords

• Expense operations
• Data Consistency

Revision Information

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