The four events you should separate
A COD order can be shipped, delivered, collected and paid to the merchant at different times. Treating those statuses as one event creates accounting and operational gaps.
A basic reconciliation workflow
Start with the order ID and shipment status. Confirm delivery, then match the amount expected from the courier, the amount actually collected and the payout received.
Where problems usually appear
Failed delivery, return-to-origin, courier fees, delayed settlements and manual spreadsheets can all create discrepancies.
What a connected system changes
When order, courier and financial data share the same context, teams can investigate exceptions instead of rebuilding the whole reconciliation.
Controls that make reconciliation auditable
A reliable process should preserve the order reference, courier reference, expected COD amount, delivery status, collection status, payout batch and any fee or deduction. The goal is not only to calculate an outstanding total, but to explain exactly which orders created it.
Metrics management should review
Useful controls include delivered-but-unpaid value, average settlement age, failed-delivery rate, return-to-origin value, courier deductions and unresolved exceptions by settlement period.
Every event should remain connected to the product, contact or transaction that created it. That is what lets ERP explain a number instead of only displaying it.