Flipkart Sales Returns: Credit Note Accounting in Tally
Returns are where Flipkart bookkeeping usually breaks. A sale that was booked, taxed and settled comes back weeks later, dragging a refund, a GST reversal, a reverse shipping fee and a TCS adjustment behind it. If your books only record the happy path, every return makes them a little more wrong. This guide covers the full accounting lifecycle of a Flipkart return in TallyPrime.
Where returns appear in Flipkart's reports
Two reports capture the same return from different angles. In the sales/GST report, a return shows as a row with Event Type = Return, carrying the original Order Item ID, invoice reference, negative-impact Taxable Value and IGST/CGST/SGST amounts, and the Customer's Delivery State. In the settlement report, the return shows up as adjustment rows against the same Order Item ID: the earlier payout is clawed back, commission and some fees may reverse, and a Reverse Shipping Fee is charged. Matching these two views by Order Item ID is the core discipline; a return is not fully booked until both sides are in Tally.
The credit note entry
For each Return event, raise a credit note that mirrors the original sales voucher: debit Sales Returns (or reduce the rate-wise sales ledger, per your CA's preference), debit the output GST ledgers for the IGST or CGST/SGST being reversed, credit the Flipkart party ledger for the invoice amount. Keep the linkage to the original invoice number from the report; GST rules require credit notes to reference original invoices, and it is what makes your GSTR-1 credit note section reconcile. Tax positions on cross-period returns can get nuanced, so confirm edge cases with your CA.
The settlement side: what the return actually costs you
| Component | Direction | Tally treatment |
|---|---|---|
| Sale value clawback | Deducted from settlement | Offset by the credit note against party ledger |
| Commission reversal | Credited back (varies by case) | Reduce Flipkart Commission expense |
| Reverse Shipping Fee | Charged to you | Expense ledger, the true cost of the return |
| TCS adjustment | Reversed on returned value | Reduce TCS Receivable |
The Reverse Shipping Fee deserves its own ledger because it is the clearest per-SKU signal of a returns problem: rising reverse shipping against one product usually means sizing issues, quality complaints or a misleading listing.
Timing: the cross-month return problem
A July sale returned in August means the sale sits in July's GSTR-1 and the credit note in August's. Your books must respect the report dates, not netting the two events silently. This is also why re-importing corrected reports matters: Flipkart's own reports for a period can include late-arriving return rows. A duplicate-safe import, one that recognises already-booked Order Item IDs and only picks up genuinely new rows, lets you re-download and re-upload a period without double-counting, which is exactly how TallySutra's Flipkart import handles it. Returns that cannot be matched to an original sale in your books land in its exception queue for a human decision instead of being imported blind.
A monthly returns hygiene checklist
- Filter the sales/GST report for Event Type = Return and count rows; every one needs a credit note.
- Match each return to its settlement clawback by Order Item ID; investigate returns with no settlement impact and vice versa.
- Total Reverse Shipping Fees for the month and review the top SKUs driving them.
- Verify TCS Receivable reflects return reversals before reconciling with the GST portal.
- Confirm GSTR-1 credit note totals match the credit notes posted in Tally.
This checklist folds naturally into a broader close process; see the full Flipkart month-close checklist for where returns fit among the other steps. If the volume of credit notes is what stops you doing this properly, that is the part worth automating: TallySutra generates return credit notes and the matching settlement adjustments from the official reports you upload (file-upload only, no API access to your account), with plans sized by voucher volume.
Returns are unavoidable on Flipkart; unbooked returns are not. Treat every Return row as a first-class accounting event and your margins, GST filings and settlement reconciliation all stay honest.
Finally, watch the ratio of Return rows to Sale rows per month in the report itself. A rising trend is an operations signal long before it becomes an accounting problem, and because your credit notes are posted item-wise, Tally can show returns by SKU and by month without any extra effort. That visibility is the reward for booking returns properly: the same entries that keep GST honest also tell you exactly which products to fix, reprice or drop from the catalogue.
Frequently asked questions
Do I need a credit note for every Flipkart return?
Yes, for every Return event against a sale you invoiced. The credit note reverses the sale value and the output GST, and must reference the original invoice number, which the Flipkart sales/GST report provides on the Return row. Skipping credit notes overstates both turnover and GST liability, and creates mismatches between your books, GSTR-1 and the settlement report.
What is the actual cost of a Flipkart return to my business?
Typically the Reverse Shipping Fee plus any non-reversed fees, plus the product-condition risk if the item comes back unsellable. The sale value itself is clawed back but offset by your credit note, so it is not a cost. Tracking reverse shipping in its own ledger per month, and reviewing which SKUs drive it, is the fastest way to see and reduce your true returns cost.
How do I handle a return that arrives in a later month than the sale?
Book the credit note in the month the return event occurs, referencing the original invoice, rather than reopening the earlier month. The sale stays in its original GSTR-1 period and the credit note appears in the later period's return, which is the standard GST mechanism. Confirm treatment with your CA where returns cross financial-year boundaries.
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