Flipkart NEFT Settlement & Bank Reconciliation Guide
The bank statement is the one document in your accounting stack that nobody can argue with, which is why every Flipkart reconciliation should end there. The good news: Flipkart's settlement report is built for this. Every order-item row carries a NEFT ID and NEFT date identifying the exact bank transfer it was paid in. The bad news: real bank statements are messier than the report implies. This guide covers the clean path and the exceptions.
How the NEFT linkage works
Flipkart settles on payment cycles. Each cycle, it bundles the Settlement Value of many order items into one NEFT transfer. The settlement report stays order-item-level, so the reconciliation identity is simple: for any NEFT ID, the sum of Settlement Value across its rows should equal one credit on your bank statement dated on or near the NEFT date. Sale Amount, the gross figure, plays no role in bank matching; only Settlement Value, net of Commission, Collection Fee, Fixed Fee, Shipping Fee, Reverse Shipping Fee, GST on Fees, TCS and TDS, reaches the bank.
The five-step monthly routine
- Download the settlement report covering all NEFT dates in the month.
- Pivot rows by NEFT ID, summing Settlement Value per group.
- Pull the bank statement and isolate Flipkart credits (the narration usually carries the NEFT reference).
- Match group totals to credits one-to-one; tick both sides.
- Post one receipt voucher in TallyPrime per matched NEFT, debiting bank and crediting the Flipkart party ledger.
When the match fails
| Situation | What happened | Fix |
|---|---|---|
| Two report groups, one bank credit | Bank clubbed same-day NEFTs in the statement view | Match on the combined total; keep both NEFT IDs in the voucher narration |
| Bank credit with no report group | Settlement report window missed a cycle | Re-download with a wider date range |
| Report group with no bank credit | NEFT failed or bounced to a changed account | Check Seller Hub payment status; escalate to support |
| Group total off by a small amount | Negative rows (returns, recoveries) missed in the pivot | Include all rows for the NEFT ID, including negatives |
Negative rows are the classic trap. A customer return settled in the same cycle appears as a negative Settlement Value row under the same NEFT ID, reducing the transfer. Pivot only the positive rows and your total will overshoot the bank credit every time. The accounting behind those negative rows is covered in our returns and credit notes guide.
Posting pattern in TallyPrime
Keep the receipt voucher clean: bank debit, Flipkart party credit, amount equal to the bank credit, NEFT ID and date in the narration. The fees, GST on fees, TCS and TDS belong in separate journals against the party ledger, not stuffed into the receipt. This separation means your bank book mirrors the bank statement line for line, which is what makes Tally's bank reconciliation feature actually usable, and it keeps the party ledger as the single place where gross sales, fees, taxes and receipts all meet and cancel out.
Doing it at volume
At a few NEFTs a month this is a spreadsheet job. At daily cycles across high order volume, the pivot-match-post loop is exactly the kind of deterministic work software should own. TallySutra performs the NEFT grouping and settlement reconciliation automatically from the settlement report you upload, generates the receipt and fee vouchers as balanced Tally XML, and flags any NEFT group that does not tie out into an exception queue for review. It reads only the files you give it, there is no connection to your bank or your Flipkart account, and re-uploading a period is duplicate-safe. The Gateway desktop app can push approved vouchers straight into TallyPrime on your machine. However you do it, the standard is the same: every Flipkart rupee in the bank should be traceable to the order items that produced it, and every order item to the NEFT that paid it.
A note on timing differences: the NEFT date in the report and the value date on your statement can differ by a working day around holidays, so match on amount and reference rather than insisting on identical dates. Keep unmatched items visible in a suspense list rather than forcing approximate matches, and clear the list before closing the month. If you operate multiple bank accounts, confirm which one Flipkart pays into after any account change, because a stale account mapping is the usual culprit behind a payout that seems to vanish and later surfaces as a failed-transfer status in Seller Hub.
Frequently asked questions
The settlement report total does not match my bank credit. What first?
Re-pivot including negative rows. Returns and recoveries settled in the same cycle appear as negative Settlement Value rows under the same NEFT ID, and excluding them makes your total overshoot the bank credit. If it still fails, check whether your bank clubbed multiple same-day NEFT transfers into one statement line and match on the combined total instead.
Should fees be part of the bank receipt voucher in Tally?
No. The receipt voucher should contain exactly what the bank statement shows: the net Settlement Value credited. Fees, GST on fees, TCS and TDS belong in separate journal entries against the Flipkart party ledger. This keeps the bank book identical to the bank statement, which makes Tally's reconciliation feature work cleanly and keeps the audit trail readable.
What if a NEFT shown in the report never reached my bank?
First verify the payment status in Seller Hub, since the report can include cycles where the transfer failed, for example after a bank account change. If the status shows paid but the credit is absent beyond a couple of working days, raise a ticket with Flipkart seller support quoting the NEFT ID and date from the settlement report. Do not post the receipt until the money is visible.
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