ShipOpsHow InstaWorld pays your COD, and how to check it
InstaWorld has no payout API. Its tracking response carries an invoice_status of Paid, Approved or empty per parcel, but no amount, no date and no receipt, so ShipOps does not treat it as money. Your COD comes to you on an InstaWorld statement, and ShipOps reads that statement when you drop it in.
When InstaWorld pays
InstaWorld pays delivered COD on a statement from its finance side. It has not published a cycle and exposes none through the API, so this page does not promise a day. Once you have uploaded two or three statements, ShipOps learns your rhythm from them.
What the InstaWorld payout receipt contains
The statement is whatever InstaWorld's finance team sends you, typically a sheet with one row per parcel: tracking number, COD collected, charges, tax, net. ShipOps reads it with its layout reader: it profiles the columns, checks every row (net equals the sum of its components), and projects the lines onto your orders. The first read of a new layout is learned once and cached for your account.
The per-parcel invoice_status on the tracking response is deliberately not read as a payment. It contradicted the resolver on exactly the parcels that mattered during live verification, and it carries no amount.
Where the money goes wrong
These are the discrepancies ShipOps finds on InstaWorld receipts, in the order they usually cost the most:
- Delivered, on no statement. The trail says Delivered; no uploaded statement carries the tracking number. Once you have the statements for the period, these are the parcels to ask about.
- Short collected. A row's collected amount below the order's COD.
- Charges on a parcel marked delivered to shipper. A return priced as a delivery.
- A statement whose rows do not add up. ShipOps refuses to file a statement whose arithmetic does not close rather than guess which column shifted.
What ShipOps does with a InstaWorld payout
You upload the statementDrop the statement into the Money screen. ShipOps reads it, checks every row, matches the lines to your parcels, and files it as a receipt. Uploading is never charged. The Money screen then shows what reached the bank, what InstaWorld still owes (delivered parcels on no statement), and what is at risk.
Returns are priced from the rows they land on, so an RTO has a real cost on the order.
No API means ShipOps cannot see a payment InstaWorld has made until you upload the statement. "Courier owes you" for InstaWorld is only as current as your last upload.
invoice_status is shown as what it is, a flag, never as a payment.
Questions merchants ask about InstaWorld payments
When does InstaWorld pay COD?
On statements from its finance side; no cycle is published and none is exposed through the API. Upload two or three statements and ShipOps learns your rhythm.
Does invoice_status Paid mean I have been paid?
ShipOps does not assume so. It carries no amount, no date and no receipt, and during live checks it disagreed with the trail on parcels that mattered. The statement is the truth; the flag is a flag.
What format does the InstaWorld statement need to be in?
The sheet InstaWorld sends you, CSV or XLSX. ShipOps profiles the columns on first read, checks every row, and remembers the layout for your account.
How do I find InstaWorld parcels that were delivered but not paid?
Upload the statements for the period; delivered parcels on none of them are listed under "courier owes you" with their delivery dates.
How other couriers pay
The general guide: courier COD payment reconciliation in Pakistan.
See what InstaWorld still owes you
Connect InstaWorld and ShipOps matches every payout against your orders. Short-paid, skipped and zero-collected parcels come out as a list you can send to your account manager. Free to start.