Reconcile COD remittances from delivered AWB to bank receipt

The order report shows ₹20,000 in delivered cash-on-delivery orders. The courier statement shows ₹19,400, and the bank received ₹19,000. Calling the whole ₹1,000 gap a “COD shortfall” hides two different investigations.

COD reconciliation should explain how an eligible order amount becomes a carrier collection obligation, how that obligation enters a remittance, and how the remittance reaches the bank or other agreed settlement destination. A delivered status, a statement row and a bank credit are different evidence.

This guide follows a merchant or logistics finance team's courier COD account. Its decision is whether each supported obligation is explained by approved deductions and allocated cash. Marketplace commissions, promotional adjustments and seller-payout rules require their own settlement interpretation; they should not be imported into a courier ledger without review.

Define what is due before matching receipts

Start with the agreed population and due dates. Identify which delivered shipments carry a COD collection obligation, which have an authorised payment-mode change and which have an unresolved collection exception. A status alone does not establish that every expected amount was collected or is already overdue.

Record order identity, AWB and parcel relationship, customer charge, collection amount, delivery/collection status, agreed settlement timing and any authorised change. Preserve partial deliveries or split shipments rather than forcing every order into one AWB and one payment.

Shiprocket distinguishes an order report from a remittance report for delivered AWBs. That separation is useful when gathering the records for reconciliation. The account's actual settlement terms still determine what is due and when. Shiprocket — Choosing scheduled reports.

Build two bridges from the same example

In this illustrative closed-period example, ten delivered COD orders create a confirmed ₹20,000 settlement obligation. The remittance statement lists ₹600 in deductions and a net amount of ₹19,400.

There are two questions. Is the ₹600 deduction supported and authorised under the agreement? And why is the identified bank receipt ₹400 below the statement net?

If finance approves all ₹600 of deductions and later identifies another ₹400 credit belonging to the same batch, the bridge closes. If only ₹450 of deductions is supported, the current unexplained amount is ₹20,000 − ₹450 − ₹19,000 = ₹550: ₹400 not yet matched to cash plus ₹150 of disputed deductions. After the additional ₹400 is identified, only the ₹150 dispute remains. Keep the two cases linked to the same obligation without adding the original ₹1,000 gross gap again.

An over-remittance needs the same care. If identified cash were ₹19,500, the statement-to-cash balance would be −₹100 while the unsupported deduction remained ₹150. Their signed net is ₹50, but that does not resolve either case. Investigate the surplus credit and the deduction separately instead of offsetting them without authority.

Replay the ledger with editable inputs

The COD ledger sheet in the illustrative review workbook contains both the ₹20,000 obligation bridge and the separate ₹9,000 bank-allocation example below. All values are fictional. The cases are independent and must not be added together.

Start with ₹450 approved deductions and no later credit. The sheet shows a ₹400 statement-to-cash balance and ₹150 deduction dispute. Change the later identified credit to ₹400: the cash balance clears, while the dispute remains. Restore the starting values before testing a different system against the same answer key.

The source-completeness field is part of the comparison. Selecting No leaves the derived bridge unavailable; it does not turn missing rows into a zero obligation. A verified zero and an absent input also produce different results. The worksheet calculates a teaching example, while the finance reviewer still establishes the eligible population, contractual due basis and approved treatment.

Match at the right level

Use a settlement batch reference when available, together with the account, currency, date window and constituent AWBs. A bank credit covering several batches needs an allocation record; it should not be attached in full to each one.

For an illustrative allocation, batch R1 has ₹6,000 net outstanding and R2 has ₹4,000. A ₹9,000 bank credit supported by the remittance can allocate ₹6,000 to R1 and ₹3,000 to R2, leaving ₹1,000 on R2. Both controls must hold: total allocations cannot exceed the bank credit's available value, and allocations to a batch cannot exceed its supported outstanding amount. A later credit has its own bank identity and allocation.

Preserve unmatched cash as an explicit item. Do not force a bank receipt onto the nearest date merely to clear the queue. Similarly, a remittance file that repeats an AWB may be a correction, a split amount or a duplicate row. Its identity and version determine the treatment.

A reliable join explains the relationship; it does not discard inconvenient rows.

Route differences to people who can resolve them

Customer operations confirms authorised order and payment-mode changes. Logistics or the carrier account owner obtains remittance detail and challenges unsupported deductions. Finance matches cash and approves ledger treatment. IT resolves missing files, changed columns and failed imports.

The queue should show the amount, currency, due basis, original detection date, evidence and next action. Distinguish “not yet due”, “due but not stated”, “stated but not received”, “received but unidentified” and “commercial deduction disputed”.

Age items from the relevant contractual milestone and keep the calculation visible. A new import should not reset the age of an old unexplained balance.

Choose a repeatable daily process

A controlled workbook can support a small population if originals, transformations and decisions are preserved. Native settlement reports may handle part of the work. An integration becomes useful when mapping, batch allocation and exception carry-forward consume recurring effort.

Reconciliation flow: validate the eligible obligation → allocate remittance lines → review deductions → match bank credits → assign unresolved differences → confirm the approved outcome. When the bank reference is missing or a source file is incomplete, keep the affected population open.

Run import checks for row count, gross and net amounts, duplicate identities and source period. A file containing only part of the courier's day can still balance internally. Compare coverage with the expected shipment population before calling the period complete.

Measure what remains unexplained

Track unresolved value and age by exception type, matched bank value, disputed deductions and the time spent reviewing the same completed population. Distinguish money recovered from money that merely arrived within its agreed timing.

For a workbook, native courier report or integration, require the same observable results: both money bridges reconcile, the ₹9,000 credit is never allocated twice, an incomplete source period stays open and an unsupported deduction survives a later cash receipt. A high row-match percentage cannot substitute for those controls. Keep surplus credits visible as signed exceptions alongside the positive balances.

Before automating ledger entries, test partial remittances, a changed payment mode, a revised statement, a repeated file and a bank credit arriving in a later period. Finance should approve the accounting treatment separately from the matching logic.

Make each rupee traceable to a decision

The useful COD result is a bridge from confirmed collection obligation to settlement and cash, with every unresolved amount classified. Keeping deduction disputes and missing cash separate gives each owner a clear question to answer.

Next actions

1. Choose one courier and a completed period with agreed opening balances.
2. Reconcile eligible obligations, statement deductions and bank allocations separately.
3. Assign the remaining differences by cause and due basis.
4. Preserve the evidence and resolution reference through later credits.
5. Use recurring cases to define a bounded reconciliation pilot.

For a COD assessment, identify the courier account, completed period and the part of the obligation-to-bank bridge that remains unexplained.