5 Accounting Challenges Of Cash On Delivery Across The EU: Ecommerce Sellers’ Reality

Published:
September 11, 2026
5-accounting-challenges-of-cash-on-delivery-across-the-eu:-ecommerce-sellers’-reality

Two people handling a delivery paid for by cash.

Image source

A cash-on-delivery order can look complete in an ecommerce dashboard while still being unfinished in the accounting records.

The parcel may have left the warehouse, reached the customer, and been marked as delivered. Yet the seller might not receive the money collected by the courier until several days later. Between those two events, the business may already have VAT obligations, inventory movements, revenue entries, courier receivables, fees, or possible return exposure to account for.

That distinction becomes more important when an ecommerce business sells across several European Union markets. EU VAT provides a common framework, but national rules, special schemes, local registrations, inventory locations, and operational practices can change how individual transactions need to be handled.

For finance teams, therefore, the useful question is not simply, “Was the order delivered?” It is: “Which event should trigger revenue recognition, VAT reporting, a courier receivable, inventory movement, and cash recognition for this particular transaction?”

Understanding those separate events is the foundation of reliable cash on delivery accounting.

1. VAT Chargeability Does Not Follow One Universal COD Rule

The first accounting challenge is separating the customer’s payment method from the VAT tax point.

It can be tempting to assume that because the customer pays cash when the package arrives, VAT should also be recorded when that cash eventually reaches the seller’s bank account. That is not generally how the system works.

Under the EU VAT framework, VAT normally becomes chargeable when goods or services are supplied. Member States can apply special rules in particular situations, including permitted cash-accounting arrangements, which is why the seller’s circumstances and the applicable national rules still matter.

Delivery, collection, and settlement are different events

Consider a simple COD sequence:

  • Day 1: The seller dispatches the parcel.
  • Day 3: The courier delivers it and collects €100 from the customer.
  • Day 5: The courier confirms the collection in its settlement report.
  • Day 8: The seller receives the money in its bank account.

Those four dates should not automatically be treated as one accounting event.

For businesses applying IFRS, revenue recognition is based on when the promised goods or services are transferred to the customer, meaning when the customer obtains control, rather than simply when cash enters the bank account.

VAT timing requires its own assessment.

Image source

2. Courier Collections Create a Separate Reconciliation Layer

Card transactions normally produce a payment trail between the order platform, payment processor, and bank. Cash on delivery inserts another party into that flow.

The courier or logistics provider physically receives the customer’s money. The seller therefore has an economic claim on money that has already been collected but has not yet reached its bank account.

That intermediate stage is one of the most important differences in COD bookkeeping.

A clearing account helps separate sales from cash

A practical accounting structure is to use a COD clearing account or courier receivable.

Imagine a €120 order is successfully delivered. Instead of waiting for the bank deposit before recording the entire transaction, the accounting system can track the amount temporarily due from the logistics provider.

When the courier eventually settles the balance, the business clears that receivable against the bank deposit and records any fees, adjustments, or deductions separately.

For example:

Customer order value: €120
Cash collected: €120
Courier or COD fee: €4
Amount transferred: €116

If the seller looks only at the bank statement, the €116 deposit can easily be mistaken for €116 of revenue. In reality, the underlying sale was €120 and the difference may represent a logistics expense.

A structured cash on delivery service becomes easier for an accounting team to work with when settlement data can be matched against individual orders, collections, deductions, returns, and remittances.

The point is not simply to know how much money arrived. Finance needs to understand why that exact amount arrived.

Reconciliation should happen at the order level

A monthly courier statement showing only a total payout may be insufficient when an ecommerce business handles hundreds or thousands of COD shipments.

For each transaction, the finance team should ideally be able to identify:

  • ecommerce order ID
  • shipment or tracking ID
  • invoice amount
  • delivery date
  • amount collected from the customer
  • currency
  • COD fee
  • shipping charge
  • return or refusal status
  • settlement batch
  • remittance date
  • amount deposited into the seller’s bank account

3. Settlement Timing Can Distort Working-Capital Reporting

COD can create healthy sales numbers without creating equally strong bank balances on the same day.

That difference matters especially for fast-growing ecommerce sellers.

Suppose two businesses each complete €100,000 of COD deliveries during a week. Seller A receives courier settlements every few days, while Seller B receives one larger remittance later in the month.

Their revenue may appear similar, but their short-term liquidity positions can be very different.

Collected cash is not necessarily available cash

Until the courier remits the funds, part of the seller’s working capital is effectively sitting outside its bank account.

That can affect decisions involving:

  • supplier payments
  • payroll
  • VAT payments
  • advertising budgets
  • inventory purchases
  • freight costs
  • warehouse expenses

This is why the courier receivable should be visible in management reporting rather than disappearing between “sales” and “bank.”

A finance team looking only at its ecommerce dashboard might conclude that €40,000 was generated during the week. A treasury report might show that only €22,000 is currently available. The difference may include unsettled COD collections, returns, processing deductions, or timing differences. In such cases, the more frequently the COD collection fee is paid out to the seller, the more profitable the entire model becomes. Few COD fulfillment providers offer regular, frequent payouts, as this requires a robust internal system, like the one WAPI has established to ensure weekly payments to sellers.

4. Inventory Location Changes the Accounting Map

Where the customer lives is only one part of EU ecommerce accounting.

Finance teams must also understand where inventory was stored before the order was fulfilled and how it moved between countries.

That becomes increasingly important as sellers move from shipping everything from one central warehouse to holding stock closer to major customer markets.

Local fulfilment can create different VAT flows

Consider an ecommerce company serving customers in Spain.

Shipping an eligible B2C distance sale from inventory located in another Member State can involve different VAT reporting mechanics from fulfilling the customer directly from inventory already stored in Spain.

If the business operates through a warehouse in Spain, the accounting system should be able to distinguish Spanish domestic transactions from cross-border inventory movements and other EU sales rather than treating every Spanish customer order as the same type of transaction.

The same principle applies when a business distributes inventory across Poland, Romania, Italy, Germany, or other Member States.

Stock location can affect VAT registrations and reporting obligations, while the movement of the goods can determine how a transaction is classified.

5. Failed COD Deliveries Need Their Own Accounting Status

One of COD’s defining features is that dispatch does not guarantee collection. A seller may pick, pack, and ship an order only for the customer to refuse the parcel or for delivery attempts to fail. That creates a different accounting outcome from a successfully delivered and collected order.

“Shipped” should never equal “paid”

Reporting problems start when the ecommerce, warehouse, courier, and accounting systems each define a “completed” order differently. The warehouse calls it complete at dispatch, the 3PL platform calls it fulfilled, and the courier calls it out for delivery. All while the finance team still has no confirmation that the parcel was handed over and the cash collected.

For COD transactions, accounting statuses should ideally distinguish:

  • order confirmed
  • picked and packed
  • dispatched
  • delivery attempted
  • delivered
  • cash collected
  • cash pending settlement
  • remitted
  • refused
  • returned to warehouse
  • cancelled or written off

A Practical COD Accounting Control Checklist

The strongest process connects ecommerce, warehouse, courier, tax, and bank data instead of asking finance to reconstruct transactions afterward.

A business reviewing its COD accounting setup can begin with the following controls.

Separate the important dates

Each order should preserve, where applicable:

  • order date.
  • dispatch date.
  • delivery date.
  • collection date.
  • invoice date.
  • return date.
  • settlement date.

Maintain a dedicated courier clearing account

Cash collected but not yet remitted should remain visible. The account should be reconciled regularly against courier settlement files and bank deposits.

Reconcile gross amounts before net payouts

Start with what the customer paid. Then separately identify courier charges, COD fees, return costs, adjustments, and other deductions before reaching the net amount transferred to the bank.

Track fulfilment country

The accounting export should contain the actual inventory or warehouse location used for the order. Customer country alone is not enough to understand the complete VAT and inventory flow.

Give failed orders distinct statuses

Refused, undelivered, returned, and cancelled COD orders should not be grouped with completed collections. This makes revenue reversals, VAT corrections, and inventory adjustments easier to identify.

Review country rules separately

An EU-wide chart of accounts can support consistent reporting, but tax rules should still be configured and reviewed country by country.

The European Commission’s framework provides the starting point, while national tax authorities provide the detailed rules that determine how businesses apply VAT locally.

Build the Ledger Around Events

Cash on delivery accounting becomes much easier to understand when the business stops treating an e-commerce order as a single financial event.

One order can create several separate moments: inventory leaves the warehouse, the parcel reaches the customer, revenue becomes recognisable, VAT becomes chargeable, the courier collects cash, a receivable arises, fees are deducted, and the final settlement reaches the bank.

A refused parcel produces another sequence entirely. When those events are captured separately, finance teams gain cleaner books, more useful working-capital reports, and a much clearer picture of where the business’s cash actually sits.

What Is EcomBalance? 

A screenshot of the EcomBalance website home page.

EcomBalance is a monthly bookkeeping service specialized for eCommerce companies selling on Amazon, Shopify, eBay, Etsy, WooCommerce, & other eCommerce channels.

We take monthly bookkeeping off your plate and deliver you your financial statements by the 15th or 20th of each month.

You’ll have your Profit and Loss Statement, Balance Sheet, and Cash Flow Statement ready for analysis each month so you and your business partners can make better business decisions.

Interested in learning more? Schedule a call with our CEO, Nathan Hirsch.

And here’s some free resources:

This article originally appeared on EcomBalance Blog and is available here for further discovery.

FIND US ONLINE

WEEKLY DTC INSIGHTS

TRUSTED BY THOUSANDS

TRUSTED PARTNER

Choose a language