Reconciling cash-on-delivery remittances from your courier
How COD payout rows are created when Bosta remits, how to read the aging buckets, and when to record a discrepancy or a write-off.
Operations
Cash on delivery means the courier collects your money before you see it. The COD payouts screen in Storix turns Bosta's remittances into rows you can actually reconcile, so every pound your shoppers handed over is either matched to a shipment or flagged with a reason. This lesson walks you through the whole reconciliation routine: where the rows come from, what the aging buckets mean, and the only two corrections you are ever allowed to make.
Open the payouts screen from the admin menu under Shipping ← COD payouts («الشحن ← توريدات الدفع عند الاستلام»). Each row is one shipment's cash collection: the amount the shopper paid, the amount the courier actually remitted, and the difference if the two disagree. You do not create rows by hand and you cannot mark a row settled manually — a payout row appears and settles automatically when the shipment reaches the Settled status in the carrier's event feed, because the remittance itself is recorded by that event.
Read the aging buckets before anything else
The screen groups unsettled collections by how long the money has been outstanding: 0–2 days, 3–7 days, 8–14 days, and 15+ days. Egyptian couriers typically cycle remittances weekly, so the first two buckets are healthy. When the 8–14 bucket grows, pull the courier's statement and compare — always reconcile oldest bucket first, because reconciling is easier while the trail is fresh; when 15+ grows, chase the courier before recording anything, because a late transfer is not a discrepancy — it is a delay, and the buckets exist precisely to tell the two apart.
Record a discrepancy when the amounts disagree
If the courier remitted less than the shopper paid (fees taken twice, a partial handover, a wrongly closed trip), open the row and choose Discrepancy. Write the reason in plain words — what Bosta's statement says, what the shipment says, and the ticket number if you opened one. The reason is capped at 500 characters, so paste the numbers, not the whole statement. A recorded discrepancy moves the row out of your outstanding buckets and into the explained list, keeping the aging view honest.
Write off only with a second pair of eyes
A Write off removes an unresolvable amount from your receivables — for example a trip the courier will never pay back. It is deliberately a two-person action: the admin who recorded the discrepancy is refused with a discrepancy_maker_cannot_write_off error if they try to write it off themselves, so a second admin has to review and confirm. That maker-checker rule protects you from one tired person closing the books alone at midnight.
Export for the accountant
The Export CSV button on the screen produces the reconciliation file your accountant needs. The button follows the Export data permission, so team members without it can reconcile on screen but cannot download. Combine the export with the P&L lesson to see how remittance gaps eat into the month's net profit.
Related lessons: shipping delay SOP when parcels stall before settlement, and cutting COD returns to keep less cash in the courier's hands in the first place.