Flipkart Payment Reconciliation: Step-by-Step Guide
Reconciliation is the difference between hoping Flipkart paid you correctly and knowing it. Sellers who skip it lose money in two ways: short settlements that go unchallenged, and books that drift so far from the bank statement that year-end becomes archaeology. Here is a reconciliation process you can actually run every month, whether you do it in spreadsheets or automate it.
What you are reconciling, exactly
Flipkart reconciliation is a three-way match:
- Orders to settlements: every dispatched order item should eventually appear in a settlement report row, either as a payment or an adjusted return.
- Settlements to bank: rows grouped by NEFT ID should sum exactly to the credits on your bank statement.
- Settlements to books: the fees, TCS and TDS in the report should match the expense and asset entries in TallyPrime.
The settlement report makes this possible because it is order-item-level and carries the NEFT ID and NEFT date on every row, alongside Sale Amount (gross), Settlement Value (net) and each fee column separately.
The monthly process
- Download the settlement report covering all NEFT dates in the month, plus the sales/GST report for the same period.
- Group settlement rows by NEFT ID and total the Settlement Value per group.
- Match each group total to a bank credit. Same-day NEFTs can merge on some bank statements, so match by NEFT reference where your bank shows it.
- Verify fee reasonableness. Commission as a percentage of Sale Amount should be stable within a category; a jump usually means a rate-card change or a misclassified SKU.
- Check unsettled items. Orders delivered but absent from any settlement beyond the normal payout cycle deserve a ticket to Flipkart support.
- Post entries in Tally only after the above ties out, so the books reflect verified reality.
The mismatches you will actually find
| Symptom | Usual cause | What to do |
|---|---|---|
| NEFT group total ≠ bank credit | Bank clubbed transfers, or a recovery/adjustment row missed | Re-check by NEFT reference; scan for negative rows |
| Order item never settled | Return in transit, or settlement in a later cycle | Track order status; escalate if aged |
| Negative Settlement Value rows | Customer return: reverse shipping fee plus refund exceed fee reversals | Post as credit note plus expense, not as a deletion |
| Fee % suddenly higher | Rate card revision or wrong category mapping | Compare against Flipkart's published rate card for your category |
Posting the reconciled result in TallyPrime
Once a NEFT group ties out, post one receipt voucher for the bank credit, journals for the fee columns (Commission, Collection Fee, Fixed Fee, Shipping Fee, Reverse Shipping Fee) and GST on fees, and entries moving TCS and TDS into receivable ledgers, all against the Flipkart party ledger. If your sales vouchers were posted from the sales report at gross value, the party ledger should net to the unsettled balance only. Our NEFT bank reconciliation guide covers the bank-side matching in more depth.
Automating the boring 90%
Everything above is deterministic, which means software can do it. TallySutra ingests the settlement and sales reports you upload from Seller Hub (file-upload only; it never connects to your Flipkart account) and runs the reconciliation automatically: rows grouped by NEFT ID, fees itemised, TCS and TDS split out, and balanced TallyPrime vouchers generated for everything that ties out. Anything that does not reconcile, a short payment, a duplicate row, an unmapped SKU, goes to an exception queue where you or your CA resolve it before it can enter the books. Re-uploading a corrected report is safe because previously imported rows are recognised and skipped. If you currently spend a day or more on this each month, the feature walkthrough shows what the automated flow looks like end to end.
Run this discipline for two or three months and something changes: you stop treating Flipkart's numbers as a black box. Short payments get caught while they are still disputable, and your TallyPrime data becomes something you can hand to a CA or a lender without apologies.
One further habit multiplies the value of all of this: document each month's reconciliation in a simple working file listing every NEFT ID, its report total, its bank credit and the status of any difference. When a dispute with Flipkart drags on, that record, backed by the unedited settlement reports, is what turns an argument into a claim. It also gives your CA an instant view of open items at filing time, and it means a staff change never resets your process to zero, because the method lives in the file rather than in someone's head.
Frequently asked questions
How often should I reconcile Flipkart payments?
Monthly at minimum, aligned to your GST cycle, because that is when sales figures get locked into returns. High-volume sellers benefit from weekly reconciliation since Flipkart settles on rolling cycles and disputes over short payments are much easier to raise while the settlement is recent. Automated reconciliation makes the weekly cadence practical even for small teams.
What if an order item never shows up in any settlement report?
First confirm the order actually completed; returns and RTO items settle differently or not at all. If a delivered item is absent beyond the normal payout cycle for your account, raise a ticket with Flipkart seller support citing the Order Item ID. Keeping an unsettled-items list as part of monthly reconciliation is what makes these cases visible in time.
Can reconciliation be fully automated?
The matching can be: grouping rows by NEFT ID, totalling Settlement Value, comparing against bank credits and generating vouchers are deterministic steps that tools like TallySutra automate from uploaded reports. Judgement calls cannot: deciding whether a fee spike is legitimate or disputing a short payment still needs a human, which is why an exception queue and CA review step matter.
TallySutra turns Amazon, Flipkart and Meesho reports into reconciled, reviewed TallyPrime vouchers — duplicate-safe, with every rupee traceable to its source row.
Book a 30-minute demo