AP use case · Order-to-cash

Cash on delivery.
Chaos on remittance.

Your 3PL collects cash across a thousand pincodes and remits on its own cycle, minus its own charges. Finnoto matches every COD order to its remittance line and bank credit - so collected never quietly differs from received.

COD console

Collected ↔ remitted ↔ credited,
order by order.

COD recon · Delhivery · week 47 Live
₹9.8L
COD delivered value · 2,304 orders
₹9.1L
Remitted & matched to bank
₹68,400
Delivered, not yet remitted · ageing
OrderCollectedRemittedStatus
ORD-77123₹1,449₹1,449Matched · UTR tied
ORD-77168₹2,199₹2,199Matched · COD fee valid
ORD-77201₹899-✕ Delivered day 9 · not remitted · claimed
Ageing escalation → 3PL
42 orders delivered >7 days, ₹68,400 unremitted - order-wise annexure sent; SLA breach flagged on weekly scorecard.
Bank tie-out
Remittance UTR HDFC-2214 = manifest total minus contracted COD fee ₹12/order - verified.
per-order COD ageing · 3PL scorecards · gateway payouts reconciled on the same rails

Illustrative product behaviour - values shown are examples.

Why it's hard today

COD float hides losses
inside the delay.

Between delivery and remittance sits a float that absorbs missing orders, wrong fees and lost cash - invisible unless every order is tracked individually.

Multiple 3PLs, multiple cycles

Each courier remits on its own schedule, format and fee logic. Aggregate matching hides exactly the orders that went missing.

Ageing without ownership

"It'll come in the next remittance" works until it doesn't. Without per-order ageing, nobody notices the ones that never arrive.

Fees nibble the float

COD charges, weight-based surcharges, RTO fees - deducted at source from remittances, rarely validated against contract.

The Finnoto difference: COD, gateway and marketplace flows reconcile on one platform - the same order-level engine, whatever the payment mode.
How Finnoto runs it

Order-level custody,
from doorstep to bank.

1
Track from delivery
Every COD delivery starts a remittance clock - per order, per courier, per pincode.
2
Match remittance files
3PL remittance manifests matched line-wise to orders; bank UTRs tied to manifest totals.
3
Validate fees
COD charges and surcharges checked against contracted rates before acceptance.
4
Escalate ageing
Unremitted orders past SLA escalate automatically with annexures; courier scorecards drive allocation decisions.
FAQ

Frequently asked questions

Which 3PLs and gateways are covered?

Delhivery, Shiprocket, XpressBees, Shadowfax and other major couriers for COD; Razorpay, PhonePe, Paytm, Juspay and bank gateways for prepaid - one reconciliation across both.

What about RTO orders?

RTO events close the remittance expectation and open the return-side tracking - the order stays accounted for either way, never orphaned between systems.

Can courier performance feed allocation?

Yes - remittance SLA, shortage rate and fee accuracy per courier are scored continuously, giving ops hard data for volume allocation.

Shrink the float. Keep the cash.

Per-order COD truth across every courier you run.

Talk to us