Courier and Last-Mile Reconciliation for Indian E-commerce and D2C Brands

A Bengaluru D2C brand selling apparel, footwear and accessories online — direct-to-consumer through its own site plus listings on Myntra, Ajio and Amazon — spends ₹6.8 crore annually on courier and last-mile across Blue Dart (15 percent), DTDC (24 percent), DHL Express (4 percent), India Post Speed Post (8 percent), Shiprocket (aggregating multiple partners on tier-2/3 lanes, 34 percent), Delhivery (10 percent) and Ekart (5 percent). May 2026 spend: ₹58 lakh on 1.42 lakh AWBs. The CFO reconciles four concurrent rails — tariff structure per AWB per partner, weight-dispute outcomes inside 14-day windows, OTP-delivery verification tied to COD remittance, and Section 393 code 1002 TDS withholding with 194C(6) declaration discipline. Courier last-mile reconciliation India at D2C scale is where partner-mix drift, slab-boundary error and rate-card version mismatch silently eat 1.5-3 percent of logistics spend.

Quick reference

Who are the dominant Indian courier and last-mile partners?

The D2C and e-commerce courier landscape splits across:

A typical D2C brand uses 5-8 partners concurrently — a premium partner for metro same-day, a mass-segment partner for the bulk of tier-2 volume, a rural partner for India Post coverage, and a multi-courier aggregator (Shiprocket or Pickrr) to route tail-distribution efficiently.

What are the four reconciliation rails?

Rail 1 — Per-AWB tariff against partner-specific structure

Each AWB is rated at booking from the partner’s tariff card with the rate-card version effective on the booking date. The audit re-rates each AWB from the booking record and compares to the partner’s invoice. Recurring exception patterns:

• Slab-boundary error — a 502 g shipment billed at the 501-1000 g slab when the partner card has 501-750 g and 751-1000 g sub-slabs
• Zone mis-classification — a tier-2 city pin classified as tier-3 attracting the higher slab rate
• Service-tier downgrade — surface-premium booked but billed as standard surface
• Rate-card version mismatch — renegotiated card effective 1 May but May invoices still billing on April rate

Industry-typical mis-billing on a 1.4 lakh-AWB monthly book is 0.3-0.9 percent of spend.

Rail 2 — Volumetric weight-dispute resolution

Volumetric weight applies on every AWB. The billed weight is the higher of actual and volumetric (L×B×H÷5000 for surface, ÷4000 for air). When the partner’s hub re-weigh records a higher value than the brand-declared, a slab upgrade is triggered. The brand has a 14-day window to contest:

• Accepted upgrade — brand agrees, slab differential billed
• Contested write-off — brand supplies valid pick-pack evidence, partner writes off
• Unresponded billed — brand misses the 14-day window, partner bills the upgrade

D2C brands with high SKU variability typically see 4-9 percent of AWBs flagged for volumetric upgrade.

Rail 3 — OTP-delivery verification and COD remittance lifecycle

OTP-delivery is contractually mandated on most D2C COD shipments. The flow:

1. Rider scans ‘out for delivery’; recipient receives OTP on registered phone
2. Rider arrives at doorstep, recipient shares OTP
3. Rider enters OTP, marks ‘delivered’
4. COD cash collected at delivery

COD remittance lifecycle from courier-side: rider hub-deposit end-of-day → courier treasury reconciles AWB-wise on T+1 to T+2 → remit to brand on T+3 to T+7 contracted SLA.

The brand’s reconciliation ties OTP-confirmation per AWB to the COD remittance file. Recurring exception patterns:

• COD shown delivered but not remitted on contracted T+X
• COD remitted in cumulative settlement without AWB-detail
• COD reversed post-remittance on RTO claim
• COD partial remittance with retained against RTO percentage

Typical exception rate is 0.4-1.2 percent of COD value with recovery taking 14-30 days.

Rail 4 — Section 393 code 1002 TDS and Section 52 CGST TCS

Section 393 code 1002 — 1 percent (individual/HUF) or 2 percent (company/firm) TDS deducted by the brand on courier invoices.

Section 194C(6) preserved nil-deduction route — small transporters owning 10 or fewer goods carriages with PAN-based declaration are non-deduction vendors. The brand maintains the declaration register live and re-validates at every FY boundary.

Section 52 CGST TCS — where the brand uses an aggregator (Shiprocket, Pickrr), the aggregator is an e-commerce operator under Section 52 and collects TCS at 0.5 percent CGST + 0.5 percent SGST (or 1 percent IGST) on consideration. The brand claims the credit in GSTR-2B.

Section 9(5) NOT applicable — standard courier and last-mile freight is not on the Section 9(5) list. The courier raises SAC 996819 invoice at 18 percent forward charge.

Worked example — Bengaluru D2C brand, 1.42 lakh AWBs, May 2026

The CFO’s month-end close ties:

• Per-AWB tariff against partner card with rate-card version
• Weight-dispute register with 14-day window outcomes per partner
• OTP-confirmation vs COD remittance per AWB
• Section 393 code 1002 TDS deducted + 194C(6) declarations + Section 52 TCS credit

What does the Section 393 / GST overlay look like?

• Section 393(1)(a) code 1002 (legacy 194C) — 1-2 percent TDS on courier invoices. See Payment Code 1002 — Contractor Payments.
• Section 194C(6) preserved — small-transporter nil-deduction with PAN declaration framework.
• Section 52 CGST TCS — 0.5 percent CGST + 0.5 percent SGST (or 1 percent IGST) on consideration where aggregator-rolled invoices apply. Credit in GSTR-2B.
• SAC 996819 at 18 percent forward charge — standard courier invoice; ITC reclaimable subject to GSTR-2B match.
• Section 9(5) NOT applicable — to standard courier services. Section 9(5) lists are specified categories only.
• Cross-era note — pre-1 April 2026 TDS under legacy 194C cross-referenced to code 1002 for at least one FY cycle. See TDS payment codes 1001-1092 India.

CBIC authority reference

For SAC 996819 (supporting services in transport), Section 9(5) of the CGST Act on e-commerce operator liability, Section 52 CGST TCS framework, and the GST treatment of courier and last-mile delivery services see the CBIC GST portal.

What automated reconciliation changes

Running a D2C brand’s courier book across 5-8 partners with per-AWB tariff verification, weight-dispute 14-day-window resolution, OTP-confirmation tied to COD remittance, Section 393 code 1002 TDS with 194C(6) declaration discipline, and Section 52 CGST TCS credit from aggregator-rolled invoices is the most settlement-dense workflow in D2C logistics. Purpose-built reconciliation software India holds the courier partner master with version-controlled tariff cards, the AWB-level matching engine with weight-dispute resolution, the COD remittance reconciliation against OTP confirmation, and the Section 393 code 1002 + Section 52 CGST TCS multi-code ledgers in one frame. Customer outcomes include match rate improvement from 51 percent to 88 percent on revenue-grade ledgers. Build is two-to-four weeks on AWS Mumbai (ISO 27001:2022). For the SAC 996819 ITC reclamation discipline see GST reconciliation software.

Continue reading in the Logistics cluster

• 3PL settlement reconciliation for Indian logistics operators
• FASTag toll reconciliation for Indian fleet operators
• Ocean freight and container tracking reconciliation for Indian exporters
• Logistics reconciliation hub