COD Remittance Reconciliation

Couriers collect cash on your behalf and pay it back in batches. Checking those batches against your orders by eye, line by line, is slow, so short payments, missing orders and double fees tend to go unnoticed until they are too old to dispute. The cost is cash you delivered and never received.

Load your orders as a CSV (order reference and COD amount at least) and each courier statement as a CSV (reference and amount remitted, optionally fee, date and statement number). The app normalises references so ' ORD-10230', 'ord-10230' and '10230' can still match, then matches by order reference and falls back to waybill. For every order it says matched, short-paid, over-paid, not remitted yet, overdue or skipped, and it lists remittance lines that match no order. Totals show cash expected, cash received, fees and what is still outstanding, with ageing buckets and a tolerance for small rounding differences. The Disputes tab produces a list and a ready message for each courier, and you can export it as CSV.

What is inside:

• Data and settings, Summary, Orders, Ageing, Disputes and How it works tabs
• Column mapping, so your own export headers can be used
• Windows-1252, semicolon, tab and comma files, Arabic text and a byte order mark are handled
• A worked example with 70 invented orders and 3 invented statements, and EXAMPLE-DATA CSVs

How long a courier may take to remit, and what fees apply, come from your own courier agreement: they are settings, not facts the app knows. The app does not contact any courier and does not move money. It is not tax or legal advice, not an FTA-approved system, and no platform or courier endorses it.

How it differs from the receivables ageing tracker in the catalogue: that tracks customer invoices you issue. This matches courier cash remittances to individual COD orders, which is a different job.

Tested: every calculation was compared with an independent Python (Decimal) calculation on randomised cases, CSV edge cases (quotes, commas, Arabic text, byte order mark) were run through the importer, and the screens were driven in a headless Chromium browser at phone and desktop widths. It has not been tested on a real phone, in Safari, Firefox or Edge.