Shipping Invoice Reconciliation: A Guide for Indian Sellers

Your shipping dashboard shows one amount when you book a parcel, but the final bill may look different. Some differences are legitimate: a provisional charge may change after measurement, or a return movement may be billed later. Others need investigation, such as a duplicate debit or a fee that does not match your agreement.

Shipping invoice reconciliation means matching each billed charge to the shipment, applicable rate and supporting event. For Indian D2C sellers, it also means keeping shipping expenses separate from COD money collected on their behalf. This guide shows how to build a repeatable check using a spreadsheet, without treating every price difference as an error.

1. Gather the records that explain each charge

Start with one billing period and collect the source files before checking totals. An invoice alone rarely explains everything. You need shipment details, the rate terms applicable when the booking was made, and records of subsequent adjustments.

If you use a shipping wallet, download its transaction ledger too. A wallet recharge is funding, not automatically a shipping expense. Likewise, an invoice may summarise debits already posted to the wallet; recording both as separate expenses can double-count costs.

• Shipment export: order ID, AWB, courier, service, booking date, destination PIN code, payment mode and current status.
• Rate evidence: booking quote, applicable rate card or commercial agreement, including surcharge and tax terms.
• Billing records: invoices, shipment-level charge breakdowns, wallet debits, reversals and credit notes.
• Exception records: cancellations, RTO movements, customer returns and approved adjustments.
• COD records: collections, remittance statements, permitted deductions and corresponding bank credits.

2. Build an AWB-level reconciliation sheet

Use the airway bill number, or AWB, as your main shipment identifier. Keep the order ID alongside it, but do not rely on order ID alone: one order can have multiple parcels, replacement shipments or a separate return AWB.

Keep one row per charge event rather than forcing every transaction into a single shipment row. A forward charge, RTO charge and later reversal may all relate to the same AWB. Add a summary tab that totals these rows by shipment.

Preserve the original exports and do your checks in a working copy. This makes it easier to explain a discrepancy when statements are updated later.

• Identity columns: invoice number, transaction ID, AWB, order ID, courier and service.
• Charge columns: charge type, expected amount before GST, billed amount before GST, GST and variance.
• Tracking columns: shipment event, transaction date, supporting evidence, review status and dispute reference.
• Resolution columns: approved adjustment, credit reference, posting date and remaining difference.

3. Recalculate the expected shipping charge

For each shipment, check the origin–destination lane or zone, service selected, applicable chargeable weight and rate slab. Use the terms effective for that booking, not today's dashboard rate. Check whether extra-weight slabs are rounded up and whether the quote included applicable surcharges.

Compare like with like. A tax-inclusive invoice total cannot be compared directly with a freight estimate that excludes GST. Separate freight, other fees and tax before deciding that a shipment was overcharged.

For illustration only, suppose a booking estimate shows ₹80 freight plus a ₹15 COD fee, both before GST. The invoice lists those amounts plus a ₹10 delivery-area surcharge. The ₹10 difference needs checking against the destination and agreed terms. It is not automatically an error merely because the initial estimate did not show it.

• Confirm the courier and service billed match the service actually booked or an authorised change.
• Check the billed weight slab against the applicable shipment measurements and rules.
• Verify any COD, fuel, remote-area or other surcharge against your commercial terms.
• Where a fee has a percentage calculation or minimum amount, verify the correct base and minimum.

4. Review cancellations, returns and duplicate entries

Exception shipments deserve a separate pass. A cancelled label does not always produce an immediate reversal, and a shipment booked near month-end may generate charges in the following period. Compare booking, pickup, cancellation and billing dates before flagging a missing credit.

Distinguish return-to-origin movements from customer-initiated returns. They are different events and may have different pricing. An RTO does not necessarily cancel the original forward freight; whether additional charges apply depends on your agreement.

Repeated AWBs are not proof of duplicate billing. First compare charge type, transaction reference and movement. Two identical forward-freight debits without a matching reversal, however, deserve investigation.

• Booked but never handed over: check cancellation and reversal rules.
• RTO: verify the shipment event and applicable return charge.
• Customer return: connect the reverse AWB to the original order without merging their charges.
• Replacement shipment: treat it as a separate movement, even when the customer pays nothing.

5. Reconcile COD remittances separately

COD collection is customer money received on your behalf; it is not a reduction in the underlying shipping expense. Maintain a separate COD ledger linking delivered COD AWBs, collected amounts, settlement references and bank receipts.

Start with the remittance statement: collected amounts included in that settlement, less deductions or adjustments permitted under your arrangement, should explain the net remittance. Then match that amount to the bank credit. Delivery alone does not mean a shipment belongs in the next bank transfer; check the agreed settlement cycle and cutoff.

Pay particular attention to fees shown in both billing and settlement reports. They may be the same charge displayed in two places, not two deductions. Trace the actual wallet movement or settlement deduction before counting it twice.

6. Raise discrepancies with a complete evidence pack

Submit a concise discrepancy sheet within the dispute window stated in your agreement or platform terms. Group issues by category so the billing team can investigate them consistently. State what was billed, what you expected and the document or calculation supporting the difference.

A ticket marked resolved is not the final accounting step. Confirm that the approved adjustment actually appears in the wallet, settlement or credit note, and link it back to the original charge.

For GST treatment and input tax credit eligibility, have your accountant review the relevant documents, GSTIN details and GSTR-2B matching where applicable.

• Include the invoice number, AWB, transaction reference and disputed amount.
• Attach the applicable quote or rate terms and relevant shipment evidence.
• Request a calculation breakdown where the reason for a charge is unclear.
• Record the response, approved amount and actual credit separately.

7. Make reconciliation a regular operating habit

Review new exceptions weekly and close each billing period after matching invoices, wallet movements, credits and COD settlements. Prioritise duplicate debits, unexplained fees and unresolved credits. Track how long exceptions remain open, not just how many tickets you raise.

ShipPilot offers multi-courier domestic shipping with live rate comparison. When booking through it, preserve the selected service and quote alongside the AWB so you have a useful reference for later checks.

The goal is not to challenge every charge. It is to make every shipping expense traceable to a shipment, an agreed pricing rule and a real event—while ensuring every approved credit and COD remittance reaches your books.