🎁 Early Access Open: Get 1 Month of Growth Tier Free when you sign up

Flipkart

Flipkart seller reconciliation

Last reviewed·ReconPe Editorial

Flipkart’s payout structure packs commission, fixed fee, collection fee, and shipping fee into separate columns of the Payments Report — each with its own category-specific variance pattern. ReconPe parses the four-fee structure, reconciles every order via ACRE probabilistic matching, flags per-fee variance against your rate card, and carries open exceptions across cycles so F-Assured claim reversals and return deductions from earlier runs auto-link when they eventually settle.

Where Flipkart reconciliation breaks down manually

Flipkart has five distinct fee types

Commission, fixed fee, collection fee, shipping fee, and F-Assured fee — each calculated on different slabs. Manually verifying all five across thousands of orders is where margin gets lost.

F-Assured adds another layer of variance

F-Assured orders carry premium fees in exchange for faster delivery promises. ReconPe isolates F-Assured line items and confirms the fee charged matches the Flipkart Plus rate card — catching miscategorised orders automatically.

Return deductions are often opaque

Flipkart deducts return shipping, customer-claim settlements, and quality-check adjustments as separate line items on later settlements. ReconPe links deductions back to the original order so you can trace what was recovered and what wasn't.

Settlement cycle creates timing gaps

Flipkart settles on a T+7 to T+10 cycle depending on seller tier. Funds for a given invoice date may arrive across two bank credits over different days. ReconPe handles split settlements automatically without manual aggregation.

How ReconPe handles Flipkart

Per-order fee variance against rate card

Upload your Flipkart rate card once. Every settlement row is compared against expected commission, fixed fee, F-Assured, and shipping — variance is flagged per order with exact rupee impact.

Audit-ready output for Flipkart account reviews

Every reconciliation run produces a versioned export with source, target, variance, and resolution context. CAs and Flipkart category managers get the clean trail they ask for.

Why a Flipkart payout rarely matches on the first try

The Flipkart settlement workbook is one of the messier files in Indian commerce. These are the specifics ReconPe handles because it was built against the real file — including the rounding and header quirks that only show up in an actual export.

A Flipkart payout is four streams, not one

A single bank NEFT nets your orders, fee rebates, storage-recall charges and ads-wallet settlement together. Match the Orders sheet alone and every payout reads as short. ReconPe aggregates all four into the expected credit, with a ₹5 tolerance that absorbs Flipkart's per-line versus bank-recorded rounding.

Roughly thirteen sheets — one is a help page

The settlement workbook ships Orders, MP Fee Rebate, Storage Recall, Ads, TCS Recovery, TDS, GST Details and more. ReconPe reads the sheets that carry money and skips the instructional cover sheet that otherwise gets parsed as 83 rows of garbage.

Headers arrive with Excel formulas baked in

Real Flipkart exports carry text like "Commission (Rs.) =SUM(...)" inside the header cell. ReconPe sanitises the formula out before mapping — without it, every downstream column shifts by one and the whole file mis-reads.

TCS, TDS and GST come out as their own lines

Rather than lumping statutory deductions into one fee blob, ReconPe separates TCS recovery, TDS and the GST charged on each fee — so the input-credit and TDS-credit figures you file are the reconciled ones.

Frequently asked

Does ReconPe handle Flipkart Plus and F-Assured fees differently?

Yes. F-Assured orders are flagged in the Flipkart settlement report and ReconPe's rule engine applies the F-Assured fee slab separately from the standard commission. If you expect F-Assured fee on an order and it wasn't charged (or was charged on a non-F-Assured order), ReconPe flags it as a type mismatch.

Can ReconPe reconcile Flipkart returns and RTO entries?

Yes. Returns, RTOs, and customer-claim settlements from Flipkart appear as negative line items on later settlement reports. ReconPe links them back to the original order by SKU + order ID and flags cases where the net refund doesn't match the original settlement.

How does ReconPe handle Flipkart's split settlements?

Flipkart often splits a single order's payout across two settlement dates (typical pattern: commission and fixed fee on one cycle, shipping deduction on the next). ReconPe's matching engine reconciles across the full invoice period rather than forcing a 1:1 match per day.

Does ReconPe work for Flipkart Grocery and Flipkart Wholesale?

Yes. Both Flipkart Grocery and Flipkart Wholesale use the same core settlement report schema. ReconPe's auto-detection handles the variant columns without requiring a new rule set per vertical.

What about commission variance on promotional orders (Big Billion Day etc.)?

Promotional-event orders often carry reduced commission or waived fees. If your rate card captures the promotional rate for that window, ReconPe compares actuals against it. Otherwise, all promotional orders are grouped so you can review them together.

How long does the first Flipkart reconciliation take?

Under 5 minutes. Upload your Flipkart settlement report and bank statement, let schema detection run, review the suggested rule set, and kick off reconciliation. The first clean run ships on day one.

Riya at her desk late at night under warm desk-lamp light, eyes narrowed on a laptop screen displaying a Flipkart settlement CSV with 4,800 rows. The OrderID OD123456789 repeats across multiple rows with different transaction types (Order, Fee, Return, COD, TDS). A WhatsApp notification at top-right reads: 3:00 AM — Flipkart Seller (Client) — 'the file crashed again'. A sticky note on the right reminds: VLOOKUP assumes one match per key. Marketplace settlements never do.
Finance Manga · EP02

Why VLOOKUP breaks at 2,000 orders a month

A 3am WhatsApp from a Flipkart seller: 'the file crashed again.' Riya opens it — 4,800 rows, OrderID duplicated six times per order. Direct matching dies at this scale. Set matching is the answer.

Read

Audit your next Flipkart settlement in minutes

Free tier — 5 free reconciliations, 1 marketplace. Catch the fee variance your spreadsheet is quietly missing.

Start free