How to Import Flipkart Reports into Tally Prime (2026)
Every Flipkart settlement cycle produces hundreds or thousands of order-item rows, and each row carries a sale, a stack of fees, TCS and TDS. Typing all of that into TallyPrime by hand is where most sellers' books quietly fall behind. This guide walks through exactly which Flipkart reports you need, what their columns mean for your accounts, and how to turn them into balanced TallyPrime vouchers without manual data entry.
The two Flipkart reports your books depend on
Flipkart Seller Hub gives you many downloads, but only two matter for core bookkeeping. The first is the settlement report. It is order-item-level, which means one row per order item, not one row per payout. Each row shows the NEFT ID and NEFT date of the bank transfer it belongs to, the gross Sale Amount, the Settlement Value (the net figure after fees), and the individual deductions: Commission, Collection Fee, Fixed Fee, Shipping Fee, Reverse Shipping Fee and GST on Fees, plus TCS and TDS columns.
The second is the sales report (GST report). This carries the Order Item ID, Event Type (Sale or Return), Invoice Number and Date, Taxable Value, IGST/CGST/SGST amounts, Invoice Amount and the Customer's Delivery State. This is the report your sales vouchers and GST workings come from; the settlement report is what your receipts and expense vouchers come from.
| Report | Where to download | What it drives in Tally |
|---|---|---|
| Settlement report | Seller Hub > Payments | Receipt vouchers, fee expenses, TCS/TDS entries |
| Sales / GST report | Seller Hub > Reports | Sales vouchers, credit notes, GST tax ledgers |
Step 1: Download the reports for a clean period
- Log in to Flipkart Seller Hub and pick a defined period, ideally a full month so it lines up with your GST filing cycle.
- Download the settlement report for every NEFT payout dated in that period.
- Download the sales report for the same period, and note that Return rows will appear alongside Sale rows.
- Do not edit the files. Renaming is fine; changing columns or deleting rows breaks any automated import and your audit trail.
Step 2: Decide your ledger mapping before importing anything
Whether you import manually or with a tool, the mapping decisions are the same. A typical structure looks like this: Flipkart as a sundry debtor party ledger, one sales ledger per GST rate, expense ledgers for Commission, Collection Fee, Fixed Fee, Shipping Fee and Reverse Shipping Fee, an input GST ledger for GST charged on fees, and asset ledgers for TCS (u/s 52) and TDS (u/s 194-O) receivable. Agree this chart of accounts with your CA once, then keep it stable so month-on-month comparisons stay meaningful. Specific tax treatment, especially how you claim TCS and TDS credits, should always be confirmed with your CA.
Step 3: Convert rows into TallyPrime vouchers
Manually, that means one sales voucher per invoice, credit notes for returns, a journal for fees per settlement, and a receipt per NEFT. Most sellers give up somewhere around the second hundred rows. The file-upload route automates the same steps: with TallySutra's Flipkart-to-Tally workflow you upload the official settlement and sales reports exactly as downloaded, the platform parses each order item, builds balanced vouchers, and anything ambiguous, such as an unmapped SKU or a fee that does not reconcile, lands in an exception queue instead of silently importing wrong. A CA review step lets your accountant approve batches before anything touches your books. The output is standard Tally XML you import into TallyPrime, or you can push entries through the TallySutra Gateway desktop app. To be clear about how this works: TallySutra reads the report files you upload. There is no live connection to your Flipkart account and no background API sync, so you stay in control of what enters your books and when.
Step 4: Handle re-imports without duplicates
Real months are messy. You will re-download a corrected report, or import overlapping date ranges. Because every Flipkart row has a stable Order Item ID, a duplicate-safe importer can recognise rows it has already converted and skip them, which is exactly how TallySutra's re-import behaviour works. If you are importing manually, keep a register of imported NEFT IDs and invoice numbers, and reconcile voucher counts against report row counts before closing the month. For a deeper look at what each settlement column means, see our Flipkart settlement report explainer.
Done this way, a month of Flipkart activity becomes an afternoon's work instead of a week's, and your TallyPrime data stays reconciled to the rupee against what Flipkart actually paid you.
Frequently asked questions
Can TallySutra connect directly to my Flipkart seller account?
No. TallySutra works in file-upload mode only: you download the official settlement and sales reports from Flipkart Seller Hub and upload them. There is no live API connection or background sync. This keeps you in control of exactly which periods enter your books, and every import can be reviewed and approved before vouchers are generated.
Which Tally versions does the import work with?
TallySutra generates standard Tally XML, which TallyPrime imports natively through its data import function. You can also use the TallySutra Gateway desktop app to push vouchers into a running TallyPrime instance on your machine. Note that the Gateway installers are currently unsigned beta builds, so Windows may show a publisher warning during installation.
Do I still need my CA if imports are automated?
Yes. Automation removes the typing, not the judgement. Ledger mapping, GST rate decisions and how you claim TCS and TDS credits still need professional confirmation. TallySutra actually builds this in: its CA review and approval step lets your accountant check each batch and resolve exceptions before anything is exported to TallyPrime.
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