COD remittance and reconciliation: when you get paid and where cash leaks
· by Lucas Reda · in Cash on Delivery · 12 min read

In COD the money passes through the courier, the carrier and the operator before it reaches you. How long that takes, where the amount goes missing and how to reconcile every week.
In cash on delivery, the money goes from the customer to the courier, then the carrier, then the operator, and only then to the seller. Across the market, that COD remittance takes anywhere from days to weeks, depending on how many intermediaries sit in the chain. At N1, payouts for delivered orders go out on D+2, reconciled order by order.
Sellers coming from card payments are surprised by two things in cash on delivery. The first is timing: the money is not captured at checkout. It only exists after delivery. The second costs more: silent losses. Without order-level reconciliation, the gap between what was delivered and what was paid out disappears inside a total that looks fine.
This guide covers the money path, the six places where COD cash usually leaks, a weekly reconciliation checklist and what to get in writing from any partner before you ship the first order.
How the money moves in COD
A card order moves through a payment gateway. A COD order moves through logistics. Four hands, in this order:
- Customer to courier. The customer pays at the door, at a pickup point or at a locker, in cash or by card, depending on what the service accepts.
- Courier to carrier. The courier settles the day's collections. The carrier consolidates amounts per shipper.
- Carrier to operator or platform. The carrier remits to whoever contracted the shipping, usually in batches, on its own cycle.
- Operator to seller. The operator reconciles, deducts what was agreed and pays out the net amount.
Each hand-off has its own timing and rules. A public example makes the design clear. The general terms of Hungary's national post, Magyar Posta, state that the cash on delivery amount (árufizetés) is transferred to the sender's bank account no later than the second working day after delivery, or paid in cash by the fourth working day. The same document says transfers to the same account are bundled into a single daily transfer, regardless of how many parcels it covers.
That detail explains half of all reconciliation problems. One amount lands in the bank. The orders behind it have to be rebuilt from a report. Without that report, nobody knows whether yesterday's batch had 40 orders or 39.
And that is only the first leg. If an operator, aggregator or fulfillment partner sits between the carrier and you, each one adds its own closing cycle.
When do I get paid for COD orders?
It depends on how many legs the money travels and how each leg closes. Broadly:
- Carrier to the shipping contract holder: some national posts publish short terms for their own leg, like Magyar Posta's two working days. Others, like the terms of Poczta Polska's Pocztex service, define the service (collect from the recipient, then forward to the sender's address or bank account) and leave the maximum amount to the price list or contract, with no payout deadline in the general terms.
- Operator to seller: this is where the timeline stretches. Weekly, fortnightly and monthly cycles all exist in the market, with or without a minimum withdrawal amount. There is no consolidated public data on this. What exists is each partner's contract.
So the right question is not "how long does COD take" but "how long does it take with this partner, counted from which event". D+2 from delivery is very different from D+2 after month-end close.
With the N1 cash on delivery service, payouts for delivered orders go out on D+2, to a global account or in crypto.
Even with a short payout term, COD cash flow is not card cash flow. You pay for ads today and the money lands after delivery. Model the working capital and the COD margin before you scale spend.
Where COD cash leaks
COD leaks are rarely fraud. They are almost always small discrepancies nobody saw, repeated across hundreds of orders. The six most common:
1. Delivered but never settled
Tracking says "delivered", but the amount never shows up in any batch. A misread barcode, a delivery recorded without collection, an amount stuck at one leg. If you only check the payout total, this order does not exist for you.
2. Collected amount differs from the order value
The customer paid less than the order price. Typical causes: a discount given at the door, a product swap, a coupon applied after the label was printed, rounding. Poczta Polska's terms, for instance, allow the COD amount shown to recipients by SMS at pickup points and lockers to be rounded to whole złoty. Pricing in round local-currency amounts removes the cent-level gaps that compound.
3. Currency conversion
In Poland (PLN), Hungary (HUF), Romania (RON) and the Czech Republic (CZK), customers pay in local currency, not euros. The European Central Bank lists these countries as EU members outside the euro area. In Hungary, COD is collected in HUF. If you are paid in another currency, someone converted it. Ask which rate, from which date, with what spread. In a hypothetical example, a 1.5% spread on your whole volume can outweigh many of the fees written into the contract.
4. Fees deducted without detail
The payout arrives net, with one line for "fees" or "adjustments". Without a per-order breakdown (collection fee, outbound shipping, return shipping, storage, handling) you cannot check whether the agreed rate card was applied. An aggregated line is a line you cannot audit.
5. Returns counted as deliveries, and the reverse
"Delivered", "refused" and "returned" mean different things financially:
- Delivered: creates a receivable and a fee payable.
- Refused: no revenue, plus outbound shipping, return shipping and handling.
- Returned after payment: revenue first, then a reversal. In the EU, consumers have 14 days to withdraw, counted from delivery, according to the official Your Europe portal.
If a report lumps all three into "not delivered", your COD refusal rate disappears from view. If a refused order shows as delivered, you will expect money that never existed. If a return is not shown as a reversal, the reversal arrives later, unannounced, in a future batch.
6. Orphan orders
Two kinds. An order with no financial line: shipped, but never marked paid, refused or returned. And a financial line with no order: a credit or debit that matches no order ID in your store. Both belong on a named exceptions list with a value, not as a residue in a sum.
A seventh, if customers pay by card at the door
In several markets, customers pay COD by card on the courier's terminal. In Hungary, a PwC survey with the national e-commerce association found card-on-delivery more popular than cash-on-delivery (35% vs 30%). Cards bring chargebacks into COD. Poczta Polska's terms state that a contract shipper accepting card payment for the COD amount bears full responsibility for chargeback claims. Check whether your contract says the same and how reversals appear in the report.
Weekly COD reconciliation checklist
Block one hour a week. Daily reconciliation is overkill for most operations. Monthly is too late, because claim windows are short. The general terms of CTT Expresso in Portugal, for example, give 30 days from the date the collection should have been received to file a written claim for a COD amount that was not settled.
Match the payout report against your order base and check:
| Report field | What to check | Red flag |
|---|---|---|
| Order ID and tracking number | Every order shipped this week appears in some status | Order shipped with no line for more than 10 days |
| Final status | Delivered, refused and returned are separate | Only "delivered" and "not delivered" exist |
| Expected COD amount | Equals the store order price, in local currency | Gaps on orders with no swap or discount |
| Declared collected amount | Equals the expected amount | Repeated lower amounts, or rounding always down |
| Delivery date | Matches tracking | Delivery date after the payout date |
| Batch date and number | Every delivered order lands in a batch | Delivered order older than the contract term and in no batch |
| Collection fee | Matches the contract rate card | Fee varies by order with no explanation |
| Outbound and return shipping | Return shipping only on refused and returned orders | Return shipping charged on a delivered order |
| Currency and FX rate | Rate, date and source are stated | No rate stated, or worse than the day's reference |
| Adjustments and reversals | Each adjustment points to an order | "Adjustments" line with no order ID |
| Batch total | Sum of lines equals the amount credited | Gap between the sum and the bank statement |
Then track three numbers week over week:
- Receivables by age. Delivered but not yet paid out, in buckets of 0 to 7, 8 to 14 and 15+ days. Ageing money is a signal before it is a problem.
- Open discrepancies. Count and value, with the date opened. If the list only grows, your dispute process is not working.
- Acceptance rate by country and product. It drives your margin and your read of COD by country in Europe.
What to get in writing from any partner
Before the first order, make sure the contract or proposal answers:
- Payout term and start event. D+how many, counted from delivery, collection, batch close or month end?
- Report format. Order by order, with your store order ID, tracking, status, collected amount, fees and batch date. As CSV or API, not only PDF.
- Separate statuses. Delivered, refused, returned and lost as distinct states.
- FX. Collection currency, payout currency, rate source, reference date and spread.
- Fee breakdown. Every deduction tied to an order and a rate-card line.
- Chargebacks and reversals. Who is liable when the customer paid by card at the door, and how reversals show up.
- Dispute window and channel. How many days you have and where to send it.
- Withdrawals. Minimum amount, frequency, accepted accounts and international transfer cost.
If a partner will not answer in writing, you already have your answer.
Local currencies and the Gulf
Of the 16 markets where N1 runs COD, four in Europe collect in their own currency: Poland, Hungary, Romania and the Czech Republic. Bulgaria adopted the euro on 1 January 2026, according to the ECB. Croatia, Slovakia, Spain, Portugal, Greece, Germany and Italy already collect in euros. In the Gulf, each country has its own currency (Saudi riyal, UAE dirham, Kuwaiti dinar, Qatari riyal).
For reconciliation, the rule is simple: check each order in the currency it was collected in, then convert. Converting first buries the discrepancy inside FX movement. See the country differences in the COD Europe map 2026 and in COD in the Gulf vs Europe.
Worked example with round numbers (hypothetical)
An operation in Poland ships 500 orders at 200 PLN in one week.
- 380 delivered, 100 refused, 20 still in transit.
- Expected value of delivered orders: 380 × 200 = 76,000 PLN.
- The batch arrives at 75,200 PLN gross.
An 800 PLN gap looks like rounding. Order-level reconciliation shows 3 delivered orders never settled (600 PLN) and 4 orders collected with a 50 PLN doorstep discount (200 PLN). The first group gets disputed. The second becomes a customer-service rule. Without matching by order ID, those 800 PLN would pass as "normal" and repeat every week.
How N1 handles reconciliation
At N1, each delivered order is reconciled against the amount collected at the door and added to your balance. In the dashboard, each order's payment status shows whether it is unpaid, paid or transferred (see order status), and the N1 dashboard shows balance, forecast and payout history. When you view amounts in another currency, the dashboard shows the rate used, as covered in dashboard filters. Refused and returned orders are separate states.
Frequently asked questions
How long does COD remittance take?
Across the market, days to weeks. The carrier's leg can be short (Magyar Posta publishes up to two working days after delivery for bank transfers), but each intermediary adds its own cycle. At N1, payouts for delivered orders go out on D+2.
What is COD reconciliation?
Matching, order by order, the amount that should have been collected, the amount the carrier says it collected, the amount credited and the fees deducted. When all four agree, the order is closed. When they do not, the gap becomes a named exception with a value.
Am I paid in the customer's currency?
Customers pay in local currency: PLN in Poland, HUF in Hungary, RON in Romania, CZK in the Czech Republic, euros in N1's other European markets. If you are paid in a different currency, ask for the rate, date and source of the conversion.
What should I do when the payout does not match?
Split the gap by order, classify it (never settled, wrong amount, fee, FX, wrong status) and dispute it in writing within the contract window. Without order-level data there is nothing to dispute.
Can I withdraw to a global account or in crypto?
At N1, yes: withdrawals go to a global account or in crypto. Tax and FX treatment of what you receive depends on your structure. Check with your accountant.
How often should I reconcile?
Weekly works for most operations. It is frequent enough to dispute within windows like the 30 days in CTT Expresso's terms, and spaced enough for the week's batches to close.
Next step
If you want to sell cash on delivery in Europe or the Gulf with D+2 payouts and order-level reconciliation in your dashboard, see the N1 cash on delivery solution and the N1 dashboard. To discuss your operation, talk to a specialist.