How do I reconcile COD remittances from courier partners?
Match every delivered COD order to the courier’s remittance, catch short payments and delays, and keep cash-on-delivery money from going missing.
Anadoris Digital · · 4 min read

Cash on delivery is still a large share of orders for many Indian D2C brands. The courier collects cash from the customer, holds it, and remits it to you or your shipping aggregator after a cycle, minus charges. Between delivery and remittance, the money is out of your sight.
Most leaks are small: a few orders missing from a remittance, a deduction nobody explained, an order marked delivered that the customer says they never received. Over months they add up, and without order-level matching nobody notices.
What you need to record for each COD order
- Order number and invoice number.
- Courier or aggregator and AWB number.
- COD amount to be collected.
- Delivery status and delivered date from tracking.
- Remittance reference and date when paid.
- Any deductions, such as COD handling charges, with reasons.
An ERP or order system connected to your couriers can fill most of these automatically. The remittance details come from the courier’s or aggregator’s remittance report.
How the reconciliation works
- Import the remittance file, usually a list of AWBs with amounts.
- Match each AWB to the delivered COD order in your system.
- Flag differences in amount, which often point to wrong COD values or deductions.
- Mark matched orders as paid and post the receipt against the customer or courier account.
- List delivered COD orders not yet remitted, with days since delivery.
- Raise unremitted orders past the agreed cycle with the courier or aggregator.
Courier charges and deductions
Some couriers remit the full COD amount and invoice their charges separately. Others deduct charges from the remittance. Either way, record charges as expenses and keep the COD receivable at the full collected amount. Netting them together hides both the true shipping cost and any unexplained short payments.
Check that COD handling charges match your contract or rate card. Errors in weight or zone can also show up as higher freight deductions.
Disputed deliveries
Occasionally a parcel is marked delivered but the customer says they never received it, or the courier records it as delivered and later reverses it. Keep these cases in a separate list. Ask the courier for proof of delivery, and do not mark the order as collected until the remittance actually arrives.
Using aggregators
If you ship through an aggregator that works with several couriers, the aggregator usually remits COD to you after collecting it from each courier. Your reconciliation is then with the aggregator. The same rules apply: match by AWB, track ageing and record deductions separately. Check whether the aggregator can offset COD against your shipping wallet, and make sure your books record both sides of that offset.
COD reconciliation checklist
- Every COD order has an AWB and COD amount in the system.
- Delivered status is updated from courier tracking automatically.
- Every remittance file is imported and matched by AWB.
- Charges are recorded separately from collections.
- Ageing report of delivered but unremitted COD orders.
- Disputed delivery list with follow-up owner.
- Monthly comparison of COD receivable in the ERP with the courier’s statement.
Remittance cycles and charges differ between couriers and aggregators and can change. Use the terms in your current agreement, not general expectations.
Reducing COD exposure in the first place
Reconciliation catches leaks, but less COD means less to reconcile. Use the ERP’s data to see which pin codes, products and customer types have high refusal rates or long remittance delays. Many brands confirm COD orders by call or message before dispatch, offer a small benefit for prepaid payment, or restrict COD above a certain order value or in specific areas.
These are business decisions with trade-offs, since COD can increase conversion. The point is to make them with data, by comparing the margin on COD orders after refusals and charges with prepaid orders on the same products.
Posting COD in the books
In accounting terms, a delivered COD order creates a receivable from the courier or aggregator, not from the customer. When the remittance arrives, the receivable is cleared against the bank receipt. Courier charges are posted as an expense, with GST input credit where the courier’s invoice allows it. Keeping these entries separate makes the courier ledger match their statement, which is the quickest way to spot a gap.
Finally, compare your courier ledger in the ERP with each courier’s own statement at month end. The two should agree on collections, remittances and charges. Any difference that is not explained by timing deserves a closer look, because it usually points to a missing remittance, a charge you did not expect or an order recorded twice.
Where to start
- Pull the last few months of COD orders and remittance files.
- Match them by AWB in a spreadsheet to measure the size of the gap.
- Raise any old unremitted orders with each courier.
- Set up automatic import and matching in your ERP.
- Review the ageing report every week.
Anadoris Digital can connect courier tracking and remittance files to your ERP so COD reconciliation runs as a routine rather than a quarterly clean-up.
Related service: ERP Solutions · More on this topic: ERP Solutions articles
