Skip to main content
Free planning resources

Reconcile a COD order with the money received

A delivered parcel and a courier payment are different events. Use this worked example to agree the references, deductions and staff review your online store needs before building a settlement dashboard.

By BringPak Editorial Team · Updated 20 October 2026. All five records and amounts are invented. They are not courier rates, client results or a statement of tax treatment. BringPak provides website and workflow development; this resource does not provide courier collection services.

Download the blank COD settlement review worksheet (TXT)

Five records with different review outcomes

For a delivered order with confirmed amounts, this exercise uses expected remittance = COD collected − agreed deductions. Difference = remitted amount − expected remittance. A negative difference needs investigation; it does not by itself prove a courier owes that amount. The exercise assumes one parcel and one allocated remittance per order, with no split shipment, refund or batch adjustment.

Synthetic amounts in PKR. Unconfirmed means missing information, not zero.
Order / trackingParcel stateCOD amountDeductionsRemittedExpectedDifference
DEMO-101SAMPLE-ADelivered2,5001802,3202,3200
DEMO-102SAMPLE-BDelivered3,2002202,8802,980-100
DEMO-103SAMPLE-CReturned1,8001800Not calculatedNot calculated
DEMO-104SAMPLE-DIn transit4,100UnconfirmedUnconfirmedNot calculatedNot calculated
DEMO-105SAMPLE-EDelivered2,000Unconfirmed1,800Not calculatedNot calculated

DEMO-101: delivered

Listed amounts match; verify the statement and receipt.

DEMO-102: delivered

Less remitted than the listed expectation; investigate the difference.

DEMO-103: returned

No delivered-sale remittance expected; review return charges separately.

DEMO-104: in transit

Wait for a verified delivery and settlement statement.

DEMO-105: delivered

Unresolved: confirm deductions and remittance before reconciling.

Investigate the PKR 100 difference

DEMO-102 has PKR 3,200 in COD and PKR 220 in listed deductions, giving an expectation of PKR 2,980. The allocated remittance is PKR 2,880, a difference of −PKR 100. Compare the original statement, shipment reference and bank or wallet receipt. An omitted agreed adjustment, an incorrect allocation or a missing payment can lead to different next actions.

Do not overwrite the deduction just to make the row balance. Record what staff found, who reviewed it and which evidence supports a correction. If one payment covers many shipments, reconcile its batch total before allocating it to orders. A tracking label should not be counted twice when the same statement is imported again.

Keep returns and unknown charges visible

DEMO-103 is returned. Its PKR 1,800 order value is not delivered-sale cash received; the listed return charge needs a separate ledger review. Confirm the returned stock condition and the actual provider agreement. DEMO-104 is still in transit and must not be treated as collected cash.

DEMO-105 is delivered, but its deductions are unconfirmed. A PKR 1,800 remittance cannot be marked correct merely by assuming a PKR 200 fee. Leave the row unresolved until the statement supports the deduction. There is deliberately no whole-batch settlement total here because some records have missing amounts or different parcel states.

Specify the dashboard before commissioning it

  • Match order, shipment and statement references. Define split parcels, duplicate statements and re-booked tracking numbers.
  • Keep delivery evidence, expected amounts, provider deductions, remittance allocation and actual receipt as separate fields.
  • Distinguish missing information from zero. Require a reason and evidence reference for staff corrections.
  • Test one matched order, one discrepancy, one return and one missing fee before accepting the workflow.
  • Agree provider access, import frequency, statement formats, staff permissions and reconciliation ownership. A website build does not establish access to every courier API.

Use the example in your store brief

Read the COD order workflow guide, plan inventory and order records, or compare e-commerce development scope. For a Karachi business, see how we organise remote e-commerce project reviews.

Bring a synthetic statement sample and your unresolved rules to a workflow discussion. Remove customer details, credentials and private payment information from initial enquiries. About these planning examples.