COD (Cash on Delivery): Delivery-Payment Release and Fraud Controls

COD Is a Release and Collection Design

The SSDER glossary defines COD as collect cash on delivery. In procurement, COD changes the handoff: the carrier or seller may be asked to collect payment when the customer receives the goods. The term does not by itself say whether the buyer may inspect first, whether partial delivery is allowed, or when title and risk transfer.

Write the trigger precisely. Is payment due at the first delivery attempt, after count and visible inspection, after a signed proof of delivery, or after a verified electronic transfer? State who owns the goods during refusal, delay, return and cash transit.

Define Collector, Payment Method and Evidence

Name the collector and authority: seller, carrier, agent, driver, marketplace or payment provider. Specify currency, maximum amount, accepted cash or electronic methods, receipt format, refund route and settlement deadline. Drivers should not improvise a bank-account change or accept an unverified transfer screenshot.

The delivery record should identify payer, receiver, package count, condition, amount due, amount received, method, receipt, time, location and collector. Use a secure reference that links the transaction to the PO, order, invoice, shipment and proof of delivery.

Separate Delivery, Inspection and Acceptance

COD can create pressure to sign before checking the load. Define whether the receiver may inspect packaging and count, what visible damage or shortage is recorded, and whether a reservation still allows payment or triggers refusal. Delivery, payment and technical acceptance should be separate fields.

For high-value or regulated goods, consider a controlled payment provider, identity check, two-person handoff or pre-authorised limit. The aim is to reduce theft and dispute without making the driver responsible for a technical quality decision.

Returns, Refusals and Reconciliation

A refused COD delivery needs an immediate status, secure return, inventory disposition, payment reversal or refund rule and cost owner. Partial delivery should state whether the collector takes the amount for delivered units only or returns the entire order. Do not let an unpaid return become an unowned stock movement.

Reconcile daily or per settlement cycle: order, invoice, COD amount, delivery proof, receipt, bank or provider settlement, fee, refund, return and exception. Investigate short collections, duplicate receipts, chargebacks and late remittance by route, collector and customer.

Worked Example: Payment Screenshot at the Door

A receiver shows a mobile screenshot for a COD payment and asks the driver to release the pallet. The account name is different, the transfer is pending and the invoice amount excludes a newly added fee. The driver signs delivery and the seller later cannot recover the balance.

The corrected process accepts only an authorised payment reference confirmed by the provider, records the receiver and amount, and blocks release when the collection rule fails. The contract defines return, refund, fee and fraud escalation so the driver is not forced to decide alone.

Metrics and Governance

For COD cash on delivery procurement controls, measure both service and evidence quality. Useful indicators include first-pass acceptance, exception rate, response time, unplanned cost, document completeness, damage or discrepancy rate, and the percentage of shipments that follow the approved process. A dashboard should distinguish a supplier failure from a carrier, terminal, broker or internal master-data failure.

Review the metric trend with procurement, logistics, finance, quality and the responsible specialist. Use a monthly exception sample to test whether the control worked in a real transaction, not just whether a field was filled. Repeated exceptions should change the sourcing strategy, contract, lane design or supplier development plan.

Keep the control proportionate to risk. High-value, regulated, time-critical or safety-sensitive cargo needs stronger evidence and faster escalation than a routine shipment. Record the decision owner, approval date, source documents and follow-up action so the next buyer can understand the operating history.

Supplier and Carrier Questions

• Which COD or related glossary condition is assumed in your quotation, procedure or service description?
• Which party owns each data field, physical handoff, inspection, document and exception?
• What evidence will be available before release, loading, movement, receipt, invoice approval or claim?
• What changes require advance notice, requalification, a revised price or a new risk decision?
• How will the supplier report incidents, delays, mismatches and corrective actions, and within what response time?

Implementation Sequence

Implement the control in a small, representative lane first. Capture the baseline process, test the required data and evidence, run a real transaction, and review every exception with the people who performed the work. Do not declare the control effective only because a supplier signed a procedure.

After the first three shipments or operating cycles, update the purchase-order clause, work instruction, scorecard and training. Scale the control to other suppliers only when the evidence is repeatable and the owner can explain what happens when the normal path fails.

Common Mistakes to Avoid

• Using COD without defining delivery, inspection, payment, title and risk milestones.
• Allowing drivers or agents to accept unverified transfers, bank-account changes or informal receipts.
• Treating a signature as proof of full quantity, condition and payment.
• Leaving refusal, partial delivery, return, refund and chargeback ownership unclear.
• Failing to reconcile collection, invoice, delivery, settlement, fees and exceptions.

Procurement Implementation Checklist

• Define COD trigger, payer, collector, payment methods, limit and currency.
• Specify identity, receipt, proof-of-delivery and payment-verification evidence.
• Separate delivery, inspection, payment, title, risk and technical acceptance statuses.
• Set partial, refusal, return, refund, chargeback and fraud workflows.
• Protect cash, devices, payment references, bank changes and customer data.
• Reconcile order, invoice, receipt, settlement, fees, returns and collector performance.

Frequently Asked Questions

Related Kurums Guides

• Declared Value Controls
• Cargo Manifest Controls
• Customs EDI and Entry Data
• Collecting Banks and Documentary Collection
• Combination Rates
• Blanket Rates

Standards and Authoritative Sources

• U.S. Trade.gov — Trade Finance Guide
• FTC — Avoiding scams and fraud in business
• UCC — Uniform Commercial Code
• ISO — ISO 31000 Risk Management

Glossary terms covered: COD, CASH ON DELIVERY, payment on delivery, proof of delivery, collection, return, fraud